Related
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, everybody!
I am stuck with the problem, I cannot solve, and cannot google.
I saw a lot of similar, but none of the directions helped me to fix my phone.
I've got my Nexus 4 which was a great phone until I updated it to 4.3, some of the screen portions became senseless on some applications (starting from SMS, to some game apps).
I was suggested to downgrade or change ROM, which I am trying to figure out right now.
I've rooted my phone with SuperSU-v1.85 and installed Clockwork-6.0.4.3.
Once I've done it, I was trying to load an images of cm-11 and gapps-4.4 with
adb push
it finished all operations in cmd, however, I got
E: Can't mount /sdcard
Thus, I've tried to install all zips from sideload and my cmd.
I didn't touch kernel.
Once I've done this, I tried to reboot, but Cyanogen stuck, running circles.
I've tried to do factory reset, clear cache and dalvik, however none of those worked.
I also have been doing this with a more stable release (cm-10.2.0), but I got same thing.
bagelisnotaname said:
Hi, everybody!
I am stuck with the problem, I cannot solve, and cannot google.
I saw a lot of similar, but none of the directions helped me to fix my phone.
I've got my Nexus 4 which was a great phone until I updated it to 4.3, some of the screen portions became senseless on some applications (starting from SMS, to some game apps).
I was suggested to downgrade or change ROM, which I am trying to figure out right now.
I've rooted my phone with SuperSU-v1.85 and installed Clockwork-6.0.4.3.
Once I've done it, I was trying to load an images of cm-11 and gapps-4.4 with
adb push
it finished all operations in cmd, however, I got
E: Can't mount /sdcard
Thus, I've tried to install all zips from sideload and my cmd.
I didn't touch kernel.
Once I've done this, I tried to reboot, but Cyanogen stuck, running circles.
I've tried to do factory reset, clear cache and dalvik, however none of those worked.
I also have been doing this with a more stable release (cm-10.2.0), but I got same thing.
Click to expand...
Click to collapse
Try another rom besides CM.
scream4cheese said:
Try another rom besides CM.
Click to expand...
Click to collapse
Tried MIUI.
Same thing.
Did I brick it?
scream4cheese said:
Try another rom besides CM.
Click to expand...
Click to collapse
I've tried stock ROM 4.2.2, flashed it with flashall.bat, stupidly, it works.
However, what is the problem with the custom ROMs?
Do I do something wrong?
ps. screen is still unresponsive in some areas.
Maybe you'll have better luck with TWRP 2.6.3.3.
audit13 said:
Maybe you'll have better luck with TWRP 2.6.3.3.
Click to expand...
Click to collapse
Just tried it.
Didn't work out with MIUI.
Just put the files directly onto the phone either by downloading them on it or transferring normally over USB.
Reboot into recovery
From here you got options but to make it simple do a full wipe. A full wipe is deleting everything but your internal storage. That includes / system /data and everything else your recovery shows but the internal storage. Then just flash the ROM zip and gapps zips from your internal storage after the wipe and reboot
If you delete your internal storage you will wipe out the zips you just put there. Along with your media. Pictures music and whatever else is on there
Wiping your data will wipe your apps. So if you want, back them up with something like titanium backup prior. They will still be there after you flash the custom rom as long as you don't wipe your internal storage.
Hello,
I decided that as I was tired of Google Play's ever growing size and because my phone had started making random error noises I'd try rooting it. I also like trying out stuff with technology. It's proving more difficult than I expected though
Here's what I have / what I did:
1. Rooted phone using update.zip that I got from somewhere on XDA.
2. Put a temporary CWM file and ROM (Cyanogenmod 7.2 which I got via XDA: 'CM_totoro_RC_04').
3. Went into CWM and tried to install the ROM. I can't remember exactly what happened but it looked like it was working i.e. there was an 'installation complete' message but when I boot into recovery mode some blue text comes up and what I'm left with is:
"(Invalid argument)
E: Can't mount /cache/recovery-last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache
(Invalid argument)"
I think there's more than that but that's what I'm left with on the screen.
I did wipe the user data and cache and I have tried a different CWM but there's no change.
I'm using a laptop with a Linux system and it won't recognise the phone in its current state. I think Heimdall is a cross-platform equivalent to Odin but I'd prefer not to get into that as I'd like to try and keep things simple. I have a second phone (which is working and recognised by my laptop) so I can put ROMs etc on its SD card and then physically transfer the SD card into the Galaxy Y.
I do not have a backup of the Galaxy Y before rooting so I don't think it's easy to get back to where it was before I rooted it.
Is the CWM fully compatible with the Galaxy Y? How come the message says that the installation is complete yet it's not working? Am I not following the correct steps after it says installation complete (I think I selected 'reboot' from CWM at this point)? Am I not giving the phone long enough to boot after flashing the ROM (it seems to stop at the Samsung logo screen)? Is it worth trying a different ROM, after all CM7.2 is an unofficial port?
Prior to rooting I hadn't altered anything important i.e. the phone was as it was at manufacture.
On re-reading the installation instructions I note that I didn't:
- Format /system partition
- Install the kernel provided at Download links
I couldn't find the kernel though - was this a critical oversight?
Any help or suggestions much appreciated. Thanks!
To start off with if you are using cm7 you need to be using the cm7 common kernel
You also need to use the ext formatter to convert system to ext
Once that is done you need to reboot to recovery
Format system data cache
Mount system data cache
Flash rom zip
If you still get cache error just make a nandroid backup in cwm then advanced restore cache only
Full instructions and links to everything you need will be on the cm7 rom thread
If all else fails flash stock rom via odin & start again - see my firmware thread Link in signature
Thanks! As seems normal though the information isn't that clear (to me at least). I searched for 'cyanogenmod 7.2 galaxy y' and went to
http://forum.xda-developers.com/showthread.php?t=2537457
In the second post are 2 downloads - I'm assuming it's the first one as I think the one I've already tried the 'totoro' one?
I'll give this a bash later and post back...
ksjs said:
Thanks! As seems normal though the information isn't that clear (to me at least). I searched for 'cyanogenmod 7.2 galaxy y' and went to
http://forum.xda-developers.com/showthread.php?t=2537457
In the second post are 2 downloads - I'm assuming it's the first one as I think the one I've already tried the 'totoro' one?
I'll give this a bash later and post back...
Click to expand...
Click to collapse
That is a very old build
The version of cm7 that roms are based on is
http://forum.xda-developers.com/showthread.php?t=2673610
Kernel required
http://forum.xda-developers.com/showthread.php?t=2673603
Ext formatter
http://www.mediafire.com/download/s6191k8ze9en0l6/ext4_formatter.zip
Follow instructions in this post
http://forum.xda-developers.com/showpost.php?p=50899031&postcount=3
Big thanks for your post - perfect! I now have CM7.2 installed and a less bloated phone
Hello guys!
I am Luis, from Spain (please, forgive my writen english) and I must say that I have used your help before, but never I have need to write my doubts until now.
I have the Moto X play without any SDcard, and I want to change the original ROM (I am already root with TWPR and SuperSU) and my doubt is when I will make the Data wipe and factory reset if all my backups and even the new ROM will be erased from the internal storage.
My last experience on installing ROMs was in 2010 on a HTC Desire, so you can imagine my ignorance with this issues.
Are the next steps correct for installing new ROM?
* 1. Copy the ROM to the phone.
* 2. Go to recovery TWPR and wipe data and do a factory reset. In this point I have the doubt of the erasing data.
* 3. On TWPR go to install, select the ROM and go on.
* 4. Reboot.
Many thanks for pay attention!
Kind regards,
Luis
if you haven't sd card following the next steps:
1 - enter the recovery and full wipe
3 - plug your device in your computer and copy the rom and the gaaps in your phone
4 - flash rom and gaaps and reboot
https://youtu.be/Fk4hN9gZT90
Follow this tutorial
diegomartinezlovey said:
if you haven't sd card following the next steps:
1 - enter the recovery and full wipe
3 - plug your device in your computer and copy the rom and the gaaps in your phone
4 - flash rom and gaaps and reboot
Click to expand...
Click to collapse
Thank you for your response, Diego. But I have the problem that within tWRP, the USB Mounting doesn't work, I can't see the Storage unit in my windows PC. Can I send the files via "adb push file /sdcard"? I think that other way is buying a SDcard.
mani198 said:
Follow this tutorial
Click to expand...
Click to collapse
Thank you, mani, but I don't want to restore the default software on the phone; I want to erase it,
@mani198 very rare, twrp is usb on the go, maybe you can't install the motorola 's drivers or try in another usb port...or buy a SDCard
diegomartinezlovey said:
@mani198 very rare, twrp is usb on the go, maybe you can't install the motorola 's drivers or try in another usb port...or buy a SDCard
Click to expand...
Click to collapse
Finally I've had success changin the ROM! You have reason, only data wipe and the factory reset keep the rom data in /sdcard folder.
Many thanks!!
Magilzhi ????
luis_j said:
Finally I've had success changin the ROM! You have reason, only data wipe and the factory reset keep the rom data in /sdcard folder.
Many thanks!!
Click to expand...
Click to collapse
Great to hear this worked. Im using an usb otg stick to change roms after my sc card slot/reader is damaged and never knew this method also works.
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).