Database Users

[RECOVERY] TWRP Recovery [v2.8.6.0]

CM dropped CWM support in CM-12.0 in favor of CM's own recovery, which has different bugs and is generally very simplified recovery (does only wiping/flashing images). So I decided to go on with a different recovery from now on.
This recovery is LVM compatible.
Requirements
U8800 with 404020 baseband (If you ever installed 2.3 stock firmware, you're ok!)
Strongly recommended: Unlocked pink screen
How to install
Method 1 (by recovery)
Download the zip from downloads below
Save it to your phone (internal or external SD)
Reboot to your current recovery
Install the zip
Reboot recovery
Method 2 (by pink screen)
Download the zip from downloads below
Save it to your PC
Reboot your phone in pink screen mode
Extract recovery.img from the zip
Save the zip on your phone's image/ directory (where boot.img and other files are located)
Reboot to recovery
Downloads
LegacyHuawei
twrp-recovery-v2840.zip
twrp-recovery-lvm-v2830.zip
Things to know
When backupping, tick "cust". This holds boot.img and other files which are grucial for restoring a full backup.

Thanks for the great job Blefish. It works flawlessly

Uploaded TWRP recovery v2.8.4.0.
Changes:
* Support for offmode charging
* LVM/NON-LVM compatible. You can use this recovery for NON-LVM ROMs.

Hi Blefish
Thanks for the updated recovery.
I had a question, if we were to flash say your CM11 rom, I guess we need to uninstall LVM as you had mentioned before or just flash directly using this recovery
Great job again

mohammad.nomaan said:
Hi Blefish
Thanks for the updated recovery.
I had a question, if we were to flash say your CM11 rom, do we need to uninstall LVM or just flash directly using this recovery
Great job again
Click to expand...
Click to collapse
You can use this recovery, however LVM needs to be uninstalled. The new BlePart-LVM-11 script makes it easier for you . However, I still want to do one mor CM11 release, with LVM support. Theoretically the new CM12 release is LVM/NON-LVM compatible too but it has problems on installing the ROM (the space on /system is not enough).

Blefish said:
You can use this recovery, however LVM needs to be uninstalled. The new BlePart-LVM-11 script makes it easier for you . However, I still want to do one mor CM11 release, with LVM support. Theoretically the new CM12 release is LVM/NON-LVM compatible too but it has problems on installing the ROM (the space on /system is not enough).
Click to expand...
Click to collapse
Thanks Blefish for the update.
Just installed the new recovery, Off-Mode charging is working fine.
I like the new white charging animation

Blefish, thanks a lot!!
Perhaps, in the next update, you could enable the LED to show the charging progress , if possible..

tsioy said:
Blefish, thanks a lot!!
Perhaps, in the next update, you could enable the LED to show the charging progress , if possible..
Click to expand...
Click to collapse
Yes, I am planning that. The thing was that in CM's healthd (charger is using that) it is supported, but in Omni's healthd it's not supported. I will probably implement it myself if someone has not done it yet.

VERY NICE, thanks!

New version uploaded, enjoy!
Next releases will be uploaded at LegacyHuawei
This version adds the RPC side charging (more stable) and it also enables charging led indicators.

I installed 2850 and now I can't access the sdcard (in TWRP). It works fine if I boot it normally, so I'm guessing it's not a problem with the sd card?
I tried the option to mount the sdcard, but when I try it, TWRP doesn't tick that option. All the others work, though (cust, system, data, ...)
Any suggestions?

phone wont boot into twrp now, it just shows the twrp splash screen then restarts

New version uploaded!
No changes have been done on my side, other than updating to android-5.1 codebase where this recovery is compiled from.

@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0

Webtag said:
@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0
Click to expand...
Click to collapse
Try replugging the SD card while in recovery. Sideload was working well for me, but it does require updated ADB. Does it tell you an error message on the screen?

Blefish said:
Try replugging the SD card while in recovery. Sideload was working well for me, but it does require updated ADB. Does it tell you an error message on the screen?
Click to expand...
Click to collapse
Replugging the SD does nothing, and I only get error message in Adb sideload mode after about 5-10 min. This is the same problem that @rexnanet had with version 2.8.4.0, but my sd doesn't mount after inserting it when in TWRP

Webtag said:
@Blefish On the U8800 Pro version it doesn't mount my external SD card. This has been a problem on many recoveries, but on twrp 2.8.1.0 by @Lihis it works. Can you find a way to make twrp 2.8.6.0 detect the SD Card? And BTW ADB Sideload does not work either, but works on 2.8.1.0
Click to expand...
Click to collapse
I've did some dirty edits in the recovery ramdisk and the SD Card can now be read and cm12.1 can be installed: http://www.mediafire.com/download/vzzc64h9zoh60h4/image-new.img
Hopefully Blefish will do a proper fix soon, though

CrysisLTU said:
I've did some dirty edits in the recovery ramdisk and the SD Card can now be read and cm12.1 can be installed: http://www.mediafire.com/download/vzzc64h9zoh60h4/image-new.img
Hopefully Blefish will do a proper fix soon, though
Click to expand...
Click to collapse
Hello CrysisLTU this imagen-new and Blepart-LVM, can used in U8800pro o U8800-51?

Links are gone. Pls someone upload the latest file to somewhere.

[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).

Stuck in recovery with no image to flash

First of all, I read this thread, but no luck.
Situation:
* I unlocked bootloader, installed TWRP 3.1.1-1 and flashed Freedom OS, succeding.
* Then I decided to try the Oreo open beta, but had a problem (error 7 flashing it), so I wanted to get back to Freedom OS
* After flashing Freedom OS again (with success) I rebooted but I was stuck at boot logo.
* I decided to flash again OOS 4.5.14, but I misclicked something and I found my self in TWRP with no ROM to flash on SDcard (I think I have checked also internal storage while wiping).
* PANIC!
So, 3 questions:
1) given that I want to stay encrypted (if still possible at this point) should I decrypt data or not at TWRP boot?
2) if I chose decrypt with the unlock code (read that I did) I have to go with decrypt or formatting is enough to keep crypt?
3) MORE IMPORTANT: how do I get a ROM to flash into the phone. Reeboting in TWRP sometimes I see the internal storage, but when I drop a firmware in it I get the transfer windows stuck at 0% and it disappear after a few seconds.
Thanks in advance to who will help me!

this might help - https://forum.xda-developers.com/showthread.php?t=2318497

chris4500uk said:
this might help - https://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
Thanks for the suggestion and... it's a beginning.
The problem is that if I sideload a small file like Magisk upload is ok, even if (obviously) it can't install.
When it comes to Oxygen OS I get I cannot read file error.
I doubleclicked the file and it opens in PC, so it isn't corrupted.

I'd be tempted to try another USB cable and maybe another computer if you have one. Failing that, if it's a problem with TWRP your last resort may be a complete low level flash. A good guide is here - https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Edit: I should say be careful if you do have connectivity problems, as flashing using unbrick tools while your connection is bad would not be a good idea at all since it could make things even worse (maybe even hard brick)

I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.

Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.

Zocker1304 said:
Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.
Click to expand...
Click to collapse
No; i couldn't. But I solved simply by using "Format data".
SOLVED

UncleDan said:
I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.
Click to expand...
Click to collapse
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.

jhs39 said:
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.
Click to expand...
Click to collapse
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]

UncleDan said:
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]
Click to expand...
Click to collapse
There are two with download links included in the instructions thread for flashing Oreo. I recommend the Blu Spark TWRP over the Chinese TWRP. It will be updated more often.

A2017G V1.2 0B09 - Cannot install ROMs without Gapps

My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.

xectis said:
My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
Click to expand...
Click to collapse
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?

Choose an username... said:
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Click to expand...
Click to collapse
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.

xectis said:
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
Click to expand...
Click to collapse
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center

Choose an username... said:
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Click to expand...
Click to collapse
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.

xectis said:
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
Click to expand...
Click to collapse
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547

xectis said:
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Click to expand...
Click to collapse
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev

Choose an username... said:
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Click to expand...
Click to collapse
I see. All clear now. You've been most helpful, thank you again.

[/QUOTE]
xectis said:
I see. All clear now. You've been most helpful, thank you again.
Click to expand...
Click to collapse
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.

Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.[/QUOTE]
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.

Choose an username... said:
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Click to expand...
Click to collapse
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.[/QUOTE]
I did everything you suggested but I still get the 'To start Android use your password'. No wories I'll go back to my old ROM. Thanks anyway.
***Update*** I made a mistake in formatting SYSTEM instead of DATA. Now it works fine installing the ROM's I mentioned. You are a champ!
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).

xectis said:
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways

Choose an username... said:
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Click to expand...
Click to collapse
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.

xectis said:
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
Click to expand...
Click to collapse
Use the zip anyways

Choose an username... said:
Use the zip anyways
Click to expand...
Click to collapse
Ok I'll give it a try.

Damaged File System - Need Fastboot Help

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.