[RECOVERY] TWRP Recovery [v2.8.6.0] - Huawei Ideos X5 U8800

CM dropped CWM support in CM-12.0 in favor of CM's own recovery, which has different bugs and is generally very simplified recovery (does only wiping/flashing images). So I decided to go on with a different recovery from now on.
This recovery is LVM compatible.
Requirements
U8800 with 404020 baseband (If you ever installed 2.3 stock firmware, you're ok!)
Strongly recommended: Unlocked pink screen
How to install
Method 1 (by recovery)
Download the zip from downloads below
Save it to your phone (internal or external SD)
Reboot to your current recovery
Install the zip
Reboot recovery
Method 2 (by pink screen)
Download the zip from downloads below
Save it to your PC
Reboot your phone in pink screen mode
Extract recovery.img from the zip
Save the zip on your phone's image/ directory (where boot.img and other files are located)
Reboot to recovery
Downloads
LegacyHuawei
twrp-recovery-v2840.zip
twrp-recovery-lvm-v2830.zip
Things to know
When backupping, tick "cust". This holds boot.img and other files which are grucial for restoring a full backup.

Thanks for the great job Blefish. It works flawlessly

Uploaded TWRP recovery v2.8.4.0.
Changes:
* Support for offmode charging
* LVM/NON-LVM compatible. You can use this recovery for NON-LVM ROMs.

Hi Blefish
Thanks for the updated recovery.
I had a question, if we were to flash say your CM11 rom, I guess we need to uninstall LVM as you had mentioned before or just flash directly using this recovery
Great job again

mohammad.nomaan said:
Hi Blefish
Thanks for the updated recovery.
I had a question, if we were to flash say your CM11 rom, do we need to uninstall LVM or just flash directly using this recovery
Great job again
Click to expand...
Click to collapse
You can use this recovery, however LVM needs to be uninstalled. The new BlePart-LVM-11 script makes it easier for you . However, I still want to do one mor CM11 release, with LVM support. Theoretically the new CM12 release is LVM/NON-LVM compatible too but it has problems on installing the ROM (the space on /system is not enough).

Blefish said:
You can use this recovery, however LVM needs to be uninstalled. The new BlePart-LVM-11 script makes it easier for you . However, I still want to do one mor CM11 release, with LVM support. Theoretically the new CM12 release is LVM/NON-LVM compatible too but it has problems on installing the ROM (the space on /system is not enough).
Click to expand...
Click to collapse
Thanks Blefish for the update.
Just installed the new recovery, Off-Mode charging is working fine.
I like the new white charging animation

Blefish, thanks a lot!!
Perhaps, in the next update, you could enable the LED to show the charging progress , if possible..

tsioy said:
Blefish, thanks a lot!!
Perhaps, in the next update, you could enable the LED to show the charging progress , if possible..
Click to expand...
Click to collapse
Yes, I am planning that. The thing was that in CM's healthd (charger is using that) it is supported, but in Omni's healthd it's not supported. I will probably implement it myself if someone has not done it yet.

VERY NICE, thanks!

New version uploaded, enjoy!
Next releases will be uploaded at LegacyHuawei
This version adds the RPC side charging (more stable) and it also enables charging led indicators.

I installed 2850 and now I can't access the sdcard (in TWRP). It works fine if I boot it normally, so I'm guessing it's not a problem with the sd card?
I tried the option to mount the sdcard, but when I try it, TWRP doesn't tick that option. All the others work, though (cust, system, data, ...)
Any suggestions?

phone wont boot into twrp now, it just shows the twrp splash screen then restarts

New version uploaded!
No changes have been done on my side, other than updating to android-5.1 codebase where this recovery is compiled from.

@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0

Webtag said:
@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0
Click to expand...
Click to collapse
Try replugging the SD card while in recovery. Sideload was working well for me, but it does require updated ADB. Does it tell you an error message on the screen?

Blefish said:
Try replugging the SD card while in recovery. Sideload was working well for me, but it does require updated ADB. Does it tell you an error message on the screen?
Click to expand...
Click to collapse
Replugging the SD does nothing, and I only get error message in Adb sideload mode after about 5-10 min. This is the same problem that @rexnanet had with version 2.8.4.0, but my sd doesn't mount after inserting it when in TWRP

Webtag said:
@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0
Click to expand...
Click to collapse
I've did some dirty edits in the recovery ramdisk and the SD Card can now be read and cm12.1 can be installed: http://www.mediafire.com/download/vzzc64h9zoh60h4/image-new.img
Hopefully Blefish will do a proper fix soon, though

CrysisLTU said:
I've did some dirty edits in the recovery ramdisk and the SD Card can now be read and cm12.1 can be installed: http://www.mediafire.com/download/vzzc64h9zoh60h4/image-new.img
Hopefully Blefish will do a proper fix soon, though
Click to expand...
Click to collapse
Hello CrysisLTU this imagen-new and Blepart-LVM, can used in U8800pro o U8800-51?

Links are gone. Pls someone upload the latest file to somewhere.

Related

[Recovery] Unofficial CWM Recovery 5.0.2.7[u8800pro&u8800]

I take no responsibility for any harm that comes to your phone as a result of applying this mod.
unofficial Clockwork Mod Recovery 5.0.2.7 for u8800pro and u8800 [upgrade to offical 2.3 GB]
Installation Instructions (upgrading - root explorer method):
Using any file explorer which is able to remount as writeable (such as root explorer), browse to the /cust_backup directory and remount it as writeable
Navigate to the image directory and backup up the current recovery by renaming it to something like recovery.bak, or _recovery.img
Rename the downloaded recovery to recovery.img and copy to the image directory.
Installation Instructions (new install):
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see recovery.img etc.
(optional) Rename recovery.img to recovery_backup.img
copy the new recovery.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Hold volume + and power to boot to recovery.
Install any custom rom
change:
mod the kernel,Ums is worked now
use zte u880‘s charge png
can install zip from emmc and use emmc backup&restore
add ext4 fs support
about SDcard
if you can't mount SDcard in recovery,do this:
enter "advanced"--"Reboot Recovery"
then you could use the SDcard
ps:this is issue of offical GB,not recovery!
Download
http://sourceforge.net/projects/genoandroid/files/
mount sd_external error!
akalos said:
mount sd_external error!
Click to expand...
Click to collapse
have detailed info?
my worked fine
genokolar said:
have detailed info?
Click to expand...
Click to collapse
I tried to backup my rom to the external storage card,but was not possible
internal is ok
akalos said:
I tried to backup my rom to the external storage card,but was not possible
internal is ok
Click to expand...
Click to collapse
test it ,work fine for me
akalos said:
I tried to backup my rom to the external storage card,but was not possible
internal is ok
Click to expand...
Click to collapse
I have same problem!
please upload the recovery.log
Did you finally find out if there is a bug in the recovery?
Once you put the recovery, would Rom Manager detect it?
Copix said:
Once you put the recovery, would Rom Manager detect it?
Click to expand...
Click to collapse
no
10 digits
Got it. Unofficial...
Tested on u8800 and works very good. SD card sometimes can't mout properly, but i guess it's not an issue from CMW.
I've done a official GB backup, restored without a glitch, installed ICS demo without any problem too.
Can I upgrade my u8800 to official beta 2.3.5 and use this CWM to upgrade to cm7 or miui if I won't be able to use ics demo?
Sent from my u8800 using XDA App
Yes.
Sent from my ragelis
for me does not work. after several times trying to restore my miui backup (the onlyy one) it gave random errors some times, but after I was able to restore 2 times, I cant pass the miui boot.
MaRcIuPT said:
for me does not work. after several times trying to restore my miui backup (the onlyy one) it gave random errors some times, but after I was able to restore 2 times, I cant pass the miui boot.
Click to expand...
Click to collapse
Was it a backup you did with this CWM version? Or with the stockwell's CWM? The old backups don't work with this one I believe.
the backup its before this version of course. but even with this new CWM I cant flash new rom. I says error blablabla id u8800pro. I installed this because I wanted to try new ICSrom but now Im stuck to it lol
MaRcIuPT said:
the backup its before this version 4 of course. but even with this new CWM I cant flash new rom. I says error blablabla id u8800pro. I installed this because I wanted to try new ICSrom but now Im stuck to it lol
Click to expand...
Click to collapse
Have you flashed official GB before installing this recovery? I think you need to do that before this works in the original U8800.
yes I did ! the ICS works but not others.
Hmm, I tried to restore my backup from yesterday done with stockwells 5.0.2.6 recovery and my phone got ****ed up. I know I shouldn't have done this but I just had to try. xD Now I can't get past the Huawei logo, when I push the power the phone starts but just turns off after couple of seconds. I can get to bootloader (pink screen) but not to recovery. I hope no one else has tried this and I hope I get my phone working again.
Would anyone have any advice how to get my phone back up and running? Or should I just go bring it to warranty support?
have you tried to replace the recovery.img from this topic again? that happened to me too when I tried to go back with CWM v4 but then I replaced with this

[RECOVERY] ClockworkMod Recovery [v6.0.4.6]

Version 6.0.4.6 - Stable
Bugs (Report):
No offmode charging.
Sideloading does not work with large files.
CMD side (adb) reboot is not working.
Installation:
Reboot to recovery.
Download the flashable zip below & flash it on top of your current recovery.
If you don't have custom recovery installed before, refer to 5.5.0.4 instructions before updating to 6.0.4.6.
Downloads:
Sourceforge
Version 5.5.0.4 - Stable
Bugs (Report):
No capacitive key support on Synaptics, due to v5.5.0.4 not having virtual keys implemented.
Installation:
Root your phone.
Download the recovery.img down below.
Save it to wherever you want.
Make sure the image name is recovery.img, rename if needed.
Download any root file manager, which can mount and show hidden folders.
Mount /.cust_backup as rw.
Copy and replace recovery.img from SD card to /.cust_backup/image/recovery.img
Usage:
Make sure you have disabled fast boot (on official Gingerbread). Go to Settings->Applications->Fastboot and disable it.
Start the phone in recovery mode [Volume Up] + [Power]. Hold the keys down until you can see boot logo.
To move up, press [Volume Up].
To move down, press [Volume Down].
To select, press [Power].
Downloads:
MediaFire
Credits:
TomGiordano at GitHub. Thanks for helping me fix rmt_storage.
dzo at XDA. Thanks for giving instructions.
Cyanogenmod. Thanks for the original ClockworkMod Recovery.
Nice going there! You used 2.35 kernel for this?
Also touchscreen not working anyway in recovery so that's not really a problem.
You are able to create/restore backups? Tried flashing any custom rom?
Also have a look at /tmp/recovery.log
ret4rt said:
Nice going there! You used 2.35 kernel for this?
Also touchscreen not working anyway in recovery so that's not really a problem.
You are able to create/restore backups? Tried flashing any custom rom?
Also have a look at /tmp/recovery.log
Click to expand...
Click to collapse
Yeah, I extracted it from boot.img. I saw stockwell had this working, maybe he had a custom recovery kernel for that. The rebooting issue is making thing hard, I almost backed it up, but it rebooted, so that's the main problem. If I get that fixed, I'll try flashing/backup.
Also, in 2.2, I was able to just start the phone with volume down + power, to get to recovery, but in 2.3, this doesn't work for me. I can only get there when I use "adb reboot recovery".
-EDIT-
Got it working, thanks genti7. It starts with vol up + power.
Before my phone bricked i got that problem too with 2.3 stock i cant enter on recovery with key combo
Blefish said:
Yeah, I extracted it from boot.img. I saw stockwell had this working, maybe he had a custom recovery kernel for that. The rebooting issue is making thing hard, I almost backed it up, but it rebooted, so that's the main problem. If I get that fixed, I'll try flashing/backup.
Also, in 2.2, I was able to just start the phone with volume down + power, to get to recovery, but in 2.3, this doesn't work for me. I can only get there when I use "adb reboot recovery".
Click to expand...
Click to collapse
its volume up + power not volume down + power. Try again.
Done any progress?
I don't have time today, will continue tomorrow. I realized that the /boot partition is wrong, can someone help me with this? Maybe the data one is wrong too, the logs say something about that. I'll post correct details tomorrow.
Sent from my U8800
The reboot is probably because you aren't running the rmt_storage server. The modem needs this to run and so reboots the phone without it. The HW recovery mounts /system to run it which is a stupid idea because /system may not always be there. rmt_server needs some shared libs so you will have to copy them to the recovery image too.
Attached is a recovery that I made, it's v4 but should work. I just modified the hw recovery so it needs a working /system. Obviously there's nothing to flash yet (and you won't be able to flash the old ROMs because amss has changed). I don't intend to support this but feel free to try it out.
dzo said:
The reboot is probably because you aren't running the rmt_storage server. The modem needs this to run and so reboots the phone without it. The HW recovery mounts /system to run it which is a stupid idea because /system may not always be there. rmt_server needs some shared libs so you will have to copy them to the recovery image too.
Click to expand...
Click to collapse
Thanks. Will do today.
Sent from my U8800
dzo said:
Attached is a recovery that I made, it's v4 but should work. I just modified the hw recovery so it needs a working /system. Obviously there's nothing to flash yet (and you won't be able to flash the old ROMs because amss has changed). I don't intend to support this but feel free to try it out.
Click to expand...
Click to collapse
Dzo did you upgrade AMSS to 2.3.5 beta or did you stay on B138SP04?
boss_y said:
Dzo did you upgrade AMSS to 2.3.5 beta or did you stay on B138SP04?
Click to expand...
Click to collapse
You must upgrade amss for the new kernel to work, it also has a new bootloader. Attached is a boot.img that will give you root access with adb in the gb beta rom.
Hold on... maybe we have clockwork
QT @tomgiordano: Sorry, I didn't get notifications for either of your tweets. http://205.185.123.36/u8800-35-recovery.img
Credits to tomgiordano
I'm not home for testing..
Sent from my IDEOS X5
well, about the CWM recovery,you can try the recovery Genokolar has released for the u8800+(or pro), it can work fine. I have tried it, and i have flashed a zip successfully!
PS: i am using u8800 (not u8800+), the official 2.3.5(u8800) has the same partition as u8800+.
dzo said:
You must upgrade amss for the new kernel to work, it also has a new bootloader. Attached is a boot.img that will give you root access with adb in the gb beta rom.
Click to expand...
Click to collapse
did not root mine
demolition23 said:
Hold on... maybe we have clockwork
QT @tomgiordano: Sorry, I didn't get notifications for either of your tweets. http://205.185.123.36/u8800-35-recovery.img
Credits to tomgiordano
I'm not home for testing..
Sent from my IDEOS X5
Click to expand...
Click to collapse
This is working good...just tried flashing tweak zip installed with out problems.....
krish_nank said:
This is working good...just tried flashing tweak zip installed with out problems.....
Click to expand...
Click to collapse
Good news!
Sent from my IDEOS X5
krish_nank said:
This is working good...just tried flashing tweak zip installed with out problems.....
Click to expand...
Click to collapse
can you try flash a rom ?
Darksage07 said:
can you try flash a rom ?
Click to expand...
Click to collapse
In theory,yes but current ROMs must be modified to support this recovery.so no flashing ROM for now...
This maybe work is an backup ROM..I think... :-\
Sent from my IDEOS X5
demolition23 said:
In theory,yes but current ROMs must be modified to support this recovery.so no flashing ROM for now...
This maybe work is an backup ROM..I think... :-\
Sent from my IDEOS X5
Click to expand...
Click to collapse
hmm maybe not .krish_nank can you send me the zip that you flashed ? so i can check one thing

Help a n00b there please :o3

Hey, look what i've done while desperately trying to install GearCM or CM12 ROM. First, i installed TWRP on my i9500 device. After that, i put the GearCM 5.1 and Gapps for 5.1 on sdcard, but i got mad really fast when i saw i can't install ANY ZIP from sdcard, then tried another CUSTOM ROMS, same problem, i wiped cache and system ( ye, system ) ) - dont ask why i did that - Anyway, now i have no system files on phone, and on my sdcard i only got that useless ZIPs.
Ah, forgot to mention, the error showing up everytime i tried to install a zip was : "Zip corrupted, Operation aborted" (something like that ).
NOTE : I can't boot normally, but i can boot in recovery (TWRP) . I can't flash another rom using odin as i can't switch usb debugging ON.
Ah, please, don't laugh too much, im pretty serious
Oh, some1 explain this to me -> I tried to install zip @ adb as i saw explained on a blog -> got stuck at recognizing phone-pc due to driver error, so i decided to try last time installing the custom ROMs( THE SAME ZIPs i got error before) from recovery -> install zips. AND GUESS WHAT, less than 20s rom is installed without any errors, i dont know if to be mad or happy. Atleast explain me what happened there.
wowempire said:
Hey, look what i've done while desperately trying to install GearCM or CM12 ROM. First, i installed TWRP on my i9500 device. After that, i put the GearCM 5.1 and Gapps for 5.1 on sdcard, but i got mad really fast when i saw i can't install ANY ZIP from sdcard, then tried another CUSTOM ROMS, same problem, i wiped cache and system ( ye, system ) ) - dont ask why i did that - Anyway, now i have no system files on phone, and on my sdcard i only got that useless ZIPs.
Ah, forgot to mention, the error showing up everytime i tried to install a zip was : "Zip corrupted, Operation aborted" (something like that ).
NOTE : I can't boot normally, but i can boot in recovery (TWRP) . I can't flash another rom using odin as i can't switch usb debugging ON.
Ah, please, don't laugh too much, im pretty serious
Click to expand...
Click to collapse
*stare and laughing a lot*
*Just kidding, okay? :silly: *
And then;
You have corrupted zips. You need to redownload the package completely (ROM+GApps) and transfer it to your external SD card and flash. You can transfer the downloaded zips by using adb push command or remove your external SD card and plug it to anything else (read: SD card reader; of course ).
Sent from my ASUS_Z00AD
krasCGQ said:
*stare and laughing a lot*
*Just kidding, okay? :silly: *
And then;
You have corrupted zips. You need to redownload the package completely (ROM+GApps) and transfer it to your external SD card and flash. You can transfer the downloaded zips by using adb push command or remove your external SD card and plug it to anything else (read: SD card reader; of course ).
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yeah, maybe im not exactly as n00b as you think. I used exactly the same zips after(same procedure tho), and it worked smooth(i didn'teven touch them).
NOTE : I think i said i tried using adb to install zips but i got a driver error which i couldn't solve.
I've had that issue for some time especially with CM, have you tried verifying the sh1 checksum once you've loaded it onto your sd card?
Thanks.

[Recovery] Twrp 2.8.7.0 Kipper

I have build a twrp recovery for Wileyfox storm (kipper)
Enjoy it.
All credits go to TeamWin developpers.
flash with fastboot
fastboot flash recovery TWRP-2.8.7.0-kipper-recovery.img
TWRP-2.8.7.0-Kipper-brown-recovery
Edit:
TWRP-2.8.7.0-Kipper-blue-recovery
Nice job ;D
Awesome. It works flawlessly Is there any chance of any custom rom? maybe pure AOSP marshmallow with layers support? is the kipper source released?
I saw twrp 3.0.0.0 can you please compile it?
This works very well, backup, restore. Just one thing i just hope would be great to be there is the OTG drive support.
aciupapa said:
I saw twrp 3.0.0.0 can you please compile it?
Click to expand...
Click to collapse
What extra features does twrp3.0.0.0 have please? The current cm13 marshmallow nightly for wileyfox storm require the cm recovery to install the update zip.
You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.
backfire_12 said:
You can able to update to every nightly even you're on TWRP 2.8.7.0 ( I've been using it since and been able to do nandroid backup for that matter, which you can't using CM recovery).
BTW TWRP main highlight is "•Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow"
If your using adopted storage on Android M, using TWRP 2.8.7.0 will not show the adopted SD card.
You can further check the released note from TWRP website for more info.
Click to expand...
Click to collapse
https://s.basketbuild.com/devs/beroid/Wileyfox%20Storm%20-%20Kipper/TWRP
Anyone tried TWRP_3.0.0-0_kipper recovery at all yet? I have the TWRP_3.0.1-0_crackling_20160402 recovery working fine on my Swift, however since my backups are from the TWRP 2.8.7.0 kipper recovery i have not tested the TWRP_3.0.0-0 version on my Storm!
On the 3.0.0 v2 touchscreen doesnt work for me
aciupapa said:
On the 3.0.0 v2 touchscreen doesnt work for me
Click to expand...
Click to collapse
I had a try at installing both test version 1 and 2 however the recovery loads yet none of the tile's responded after installation/ loading up completed.
hi i need video how do this recovery plz
Ok so I tried to install the given 2.8.7 version and it worked, but it always said 'wrong password' when trying to decrypt my phone. The same password worked when regularly booting the system. So I thought I might try a newer version and downloaded the _test.zip from the link provided in the thread. Unfortunately, now my phone seems to be bricked! It always boots into Recovery, which asks for my password but does not react to any input on the touchscreen. I can not boot the system or the bootloader, adb and fastboot do not find the device and if I hold the power button (or volume-down + power button) for several seconds it just again reboots into the broken recovery. Does anyone have an idea how to get out of this? Any help is greatly appreciated.
Edit: OK, now I feel dumb. The key combination to get into the bootloader is volume-up+power, not volume-down+power. Now I can continue to try different recoveries in the hope that one of them can decrypt the phone correctly and reacts to the touchscreen.
saikoa7a8a said:
hi i need video how do this recovery plz
Click to expand...
Click to collapse
If that's how you write, good luck breaking your phone... This thread has good instructions if you want to risk it, just replace the recovery image it has you download and use with this one.
http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992

[HOW-TO] Updating Nook HD+ Internal EMMC from CM11 to LN14.1

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).

Categories

Resources