I bricked my phone and kept trying too recover it with odin. I never completed the process but now i am able too get into recovery. Can anyone give me a update.zip that will flash in the stock recovery? I tried SPH-D700-DG27-8Gb-REL and changed the name into update zip, but it says
Install from sdcard..
Finding update package..
E:Cant mount /dev/black/void/179:1
(no such file or directory)
E: Cant mount SDCARD:update.zip
Installation aborted
Unfortunately, once your phone is bricked, the only way to recover it is using odin. When your phone is bricked, it's because the filesystem on the nand is messed up (like when you unplug a hard drive halfway through a format, it no longer has a filesystem and needs to be formatted). If you're having trouble with odin, first make sure you're setting it up and using it correctly, here's a link to the odin guide: http://forum.xda-developers.com/showthread.php?t=773032]link Also, that tar file isn't in the format the update.zip method in recovery is expecting, and that's why it fails to mount the zip you created. Plus, you can't simply rename a tarball into a zip without actually changing the encoding, they are two completely different file types (Would you change the brand badge on your mazda to a nissan and expect a nissan only shop to know how to fix it simply because it says nissan? :]).
If that doesn't work, try turning off BOTH your phone and computer. Pull the battery out of your phone and boot up your computer. Login and start up odin. THEN put your phone in download mode and FINALLY connect to the computer. Start the flash. Let me know if this helps !
fyi, where odin is getting stuck is also an important detail.
EDIT: Almost forgot, make sure you are using the drivers posted on these forums. There are many versions out there that are known to cause problems.
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.
I'm new to the Moto Droid world coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.
beeewell said:
I'm new to the Moto Droid world
coming from Samsung, and trying to learn about it. I've googled and read a lot about all of the topics below, and I'm looking to learn more. Here are some observations/issues that I'd appreciate any insight on - It would also be helpful to know if these are known, open/unresolved issues:
My device is rooted and unlocked, running sys. ver. 183.46.10.xt907.Verizon.en.US, build KDA20.62.10.1. (I think that's stock Verizon). I have CWM ver. 6.0.4.8 installed. When I try a nandroid backup to my external sd card (/storage/sdcard1), boot-image, recovery image, and system complete normally. When it tries to backup data, I get the error "Can't mount /data!". When I look at my external SD card, I see 4 non-empty files (boot.img, recovery.img, system.ext4.tar.a, system.ext4.tar.b) and 1 empty file (system.ext4.tar). Is there anything I can do to get CWM to backup data also? Do I need to resort to backing up with ADB to get everything?
When I reboot from CWM, I get "rom may flash stock recovery on boot - can't be undone" with "no" or "yes - disable recovery flash" as my choices. I think either choice keeps my CWM recovery. I then get "root access possibly lost - fix? with "no" or "yes fix root (/system/xbin/su)". If I select "yes fix root (/system/xbin/su)", it keeps root, and if I select "no", it loses root. Shall I consider these as minor annoyances that I shall forever live with?
I've tried to flash TWRP, and the only version that I've been able to boot up is the latest one, version 2.8.1.0. The problem is that the font is too big, or our screen size is too small for that version. Is there a version of TWRP that works on our device? I tried ver 2.5, and it doesn't boot.
To flash, I boot the phone into AP Fastboot and use mfastboot on my Windows PC.. Flashing seems to work, but I always get the "<bootloader> variable not supported" message at the start. Is this anything to worry about or indicating some other problem?
Thanks in advance for any and all responses.
Click to expand...
Click to collapse
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645
Thank You !!
ATTACK said:
You're using the wrong TWRP. Use TWRP281KK.img > http://d-h.st/511
All the info you need is here > http://forum.xda-developers.com/dro...oot-unlock-t2869432/post55282645#post55282645
Click to expand...
Click to collapse
Thank you so much for your reply, and for pointing me to the correct TWRP for my device. It worked like a charm !! :good:
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).
I want to flash a rom but it always does something and that is keeping me from flashing a rom it says
Filesystem detected /dev/block/bootdevice/by-name/system
And then it says patchingsystem image unconditionally
And the it does it again and after that script ran successfully
The roms i try are the ones of mparus on xda
Please help i really want lineageos or cm13
Hello, I did not understood very good if you had some errors or not, but try in this way:
-Install the latest stable TWRP, you can find it in the first post of the LineageOS thread
-Download the ROM and the GApps and copy them on a microSD card, if you do not have it you can copy the files in the device memory
-Reboot to recovery
-Click on "Wipe", then swipe to do a factory reset
-Now install and select first the ROM and then the GApps zip
-Swipe to install and it should work s
If you have any problem, please describe them accurately so I can understand and help you
I shall try this weekend i need to first backup everything again maybe it will work cus i did system and data wipe
Nope followed every step still it says
Detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally
Detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally
And then it stops i dont know why this happens
After the part above it installs gapps normally
Maybe the zip are damaged, try to download again the ROM
Already tried
I think it is something with my phone
What recovery are you using?
Twrp 3.0.3
Try with the 3.0.2.0 one
Did same redult
Result
I am going to buy a new phone next month so i am going to give up thnx for youre help anyway