[H918] Stock DeOdex Flashable ROM. - LG V20 Guides, News, & Discussion

[H918] Stock DeOdex Flashable ROM. - LG V20 Guides, News, & Discussion

Hello! Here is a flashable ROM for the LG v20! This is STOCK, rooted, and deODEXd
(This ROM here is Stock ODEXd, and rooted for those who want that instead.)
This ROM can be used to restore your phone in the event of bootloops, crashing, accidentally wiping /system, broke your kernel, deleted a system app, or whatever... We finally have a way to fix our phone OS! So I hope this turns on the spark on you modders out there.
This zip will NOT wipe your data. It will wipe /system. It is not necessary (currently) to wipe /data for this, since we are all on the same exact base.
This ROM comes pre-rooted, comes with the insecure kernel (no mods done to kernel, just disabled the security bit). The kernel comes with no-verity, and no force encrypt. So if your /data was not already encrypted, you can flash without worry of encryption. If you do not wipe /data, it is highly recommended to at least wipe /cache and Dalvik cache.
Major thanks to @JesusFreke for smali+baksmali, also for debugging it to work with Nougat
Major thanks to @SuperR. for the kitchen )
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for mentioning someone should do it. Also, he supplied the stock System.img. /RealMVP
Also, a HUGE thanks to @nyfl2004. He very kindly fixed my updater-script, and repacked the ROM.
Below, you will find a download link, and instructions which contain ONLY the system.img. This IMG is flashable in TWRP. It is 100% stock, and it will simply convert (overwrite) your existing /system partition to a deODEXd partition.
Open WinRAR and check that the following items are 100% to this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract the RAR archive, and then right click the system_new.img --> Properties. Ensure that the SIZE field is identical to the SIZE from the .RAR file in the picture here, and in your file as well. Copy the file to your phone.
Please make sure you are on TWRP RC8 as provided by @jcadduono
do "adb reboot recovery" and Install > Install image > then find the .img file and flash. There is NO need to format data OR system. Simply flash and reboot. Might need to reboot again if you get stuck on the TMobile splash screen at first. ROM is already deodexed and ZipAligned. Also, the default Debloat (as provided by the kitchen) has been applied.
Basically flash this IMG over your current ROM to deODEX it. ↓
https://mega.nz/#!WANykaDb!mcx6Wm5NeNOw4aTeHyn5jcr2IQsywuHWSHegnZTqjZY ←LINK
IF YOU CAN BOOT TO TWRP, YOU CAN FIX YOUR PHONE! Instructions below
These instructions are only for people who are getting bootloops and have no way of using their phone. If you can get to TWRP, you can get your phone back up and running.
Almost always it's a corrupt /system, or perhaps you were/are encrypted.
Verify which version of TWRP you are on? If not on RC8, please flash that version.
Before starting, in TWRP, go to Settings --> and ensure that the box for "Use rm-rf...." is UNCHECKED
For the encryption, the only way to get around that is to Format Data. This will erase all your apps, and files (pictures etc). To do this (it will wipe all your things, and this is only to decrypt your data, so if you don't need to do this, don't) , go to TWRP --> Wipe --> Format Data --> follow on-screen instructions to erase your data.
Then do Wipe --> and swipe to do the Factory Reset. Now, go back to Wipe --> Advanced Wipe. Checkmark Dalvik, System, Data, Internal Storage, and Cache, and wipe those items (swipe to wipe).
Now, in TWRP, go to Mount, and make sure that System, Data, and Cache are all CHECKED. "Mount system as read-only" is UNCHECKED. Press the Back button. Go back into Mount and ensure System is still checked, and go back to the TWRP main menu again.
Now go to Advanced --> File Manager. Ensure that the system folder is empty. Press the back button. Inside of Advanced, click Fix Contents, and swipe.
Go back to the Wipe --> Advanced Wipe, and redo the format of all the aforementioned directories.
Flash the Stock ROM (deODEXd would be better IMO, but whichever). Just to be safe, also flash the no-verity.zip from the recowvery thread.
Then again, in TWRP, go to Mount, and make sure that System, Data, and Cache are all CHECKED. "Mount system as read-only" is UNCHECKED. Press the Back button. Go back into Mount and ensure System is still checked, and go back to the TWRP main menu again.
Now go to Advanced --> File Manager. Ensure that the system folder is NOT empty.
Back out and hit Reboot --> Boot to system.
A lot of these operations are redundant, but if you can still access TWRP, you should be able to fix the issue. The only way that you will have problems, is if you did a DD command and wrote something to a wrong path.
Others that can no longer access TWRP do have a still unfixable problem... But you should be good to go.
After doing all the steps, you should be able to boot.
It will first take you to the LG logo for a few seconds, and then it will reboot itself. You will see the BOOTLOADER NOT SECURE thing, and then the LG logo again. After a few seconds the TMO splashscreen will appear and do its chime sound. Give it a good 10 minutes, at which point it should take you to the Android OS page where you will have a progress bar. Once that progress bar finishes, your phone will be live. Please let me know what happens.
Debloat (Removed). Nothing yet

Just note that if you add Google Assistant via buildprop you can't access smart world. Not that I care much but just a note.. It will not recognize your device as an LG device so it will not open.

Looking forward to this. Thank you

if the build prop is changed, does that mean that Google Daydream will work? I know the screen is not ideal, but I do kinda miss my Gear VR (former s7 edge owner).

cmart4 said:
if the build prop is changed, does that mean that Google Daydream will work? I know the screen is not ideal, but I do kinda miss my Gear VR (former s7 edge owner).
Click to expand...
Click to collapse
I'm not sure. I was only going to do that so that the Pixel launcher would work. But @Swizzle82 has informed us that this would break Smart (LG Smart). Might just leave the build.prop alone, and let the user decide to change. Either way, I have yet to make a package that will flash. Then I have to see if it boots lol.

System.img link posted in OP! Overwrites current /system, no need to format. Enjoy!

Tilde88 said:
System.img link posted in OP! Overwrites current /system, no need to format. Enjoy!
Click to expand...
Click to collapse
Thanks for your work much appreciated!
Sent from my Pixel XL using XDA-Developers mobile app

Thank you so much for your work.
Could you please list the apps you removed.

netgar said:
Thank you so much for your work.
Could you please list the apps you removed.
Click to expand...
Click to collapse
Added to OP!
I'll remove more unnecessary stuff tomorrow. I'm done for today. Pokemon Moon time for me!

I installed this and my phone reboots to TWRP as a matter of fact it does this with any system image I install. Any suggestions to help with this I have looked all over and I can't seem to find anything. I would love to go back to stock and start over but that seems difficult in itself.

crazyc78 said:
I installed this and my phone reboots to TWRP as a matter of fact it does this with any system image I install. Any suggestions to help with this I have looked all over and I can't seem to find anything. I would love to go back to stock and start over but that seems difficult in itself.
Click to expand...
Click to collapse
Have you flashed no verity (or SuperSU)? If not, this can happen. Something to do with the encryption. If you cant get anything to work as you say, I would flash the stock .ZIP that is in the recowvery thread, and ensure to fully unencrypt. You will lose any data in the system.
Also what TWRP version are you on?

Tilde88 said:
Have you flashed no verity (or SuperSU)? If not, this can happen. Something to do with the encryption. If you cant get anything to work as you say, I would flash the stock .ZIP that is in the recowvery thread, and ensure to fully unencrypt. You will lose any data in the system.
Also what TWRP version are you on?
Click to expand...
Click to collapse
I was successfully able to boot into the system!! I am going to set up my device and and go from there!! Crossing fingers I don't have anymore issues.

Thanks

Was looking through your debloat list and can't seem to find a lot of those in my system. You had att smart wifi in your Tmo system?

Swizzle82 said:
Was looking through your debloat list and can't seem to find a lot of those in my system. You had att smart wifi in your Tmo system?
Click to expand...
Click to collapse
No. Like i said, this is the default debloat list included in the kitchen. It bundles in known things throughout android devices. Custom debloat is next. But i work today, so idk if ill do anything.

Is there an easy way to get permissive, I flashed your rom which saved my butt but now I don't have permissive. I don't want to mess up the system or have to flash dirty recowvery again. Thanks in advance.

crazyc78 said:
Is there an easy way to get permissive, I flashed your rom which saved my butt but now I don't have permissive. I don't want to mess up the system or have to flash dirty recowvery again. Thanks in advance.
Click to expand...
Click to collapse
Look for SELinuxModeChanger
---------- Post added at 06:39 PM ---------- Previous post was at 06:27 PM ----------
Is this a backup or a rom to replace what we have after rooting?

vibrantliker said:
Look for SELinuxModeChanger
Click to expand...
Click to collapse
Google banned it from the Play store

crazyc78 said:
Google banned it from the Play store
Click to expand...
Click to collapse
Here..

vibrantliker said:
Here..
Click to expand...
Click to collapse
Thanks!!
---------- Post added at 01:03 AM ---------- Previous post was at 12:47 AM ----------
It's not working it says it can't get root access. I am rooted I checked the settings in SUPERSU and it granted the app access. Any other ideas? I read something that it hasn't worked since lollipop and it was difficult to work on marshmallow. Ugh I really don't want to root again. I just want Viper to work.

Related

[ROM/MOD]-8/12/12- AT&T Pure Stock 3.20.502.52 Rooted/Deodexed

Frist!!!!!!!

Woah a sense rom from you is something new
Sent from my Inspire 4G using xda app-developers app

Download now in the OP.
Enjoy!

If I want overclock I just need to flash an OCed kernel?
Thanks.

surtrafl said:
If I want overclock I just need to flash an OCed kernel?
Thanks.
Click to expand...
Click to collapse
I guess although I couldn't even tell you which OC kernel would even work. Maybe Lord's Sense kernel.
Sent from A VAN DOWN BY THE RIVER!

flappjaxxx said:
I guess although I couldn't even tell you which OC kernel would even work. Maybe Lord's Sense kernel.
Sent from A VAN DOWN BY THE RIVER!
Click to expand...
Click to collapse
Lordmod works good, some of the BDAce kernels also work pretty good. Just try them out see which you like best.
Sent from my A500 using Tapatalk 2

I followed all the steps:
1. Back Up your Stuff.
2. Wipe Data/ Factory Reset
3. Wipe Cache and Dalvik Cache
4. Flash .zip in recovery
5. Reboot
After the reboot, the phone just hang on HTC logo . I left it for more than 45 minutes and nothing happen. This rom does not work for me.

benkud said:
I followed all the steps:
1. Back Up your Stuff.
2. Wipe Data/ Factory Reset
3. Wipe Cache and Dalvik Cache
4. Flash .zip in recovery
5. Reboot
After the reboot, the phone just hang on HTC logo . I left it for more than 45 minutes and nothing happen. This rom does not work for me.
Click to expand...
Click to collapse
If you are using 4ext recovery, try this. (If using cwm, I don't know the process because I have never used it, but the ability should be there.)
Instead of doing steps 2 & 3, try this: in the same wipe menu, down towards the bottom, you will see "format all partitions except sd card". Hit that, then flash the zip and reboot. This works for me.
Edit: I usually do your steps 2 & 3 before the format partitions anyway, but I don't think it matters. Just makes me feel better.

Galaen said:
If you are using 4ext recovery, try this. (If using cwm, I don't know the process because I have never used it, but the ability should be there.)
Instead of doing steps 2 & 3, try this: in the same wipe menu, down towards the bottom, you will see "format all partitions except sd card". Hit that, then flash the zip and reboot. This works for me.
Edit: I usually do your steps 2 & 3 before the format partitions anyway, but I don't think it matters. Just makes me feel better.
Click to expand...
Click to collapse
Thanks for you reply. I used clockworkmod. I finally fixed the phone. But I can't explain how it happens. My phone was rooted before I tried the rom. After it hangged on HTC logo, I decided to flash it with the original AT&T rom downloaded from HTC website. First, I put PD98IMG on the root of my sdcard, and then reboot the phone (holding Vol - and Power button). The phone checked the file image to do the necessary updates. From that point the phone power on properly. I realized that the version had changed from 2.3.3 to 2.2. Then I flashed it by using the original and UNTOUCHED rom downloaded from HTC website and BINGO:laugh:. Then rom updated to 2.3.5. My phone is still unlocked and I using it with Straith Talk.
What happens? I don't know, and I can't explain it. I'm too BRAND NEW to this android world.
Thanks.

Okay i think i might give this a go, couple of questions being as this is my first go around changing the Rom.(been awhile since the WinMo days) I am rooted with the Advance hack Kit , I just used MyBackUpPro and saved it to my Sd, now after i install this Rom , can i use my back up of saved apps etc to re-install everything ?

A couple weeks ago I was able of flashing this stock rom without problems, and I found that it's the most stable and quick of all the roms I've tried so far.
But now I changed my rom to cm7, and then to other ics, and then the radio and stuff. But I've the following problem:
I can flash pretty much any rom, say RDH, some ICS, etc. But when I try to flash this stock rom from recovery, after the reboot, the phone is stuck on the white screen. I don't know whtat could be the issue. I've tried different roms and any other works on my htc inspire, but this stock rom doesn't!!
Everytime I try this one phone is stuck on the white screen. What can be the problem? Maybe that I'm on ext4? maybe that my cmw version is the touch one? Maybe the full wipe script I'm using it's not the right one? Then, how can I go back to ext3, use the right cwm and the right wipe script?
PLEASE HEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEP!!!!!! I JUST WANT TO USE THIS STOCK ROM ONCE AGAIN

dionieins said:
A couple weeks ago I was able of flashing this stock rom without problems, and I found that it's the most stable and quick of all the roms I've tried so far.
But now I changed my rom to cm7, and then to other ics, and then the radio and stuff. But I've the following problem:
I can flash pretty much any rom, say RDH, some ICS, etc. But when I try to flash this stock rom from recovery, after the reboot, the phone is stuck on the white screen. I don't know whtat could be the issue. I've tried different roms and any other works on my htc inspire, but this stock rom doesn't!!
Everytime I try this one phone is stuck on the white screen. What can be the problem? Maybe that I'm on ext4? maybe that my cmw version is the touch one? Maybe the full wipe script I'm using it's not the right one? Then, how can I go back to ext3, use the right cwm and the right wipe script?
PLEASE HEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEP!!!!!! I JUST WANT TO USE THIS STOCK ROM ONCE AGAIN
Click to expand...
Click to collapse
Reboot into recovery and find where you can format your partitions as ext3. I'm not sure where it is in CWM since I've been using 4ext for a while, but it's there somewhere. Most wipe scripts will format your partitions to ext4, so don't use the wipe script. After you have formatted all the partitions to ext3, see if there's a way to display partition info, so you can double check that they formatted correctly.

Bzow said:
Reboot into recovery and find where you can format your partitions as ext3. I'm not sure where it is in CWM since I've been using 4ext for a while, but it's there somewhere. Most wipe scripts will format your partitions to ext4, so don't use the wipe script. After you have formatted all the partitions to ext3, see if there's a way to display partition info, so you can double check that they formatted correctly.
Click to expand...
Click to collapse
alright, I just found the menu that allow me to "format system / wipe" as ext3. I did it and then I check the info of the partition and it says that the system and data are as ext3 partitions.
Then I flashed the stock rom and now I'm waiting in the white screen with the htc logo... crossed fingers
---------- Post added at 11:04 PM ---------- Previous post was at 10:50 PM ----------
dionieins said:
alright, I just found the menu that allow me to "format system / wipe" as ext3. I did it and then I check the info of the partition and it says that the system and data are as ext3 partitions.
Then I flashed the stock rom and now I'm waiting in the white screen with the htc logo... crossed fingers
Click to expand...
Click to collapse
ok, it didn't work so I'm repeating all the same steps again:
1. Back Up your Stuff.
2. Wipe Data/ Factory Reset
3. Wipe Cache and Dalvik Cache
4. Flash .zip in recovery
5. Reboot
6. Enjoy!
PD: I just want to let you know that the system, data and cache are now as ext3 and that I'm using 4ext Recovery Touch
EDIT: IS STILL IN THE WHITE SCREEN SO I'M JUST GOING TO TURN IT OFF UNTIL I HEAR ANOTHER SUGGESTION

dionieins said:
alright, I just found the menu that allow me to "format system / wipe" as ext3. I did it and then I check the info of the partition and it says that the system and data are as ext3 partitions.
Then I flashed the stock rom and now I'm waiting in the white screen with the htc logo... crossed fingers
---------- Post added at 11:04 PM ---------- Previous post was at 10:50 PM ----------
ok, it didn't work so I'm repeating all the same steps again:
1. Back Up your Stuff.
2. Wipe Data/ Factory Reset
3. Wipe Cache and Dalvik Cache
4. Flash .zip in recovery
5. Reboot
6. Enjoy!
PD: I just want to let you know that the system, data and cache are now as ext3 and that I'm using 4ext Recovery Touch
EDIT: IS STILL IN THE WHITE SCREEN SO I'M JUST GOING TO TURN IT OFF UNTIL I HEAR ANOTHER SUGGESTION
Click to expand...
Click to collapse
It's possible that you got a bad download. Try downloading it again.

Bzow said:
It's possible that you got a bad download. Try downloading it again.
Click to expand...
Click to collapse
I just check the md5 and it's alright
pd. maybe if I try installing it as a pd98img instead a flashable zip ?

dionieins said:
I just check the md5 and it's alright
pd. maybe if I try installing it as a pd98img instead a flashable zip ?
Click to expand...
Click to collapse
Try:
After wiping dalvik, format all partitions except sd card. The rest of the steps are fine.
I had the same problem as you, but thought it was due to a bad download. Haven't tested it since.
Sent from a dream.

Teichopsia said:
Try:
After wiping dalvik, format all partitions except sd card. The rest of the steps are fine.
I had the same problem as you, but thought it was due to a bad download. Haven't tested it since.
Sent from a dream.
Click to expand...
Click to collapse
alright I tried what you said but still.... is stuck on the white screen with the htc logo on it...
What if we try to go back, to factory settings, factory state, whatever is call and from there I try? but the question would be,.. how can I go back that far?
I just want to flash this rom, and the thing is that I can flash other roms but not this one.... HEEEEEEEEP!1

Did you check the md5 checksum? Does it match? If so and it doesn't work, don't know what else to suggest.
Sent from a dream.

Teichopsia said:
Did you check the md5 checksum? Does it match? If so and it doesn't work, don't know what else to suggest.
Sent from a dream.
Click to expand...
Click to collapse
yes they did match. I just don't know how to get out of this. Never happen to me before with this phone. Don't know what could be wrong. Weird.

[ROM][7/25] Stock Android 4.3 for Nexus 7 (3G) / No Root / Flashable ZIP

This is a flashable ZIP, containing the latest kernel and build of Android 4.3 by Google. It is made for the Google Nexus 7 3G, and is flashable through TWRP. I did not test it since I don't have a 3G model of the Nexus 7.
Download link: https://mega.co.nz/#!xskHxaRb!ZP3kYCk66VinJc70TswVBSAv8yZ3QoKKgUCtzVe66lY
Odexed, and no superuser management tool. Chainfire released an experimental version supporting Android 4.3 on his Google+. so I'll add that to the OP later.
Enjoy!

Anybody tested?
Also, will there be radio and bootlosder in flashable form?

Fatal1ty_18_RUS said:
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Click to expand...
Click to collapse
From what i can see, there is no bootloader and radio in it, so anyone has to flash it by himself.
EDIT: The ZIP works fine, i just flashed bootloader and radio through fastboot prior to installing it over TWRP. Haven't tested any root zips, yet.

i got 4.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
biggoldring said:
Click to expand...
Click to collapse
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?

stadicon said:
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
Click to expand...
Click to collapse
you mean you flash the zip in stock recovery??

Gabrieltan said:
you mean you flash the zip in stock recovery??
Click to expand...
Click to collapse
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..

stadicon said:
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
Click to expand...
Click to collapse
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?

Gabrieltan said:
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Click to expand...
Click to collapse
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.

stadicon said:
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
Click to expand...
Click to collapse
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx

Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta

zard said:
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?

Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta

zard said:
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
that is what i did just now... and it cause i lost my root for tb.. now trying clear data, forget root and rerun the application

Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
Yeah, i forgot to say that i full wiped first, of course (not sure if it's mandatory, though). Bootloader and radio may not be so important, as after i flashed them 4.2.2 booted successfully (before installing 4.3) which might be a sign that not much of a difference was made.
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.

stadicon said:
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
Click to expand...
Click to collapse
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??

There should be no way to lose your backups unless you have chosen purposely to do so. Check that your Titanium Backups folder is still there in SDCARD.
If I weren't on vacation using only Chromebook I'd have upped this this morning with root; I managed via ARM Chromebook dev mode with adb and fastboot to backup data from my N4 and N7 3G and then install stock, flash recovery and make root, followed by restoring my titanium data. Both devices were as they were in 4.2.2 but in 4.3 within the hour.
Furthermore I had the ability to flash Franco r170 on the N4

Gabrieltan said:
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
Click to expand...
Click to collapse
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
BTW, i think the battery drain issue is now fixed.

stadicon said:
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
Click to expand...
Click to collapse
i also dont know why.. but i can backup... ya, only can use root explorer to delete, i tried few apps, all cant delete..

gapps hosted here works: http://forum.xda-developers.com/showthread.php?t=2248654

[OFFICIAL]DualBootPatcher[RN4/mido]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DUAL BOOT PATCHER
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_data-slot.zip file will be created. For example,
AospExtended-4.2-mido.zip
After patching would create a new
AospExtended-4.2-mido_data-slot.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher.apk from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually you can do it using the app.
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
YouTube Tutorial:https://youtu.be/T44ifBaHAWs
Note:
You must always select 'Data-slots' as installation location for secondary roms on Redmi Note 4x. You can also use 'Extsd-slots' if you want to install on external storage.
If your using MIUI (Multirom, Xiaomi.eu, etc), you may need to enable documents app by going to Settings> Installed Apps before trying to patch any file in DBP.
Don't use official MIUI as primary rom.
If you're not able to boot, your phone vibrates 5 times and then reboot to TWRP after installing secondary rom, it might be that your data partition is encrypted. To fix this follow the instructions below:First backup all your data including Internal Storage, then boot to TWRP>WIPE>FOMATE DATA then type 'yes' and tap enter. Now reboot and retry DBP.
App sharing not working.
Source/Credits:
https://dbp.noobdev.io
DOWNLOADS
~ Hit Thanks:good: button below if I helped you ~

Thankyou for starting this useful thread.

drmuruga said:
Thankyou for starting this useful thread.
Click to expand...
Click to collapse
Welcome

i flash two rom,when into the primary rom, the system show the password was wrong

PrayerInc said:
i flash two rom,when into the primary rom, the system show the password was wrong
Click to expand...
Click to collapse
Boot to twrp and open filemanger, go to data>system and remove .key file(what ever you have used ex: pattern.key, password.key , etc)
One should not use any type of security lock on pimary rom.

its not working for me

varunangirash said:
its not working for me
Click to expand...
Click to collapse
What's not working?

What at "Slot ID"?

bad_request said:
Boot to twrp and open filemanger, go to data>system and remove .key file(what ever you have used ex: pattern.key, password.key , etc)
One should not use any type of security lock on pimary rom.
Click to expand...
Click to collapse
so i cant set fingerprint and password in primary rom, what about the secondray rom and others??? if they set fingerprint and password,what will happen??
why other type phone havent this problem???

Jack'O said:
What at "Slot ID"?
Click to expand...
Click to collapse
Slot I'd is just a name. Like you are using two ROMs on data slots , you can give different names to each slots.
ex: rr, aosp, miui, lineage, etc

PrayerInc said:
so i cant set fingerprint and password in primary rom, what about the secondray rom and others??? if they set fingerprint and password,what will happen??
why other type phone havent this problem???
Click to expand...
Click to collapse
Its a bug, you can try and test if it's working or not on secondary rom, as I don't use security locks I can't tell if it's working or not .

Not working
Its giving error when i am flashing zip in TWRP:crying:
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
I installed on data slot but now its not booting its vibrate for 3 times and then reboot. please help.. then i have to restore my data partition to boot again into primary rom

varunangirash said:
Its giving error when i am flashing zip in TWRP:crying:
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
I installed on data slot but now its not booting its vibrate for 3 times and then reboot. please help.. then i have to restore my data partition to boot again into primary rom
Click to expand...
Click to collapse
How much space has left on your device?

Sorry I have not been keeping pace with things here. But does it allow two miui roms to dual boot? The last I remember was that only aosp were supported, IIRC.

varunangirash said:
Its giving error when i am flashing zip in TWRP:crying:
---------- Post added at 09:56 AM ---------- Previous post was at 09:05 AM ----------
I installed on data slot but now its not booting its vibrate for 3 times and then reboot. please help.. then i have to restore my data partition to boot again into primary rom
Click to expand...
Click to collapse
Bro don't use Secondary/dual slot for rom installation

zenjedi said:
Sorry I have not been keeping pace with things here. But does it allow two miui roms to dual boot? The last I remember was that only aosp were supported, IIRC.
Click to expand...
Click to collapse
Yes you can but always use data slots.

yes first i installed in secondary then i reliazed that its not have sufficient space so i installed on data slot but when i switch to my second rom that is rr and primary is miui 8.2.5 its not booting.
---------- Post added at 10:42 AM ---------- Previous post was at 10:36 AM ----------
Please see this Ss and give suggestions

Trying to patch a .zip i get an advise to "set documents into settngs > installed apps"
and the file don't get patched of course, and all permissions are granted.

varunangirash said:
yes first i installed in secondary then i reliazed that its not have sufficient space so i installed on data slot but when i switch to my second rom that is rr and primary is miui 8.2.5 its not booting.
---------- Post added at 10:42 AM ---------- Previous post was at 10:36 AM ----------
Please see this Ss and give suggestions
Click to expand...
Click to collapse
Are you using official miui rom?

Jack'O said:
Trying to patch a .zip i get an advise to "set documents into settngs > installed apps"
and the file don't get patched of course, and all permissions are granted.
Click to expand...
Click to collapse
On miui roms you have to first enable documents app by going to settngs > installed apps
And then you can patch files.

[ROM][BETA] OFFICIAL PIE from ASUS

I am not responsible if you brick your device.
UPDATE BETA PIE ROM
Direct link Download- https://drive.google.com/uc?id=1_r6zxR34q5aN72SPhAjMLkV4GxQcD4ff&export=download
Flash procedure for pie- https://www.asuswebstorage.com/navigate/a/#/s/A9A029F390A34806BED2A412E194C44D4
For BL unlocked phones
Recommended PBRP
PBRP has function to fix the encryption after flashing the ROM. You may choose to flash decrypt.zip for your own satisfaction.
PBRP worked like a charm for me.
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Stock FULL ROM OREO 8.1
Stock Recovery & TWRP Flash-able
You have to flash full ROM if magisk is installed. Take backup & be very careful if device get encrypted after installing the ROM. (Flash decryption file- https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/mod-decrypt-data-t3787311 )
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Official ROM link- https://www.asus.com/Phone/ZenFone-Max-Pro-M2/HelpDesk_BIOS/
One click Download - https://dlcdnets.asus.com/pub/ASUS/...995.844210030.1548823414-323285766.1546595187

so after installing latest 186 ROM continue installing decrypt.zip right?

rycroot96 said:
so after installing latest 186 ROM continue installing decrypt.zip right?
Click to expand...
Click to collapse
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.

Ajeyvm said:
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.
Click to expand...
Click to collapse
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro

rycroot96 said:
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro
Click to expand...
Click to collapse
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.

Ajeyvm said:
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.
Click to expand...
Click to collapse
thank you very much for the info

Guys ... Use PBRP Recovery.. It is based on TWRP...
It automatically patches forced encryption, after flashing the firmware file...
But just to make sure flash decrypt.zip too ...

So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
Click to expand...
Click to collapse
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
Click to expand...
Click to collapse
I did exactly the same... But using PBRP recovery... Faced no issue at all...

Tyakrish said:
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
I did exactly the same... But using PBRP recovery... Faced no issue at all...
Click to expand...
Click to collapse
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?

error displayed 7 in twrp.
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution

shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Do not unzip the file.
Right click on the file, open archive. Edit the updater script. Save it. Better to use 7Zip.

watatara.102 said:
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?
Click to expand...
Click to collapse
I am not sure exactly, which partitions are encrypted. But yes I think internal storage on /data/media is not encrypted...
But if you open TWRP then you will get a message to decrypt your device... DONT do this ! It will wipe your internal storage too, even if it is not encrypted...
If you want to copy your nandroid backup, then boot up your ROM and then transfer files using MTP to your computer..
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Did you use WinRAR ? Do one thing...
After extracting zip, and editing the script, go to the root of your firmware folder, select all files then add to archive. Select archive format as zip and keep the lowest compression possible...
While flashing, disable zip verification. This should work... Otherwise try the method by @Ajeyvm

I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT

watatara.102 said:
I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT
Click to expand...
Click to collapse
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Whenever i restart my phone i get that bug report. I clear it & use the device as usual. Evrything else is working fine. No need to revert back unless u r facing some major issue.

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Oh so its not just me then, good to know

It looks good.
Edit, someone posted a review - https://youtu.be/_wli8M-71yI

Someone should really post a mirror of the official link

Official link is down does anyone has any other mirror link?

[GSI][Android 10] Install AOSP 10 on Huawei Honor 6X.

POST - v14
(This number will increase every time the post is updated.)What's new in v14?
Corrected some simple mistakes in procedure.Modified overall post for better UX.

Spoiler: Version Changelog
What's new in v13?
Modified Gapps part in requirements to make it more clear.Added useful information section. for Pro Noobs and Ultra Noobs like me.What's new in v12?
Added User Contributions and feedback section.Added Miscellaneous recommendations section.Modified some steps in installation procedure to make it even more noob friendly.Linked @lmaohelp's thread.Decreased size of text in procedure.

This ROM is based on Android 10 GSI builds of @phhusson (Thanks a ton to him).
Thanks to @Hami_Do for his hi6250 patches.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks to @Djiban for his ideas on improving the thread.
Follow this thread only if you know what you're doing. I'm not responsibe for any damage or thermonuclear wars .
Read the post completely and understand it before doing anything ATLEAST FOR THE SAKE OF MANKIND .
This thread is best viewed in PC and is Noob Friendly.
Note that I was using flux substratum theme in the screenshots. Hence, icons and colors may vary on your device.
Spoiler: Requirements
Requirements:
Huawei Honor 6X (Unlocked Bootloader. If not, follow this post (using PotatoNV) or YouTube video.
EMUI 8 (If not, you could follow this guide, direct file : link).
GSI from link (download system-quack-arm64-aonly-vanilla.img.xz, you could try others but arm64, a-only is must).
TWRP from attchments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used nano OpenGapps, NikGapps gave an error during installing, You can also try others. You can directly try the img with gapps instead of vanilla but i prefer nano gapps over vanilla).
stock recovery.
Time.
PC.
ADB and Fastboot.
Patience.
Human Brain.
ALL IN ONE GUIDE : Check it out here. It contains every thing in detail all the way from bricked device -> EMUI 2 -> EMUI 5 -> EMUI 8 -> AOSP 10 (mentioned in this post). Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What on the Earth is meant by Vanilla android? -> it is the stock / pure version of android without Google apps and services.
What is OpenGapps? Check it out at OpenGapps.org!
What is Nano (not the mathematical 10^-9) Gapps? It is a version of Gapps with Minimal installation which means only the core part of gapps is installed with very little major apps. They can be installed later.
What is ARM64? it is a 64 bit operating system/platform.
What on the moon is AOSP? It stands for android open source project which is the purest form of android.
NOTE : My device bootlooped whenever I tried installing Magisk. So, better stick with the PHH-SuperUser that you get out-of-the-box with the system image.
NOTE : Skip every step with gapps if you are already using img with gapps.
What isn't working :
VoLTE (can't be fixed as per my knowledge), Camera (FIXED NOW | trying to find a fix, replacing libcamxxx could help), Flashlight (FIXED NOW | also trying to find a fix, fixing camera may fix this too).
CAMERA AND TORCH HAVE BEEN FIXED. Thanks to @Hami_Do (flash the attched patch file whenever you are bored, LOL)
What's Working :
Everything except the ones mentioned above VoLTE.
*Tell me if something else isn't working.
***If you have a bricked device/messed up somewhere during the process and unable to figure out what to do, follow this guide by @lmaohelp .***Procedure :
Make sure your device is running EMUI 8.
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.
Reboot your device to TWRP recovery.
Format the data partition {Wipe > Format data > type "yes"}
(Optional) In TWRP, choose wipe > advanced wipe > select system, data, cache and DALVIK and format them.
Check if your device is detected by adb using
Code:
adb devices
.
Move the img file using adb to device
Code:
adb push -p *img-name*.img /sdcard/
(the img file must be in adb directory).
(Optional, only if you want nano gapps over vanilla) Move Gapps in the same manner
Code:
adb push -p *gapps-name*.zip /sdcard/
(the zip file must be in adb directory).
Install img as system image {Install > Install Image > Select > Choose system image > Swipe➡}.
(Optional, only if you want nano gapps over vanilla) Unmount and Remount system partition. Go to wipe > advanced wipe > Choose system > resize. Flash gapps.
Flash stock recovery(also available in attachments) with twrp in the same way. push it with adb using
Code:
adb push -p STOCK_RECOVERY_RAMDISK.img /sdcard/
and flash it with twrp as "Recovery" after choosing install image.
Disconnect your device from PC and reboot to recovery(stock one).
Clear cache partition and perform a factory reset(You'll get an error during factory reset but you have to do it) (your device will bootloop if wiped with twrp itself).
Reboot, Cross your fingers and wait.
>If you flashed gapps over vanilla, the first boot would take about 5 mins. else, it would be very fast. Subsequent boots on both are quite fast.
>Sometimes, I observed that flashing gapps from internal storage caused bootloop(this is because of corrupt zip), in such case get back to EMUI 8, repeat the process by flashing gapps from micro sd.
*you'll get a warning that something wrong with your device every time you boot it. IGNORE IT.
Spoiler: Additionals
Additionals:
> If you messed up somewhere during installation, you can always recover your device by following this guide.
> If you have the update.zip file from the above mentioned EMUI 8 folder directly, you could just directly flash it after wiping data, system and cache(use adb push or microsd to transfer update.zip to device).
>Its better to charge your device to atleast 70% before doing anything as you'll have ample of time to recover it if you messed up something. If not, you can still charge your device in eRecovery mode and twrp but i found some issues like heating up and slow charging.
>Don't forget to set ringtone, notification and other sounds from settings after booting.
Spoiler: Updates
Updates :
I was able to install magisk by flashing unSU zip from @Hami_Do 's thread on hi6250 manual fixes and then flashing phh's magisk after deleting phh-su from /system/bin/ but sadly, I wasn't able to use quickswitch for other launchers as it needs magisk version of 20.4 (min.) but phh's magisk is 19.3 and substratum theme engine is not working (due to some error). So, I'm sticking with the root that comes out of the box and I recommend you to do the same. EXTRAS : The Phone and Messaging apps that came out of the box with the GSI stopped working after installing magisk. So, you are installing magisk, just replace these system apps from LineageOS ones or delete them and install the google phone and messaging from play store.
During multiple tests (installing, modifying and testing the GSI for its stability in multiple ways), I found that you need not always go back to stock EMUI 8 if you messed up something. This works without error but if you have some time, getting back to stock EMUI 8 is still recommended before installing some other ROM/GSI.
Try not to touch the finger print sensor when you are at the setup after first boot. This is making the finger print sensor not recognisable until next reboot.
User Feedback and Contributions :
Thanks to @OrionThyHunter for his feedback and some fixes :
Using the Greenify app will stop the finger print sensor from working. FIX : Disable "Alternative Screen Off Mode".
Thanks to @[email protected] for finding out he following issues :
Adaptive Brightness Doesn't work. Flash the attachment in this post to fix it.
To pass SafetyNet, follow this post.
Miscellaneous Recommendations :
Use Google Camera Go app for photos. Its much better than the GSI's stock one.

Happy Flashing !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........

[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
I think VoLTE can't be fixed.
For camera, you have to replace each file in /system/lib/ starting with libcam(libcamxyz...) from stock emui 8 and check each possible combination with subsequent reboots. I'm a little bit busy right now as I'm working on AOSP 11(as I believe it'll run without much problems because it has been tested on other hi6250 devices) with @Djiban. You could just do this on your own. If you find any working combination, please post it in this thread.

[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
Finally, Fixed it dude(camera and torch) by replacing libraries! Found a patch that does the same thing. Updated the Original post.
Tried a lot to fix VoLTE but didn't work... will try again later.
CHECK IT OUT!
#endyourwait LOL!

Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.

lmaohelp said:
Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.
Click to expand...
Click to collapse
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***

Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked

Venkata Lochan Nune said:
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***
Click to expand...
Click to collapse
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.

do you mean, you testing ASOP 11 on honor 6x ? if yes wow......

[email protected] said:
do you mean, you testing ASOP 11 on honor 6x ? if yes wow......
Click to expand...
Click to collapse
Nope, not now. @Djiban is quite busy and for me to work, I'm not having a spare device. He'll do it when he's got free time.
I didn't find much noticeable differences between AOSP 10 and 11 execpt some ui improvements and under-the-hood improvements. So, I'll skip AOSP 11 and directly will work with AOSP 12 on future. I liked the new things introduced in android 12. So, I'll definitely work on it.

lmaohelp said:
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.
Click to expand...
Click to collapse
Do you have the update.zip file?
Or wait I'll attach one in few hours...

lmaohelp said:
Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked
Click to expand...
Click to collapse
This is because twrp on our phone doesn't support encryption-decryption things. So, they can only mount internal storage when you perform a complete data format by typing "yes".

Venkata Lochan Nune said:
Do you have the update.zip file?
Or wait I'll attach one in few hours...
Click to expand...
Click to collapse
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!

lmaohelp said:
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!
Click to expand...
Click to collapse
Actually, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me.

Venkata Lochan Nune said:
Actuall, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me
Click to expand...
Click to collapse
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.

lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Well you could directly flash update.zip with twrp.
Wail I'll attach it in a while. Just turned on my PC to search for it and this bloody "working on updates" came up.

lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Yeah I've faced the same problem with flashify and ofcourse other similar apps. The problem I usually get is that system partition isn't writable. After changing it to r/w, I get an error that boot image not found. (This doesn't happen in flashify, it just freezes). Not sure what the problem is maybe, huawei's anti modding measures...

This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me
EDIT : THIS IS NOT THE RIGHT ONE. STOCK RECOVERY WAS ATTACHED IN POST #1.

Venkata Lochan Nune said:
This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me.
Click to expand...
Click to collapse
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!

lmaohelp said:
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!
Click to expand...
Click to collapse
So you liked it?
And hey, attach the stock recovery for future reference if someone needs it.
Use the camera patch to fix cam and flashlight issues. It just replaces the libraries. Flash any emui 8 compatible twrp with fastboot. Take a migrate backup in case.
Google Camera GO app works like a charm and is better than the stock one so I recommended using it.
Enjoy your phone!

Database Info

welcome