Related
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
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
taodan said:
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
Click to expand...
Click to collapse
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
And yes to answer your question it is a multiROM patch for TWRP
sropedia said:
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
Click to expand...
Click to collapse
Do you have "USB debugging" checkbox, in Developer Options, checked? Also, try reboot your PC and reconect your phone to see whether it shows up as a storage device.
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
playya said:
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
Click to expand...
Click to collapse
I did a full wipe like I usually do. I would use a different version of TWRP if I knew how to change it from within TWRP. I have a follder titled ROOT that I keep all my ROMs and whatnot in, but the problem is that literally none of the folders in my internal storage are showing up from within TWRP. I can't check to see if USB debugging is enabled because theres no operating system on my phone; like I said, I did a full wipe. The fact that no folders show up also means that it doesnt recognize the backup I had. My computer still won't recognize my phone as a storage device after mounting in TWRP. Maybe I'm doing something in the wrong order? Restarting my computer didn't help.I really need to get my phone working on ANY ROM, and I appreciate all the help so far
Hi,
I'm at my wits end. I had SlimRom installed for a week and all was fine, but I was curious about what new ROMs were out there so I backed up my phone using ROM Manager and did all the usual stuff to get a new ROM. I installed Gummy, but didn't like it; I installed one other ROM that I can't remember its name, but also didn't like that. I realized my comfy home of SlimRom was where I wanted to be, so I tried to flash the backup.zip that I had created but it kept saying installation aborted (Status 0).
After hours of countless attempts and just weird behaviour (sometimes boot loops, sometimes not booting into recovery, etc.) I finally got my phone back to stock.
I downloaded the latest SlimRom file 3 times to make sure it wasn't a corrupt zip (twice from my PC and once from my phone directly). Both the zip directly from Slim as well as the backup.zip that I made with ROM Manager give me the same installation aborted. The other error it gives is "E: Error in /data/media/0/slim....zip". I'm wondering if somehow my partition is screwed up. I tried using Odin's repartition, which just erased my recovery partition, but I got that back thankfully! When I wipe data/factory reset it says wipe complete (and the ROM does reset to factory) but it also says "E:unknown volume '/sdcard/.android_secure' "...I'm wondering if that relates to why the backup.zip file won't read properly. Maybe the partition got screwed up somehow?
I can flash a SU zip so it's not a flashing problem, per se. And thankfully Odin always works!
I think I may need the stock PIT file for the Telus S4 l337m, which I found but my phone says "secure check fail: pit"
I'm not sure where to go from here...
Rom manager is your problem. That software I'd waaaaay out of date and rarely ever works on newer phones.
Get you goo manager. Allow SU. Then hit the menu button and then hit install openrecoveryscript. You will get TWRP recovery. Then you follow the OP of your ROM of choice to install.
Sent from my GT-I9505G using XDA Premium 4 mobile app
Thanks for the suggestion. I used Goo but it was no help. I can flash other ROMs fine. It seems to be just SlimBean that I can't flash :s. I've used TWRP recovery as well as CW and neither work.
Any other ideas?
This is a pickle I am completely unsure about, then... I am sorry I can't be of more assistance. It does seem like the partition is borked.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
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.
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).