Related
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).
Dear all,
I stupidly bricked my Mi Note 2 by doing OTA with TWRP installed (at least I think that is the reason) - although I have done this once with success, but at the second time, the phone won't boot anymore.
- In TWRP, it says that the internal storage is encrypted and prompts me for code
- In TWRP the storage cannot be mounted (none of the partitions can be mounted)
- Tried to flash stock ROM or stock recovery in fastboot mode, seems like the internal storage cannot be accessed either
- With Mi Assistant, still no lock
It seems that the internal storage is totally corrupted...
What can I do without going to service (luckily I'm in China right now...)? Perhaps ADB sideload stock ROM would work?
Thanks!
Delete data partition an try reboot
Can't. Got some error message - see attached.
Sense like that the internal storage can't be found at all...
Also tried to side load DEV rom via adb, but got the attached error.
No clue how to proceed...
1. Format your data partition, and then reboot TWRP. This will decrypt your phone.
2.After entering TWRP, wipe all partition and then reboot TWRP
3.Copy your ROM file into your phone, and then flash ROM
Kris Chen said:
1. Format your data partition, and then reboot TWRP. This will decrypt your phone.
2.After entering TWRP, wipe all partition and then reboot TWRP
3.Copy your ROM file into your phone, and then flash ROM
Click to expand...
Click to collapse
Hi, I have assumed this as well, however didn't figure out a way to format the data partition. In my previous screenshot I showed the error ("unable to mount" or "no such device") when trying to delete the data partition.
Do you have a more detailed instruction?
Thanks!
Here you are.
See that "Format Data" ?
CrisperNeO said:
Hi, I have assumed this as well, however didn't figure out a way to format the data partition. In my previous screenshot I showed the error ("unable to mount" or "no such device") when trying to delete the data partition.
Do you have a more detailed instruction?
Thanks!
Click to expand...
Click to collapse
Kris Chen said:
Here you are.
See that "Format Data" ?
Click to expand...
Click to collapse
That's exactly what I have done... However: "unable to mound" or "no such device", it did not work
Which one of TWRP version do you use now ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:46 PM ----------
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
I use this version !
Kris Chen said:
Which one of TWRP version do you use now ?
---------- Post added at 09:51 PM ---------- Previous post was at 09:46 PM ----------
https://mega.nz/#!NBwyjKrK!XELWAAwehtKnXgXOge_y16kEP0Uqscv_5LVx-YqTzcc
I use this version !
Click to expand...
Click to collapse
3.0.2-X by BY~XM
Do you want to switch mostly updated one and try again?
Sometime it may come from outdated version of TWRP.
CrisperNeO said:
3.0.2-X by BY~XM
Click to expand...
Click to collapse
Kris Chen said:
Do you want to switch mostly updated one and try again?
Sometime it may come from outdated version of TWRP.
Click to expand...
Click to collapse
Actually I cannot flash any recovery now: FAILED (remote: flash write failure)
Download fastboot rom and flash it with miflash tool.
Can you enter fastboot mode ? If yes, then you can do (1)as dtsun said that; (2)flash the new version of TWRP(fastboot flash recovery xxxx.img ===> "XXXX.img" means the whole file name of TWRP image file), rebooting to TWRP again and then flash your recovery ROM.
dtosun said:
Download fastboot rom and flash it with miflash tool.
Click to expand...
Click to collapse
tried and also no luck, internal storage seems like not accessible
Kris Chen said:
Can you enter fastboot mode ? If yes, then you can do (1)as dtsun said that; (2)flash the new version of TWRP(fastboot flash recovery xxxx.img ===> "XXXX.img" means the whole file name of TWRP image file), rebooting to TWRP again and then flash your recovery ROM.
Click to expand...
Click to collapse
I can enter fastboot, but like said before, cannot flash any recovery
Sorry for that. It's indeed that you have bricked your phone
Now you need to find local mobile store to repair it, or prepare for another phone - Mi 6 ~
dtosun said:
Download fastboot rom and flash it with miflash tool.
Click to expand...
Click to collapse
Do this.
What error are you getting when trying to flash MIUI fastboot rom?
I have had this problem before on my redmi note 3, although the cause was from flashing TWRP not OTA.
I tried everything I could think of to try fix it, in the end flashing fastboot rom and clean all and lock with mi flash tool was the only way.
You'll need to use mi unlock to unlock the phone again but that is easy if you have done it before.
Did you use official way to unlock bootloader?
Reply to all above:
I unlocked the phone in the official way;
Miflash didn't work, because the internal storage is not accessible.
So lessons learned: never do OTA update if you have a custom recovery installed.
But:
Latest report:
Sent back to Xiaomi (luckily I'm in China right now) and Xiaomi was awesome, the engineer replaced the main board and it costed me nothing...
Hi .
I'm tired with Huawei's encryption. It's ok with Emui Rom but for AOSP (or other based on it) it's annoying :crying:
So use this guide for remove it definitively
WARNING !!
ALL YOUR DATA WILL BE DELETED ,SO BACKUP ALL YOUR PICTURES,VIDEO ETC ... TO YOUR PC OR IN EXT SDCARD
Download and copy in sdcard,not internal ,in attached files my :
- Huawei_remove_encyption_data
- Custom TWRP 3.2.3 recovery
rename my twrp_recovery.img.zip to twrp_recovery.img (remove .zip at the end, it's for upload this files into xda (size files))
or
in Android File Host
Download
HERE
PROGRESS :
Boot into fastboot, and Run
"fastboot -w", to wipe crypto
without rebooting flash included patched TWRP (fastboot flash recovery_ramdisk twrp_recovery.img)
Boot into TWRP, then Wipe internal storage, Wipe > Format Data then write "Yes"
Then flash my Huawei_remove_encyption_data script
reboot into TWRP recovery
Now you could continue to flash AOSP/LOS/CUSTOMS ROMs
And we're Done
Changelogs
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
Note:
If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps
Enjoy :good:
Creadits:
@AL_IRAQI for the inspiration of this guide
Updated 2018-10-24
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix
This is on a good path, thank you brother for your work ...:good:
I tried on my VTR-L29C432 (P10) and it worked!
Now I can flash files from my internal storage.
It works on EMUI and custom roms, even android 9. @micky387 Thank you so much for this tool bro
It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!
caniranges said:
It just isnt working for me.
it installs twrp, but it fails with the wiping
when i try to format data it says cannot mount storage
acant install any rom either.
also refuses to download latest update in emui recovery
man, does huawei suck!
Click to expand...
Click to collapse
Which device ,mate 9 ?
download again and try the new files. I have updated my twrp and script for more support
After flashing custom ROM, my data partition was encrypted.
Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.
@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.
Hi guys.
OP updated
* Update script with busybox mount program , more stable as previous script
* Update TWRP with Static Busybox ,last teamwin stuff and some other fix
Click to expand...
Click to collapse
soft-touch said:
After flashing custom ROM, my data partition was encrypted.
Click to expand...
Click to collapse
Try with new stuff.
swith to busybox for more device variant support
huhtan said:
Need some help here.
I have a mate 9 US variant. I was directed here from [Recovery][10-09-2018][3.2.3-0] TWRP for the Huawei Mate 9 (hi3660) (https://forum.xda-developers.com/mate-9/development/recovery-twrp-huawei-mate-9-hi3660-t3834796).
1) Successfully installed TWRP 3.2.3.
2) Backed up my /system partiton using TWRP to my ext SD card.
3) Boot into fastboot and run "fastboot -w". It shows
"
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.078s]
finished. total time: 0.078s
"
Not sure it is successful or not.
4) No rebooting and flash TWRP 3.2.3 again.
5) reboot to TWRP successfully, but not able to format data. It shows "failed to mount '/data'"
---------------------------------------------------------------------------------------------------------------------------------------------
Just found these two post have different TWRP files. The version numbers are the same, but file sizes are not. Is successful with the TWRP posted in this page.
Click to expand...
Click to collapse
Same, use new script and twrp in OP and report
sfoot13 said:
@micky387 Hi!
One Question, the fstab file was taken from Honor View 10 forum or you modded that? Because I the one that I'm using was taken from there.
First I did the wipes on Twrp but my internal storage wasn't recognized when the phone booted, so I had to wipe using stock recovery and it worked, now I can use my internal memory on Twrp.
Click to expand...
Click to collapse
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
Code:
/devices/platform/e7f00000.hifi_usb/* auto auto defaults voldmanaged=usbotg:auto
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?
micky387 said:
Hi,
first, fstab is from Mate 9. The only diff with View 10 is this line.
you can add it in my fstab if you want for your device
for the second question ,I have already noted that for me, just restart in recovery mode to fix this
With TWRP do you use ?
Click to expand...
Click to collapse
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery
sfoot13 said:
Thanks for the answer
On my last testing, I flashed your fstab without problems and wiped using stock.
To flash your zip, first I need to use this twrp https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 it boots even if the phone is encrypted but you need a sdcard, after the decrypt is done, I replace it with this twrp https://marijuana.ddo.jp/cm/recovery
Click to expand...
Click to collapse
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions
micky387 said:
Thanks do you have a xda link of the second TWRP ?
It's just to see if it use too a symlinks script for our partitions
Click to expand...
Click to collapse
No, I saw the link on this post https://forum.xda-developers.com/showpost.php?p=77262856&postcount=166 but I think @love_marijuana is the dev, because of the splash screen of the twrp :silly: talk to him bro.
OP Updated
2018-11-01
* Add new Android File Host Download link
* Add new MINADBD
* Fix selinux denial with stock kernel
Click to expand...
Click to collapse
We can use all TWRP feature now in Stock kernel.
Because Huawei has removed setenforce permission into kernel , the recovery script (setenforce 0) dont work , so "use" adb and other stuff was blocked by selinux
Fix all selinux denial by this commits
Return to stock emui/encryption
Hello!
I have a mate 9 c432 b370 with LineageOS 16 by micky (but due to stopped development i want to go back, the other treble roms just aren't working that well as rhis one, and I'm having a bit of bad battery life right now)
My question is:
"If you want to come back to stock EMUI/Encryption data ,reboot into erecovery and use "download last firmware and recovery" and follow the steps"
Is this the only way to go back to stock/encryption?
A wipe data or factory reset on emui stock recovery wouldn't work?
I'm asking because i have decrypted a while ago.
The last time i tried to use erecovery it said "no packages available" with an exclamation mark.
I have flashed stock system, kernel, ramdisk and recovery to boot back several times, but this time i have decrypted the internal storage...
Just need confirmation and/or possible solution to this. @micky387
Thanks in advance
hello @micky387
noob question. is it possible to work on a mate 8 debrand(AL10C00) atm im running openkirin omnirom 5.2,
would like to try other gsi roms. to check the most compatible rom..
your reply is very much appriciated
thank you
P10 Lite / WAS-LX1
Works on P10 Lite (WAS-LX1) with a fitting TWRP (I used Darkjokers 3.3.1). Used the zip over ADB sideload, so no external SD needed. Thanks for showing us da wae pal :good:
Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks
c|nder said:
Hey dudes will this work on mate 8 Oreo ? If soon could you mod it for it ? Thanks
Click to expand...
Click to collapse
If you check by the dates, it was all discussed at the time of EMUI 8/Oreo.
Earlier with Nougat, there was no such problem (TWRP was able to access internal storage).
To the other side, with current EMUI 9.1, Vendor is read-only and proposed modifications will not work
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.
Unlocked Mediapad M3 wifi 713, damaged file system showing 0 storage, managed to get TWRP installed via fastboot, but TWRP is unable to change/repair any partition. I've tried to use "fastboot format:ext4 userdata" but I get the "remote: command not allowed" error.
Is there some way to use fastboot commands? Or some terminal command from TWRP?
thanks, jf
Bro have you unlocked the bootloader and it would be very helpfull to know how you corrupted the data partion,it could be solved maybe if you enter the second recovery (erecovery) and click on download lastest firmware install or so , then after its done with the installition it will probably not boot click power and volume down wait, do it some times until you get to the bootloader and unlock it, after factory reset it should boot but first explain a little more about your issue we dont want to srew your device up
qlue4e said:
Bro have you unlocked the bootloader and it would be very helpfull to know how you corrupted the data partion,it could be solved maybe if you enter the second recovery (erecovery) and click on download lastest firmware install or so , then after its done with the installition it will probably not boot click power and volume down wait, do it some times until you get to the bootloader and unlock it, after factory reset it should boot but first explain a little more about your issue we dont want to srew your device up
Click to expand...
Click to collapse
Not sure how things got corrupted, had installed Linage on it, but was not able to download files from any installed program. Reinstalled Linage and it blew up. Erecovery fails to download anything, don't know why. I followed the instructions here https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 to format all partitions, and still TWRP only sees 0 space, can't do anything with it..
In short - can't see how anything could screw it up more!
which version of twrp is currently installed and normally for format matters only data partition is used, have you formated the system partition too,
maybe we can try to force install the update zip / you were on nougat then lineage oreo and then in the current state right?
qlue4e said:
which version of twrp is currently installed and normally for format matters only data partition is used, have you formated the system partition too,
maybe we can try to force install the update zip / you were on nougat then lineage oreo and then in the current state right?
Click to expand...
Click to collapse
TWRP is 3.0.3-0 It is failing to mount /data (Invalid argument) nor can it mount any other partition.
Yes, was on stock nougat, then Linage oreo, then reinstalled Linage and got current state.
When I try to install zip from PC, it appears to be successful - but apparently is not.
can you intall the twrp 3.3.1-0 which is at the lineage oreo thread and then try to install los zip https://forum.xda-developers.com/mediapad-m3/development/rom-t4085115
qlue4e said:
can you intall the twrp 3.3.1-0 which is at the lineage oreo thread and then try to install los zip https://forum.xda-developers.com/mediapad-m3/development/rom-t4085115
Click to expand...
Click to collapse
The good news is... I did that, got in unbricked, installed ROM, GAPPS... installed apps - and I'm back to the same problem I had before. I can install apps, I can download from Google Drive, but programs such as Gmail cannot download attachments. even though permission to access storage is turned on. This is all to internal storage - no external chip at this time.
thoughts?
thanks, jf
For gmail you must install the micro version of the gapps not the pico one after that it should work
qlue4e said:
For gmail you must install the micro version of the gapps not the pico one after that it should work
Click to expand...
Click to collapse
It's not working for Aquamail either. Also, can't download from the web, using Brave browser.
friedsonjm said:
The good news is... I did that, got in unbricked, installed ROM, GAPPS... installed apps - and I'm back to the same problem I had before. I can install apps, I can download from Google Drive, but programs such as Gmail cannot download attachments. even though permission to access storage is turned on. This is all to internal storage - no external chip at this time.
thoughts?
thanks, jf
Click to expand...
Click to collapse
I'm having the same issue basically storage is off limits to my apps.
The developer of the Linux 15 ROM is aware of the issue, it's on the list to be fixed.