Develop Bugs

Oneplus 3 soft bricked. Attempted flashing ROM with twrp and Stock recovery!

Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.

jasj0410 said:
Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.
Click to expand...
Click to collapse
Flashing the stock firmware using TWRP should do it for you. Just perform a FULL WIPE (formatting all partitions) before flashing the rom and keep in mind that you need a modified TWRP version to flash Oxygen OS based roms. The official TWRP won't do it.

Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.

jasj0410 said:
Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.
Click to expand...
Click to collapse
Advanced Wipe
--> mark
"ART Cache"
"Cache"
"Data"
"Internal Storage"
"System"
--> swipe to wipe
If you don't get any errors
--> restart TWRP (Or you can't access the storage)
--> flash rom

Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"

jasj0410 said:
Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"
Click to expand...
Click to collapse
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?

LS.xD said:
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?
Click to expand...
Click to collapse
i literally downloaded those files you linked to me and still no luck. it shouldn't be a problem that I'm using android file manager to transfer the rom over to my phone right? I'm going to wipe everything and go to stock recovery and use adb push to flash stock rom. any other suggestions you got?

Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.

jasj0410 said:
Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.
Click to expand...
Click to collapse
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

tnsmani said:
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?

jasj0410 said:
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?
Click to expand...
Click to collapse
I doubt that though there is no specific info on this .

How to Root Using SuperSU and TWRP on Oreo OPR6 Official Release

After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!

Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?

Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk

MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.

Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.

NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.

It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.

CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.

Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.

CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up

Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?

CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.

Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.

CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.

Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?

CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you

Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.

I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.

I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.

Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance

So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!

Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)

jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?

disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.

jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.

I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..

disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.

disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app

SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.

i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.

so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

[STOCK] [H932] [20p] [Oreo] T-Mobile LG V30 Stock Collection (Debloated Added)

T-Mobile V30 H932 20P Stock Collection
Based on OEM 20P KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
Bins in these packages are unmodified and you may need to flash no-verity-opt-encrypt and rctd remover after to keep force-encryption away.
REQUIRED
TWRP on LAF or Recovery
Latest Magisk Zip (if performing clean flash)
no-verity-opt-encrypt
rctd remover
FILE BREAKDOWN
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
If you want to restore DL Mode and Stock LAF, you must flash the StockLAF package separately.
​
Bootloader: 20p Stock Bootloader ONLY
FullStock: Full 20p Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
FullStock w/Magisk: Full 20p Stock Firmware + Magisk Root - Instructions in Section B
Debloated w/Magisk: Boot+Debloated System + Magisk Root (force enc & dm-verity removed) - Instructions in Section C
StockLAF: Individual LAF image for returning to stock DL mode
Global Instructions​
Always make a backup first
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
If coming from Nougat, Clean Flash is Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo versions, Dirty Flash works fine. OS and Apps are updated.
Copy All Zips to SDCard
Flash h932_FullStock.zip
Flash Magisk
Flash no-verity-opt-encrypt
Flash rctd remover
Reboot to system and install Magisk Manager (if not installed)
B - FullStock with Magisk
This zip just cuts out the step of flashing magisk manually.
This zip should be dirty flashed on a system that already has magisk. or Magisk may not flash successfully
If this zip is clean flashed, pay close attention to flash logs. If magisk fails to repack the boot image during flash, flash Magisk again.
Flash h932_FullStock_Magisk.zip
Flash no-verity-opt-encrypt
Flash rctd remover
Wipe Dalvik+Cache
Reboot
C - Debloated with Magisk
Be aware
This ROM does NOT flash LAF, recovery, bootloader or modem firmware directly.
If you are coming from an older version of android, this rom does not include the complete device firmware, which you may want.
For those included above, you should flash FullStock before flashing this to make sure all of your device firmware is up to date.
Boot image has been patched to remove force encryption and dm-verity
This ROM has had several pre-loaded and system apps removed. If someone wants to send me a list of any additional apps that can be safely removed, i can update the rom to include them.
system/app/CloudPrint
system/app/Drive
system/app/Duo
system/app/EditorsDocs
system/app/EditorsSheets
system/app/Gmail2
system/app/GooglePay
system/app/LGAccount
system/app/LGAirDrive
system/app/LGAmazonAssistant
system/app/LGAmazonAttribution
system/app/Maps
system/app/Music2
system/app/Photos
system/app/YouTube
system/priv-app/CloudHub
system/priv-app/CollageWallpapers
system/priv-app/facebook-installer
system/priv-app/LG360VideoWallpaper
system/priv-app/LG360Wallpaper
system/priv-app/LGEasyHome
system/priv-app/LGEmail
system/priv-app/LGExchange
system/priv-app/LGQHelpService
system/priv-app/LGVVM
system/priv-app/NameID
system/priv-app/TMO_MyAccount
system/priv-app/xtra_t_app
system/vendor/app/facebook-appmanager
system/vendor/overlay/com.lge.easyhome
system/vendor/overlay/com.lge.email
system/vendor/overlay/com.lge.exchange
system/vendor/overlay/com.lge.lgworld
system/vendor/overlay/com.lge.qhelp
system/vendor/overlay/com.lge.qhelp.application
system/vendor/overlay/com.lge.qmemoplus
For best results a clean flash is recommended for this package
Format data, and remove any apps installed to external sd. Then wipe system, dalvik, cache, data, internal storage
This will ensure no lingering apps are left behind.
If coming from Nougat, Clean Flash is Highly Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo Versions
Wipe Dalvik, Cache, and System, and optionally data and internal storage
If you do not perform a clean flash, you may need to manually remove the apps left behind after flashing
Flash h932_Debloated_Magisk.zip
Reboot
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge​
Bootloader - md5:45d8897c317b2e2e7b02d0766a93556c
FullStock ROM - md5:092585a169b54f067cec27d57b0c041c
FullStock w/Magisk - md5:6854a34ed956e9b30fb8e59c34de6b39
Debloated w/Magisk - md5:5a11334c8e42dfe55f2a71bbb0820612
StockLAF - md5:9090ee8645f2018c6bd88c9169c52c1b
*************************************************************************************************************​
Encryption Notes
In Android, a stock device will have it's data encrypted. Often when working in TWRP on an encrypted device, you will be greeted by prompt asking for a passcode in order to decrypt the device. Unless that port of TWRP has been written for your specific device and supports decryption, you will not be able to decrypt the data on your phone. If you cannot decrypt the data, then TWRP cannot mount system and/or other partitions it needs to mount in order to safely flash anything. In order to solve this problem, sadly, you have to format the data partition on your phone (losing all personal data accumulated on the internal storage, so back it all up manually) The steps for this process are Format Data in TWRP, Reboot to recovery (to mount partitions), then flash your rom and root. There are a few tools out there to disable force encryption on your device. See the Required section above for links for this device.
​
Packages have been successfully tested VIA the methods outlined above.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom​​
XDA:DevDB Information
[STOCK] h93220p, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/20p/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: 20p KDZ
Version Information
Status: Stable
Created 2018-12-20
Last Updated 2018-12-28

would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.

This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots

Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Verify that you did download "h93220p_fullStock_wMagisk.zip". It worked fine for me, and I can confirm it has magisk as I was on 17.3 on 20o and magisk manager says I'm on 18.
Also, were you coming from 20o?

[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
Yes, I can make a debloated ROM. Gimme a day or two and I'll try to add one to the OP.

Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Sorry M8, but i tested this zip and verified that it flashes all partitions and then flashes magisk all in one go. I think maybe you downloaded the package without magisk by mistake.
This zip does not flash LAF, so if you had TWRP on LAF before flashing this, you should be able to just boot to download mode using the usb cable and reflash TWRP to recovery.

Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed
Click to expand...
Click to collapse
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP

weakNPCdotCom said:
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP
Click to expand...
Click to collapse
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.

Andi32790 said:
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.
Click to expand...
Click to collapse
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.

weakNPCdotCom said:
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.
Click to expand...
Click to collapse
No worries man I still have a phone plus thats why you all add the disclaimer. Idk just looking for a fix at this point.

[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM

Thanks weakNPCdotCom. I dirty flashed over 20o and it's working great.

weakNPCdotCom said:
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM
Click to expand...
Click to collapse
No worries take your time. Appreciate the work your doing

I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.

SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
I just did it and didn't loose TWRP.

It worked thank you.

SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
Just pay attention to the flash logs and make sure everything flashes properly

[Cruzer] said:
No worries take your time. Appreciate the work your doing
Click to expand...
Click to collapse
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues

weakNPCdotCom said:
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues
Click to expand...
Click to collapse
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work

[Cruzer] said:
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work
Click to expand...
Click to collapse
I did remove chrome in the ROM so ill keep that in mind when I try again tonight. I don't think I'm going to deodex it either unless I get a smooth running build.. I'm not sure the advantage in oreo anyway since it's vdex now. but ill give it another go

ROM][10] LineageOS 17.1 for honor 6x

I just find out that this rom https://forum.xda-developers.com/p8...m-lineageos-17-1-huawei-p8-lite-2017-t4064121 could be installed on our device wtih minor changes.After installing all things you will need to install stock recovery and wipe cache and try to do factory reset(i tried to but i got error massage) then you will successfully boot into rom
Contributors
 @DarkJoker360

I can confirm that this works like a charm, here I posted the instructions for those who want to install it!

Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help ?

Momo745040 said:
Hi when I try to wipe data and cache... I have an error because the data is not mounted, I've trying to change the system file to ext2 and ext4 but nothing change. I also tried to repair system file. What can I do ? My device is already emui 8 and it's an Huawei gr5 2017 bll-l22. Thanks for your help
Click to expand...
Click to collapse
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick

A big job ahead ?. I will try and I will tell you if it works thank you for your answer. One last question is there a way to keep a custom recovery because sometimes magisk's module causes a botloop (sorry for my bad English ?)

lucsi said:
Try the lastest TWRP in this thread
https://forum.xda-developers.com/p8...wrp-3-3-1-0-huawei-p8-lite-2017-t3953122/amp/
After installing system.img, u need to resize the system partition, until see the used space ~17xxmb and free ~18xx mb,
after that flash gapps
and MUST flash Magisk Phh 19.3
the flash the patch file.
After first boot, you need to, format data in erecovery
Everything works smoothly except......can not make and receive calls, ooopss
update, i try to roll back to emui8, and start the process again. it works now.
recommend to update, lets teach the old dog new trick
Click to expand...
Click to collapse
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk

Momo745040 said:
So I came back (finally) to emui 8 and I tried to install the recovery custom but I still cannot access the internal storage memory.
I think it comes from my model because I have a Huawei GR5 2017 which is supposed to be a 'copy' of the honor 6x but all the roms which require emui 5.x installed do not work.
In any case thank you very much for your help! [emoji106]
Envoyé de mon BLL-L22 en utilisant Tapatalk
Click to expand...
Click to collapse
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug

lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
Thanks you very much for your help!
I'll try this weekend (I don't have time in week).
I will come back to say if it worked

Has anyone tried these github projects to unlock the bootloader of his Honor (6X) or Huawei Device?
Maybe it is possible to accelerate these programs by using cuda cores on nvidia graphic card(s).
https://github.com/SkyEmie/huawei-ho...ock-bootloader
https://github.com/Martazza/Huawei-Bootloader-Unlocker

lucsi said:
The trick is you need 2 twrp.
https://drive.google.com/file/d/1-iErvJefoFri7HKNEU8uSnYo8kmIyVd9/view?usp=sharing
https://drive.google.com/file/d/1MnFBplsp3nZ3b0BiJ764cV67kHXeRzL4/view?usp=sharing
use twrp-3.3.1emui8v2.img for everything
In the last step after everything flashed, you flash the other twrp huaweitwrp.img
reboot into that twrp
chooose advances; fix encryption
reboot system, then you can access internal memory
the same process with android 10.
mine is also Gr5 2017 and now running 10, no bug
Click to expand...
Click to collapse
I managed to find a compatible recovery but when I flashed everything and I did a factory reset from the erecovery the phone restarts and it displays the logo lineageOs for 5 seconds then it restarts and the screen remains black then it restarts and displays the logo then it restarts in erecovery telling me that the memory has been seriously damaged.
I think I will give up here([emoji28])but anyway thank you for your help [emoji106].
Envoyé de mon BLL-L22 en utilisant Tapatalk

at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy

Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
Click to expand...
Click to collapse
Have you followed all these instructions?
matyrock said:
How can there be such awesome people? It works in my Honor 6X! And it's fully de-googled man this is just perfect! Thank you very much for this...
These are the steps (thanks @DunoCZ) I followed if an Honor 6X user want to install this ROM:
- *Upgrade to EMUI 8!*
- *Remove the saved fingerprints and Google Accounts just in case*
- Flash the TWRP recovery from @Dil3mm4
- Format cache, dalvik cache, data and system: TWRP -> Wipe -> Advanced Wipe
- Flash the ROM via TWRP (you can try with fastboot but it already works with TWRP): TWRP -> Install -> Install Image
- Resize the system partition: TWRP -> Wipe -> Advanced Wipe -> System -> Resize (DO NOT FORMAT!)
- (Optional) Install GApps, Magisk
- (Required) Install patch
- Reboot and wait
Click to expand...
Click to collapse

D0ping said:
Have you followed all these instructions?
Click to expand...
Click to collapse
i did and the diffferent thing i did is to flash back stock recovery as mentioned by op, wipe the cache and then flash huaweitwrp.im provided by lusci
i edited my post above

Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Edit: Figured it out. apparently my gapps was somehow broken. Downloaded a fresh arm64-ogapps and all is working now

Darkitz said:
Yea, i cant get it to work. No matter what i do after
- flashing system.img
- resizing the system partition
- installing opengapps
- installing magisk
- installing the patch
followed by either:
-straight up booting it.
- doing everything i can in every bootloader.
evenm if i freshly format /data the system get stuck in a boot. Have tried all of the recoveries in this thread. All are basically the same, from what i have observed.
Click to expand...
Click to collapse
follow my guide here, this is how i managed to get it work, make sure you flash the rom with your CLEAN STOCK rom
Raxul said:
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse

Raxul said:
at first it says encryption unsuccessful then i was told to format the date from twrp, now it stuck on boot animation, i have left it overnight and it reboots to bootloader with code BFM_S_NATIVE_DATA_FAIL 211 NA
reboot_panic_and_wdt_process_func
finally i managed to get it work, so now i'm going to post every single thing i did to make this rom works and i will try to be as noob friendly as possible
first thing first in case you mess everything up, i found out this guide to be some sort of remedy for all problems regarding honor 6x, because from here you will install stock emui 5 which you can use to upgrade to stock emui 8 from this guide
use the guide above if you want to go back to stock rom because every single custom rom will require you to flash from the stock rom
next i follow the guide provided here, after flashing the patch go back to stock oreo recovery which is available on the emui 8 folder you downloaded earlier
do factory reset and wipe cache after that load to bootloader again
finally flash huaweitwrp.img provided by lusci on the post #7
boot to system and enjoy
Click to expand...
Click to collapse
Ok let me make it simple for you.
1. Flash stock Oreo Rom (no need to boot it)
2. Flash TWRP by Dilemma in fastboot.
3. Go to recovery and wipe data by typing yes to decrypt data partition (if not already decrypted)
4. Go to fastboot and flash system.img
5. Reboot to recovery and resize system partition
6. Flash GApps
7. Flash los patches zip
8. Flash disable Dm verity patch
9. Flash magisk-phh zip in the end.
10. Reboot and wait.
I used these steps to flash different GSIs/ROMs and it works perfectly.

I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20

victorgrey999 said:
I managed to flash the rom but without flashing the gapps because I don't know exactly which one to flash should I flash gapps for android 10 arm64 or gapps for android 8.0 ??
try both and it gives me error 20
Click to expand...
Click to collapse
You need to resize the partition
flash android10 arm 64

lucsi said:
You need to resize the partition
flash android10 arm 64
Click to expand...
Click to collapse
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?

victorgrey999 said:
I managed to flash the rom successfully, but I don't know if this only happens to me, I feel it is slow and the cell phone is heating up more than normal. ?
Click to expand...
Click to collapse
Mine is ok. battery backup is ok.
Antutu ~96K point
You can install kernel management app to tweak the CPU freq