Database Users

[Q] Help Please! can't install any roms

Hello..I had WajkIUI_multilang_1.11.18_RTL, which was working just fine then i tried a new rom,,i didn't like it so when i tried to go back to the old rom,i just can't finish the installation,when i use the RSD lite to install the original rom it works fine then i root the device,then i installed SndInitDefy then when i go to the recovery menu i can't install the rom,,i've tried manytimes , but the same thing happens:
when i try to wipe the data or cache: E: Can't open /tmp/recovery.log
so i go to the next step by choosing the installation of the rom and i get this message:
E: can"t make /tmp/update_binary
ClockworkMod Recovery v2.5.1.8
insallation aborted
Please help my..i don't know what to do now,i went to the Wajkiui rom page and red everything carefully ..but still can't change my rom, i need to insatll the Wajkiui rom
right now the rom is : shadow-128 2.3.4
that alot

Which version of 2ndinit did you use?
The best for wajkiui is 1.4.2
Or you can try to select stable recovery instead of latest recovery.
I'm using the same config(shadow_2.3.4-134_DFP-10.sbf and WajkIUI_multilang_1.12.16_ICS.zip)

i'm using the same version..i've tryied everything in the Recover to install the rom,but i still get the same error message

This is what i'm going:
Rooted the device, installed SndInitDefy_1.42.apk and activated the Sndindefy
i copied the rom into my MC.
started my phone
Entered the boot Menu
in the RECOVERY menu there are only two options: ( Custom Recovery- Stock Recovery )
in Custom Recovery- Wipe data/cache =
formatting data...
formatting cache...
formatting sdext...
No app2sd partition found. Skipping format of /sd-ext.
formatting sdcard:/.android_secure...
Data wipe complete.
E: cant open /tmp.recovery.log
then i choose: install zip from sdcard
i chose the rom zip.
--installing: sdcard:wajkiui..
Finding update package..
opening update package..
Installing update...
E: Can't make /tmp/update_binary
Installation aborted.

Ok...
I dont't know what it could be...
Try wipe dalvik cache too.(under avanced menu)
And try to format your sd card.
It worked for me with the "shadow_2.3.4-134_DFP-10.sbf".
rooted by "root4defy134.zip" (applied in stock motorola recovery)
then installed 2ndinit 1.4.2 (2.0 worked too) and installed the latest wajkiui.

Try downloading the zip file again. Maybe it's corrupted.
Sent from my MB526 using XDA App

I've formatted the memory card..i downloaded the rom again..the problem isn't with the rom..its in the RECOVERY option..cuz b4 installing the rom the device isn't able to wipe neither the cache nor the data...and after that the rom is unable to install
plus the (avanced menu) isn't showing,
i really don't know what to do next...

Ok.
Just try now with 2nd init 2.0. Insall 1.0.7(it wil ask during install recovery,WIFI nedded)
Now you must have advanced menu.

I've done what u told me,,,and it WORKED ..yaay..lol
thats alot buddy, i've been trying to fix it for the past 3 days..and u've helped me alot..even though i insalled many roms inclding the Waijk using the same old version of 2nd init..i don't know why it gave me so much truble sudenly..anyways the problem is solved with YOUR help..
I want to thank u for ur time and concern,,

That's cool! I'm glad that I could help.

buruss said:
Ok.
Just try now with 2nd init 2.0. Insall 1.0.7(it wil ask during install recovery,WIFI nedded)
Now you must have advanced menu.
Click to expand...
Click to collapse
how to do this... please help me.. i wanna install cutom rom like thread stater, now stuck at splash screen

[Q] Please help me, error while flashing

Hi guys, I hope you can help me.
I have just rooted + flashed my motorola defy plus for the first time (on any device for that matter)
I installed 2nd init, version 0.6.... or something.
Put a rom, kernel and google apps on my sd-card
Then I turned usb-debugging off and rebooted my phone.
Now I can get into bootmenu, and this is what I do:
1) go to recovery
2) select custom recovery
3) then it says: Clockworkmod Recovery v2.5.1.8
E: Can't open /tmp/recovery.log
4) I then select wipe data/factory reset
5) then it says this: Formatting DATA
Formatting CACHE
FORMATTING SDEXT
No app2sd partition found. Skipping format of /sd-ext
Formatting SDCARD:/.android_secure
Data wipe complete
E: Can't open /tmp/recovery.log
6) After that i select install zip from sdcard
7) then I select choose zip from sdcard
8) then I select the zip file containing the rom
9) And it says: Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
Now I can't go any further and can't use my phone at all
I hope u guys can help me, and that I haven't F*ed up my phone

I have a quite similar problem.
On a defy+,rooted 2ndinit installed, backup-ed first, download the new quarx05/03 ICS, put the zip on sd, wipe data, reboot and start to install ics, but the message was
''Finding update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted"
Thanks to the previously backup I can use may phone as usual.
What I have done wrong with de ICS installation?
Thanks
PS. Sorry for probable a dummie question:What we have to do with md5 zip near the CM9 Jordan.zip?

A little help please about the subject?
Thank you

ics
The entire process
ClockworkMode v2.5.1.8
Wipping data...
Formatting DATA...
Formatting CACHE...
Formatting SDEXT..
No app2sd partition found.Skipping format of /sd-ext.
Formatting SDCARD: /.android_secure...
Data wipe complete
E: Can't open /tmp/recovery.log...
Installing: SDCard:download/CM9-ICS-MR1-120305-jordan.zip
Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
if try Wipe Dalvik Cache:
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
I guess that this is a simple and many times occured error, since nobody has any answer....

Does you disabled the usb debugging before flashing?

Yes I do, but nothing change,
Thanks

if I'm not mistaken the last release of 2nd init is not compatible with defy. Try to check this on the development forum. I hope I have been of help.

I'd tried with both 1.0.7 latest and 0.6.1.
With latest, the phone is blocked.
Thanks

I had used this. Try with it
P.S. sorry for my bad english.

Tried, the same errors,
Thanks

I don't know. Sorry. By the time i had used that.

I think you need to go to stable recovery after you wipe your data from custom recovery
Sent from my MB525 using xda premium

I think you need to go to stable recovery after you wipe your data from custom recovery
What do you mean by "stable recovery"? You talk about version 0.6. of 2nd init or something else?
Can you show a step-by step procedure?
Thank you in advance.
However, which is the procedure to un-root a defy+ and to have it with the original, fresh system?

I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?

cretu22 said:
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
Click to expand...
Click to collapse
Hi, I have exactly the same problem.. Trying to find a solution but is quite difficult. First I thought it has something to do with the partitioning, as stated in THIS topic. But, in THIS topic, people say that partitioning the SD card is not necessary at all..

@Cretu22: Yes stable recovery is CWM 0.6
Don't install stable recovery! I too faced this issue when I flashed using stable recovery. In snd init install Latest recovery and then try flashing your ROM. That should work..

I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu

fokkeh said:
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
Click to expand...
Click to collapse
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..

pranks1989 said:
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
Click to expand...
Click to collapse
Yes, its working Pressing the volume down button was not necessary with 0.6.7, that was what went wrong. Now the zips installed like a charm

i know the answer and is very simple
the problem is that you cannot create that specific folder.... because it already exist, cmp (connected music player) creates it, just delete it from SD and done!

flashing issues

so far all the roms i have taken from this forum have failed to flash, my recovery says it cant open the zip file.......
don't know what im doing wrong.......the device is rooted fine.....
after it has failed i then have problems restoring my back ups so i then need to flash stock with odin......
its a gt i9505, so i think im in the right section...
please advise....

mediaman123 said:
so far all the roms i have taken from this forum have failed to flash, my recovery says it cant open the zip file.......
don't know what im doing wrong.......the device is rooted fine.....
after it has failed i then have problems restoring my back ups so i then need to flash stock with odin......
its a gt i9505, so i think im in the right section...
please advise....
Click to expand...
Click to collapse
Which recovery are u using? And just for confirmation use root checker app and check the root status
.

123hiten said:
Which recovery are u using? And just for confirmation use root checker app and check the root status
.
Click to expand...
Click to collapse
all is good with the root checker and i am running twrp 2.5.0.1, tried to flash with cwm and the same happened......

mediaman123 said:
all is good with the root checker and i am running twrp 2.5.0.1, tried to flash with cwm and the same happened......
Click to expand...
Click to collapse
Option 1,
Flash Philz recovery and see if the issue is solved if not i would suggest a fresh start
Option 2,
1, Flash Stock firmware using
2, Reset the device from setting / account / backup&reset
3, Root using CF root
4, flash Philz recovery
5 ,Start flashing Roms u want
Please take a backup of important data B4 flashing and resseting the device

123hiten said:
Option 1,
Flash Philz recovery and see if the issue is solved if not i would suggest a fresh start
Option 2,
1, Flash Stock firmware using
2, Reset the device from setting / account / backup&reset
3, Root using CF root
4, flash Philz recovery
5 ,Start flashing Roms u want
Please take a backup of important data B4 flashing and resseting the device
Click to expand...
Click to collapse
Thanks for your help.....I will try restoring it to stock and start from the beginning.....will doing a factory reset in settings restore the stock recovery.....
I did actually try philz touch recovery....same thing happened....but I will try your option 2 and get back to you pronto.....

So I followed the steps you asked me too, twice and still no joy.....
philztouch recovery gives the following message:
E: Cab't open /external_sd/ROMS/SuperDroid_v4_m3ddog.zip (bad)
Installation aborted
Does it matter my custom rom file is on my external sd card?
The only thing i can think of is that i am trying to install a rom for different s4 variation maybe.........its the gt i9505, thats all i know....
HELP ME!!!......:crying:

mediaman123 said:
So I followed the steps you asked me too, twice and still no joy.....
philztouch recovery gives the following message:
E: Cab't open /external_sd/ROMS/SuperDroid_v4_m3ddog.zip (bad)
Installation aborted
Does it matter my custom rom file is on my external sd card?
The only thing i can think of is that i am trying to install a rom for different s4 variation maybe.........its the gt i9505, thats all i know....
HELP ME!!!......:crying:
Click to expand...
Click to collapse
Sorry for late reply
Since this also not helping I guess u have issue with root may be
Let's try little diffrnt
As per what I understood u have i9505 correct me if I m wrong
U download a pre rooted firmware from android devlpmnt thread
Flash the firmware reset and tell me the status of by he same and then will try flashing philz recovery
Edit link below for rooted firmware
http://forum.xda-developers.com/showthread.php?t=2250824
[ROM] WORLD PREMIERE: I9505 XXUBMGA DEODEX [4.2.2] - Pre-Rooted Stock ROM's Odin/CWM
.

mediaman123 said:
So I followed the steps you asked me too, twice and still no joy.....
philztouch recovery gives the following message:
E: Cab't open /external_sd/ROMS/SuperDroid_v4_m3ddog.zip (bad)
Installation aborted
Does it matter my custom rom file is on my external sd card?
The only thing i can think of is that i am trying to install a rom for different s4 variation maybe.........its the gt i9505, thats all i know....
HELP ME!!!......:crying:
Click to expand...
Click to collapse
Its telling you the problem... The rom you have above isn't complete or corrupted - IE"bad"
Either re-download the rom or try another rom...

ultramag69 said:
Its telling you the problem... The rom you have above isn't complete or corrupted - IE"bad"
Either re-download the rom or try another rom...
Click to expand...
Click to collapse
thanks, its just strange that the 2-3 roms i have tried have all returned that error message, I will download the rom you linked and get back to you.....
is that rom to go on with odin, as currently i have stock recovery......?

no joy with the linked rom......
same thing happened, i can successfully get it rooted and flash recoveries no problem......
is it possible its a sd card problem.....

also, when i go to restore the back up i make before flashing the rom, it reverts back to a brand new handset, so i need to set it all up again, put in my Google account details etc.......all my apps return obviously, but this isn't meant to happen is it......
it really is confusing me, all the other devices I have had in the past and currently have flashed ok........
when i wipe before the flash, its just the default factory reset, cache, dalvik I do , is this correct?

That should be fine, it is possible the sd card is corrupt or not communicating properly with the recovery. You could always put the rom on the internal sd card.... Just don't factory wipe or you could loose the rom you are trying to flash...

That didn't work either......so frustrated with this.......
Can someone go through the exact procedure....I know there are guides but personal experience s are best.....

mediaman123 said:
also, when i go to restore the back up i make before flashing the rom, it reverts back to a brand new handset, so i need to set it all up again, put in my Google account details etc.......all my apps return obviously, but this isn't meant to happen is it......
it really is confusing me, all the other devices I have had in the past and currently have flashed ok........
when i wipe before the flash, its just the default factory reset, cache, dalvik I do , is this correct?
Click to expand...
Click to collapse
Full Wipe Install means:
- Wipe Data / Factory Reset
- Wipe Cache and Dalvik Cache
- Format System partition
- Install

andymihail said:
Full Wipe Install means:
- Wipe Data / Factory Reset
- Wipe Cache and Dalvik Cache
- Format System partition
- Install
Click to expand...
Click to collapse
thanks....
I have been using twrp mostly....i don't believe the default wipe setting includes the system partition format...........could the absence of this formatting cause problems every time?

finally managed to flash a custom rom.......
the trick was to install the zip without any sort of wipe, then do the wipes after successful installation......
weird eh....

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

Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.

I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6

stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?

digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?

stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]

stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.

Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!

error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?

baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.

digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?

baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).

digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?

baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.

My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/

baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.

While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?

baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.

​
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....

baytee said:
​
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app

Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).

[HELP OXYGEN OS] Can´t install 5.1.5 update or flash in original recovery!!

Hello, I have an OP 5 with unlocked bootloader and i was rooted. So, I'm in 4.5.13, and i'm trying to install 5.1.5 but i need to be unrooted for this.
Somehow when i removed root (magisk) my phone entered in bootloop mode (i think that magisk lost the original boot img). I flashed the stock boot img and the phone booted normally and without root. However i think that some "crumbs" of the magisk or adway stayed in my system or phone partitions and my phone continues to say that he can´t install the OTA. I've already wiped cache and data in the recovery and tried to install with adb sideload but it fails.
I still have my OOS and is working fine, but I can't update... Any ideas?
Do you think that if I do the normal settings > restore factory settings will it work? Or that option will be also damaged?
Should i boot TWRP in fastboot, and try to do a factory reset and then flash 5.1.5?
For your information, i've never flashed anything besides magisk and the attempts to update. The rom is the original as also the recovery. To flash the magisk i always booted twrp connected by usb to my PC.
I apreciate all the help!!

pdalvares said:
I apreciate all the help!!
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.

Dirk said:
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Click to expand...
Click to collapse
Yo, i already tried it different ways, but thank you :/

pdalvares said:
Yo, i already tried it different ways, but thank you :/
Click to expand...
Click to collapse
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/

Dirk said:
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:

pdalvares said:
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
Click to expand...
Click to collapse
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.

Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
I've made what you said but it gives me the error "Updater process ended with error: 7"

pdalvares said:
I've made what you said but it gives me the error "Updater process ended with error: 7"
Click to expand...
Click to collapse
Which TWRP are you using? It should be the latest Official version, or you could try the latest codeworkx from here:
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Error 7 is a generic error code. The useful information about the error is usually in the body of text.
If you can't get TWRP to play nicely you can use it to format partitions as mentioned before, and then use it to install the stock OOS recovery from the bottom of this page:
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
The stock recovery is an .img, so in the TWRP 'Install' menu you need to select Image instead of Zip at the bottom of the screen. Move the stock recovery .img to Internal Storage and flash it. Reboot into Stock Recovery and flash full OOS zip.

Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!

pdalvares said:
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
Click to expand...
Click to collapse
Let me know how you get on. :good:

Dirk said:
Let me know how you get on. :good:
Click to expand...
Click to collapse
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
EDIT:
Could it be because the bootloader is unlocked?? Is it safe to lock it like i unlocked it? No problem?

pdalvares said:
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
Click to expand...
Click to collapse
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877

Dirk said:
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Click to expand...
Click to collapse
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "

pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
Are you trying to OTA or full ROM? OTA is not going to work. Only full ROM .zip will get the job done.
Have you considered giving up on OOS for now and just try flashing a Custom ROM from TWRP? I'd recommend Dirty Unicorns Oreo for now until Pie ROMs mature. You can get their ROM from their website.. Should be no issue at all flashing it. Opengapps ARM64, 8.1 Nano is the Gapps i'd recommend.
Wipe in TWRP, Flash Firmware/ROM/Gapps/Magisk. Job done.

pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/

pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
Initial boot can take some time.
I'm at a loss why your phone hates OOS, but it might love Custom ROMs. Give it some thought.

pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes

pdalvares said:
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
Click to expand...
Click to collapse
Good news! :good:
You can see how resilient OP phones are. You can pretty much always get them back to a working condition. I can only guess but it sounds like you were right. Something was wrong with your Bootloader after the initial problems. Glad you got it sorted.