Updated with steps to go to CM11-S update XNP44S
These days I was on 33R, rooted, with Xposed Framework installed, and lots of modules configured, including one that adds more col/lines to the Google Now launcher grid. Until now, each OTA was a pain, because although it flashed fine, I had to reinstall Xposed and I always had trouble with the launcher loosing its config (during the first boot, the grid was back to the default grid, and after reinstalling Xposed, I had to also restore a TiBu backup of Google Search to have my launcher setup again)... a pain.
This time, to go to 38R I took a different approach.
First, prepare in your /sdcard the following files:
cm-11.0-XNPH33R-bacon-signed.zip: Full XNPH33R factory image (flashable in recovery)
cm-bacon-3628510d76-to-ac1ccf7921-signed.zip: XNPH38R OTA zip. (link taken from here, thanks jaggyjags)
XNP44S update cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
SuperSU-v2.02.zip Flashable SuperSu zip (source, thanks Chainfire)
Xposed-Installer-Recovery.zip: zip that installs Xposed framework (you can generate it from Xposed Installer, or directly download this one)
With that, and assuming you already have a custom recovery installed (I used TWRP 2.7.1.1), this I what I did:
Reboot into Recovery (Vol-Down & Power)
Click Install
Select 1rst zip: cm-11.0-XNPH33R-bacon-signed.zip, but don't flash it yet
Add a zip: cm-bacon-3628510d76-to-ac1ccf7921-signed.zip (XPN38R)
Add a zip: cm-bacon-ac1ccf7921-to-5fa8c79c0b-XNPH44S-signed.zip
Add a zip: SuperSU-v2.02.zip
Add a zip: Xposed-Installer-Recovery.zip
(Optional) If you have a custom kernel zip that you know is compatible with XNP38R, you can also add it here
Swipe to confirm flash, this will actually flash all the previous zips, in order
Check to wipe Dalvik-cache/Cache
Reboot to system
Wait a couple of minute while your OPO boots to XNP38R: You've successfully flashed the OTA while preserving root, Xposed,...
Hope that helped
Enjoy XNP38R!
Edit: The method above should work if you are running CM11-S. The factory cm-11.0-XNPH33R-bacon-signed.zip does some verification on the already installed rom (for some reason, I really don't see the point).
If you have a different rom, or if it's a CM11-S rom but somehow resigned by different key, this above will fail. The update-script runs a script called otasigcheck.sh that looks into the installed rom files and checks the key that signed the /system/app/HTMLViewer.apk against the one in the OTA).
The error is: "Can't install this package on top of incompatible data. Please try another package or run a factory reset". (More details in comment #16)
In that case you should start doing the following:
Download and extract the XNP33R fastboot factory image
Boot into fastboot mode (Vol-Up & Power)
Connect your OPO to your computer (USB)
Run: fastboot flash boot boot.img
Then: fastboot flash system system.img
Then: fastboot reboot (will reboot the phone into Android)
Reboot into Recovery (Vol-Down & Power)
It should now be fine to continue from step 4 of the steps above.
If you need help with installing fastboot on your computer, please go here.
You don't need to do a wipe? I'm also struggling getting 38R
Hey if Im already on 33r do I have to flash it? Im currently on 33r rooted and when I try to flash 38r it gives me an error
Waynesta said:
Hey if Im already on 33r do I have to flash it? Im currently on 33r rooted and when I try to flash 38r it gives me an error
Click to expand...
Click to collapse
Yes you need to reflash it. It will put your phone in the state where you can then correctly flash 38R OTA.
Sent from my OnePlus One using Tapatalk Pro
rhaces said:
You don't need to do a wipe? I'm also struggling getting 38R
Click to expand...
Click to collapse
You don't need to do a wipe data, if you come from CM11-S. If you come from a different rom, you probably need to.
Sent from my OnePlus One using Tapatalk Pro
stupid question:
what is the framework xposed?
psxsnake said:
stupid question:
what is the framework xposed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Transmitted via Bacon
This is not working for me. I get Error executing updater binary in zip when flashing 33R zip
EDIT: I don't know why but I tried the option "Fix premissions" in the recovery and now it works and flashed without error.
don't wor for me or error flash or error mount ft why?
i had vanir rom
Great post. Thanks.
Can I wipe all data anyway so I can start with a fresh install of the update?
famonaco said:
don't wor for me or error flash or error mount ft why?
i had vanir rom
Click to expand...
Click to collapse
What recovery are you using? What is the error you get exactly? Can you maybe post a photo?
Sent from my OnePlus One using Tapatalk Pro
jairusz said:
Can I wipe all data anyway so I can start with a fresh install of the update?
Click to expand...
Click to collapse
Yes of course. It's not necessary though, I did so because I didn't want to wipe all data.
Sent from my OnePlus One using Tapatalk Pro
Same issue I get when trying to install the 38R by itself, described here http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311, "Can't install this package on top of incompatible data. Please try another package or run a factory reset"
CyberT3 said:
This is not working for me. I get Error executing updater binary in zip when flashing 33R zip
EDIT: I don't know why but I tried the option "Fix premissions" in the recovery and now it works and flashed without error.
Click to expand...
Click to collapse
update TWRP to 2.8.01
"Can't install this package on top of incompatible data"
rhaces said:
Same issue I get when trying to install the 38R by itself, described here http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311, "Can't install this package on top of incompatible data. Please try another package or run a factory reset"
Click to expand...
Click to collapse
TL;DR: I've updated the OP with an alternative method that should work for those getting this error .
Actually, for some obscure reason I don't know, the zip factory image for XNP33R does a verification on one file that is in /data (/data/system/packages.xml), looking for the certificate that signed a specific package from the installed rom (/system/app/HTMLViewer.apk). If the certificate isn't the same one that is bundled in the factory image, it won't flash and throw the error you got. If you scroll to the right you'll see the error is from the sha1_check on line 6:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh");
sha1_check(read_file("/tmp/releasekey"),"7241e92725436afc79389d4fc2333a2aa8c20230") && abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
Here we can see the content of otasigcheck.sh:
Code:
#!/sbin/sh
# Validate that the incoming OTA is compatible with an already-installed
# system
if [ -f /data/system/packages.xml -a -f /tmp/releasekey ]; then
relCert=$(grep -A3 'package name="com.android.htmlviewer"' /data/system/packages.xml | grep "cert index" | head -n 1 | sed -e 's|.*"\([[:digit:]][[:digit:]]*\)".*|\1|g')
grep "cert index=\"$relCert\"" /data/system/packages.xml | grep -q `cat /tmp/releasekey`
if [ $? -ne 0 ]; then
echo "You have an installed system that isn't signed with this build's key, aborting..."
# Edify doesn't abort on non-zero executions, so let's trash the key and use sha1sum instead
echo "INVALID" > /tmp/releasekey
exit 1
fi
fi
exit 0
I don't really see the whole point in doing that, as the next line will actually format system, so why care about what was there before anyway?
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
I've updated the OP with an alternative method that should work for those getting this error .
I really don't know what is going on with my phone but that didn't help anyways. I flashed boot and system from 33R in fastboot, went back into TWRP and installed the full 38R and still same issue. I tried every combination (including flash boot, syste, then in TWRP install 33R again) and nothing.
Finally what I did was fastboot flash boot system and recovery, boot into system, apply the OTA from the system and now that worked. Booted into 38R and everything worked ok, so went back to fastboot, flashed TWRP again, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
rhaces said:
I really don't know what is going on with my phone but that didn't help anyways. I flashed boot and system from 33R in fastboot, went back into TWRP and installed the full 38R and still same issue. I tried every combination (including flash boot, syste, then in TWRP install 33R again) and nothing.
Finally what I did was fastboot flash boot system and recovery, boot into system, apply the OTA from the system and now that worked. Booted into 38R and everything worked ok, so went back to fastboot, flashed TWRP again, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
Click to expand...
Click to collapse
I've modified my alternative instructions in OP, that should fix that (for others) : after fastboot system and boot it seems you need to reboot into Android (what you did). That makes sense actually as it will recompute the xml file that is also checked by the OTA. Then reboot back to TWRP.
I still wonder why it was falling though. You were on cm11-s right? What could have make the htmlviewer file have a different signature? Any idea? (did you apply any modification on top of CM11-S besides root, kernel, Xposed ?)
Sent from my OnePlus One using Tapatalk Pro
Option 1 worked fine on my rooted but otherwise unaltered OnePlus One. Thanks for the guide!
I get an error on the Xposed-installer but everything else goes well. If I remember it was a directory error message...
Envoyé de mon A0001 en utilisant Tapatalk
Related
im on stock 2.2, and when i chose vibrant galaxy s on accident, and it doesnt boot into clockworkmod, only regular recovery, i try choosing vibrant mtd, and it says no official clockworkmod out there yet so it wont lemme flash it.
Are you rooted? I accidentally forgot to do that after i odin last time and cw obviously didn't work.
The next step is to delete the zip that is already there and make rim manager put it there again. I've had to do that before for whatever reason.
Sent from my SGH-T959 using XDA App
haha i always forget to root after an odin flash
i didnt odin, this is a fresh, never before modified 2.2, except that i rooted it with superoneclick.
ok flash cwm galaxy s vibrant then reboot recovery with the file below in the root of the internal sd and when you get to stock recovery reinstall packages.that should make it popup
I address this in the noob guide. May help, signature.
Run an app that requires root to make sure you have su
Sent from my SGH-T959 using XDA App
How can I go back to the old CWR? I am currently on 4.0.1.5 (orange one) and want to flash a old Froyo ROM, Trigger 3.2
guys, is busybox absolutely neccessary?
installed it and it does not work at all
Wierd Installing Rom issue
Hello all, well to get straight to the point, i installed stock firmware, rooted and then installed Teamwhiskey "bionix-v-1.3.1". Later on i removed it by installing the stock firmware but forgot to uninstall/disable voodoo. This got me to dreaded yellow exclamation error. Some how i got that fixed and was able to install stock firmware all over gain.
Then i tried to install "Toxiccrazy8" and started getting this error.
E:Can't chown/mod /system/xbin/su
(No such file of directory)
E:Failure at line 99:
set_perm 0 0 04755 SYSTEM:xbin/su
Installation aborted
Steps i followed to install rom: [ Noob guide: How to root/odin/flash/recover ** 7-17-11 - redone completely!! ** ]
Try 1:
1) install stock firmware
2) used zip file to unroot
3) reboot, SuperOneClickv2.1.1-ShortFuse to unroot, install busybox
4) copy rom to sdcard
5) reboot in recovery mode
6) wipe/delvic cache etc
7) install from zip
Installation starts and after copying files, when its setting permissions it gives me this error.
Try 2:
1) install stock firmware
2) used zip file to root
3) reboot, SuperOneClickv2.1.1-ShortFuse to unroot, install busybox
4) deleted update.zip from sd card
5) install clockwork
6) copy rom to sdcard
7) reboot in recovery mode
8) wipe/delvic cache etc
9) install from zip
Again same error.
So i decided to try install Teamwhiskey "bionix-v-1.3.1".
Followed same format and it worked was able to install it again. Working nicely.
So this time i used their "disable_voodoo.zip" to flash and disable voodoo. Also used
Create a folder voodoo/disable-lagfix on internal sd. to disable/uninstall voodoo. All worked fine and let it rest for 15 minutes as asked. So thinking that i might be able to install other rom, i went back to my original steps and installed stock rom and followed all the steps but still getting same error:
E:Can't chown/mod /system/xbin/su
(No such file of directory)
E:Failure at line 99:
set_perm 0 0 04755 SYSTEM:xbin/su
Installation aborted
Any one can help me figuring what could be the problem. Thanks in advance
sukhbirgs, I highly suggest you just flash back to stock using ODIN. Make sure you select the re-partition box, that's what will fix your issues.
I am running the Revolution HD rom, this is how I purchased my TF101 from a friend, and I want to restore the factory rom so I can get ICS and the update for the battery issue until mike gets it implemented into Revolution.
How can I do this?
Thanks!
-edit- nevermind, I didn't notice you were running revolution.
If you want to flash back to stock, go to the ASUS Support site and download the 9.2.1.11 firmware for your device.
Unzip it 1 time (there is a zip file within the zip) so it will still have a zip.
Put the file on a microSD or the internal /sdcard/ directory depending on your version of CWM and where it can read.
Boot to CWM.
Install zip.
Choose the zip you downloaded.
Now you will be back to stock unrooted with stock recovery.
Then you will need to check for updates and grab the latest update from ASUS OTA.
If you want to root again you will need to vipermod option 1 to get root access.
Ah, thank you Fred! I did exactly that and it failed but it was the zip within a zip that killed me!
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Here's exactly what I did to go from Revolution HD 3.0.1 back to stock Asus ICS 9.2.1.11
1. Download the firmware from Asus website. The file name was US_epaduser9_2_1_11UpdateLauncher.zip. You unzip this. You get US_epad-user-9.2.1.11.zip. You put US_epad-user-9.2.1.11.zip on your microSD card.
2. Boot into CWM
3. Factory reset
4. Clear Cache
5. Clear dalvik cache
6. Mount & Storage - format /system
7. Mount & Storage - format /cache
8. Power off(from CWM menu, might be under advanced, I forgot)
9. Boot into CWM.
10. Install zip from sdcard. Choose US_epad-user-9.2.1.11.zip on your microSD.
11. Reboot after flashing is complete.
12. You should now be on Asus stock ICS with stock recovery.
13. I didn't add any of my google accounts during the initial setup because I wanted to do it after I do the 9.2.1.17 update.
14. Shut off and do a cold boot.
Worked perfectly fine for me.
What didn't work was, I was not getting the 9.2.1.17 update afterwards.
So I rooted using Vipermod, installed CWM, and manually flashed the update through CWM. I had to re-root after the update. Simply ran Vipermod again.
Been 2+ days, and it's super stable with great battery life. Not a single random reboot or crash.
gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
gee one said:
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
gbatt said:
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
Click to expand...
Click to collapse
I am pretty sure my CWM Recovery was 3.1.0.1 too.
Try replacing your CWM with Rogue XM Recovery http://forum.xda-developers.com/showthread.php?t=1446019
Awesome! That worked great. Thanks Horndroid!
I did with the help of this theard:
http://forum.xda-developers.com/showthread.php?t=2145848
Code:
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Then I flash it with TWRP 2.6.3.0
After flashing I got this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "filename"
E: Error installing zip file 'filename'
I tried Dalvik/Cache wipe but it didn't help.
Now I can't boot into Android, it show GOOGLE and then blank screen
I can go to TWRP but when I try to use ADB sideload to connect with my computer, I get this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "inner.zip"
E: Error installing zip file 'inner.zip'
I don't have any rom in SDcard but the file "signed-occam-KRT16S-from-JWR66Y"
May anybody help me with this problem, please
In the worst case, where can I fix my phone with fee
Any changes to the /system partition or by rooting can cause OTA to fail. Flashing OTA is only recommended to a pure untouched stock rom.
Follow the guides in my signature to flash 4.4 without wiping your data.
mecatro said:
I did with the help of this theard:
http://forum.xda-developers.com/showthread.php?t=2145848
Code:
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Then I flash it with TWRP 2.6.3.0
After flashing I got this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "filename"
E: Error installing zip file 'filename'
I tried Dalvik/Cache wipe but it didn't help.
Now I can't boot into Android, it show GOOGLE and then blank screen
I can go to TWRP but when I try to use ADB sideload to connect with my computer, I get this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "inner.zip"
E: Error installing zip file 'inner.zip'
I don't have any rom in SDcard but the file "signed-occam-KRT16S-from-JWR66Y"
May anybody help me with this problem, please
In the worst case, where can I fix my phone with fee
Click to expand...
Click to collapse
why dont you just search your issue and for fixes... Put your phone in recovery and use adb to push over a rom. I dont want to be the bad guy here but why flash an OTA zip if you are already rooted just flash a stock rom. So many of you make things so much harder for yourself than it has to be.
Sorry for bashing you but you also should always keep a nandroid on your phone. Do some research or try what I suggested and good luck but for future reference be mindful of what may happen if things go wrong
playya said:
why dont you just search your issue and for fixes... Put your phone in recovery and use adb to push over a rom. I dont want to be the bad guy here but why flash an OTA zip if you are already rooted just flash a stock rom. So many of you make things so much harder for yourself than it has to be.
Sorry for bashing you but you also should always keep a nandroid on your phone. Do some research or try what I suggested and good luck but for future reference be mindful of what may happen if things go wrong
Click to expand...
Click to collapse
I used OTA because I didn't want to reset my phone. I know it was stupid
I read some topic and they said my problem is TWRP 2.3.6 isn't compatible with android 4.4
(I should use CWM is).
I think now I have some think like android 4.4 in my phone but it can't boot
The problem now is I can go to recovery but can't usse adb to push a rom.
I tried some search but there was no help
eksasol said:
Any changes to the /system partition or by rooting can cause OTA to fail. Flashing OTA is only recommended to a pure untouched stock rom.
Follow the guides in my signature to flash 4.4 without wiping your data.
Click to expand...
Click to collapse
Thank you. I flash Google's ROM with fastboot and it's working now.
Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?
digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!
error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?
baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?
baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).
digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?
baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
baytee said:
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app
Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Rawrden said:
Hi,
I'm currently using the Skipsoft Android Toolkit to unlock flash TWRP onto my device. I've followed to first steps (install drivers, backup device and unlock bootloader) to the letter and everything went smooth.
Now the final part of installing TWRP is not going so well. Flashing the custom recovery works as expected and I end up in the TWRP menu. However, as soon as I reboot my phone and try to go back to the recovery via Advanced Reboot --> recovery, I end up in the default One Plus Recovery Menu. Now the tool mentioneds when this process fails, renaming the Recovery Restore Files is recommend to prevent the system from flashing the stock recovery on boot (what happens to my device). I follow this option in which I end up back in TWRP, flash a zip named 'permanent-recovery.zip' (while read only mode is turned off in TWRP) and reboot my device. Still when I use Advanced Reboot to open recovery, I end up once again in the Stock Recovery.
Is there anyone who could tell me where I am going wrong and how to solve this issue?
Thanks in advance
Click to expand...
Click to collapse
The basic "mechanics" of what happens seems to still be as follows:
As your phone is delivered with Stock OS, it has these two files installed:
Code:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I know from looking at mine when I got it that it had /system/recovery-from-boot.p installed. If it's there, it is run when it runs at boot.
To stop that behavior you have to get rid of those files before you reboot the first time from recovery or else recovery will be replaced with the stock image. I'm aware that supposedly the custom recovery supposedly renames either one or the other or both of these but am not convinced it does this or whether installing root (either Magisk or SuperSU) does it. Either way, since you're stuck with the problem, either from file-manager in TWRP if that's all you can boot to, you need to rename /system/recovery-from-boot.p to something like /system/recovery-from-boot.p.orig and maybe the other one /system/etc/install-recovery.sh to /system/etc/install-recovery.sh.orig as well.
Once even the .p file is gone, it's not going to rewrite recovery. You must, of course, be rooted before you can touch those files although if you can sideboot TWRP, it seems like you are rooted while it is booted and "should" have access to system files if you can mount system rw.
I've fixed it this way on other phones. On this one, installing the "official" TWRP and Magisk did it. When I booted into /system after installing Magisk, I looked for the .p file and found it renamed to /system/recovery-from-boot.bak.
I found a link for a Samsung s8 for the same purpose. It's probably identical. http://www.teamandroid.com/2017/04/25/install-galaxy-s8-twrp-310-recovery/3/
Click to expand...
Click to collapse
I looked into those two files while in TWRP and noticed I only had the recovery-from-boot.p file. This was already in fact renamed to recovery-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Rawrden said:
I looked into those two files while in TWRP and noticed and only had the recovery-from-boot.p file. This was already in fact renamed to record-from-boot.p.bak. I renamed it once again (just to be sure) and after flashing the .zip I mentioned earlier, the TWRP did not last another reboot...
Can I after flashing TWRP again, immediately flash Magsik? I intended to hold off rooting because the rom I was going to install has Magisk build into it. I don't want to create a conflict when flashing later on. Is this going to be an issue?
Click to expand...
Click to collapse
To me, it doesn't sound like a conflict to re-install Magisk over itself in FOS and see if that helps. The real "action" that counts is all about whether you've already booted into the OS after installing TWRP and then how you go about getting rid of the .p file without doing a regular reboot via the OS. Even installing the FOS ROM should get rid of the .p file (rename it), so something else is going on. I'll look around some more and update this if I can.
By the way: Depending upon how exactly you got from TWRP to the OS the first time, it could already have rewritten the stock recovery by the time you noticed *.p file renamed to *.bak.
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
---------- Post added at 09:26 AM ---------- Previous post was at 08:59 AM ----------
Rawrden said:
@hachamacha I've reread your post and wondering if rooting my device is even going to make a difference right now? Since I'm already able to rename files in the system directory, would it even make a difference?
Click to expand...
Click to collapse
Just saw this note:
Anytime you're in TWRP, you're automatically "rooted" for the time you're there. It's integral to TWRP having permissions to do anything like install etc. If you just "loaded" TWRP (as in fastboot boot twrprecovery.img) then you'd be rooted, but when you rebooted to the system, you'd be unrooted. While you were in TWRP, in theory you could make file system changes to the /system partition (a) if TWRP lets you mount it rw which I think that first swipe does and b) if you can see the correct files in it's file manager.
So it "seems" like those file changes should be actual file changes to the correct place. Keep in mind that while booted in TWRP, TWRP may have it's own ./system/ that has nothing to do with the OS's ./system folder, so you've got to be able to mount the OS's ./system. TWRP's ./system is already fine and of no importance for this. I can boot mine into TWRP and look around to try to clear this up, but it might not be crystal clear to me either.
The output of a TWRP terminal emulator "mount" command might be of use but it will be messy. Maybe if you can do this in emulator from TWRP:
# mount | grep system, and look at that output, perhaps put it in this post, it'd be of help. The mounted rw ./system we need is going to be the same one you'd see from adb shell or terminal emulator while booted from the OS. My guess is that the one we don't want from TWRP's perspective will be mounted as /system (params...) and that the the OS's system either will not yet be mounted and you'll have to go to mounts and mount it and then look at the output of the mount cmd again to figure out what it was mounted as. Sorry about how complicated this explanation has become. Anyway: The ./system that corresponds to the OS is the only one we care about.
There's no easy way to explain it so I'll leave it hidden to spare anyone having to look at it:
I just booted into TWRP and used terminal emulator and file manager to explore:
findings: While in TWRP, using terminal emulator to do a
$ df and then a $ mount command shows no ./system mounted specifically. // maybe not a surprise.
// TWRP just mounts it's root / file system and there is a /system folder, just not a specific mount point for it.
// TWRP does not auto mount the OS's ./system partition by default. It depends what you're going to do there.
Without going into "mounts" and clicking on /system, it won't even try to mount /system for the OS.
If you can get that mount to work in read/write mode, then you should be able to see the ./system mount using terminal emulator as such.
$ mount | grep -i system (and look specifically for ./system on the right side of whatever appears).
In theory you should be able to make changes to the OS's /system partition now. When you're done, unmount it. (I'm assuming all this works from TWRP, a dodgy assumption)
At this point: I'm just trying to figure out how TWRP does things like installs OS zips to the /system & /data partitions which it is clearly successfully able to do. It could do it without mounting anything because it could use the linux dd command, which just writes to the /dev name. OR: It could mount /system and use it. I'm not sure which.
hachamacha said:
OK: I recalled how I did this without a problem: I wrote instructions somewhere but have no idea where. This is what I think I did:
Quote:
Code:
1) fastboot flash recovery recovery.img (custom/TWRP)
2) fastboot boot recovery.img (so force it to load recovery without a traditional reboot).
3) install ROM from that point and after done just hit the reboot button (or install Magisk from that point and hit reboot).
Click to expand...
Click to collapse
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Rawrden said:
I followed these steps and I managed to install FreedomOS without any issues. My phone booted normally and after a few complimentary steps I booted back into recovery and... TWRP! No more stock recovery. Thanks a lot!
Just one more question: TWRP currently asks whether it is allowed to install itself as a system app. Now I assume it is already a system app, but I'm not expert at this so I can't say for sure. Would you recommend me to install TWRP as a system app?
Click to expand...
Click to collapse
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
hachamacha said:
Great! Glad that worked. I guess it's all about how that first boot to the OS occurs.
Anyway: Your question, I'm assuming is about TWRP "Manager" the app? If so, yes, it should be a system app. The thing is that "Official TWRP Manager" doesn't really do much of use that you wouldn't just as soon do from fastboot, so it's not critical and nothing other than TWRP manager will "not work" regardless of what you designate it. All saying it's a system app does is puts a slot for it in Magisks "root table".
Cheers.
Click to expand...
Click to collapse
Done! Can I just say how grateful I am to you for helping me out with this? Your answers have been extremely detailed and I've learned quite a few things. Unfortunately I can only thank your posts once, because you've earned more than that. Thanks again and keep being awesome!