I am running the Revolution HD rom, this is how I purchased my TF101 from a friend, and I want to restore the factory rom so I can get ICS and the update for the battery issue until mike gets it implemented into Revolution.
How can I do this?
Thanks!
-edit- nevermind, I didn't notice you were running revolution.
If you want to flash back to stock, go to the ASUS Support site and download the 9.2.1.11 firmware for your device.
Unzip it 1 time (there is a zip file within the zip) so it will still have a zip.
Put the file on a microSD or the internal /sdcard/ directory depending on your version of CWM and where it can read.
Boot to CWM.
Install zip.
Choose the zip you downloaded.
Now you will be back to stock unrooted with stock recovery.
Then you will need to check for updates and grab the latest update from ASUS OTA.
If you want to root again you will need to vipermod option 1 to get root access.
Ah, thank you Fred! I did exactly that and it failed but it was the zip within a zip that killed me!
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Here's exactly what I did to go from Revolution HD 3.0.1 back to stock Asus ICS 9.2.1.11
1. Download the firmware from Asus website. The file name was US_epaduser9_2_1_11UpdateLauncher.zip. You unzip this. You get US_epad-user-9.2.1.11.zip. You put US_epad-user-9.2.1.11.zip on your microSD card.
2. Boot into CWM
3. Factory reset
4. Clear Cache
5. Clear dalvik cache
6. Mount & Storage - format /system
7. Mount & Storage - format /cache
8. Power off(from CWM menu, might be under advanced, I forgot)
9. Boot into CWM.
10. Install zip from sdcard. Choose US_epad-user-9.2.1.11.zip on your microSD.
11. Reboot after flashing is complete.
12. You should now be on Asus stock ICS with stock recovery.
13. I didn't add any of my google accounts during the initial setup because I wanted to do it after I do the 9.2.1.17 update.
14. Shut off and do a cold boot.
Worked perfectly fine for me.
What didn't work was, I was not getting the 9.2.1.17 update afterwards.
So I rooted using Vipermod, installed CWM, and manually flashed the update through CWM. I had to re-root after the update. Simply ran Vipermod again.
Been 2+ days, and it's super stable with great battery life. Not a single random reboot or crash.
gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
gee one said:
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
gbatt said:
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
Click to expand...
Click to collapse
I am pretty sure my CWM Recovery was 3.1.0.1 too.
Try replacing your CWM with Rogue XM Recovery http://forum.xda-developers.com/showthread.php?t=1446019
Awesome! That worked great. Thanks Horndroid!
hi
motoroladefy plus MB526 from australian
i copy many of files to SD (downloaded till i finsh my monthly limit) change the name to update.zin files
same msg
now my phone cant start system freezing @ motorola logo
when i chioce power and down button then down + up open a windows wrote this :
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
copy may ROMs to SD and i choiced 2.apply update from sd
show me after check this msg:
E: signature veification failed
install aborted
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote: Error validating image file ..when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
how can i solve this please
can i get australian service center for motoroladefy plus email ?
thank you
Questions go in the Q&A section
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
need help
MarcinRN said:
What were you trying to flash and why from stock recovery? Have you rooted your defy and installed 2ndinit? You can't install any custom roms from Stock Recovery. CWM recovery is meant for such purposes.
Click to expand...
Click to collapse
in first thank you
yes installed 2ndinit and super1c,rom manger = cwm and <3e rerovery>..(byaway still <3e> see it when i prss down volum:
Android system recovery <3e> isnt mean its not stack recovery?
in first the recovery boot work with all option ( backup,recovery,back,...) i think it mean root succeed _saw blue LED
but cant install ROM ...E:signature verification failed Installation aborted)-nothing accept to install same error ..thats mean NO i cant install any ROM
restarted and wiped data,cache, again and again + (system formt) after restart cant see all option @ recovery mode only that 4 option:
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
this time i have use both -,+ volum to enter recoverymode!
i dont remember i choice unroot under recoverymode!
about LED now only white when i off the phone and connect cable but not charging only white LED
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
dlshad said:
I installed RSD v5.6 but all i downloaded (i try many of files) show me this msg:
status wrote:
Error validating image file
when i press start change msg to:
Failed flashing process.Failed flashing process. (0x7100);phone connected
Click to expand...
Click to collapse
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
MarcinRN said:
In order to flash SBF phone must be in bootloader mode. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1618718
Make sure you're flashing a proper sbf file...
Click to expand...
Click to collapse
thank you
im sure im in bootloader the white fonts black backgraound
usb conected andthe RSD see the phone
the secount of your note
i install may of files from here:
http://sbf.droid-developers.org/umts_jordanplus/list.php
all of that same error
sure i remove last 2 word (.gz)
in past i upgrate to 2.3.6 seccesed from official site
when i bought it they said its unlocked maybe not factory unlocked is that help!
in recovery mode there is <32> isnt mean its rooted not stock recovery
can i add backup option to recovery mode coz i have backup file
any help
thank you
dlshad said:
sure i remove last 2 word (.gz)
Click to expand...
Click to collapse
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Downloaded sbf file but unable to unpack
MarcinRN said:
You can't just remove the extension. You need to unpack the sbf file with WinRar or 7-zip then flash it. .gz means that file is compressed and you need to unpack it!
Click to expand...
Click to collapse
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
rahulpillai said:
I downloaded 2 different versions of sbf files but cant unpack then as when I try to do that it gives an error any solution for that ?
Click to expand...
Click to collapse
what error does it actually give? which program are you unpacking archive with?
E:signature verification failed. Installation aborted; after rooting spice mi 500
Just yesterday I rooted my spice mi 500. Was fine untill i paid and downloaded a bunch of pro apps like ROM Manager Pro, and ran some scripts, thinking it might be routine clean up. but after running some script...I am only getting the followin message. I can see my spice phone in device manager on my PC, and drivers are up to date. I am unable to use the USB properly as the PC is not recognizing my device...Pls help asap. thanks.
Android system recovery <3e>
1. reboot system now
2. apply update from sdcard
3.wipe data/factory rest
4.wipe cache partion
Plese Help... !!!
:crying:
I m having MMX A25 .
i have installed CWM 5.x.x.x.version
whenever i tried to install custom Rom in it .
It just shows me an error SIGNATURE VERIFICATION FAILED
i am totally stuck,.. !! plese somebody help me out to install custom rom.
Help would b appriciated. :good:
I have same problem with galaxy s gt i9000 Froyo with recovery 3e.
I read that this recovery doesn't allow installation of files not signed.
Tried many but no luck I'm rooted but cannot install even a custom recovery.
Did you find the solution please.
Thanks
Sent from my GT-I9000 using Tapatalk 2
I've been trying to install ilya's jb 4.2.2 cm10.1, i tried both version 12 & 13 but to no avail. Both just dropped dead in installation i'll post the error message below if anyone can help me you're very much thanked for helping a retard like me
here's the link to the rom's page
http://forum.xda-developers.com/showthread.php?t=2145187
Error Message
"Start Update
format () expects 4 args , got 5
E: error in /sdcard/"fileFolder"/"fileName.zip"
(status 7)
Installation aborted.
"
Noob4Pwn said:
I've been trying to install ilya's jb 4.2.2 cm10.1, i tried both version 12 & 13 but to no avail. Both just dropped dead in installation i'll post the error message below if anyone can help me you're very much thanked for helping a retard like me
here's the link to the rom's page
http://forum.xda-developers.com/showthread.php?t=2145187
Error Message
"Start Update
format () expects 4 args , got 5
E: error in /sdcard/"fileFolder"/"fileName.zip"
(status 7)
Installation aborted.
"
Click to expand...
Click to collapse
i get the same error. i believe it's because of the partition. u must flash this forumber one. i was pretty sure i had flashed it as i used to use this rom for a while but now i can't. so u just need to reflash the forumber partition
That error it's cause by either partition or wrong CWM recovery. I don't remember which...
Noob4Pwn said:
I've been trying to install ilya's jb 4.2.2 cm10.1, i tried both version 12 & 13 but to no avail. Both just dropped dead in installation i'll post the error message below if anyone can help me you're very much thanked for helping a retard like me
here's the link to the rom's page
http://forum.xda-developers.com/showthread.php?t=2145187
Error Message
"Start Update
format () expects 4 args , got 5
E: error in /sdcard/"fileFolder"/"fileName.zip"
(status 7)
Installation aborted.
"
Click to expand...
Click to collapse
It's a partition problem.
Just follow the steps to repartition your phone from this post.
http://forum.xda-developers.com/showthread.php?p=29505489
Sent from my U8800 using xda app-developers app
hkej said:
It's a partition problem.
Just follow the steps to repartition your phone from this post.
http://forum.xda-developers.com/showthread.php?p=29505489
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
This is how I solved the issue.
{A} backup IMEI using 5irom tool.
[1] I downloaded official B138, flashed using dload method.Reboot phone
[2] downloaded official B518 .flashed [upgrading from 2.2 to 2.3]. Reboot phone
[3]rooted the phone using super one click.
[4]downloaded CMW recovery and flashed.
entered download mode [volume up+power]
wiped factory/partition.
in mount and storage>format =cache.data & system.
[5]choose zip from sdcard ,selected forumber partition zip and instal.
[6]AGAIN choose zip from sdcard ,selected forumber partition zip and instal.
[7] choose zip from sdcard > cm10.2 for u8800 version 13.zip
[8]flashed gapps.
[9]reboot system
this method worked for me after it kept hanging on ideos logo every time i flashed the rom. long method but works. Don't forget to backup your imei.
the same problem
solved
I did with the help of this theard:
http://forum.xda-developers.com/showthread.php?t=2145848
Code:
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Then I flash it with TWRP 2.6.3.0
After flashing I got this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "filename"
E: Error installing zip file 'filename'
I tried Dalvik/Cache wipe but it didn't help.
Now I can't boot into Android, it show GOOGLE and then blank screen
I can go to TWRP but when I try to use ADB sideload to connect with my computer, I get this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "inner.zip"
E: Error installing zip file 'inner.zip'
I don't have any rom in SDcard but the file "signed-occam-KRT16S-from-JWR66Y"
May anybody help me with this problem, please
In the worst case, where can I fix my phone with fee
Any changes to the /system partition or by rooting can cause OTA to fail. Flashing OTA is only recommended to a pure untouched stock rom.
Follow the guides in my signature to flash 4.4 without wiping your data.
mecatro said:
I did with the help of this theard:
http://forum.xda-developers.com/showthread.php?t=2145848
Code:
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Then I flash it with TWRP 2.6.3.0
After flashing I got this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "filename"
E: Error installing zip file 'filename'
I tried Dalvik/Cache wipe but it didn't help.
Now I can't boot into Android, it show GOOGLE and then blank screen
I can go to TWRP but when I try to use ADB sideload to connect with my computer, I get this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "inner.zip"
E: Error installing zip file 'inner.zip'
I don't have any rom in SDcard but the file "signed-occam-KRT16S-from-JWR66Y"
May anybody help me with this problem, please
In the worst case, where can I fix my phone with fee
Click to expand...
Click to collapse
why dont you just search your issue and for fixes... Put your phone in recovery and use adb to push over a rom. I dont want to be the bad guy here but why flash an OTA zip if you are already rooted just flash a stock rom. So many of you make things so much harder for yourself than it has to be.
Sorry for bashing you but you also should always keep a nandroid on your phone. Do some research or try what I suggested and good luck but for future reference be mindful of what may happen if things go wrong
playya said:
why dont you just search your issue and for fixes... Put your phone in recovery and use adb to push over a rom. I dont want to be the bad guy here but why flash an OTA zip if you are already rooted just flash a stock rom. So many of you make things so much harder for yourself than it has to be.
Sorry for bashing you but you also should always keep a nandroid on your phone. Do some research or try what I suggested and good luck but for future reference be mindful of what may happen if things go wrong
Click to expand...
Click to collapse
I used OTA because I didn't want to reset my phone. I know it was stupid
I read some topic and they said my problem is TWRP 2.3.6 isn't compatible with android 4.4
(I should use CWM is).
I think now I have some think like android 4.4 in my phone but it can't boot
The problem now is I can go to recovery but can't usse adb to push a rom.
I tried some search but there was no help
eksasol said:
Any changes to the /system partition or by rooting can cause OTA to fail. Flashing OTA is only recommended to a pure untouched stock rom.
Follow the guides in my signature to flash 4.4 without wiping your data.
Click to expand...
Click to collapse
Thank you. I flash Google's ROM with fastboot and it's working now.
Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?
digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!
error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?
baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?
baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).
digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?
baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
baytee said:
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app
Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).