[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [H810]

[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [H810] - AT&T LG G4

Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
- Specials
- UsU compatible build so no need for a baseband package to be flashed!
- Using latest TITAN kernel sources
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM (see FAQ #20 for how to upgrade your bootloader stack)
Latest available MM based bootloader stack files: http://leech.binbash.it:8008/stock/LG/h810/20n/ (extract and follow the above FAQ for flashing)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable MM modems
- TWRP flashable N modem (recommended)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash AOSCP
Flash GApps (7.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Credits
LineageOS
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
kessaras
steadfasterX
and more..
Sources
Kernel
device tree

reserved 1

reserved 2

Hi steadfasterX,
I really appreciate your hard work and commitment. Thank you for the tools you created so we can unlock our devices.
Today I succesfully unlocked my H810 (stock MM, ARB=2), here are the steps I took:
1. Unlocked with Salt (also made basic backup; GPT compatibility - H811)
2. Installed TWRP, booted to recovery and flashed the baseband package H810_UsU_baseband_flash-in-twrp.zip
3. While still in TWRP rebooted to recovery.
4. Rebooted to system
After couple of minutes I started installing the rom from this thread - aoscp_h810_usu-4.2-20180421-unofficial.zip
Here are the steps I took:
1. Rebooted in TWRP
2. Installed TWRP flashable N modem - G4_29a_N_modem_UsU.zip
3. Full wipe (FORMAT DATA)
4. Flashed aoscp_h810_usu-4.2-20180421-unofficial.zip
Immediately after the installation started I received the following error message:
E3004: This package is for device: g4,p1,h810; this device is 3▯▯(▯▯.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/aoscp_h810_usu-4.2-20180421-unofficial.zip
I can confirm that the motherboard is H810, also when rebooted in recovery the phone is recognized by the PC as 헀h and not as the correct phone model.
Am I doing something wrong?

efto said:
Hi steadfasterX,
I really appreciate your hard work and commitment. Thank you for the tools you created so we can unlock our devices.
Today I succesfully unlocked my H810 (stock MM, ARB=2), here are the steps I took:
1. Unlocked with Salt (also made basic backup; GPT compatibility - H811)
2. Installed TWRP, booted to recovery and flashed the baseband package H810_UsU_baseband_flash-in-twrp.zip
3. While still in TWRP rebooted to recovery.
4. Rebooted to system
After couple of minutes I started installing the rom from this thread - aoscp_h810_usu-4.2-20180421-unofficial.zip
Here are the steps I took:
1. Rebooted in TWRP
2. Installed TWRP flashable N modem - G4_29a_N_modem_UsU.zip
3. Full wipe (FORMAT DATA)
4. Flashed aoscp_h810_usu-4.2-20180421-unofficial.zip
Immediately after the installation started I received the following error message:
E3004: This package is for device: g4,p1,h810; this device is 3▯▯(▯▯.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/aoscp_h810_usu-4.2-20180421-unofficial.zip
I can confirm that the motherboard is H810, also when rebooted in recovery the phone is recognized by the PC as 헀h and not as the correct phone model.
Am I doing something wrong?
Click to expand...
Click to collapse
Pls share the SALT log of the unlock process.
Sent from my LG-H815 using XDA Labs

Sure, here it is:
Code:
https://bpaste.net/show/1b84db71a154

efto said:
Sure, here it is:
Click to expand...
Click to collapse
Perfect one star for the fact that you saved that!
....and I take 4 stars as you unlocked with the totally outdated SALT 3.6. Current is 3.15!! Billions of fixes since 3.6.. It would have been just one click to update from within SALT... It's written in the OP..
Ok so extract the UsU unlock package.
Then boot in fastboot and flash these two:
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
Boot to TWRP and grab & share the recovery log
Sent from my LG-H815 using XDA Labs

I did the steps above, here is the file:
Code:
http://www.filedropper.com/efto_1

efto said:
Hi steadfasterX,
I really appreciate your hard work and commitment. Thank you for the tools you created so we can unlock our devices.
Today I succesfully unlocked my H810 (stock MM, ARB=2), here are the steps I took:
...
Click to expand...
Click to collapse
Hey, are you sure you have an H810 with MM ARB=2?
I have been trying to find a kdz to upgrade my ATT H810's LP bootloader (10o) to MM without bricking it, but no luck (all are ARB=3)...
Mind sharing part of your backup? (factory, hyp, modem, pmic, rpm, sbl1, sdi, sec & tz)
I believe this should allow me to upgrade the BL without any brick
PS: I would have sent this by PM, but it could be useful to other H810 users...

efto said:
I did the steps above, here is the file:
Click to expand...
Click to collapse
The log has been removed. Pls always use www.bpaste.net and ensure you select a long duration in the drop down.
Then share the link.
Well but I assume everything is working?
Sent from my LG-H815 using XDA Labs

Thanks a lot for all these efforts.
Hi steadfasterX first of all thankx for all these efforts to unlock LGG4 h810 and twrp and rom. I've done all these steps from unlocking to finalisation and take precautionary measures, since a month I was reading your posts regarding bricked devices. But today I did it. Right now my phone is booting as it is taking long to boot. So Thankx again for all these efforts.
After waiting 1 hour 30 mins, removed battery. First of all here is SALT log:
https://bpaste.net/show/c6f026e7377a
I installed twrp successfully, than baseband and than nmodem packages. Afterwards "aoscp_h810_usu-4.2-20180421-unofficial.zip" this rom and "open_gapps-arm64-7.1-micro-20180614.zip" this gapp and lastly Magisk 16. Rebooted and rom never started.
Again wipe and format data, installed this baseband"H810_UsU_baseband_flash-in-twrp.zip" and afterwards installed ROM. Restarted and now green screen "Demigod crash handler:Apps FIQ:XPU error!" appears with some details....
What i'm doing wrong?
Edit: GPT compatability h811 (do I need to install h811 rom? if yes than point me to it.)

smzubair said:
Hi steadfasterX first of all thankx for all these efforts to unlock LGG4 h810 and twrp and rom. I've done all these steps from unlocking to finalisation and take precautionary measures, since a month I was reading your posts regarding bricked devices. But today I did it. Right now my phone is booting as it is taking long to boot. So Thankx again for all these efforts.
After waiting 1 hour 30 mins, removed battery. First of all here is SALT log:
https://bpaste.net/show/c6f026e7377a
I installed twrp successfully, than baseband and than nmodem packages. Afterwards "aoscp_h810_usu-4.2-20180421-unofficial.zip" this rom and "open_gapps-arm64-7.1-micro-20180614.zip" this gapp and lastly Magisk 16. Rebooted and rom never started.
Again wipe and format data, installed this baseband"H810_UsU_baseband_flash-in-twrp.zip" and afterwards installed ROM. Restarted and now green screen "Demigod crash handler:Apps FIQ:XPU error!" appears with some details....
What i'm doing wrong?
Edit: GPT compatability h811 (do I need to install h811 rom? if yes than point me to it.)
Click to expand...
Click to collapse
Well.. the log you shared telling me that you are on v10 so lollipop when unlocking? Is that correct?
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Well.. the log you shared telling me that you are on v10 so lollipop when unlocking? Is that correct?
Click to expand...
Click to collapse
Yes it is correct :angel:
Edit: Here is the Recovery Log
https://bpaste.net/show/76d9d9491115
and dmesg log
https://bpaste.net/show/780d981f8419
Maybe you need em...

smzubair said:
Yes it is correct :angel:
Edit: Here is the Recovery Log
https://bpaste.net/show/76d9d9491115
and dmesg log
https://bpaste.net/show/780d981f8419
Maybe you need em...
Click to expand...
Click to collapse
Well you said that you have taken your time to read everything properly but the most important requirement before unlocking is to upgrade to marshmallow latest.. That's mentioned very clearly in the unlock OP.
the reason? exactly your errors you have at the moment. So head over to the unlocked read and read the FAQ to find out how to upgrade your bootloader to MM latest
Ensure you do a basic SALT backup before and afterwards and store then both in a safe place!!
Sent from my LG-H815 using XDA Labs

The first first boot takes forever time. how long should i wait?

kudlinux said:
The first first boot takes forever time. how long should i wait?
Click to expand...
Click to collapse
if it doesnt boot after 15 min something is wrong
-

steadfasterX said:
Well you said that you have taken your time to read everything properly but the most important requirement before unlocking is to upgrade to marshmallow latest.. That's mentioned very clearly in the unlock OP.
the reason? exactly your errors you have at the moment. So head over to the unlocked read and read the FAQ to find out how to upgrade your bootloader to MM latest
Ensure you do a basic SALT backup before and afterwards and store then both in a safe place!!
Click to expand...
Click to collapse
:crying: I admit that i've done many mistakes as i tried so many time to take a backup from SALT but always ended with an error before and after UsU. So right now I've no backup...... In uNlocking op faq #18 you mentioned
( If you lost your backup there is still a way you can proceed: Follow FAQ #20 )
but from where can I download KDZ? If from SALT than it is not downloading.

smzubair said:
:crying: I admit that i've done many mistakes as i tried so many time to take a backup from SALT but always ended with an error before and after UsU. So right now I've no backup...... In uNlocking op faq #18 you mentioned
( If you lost your backup there is still a way you can proceed: Follow FAQ #20 )
but from where can I download KDZ? If from SALT than it is not downloading.
Click to expand...
Click to collapse
do a SALT backup of your current state.
if you have issues taken a backup with SALT write in the SALT thread and post the debug log (advanced menu -> debug log -> upload button)
SALT can not download KDZs.
ah well. the h810 is special in many terms it seems. there is MM available for your model but the file you can find is 21y which has ARB 3 and so would BRICK your device.
the 20n is the first MM version for the h810 and that was delivered through OTA update only (it seems) and I cant find an info about the ARB for that so its maybe not possible to use that anyways. I'll try to find out if we can use that somehow
.

smzubair said:
:crying: I admit that i've done many mistakes as i tried so many time to take a backup from SALT but always ended with an error before and after UsU. So right now I've no backup...... In uNlocking op faq #18 you mentioned
( If you lost your backup there is still a way you can proceed: Follow FAQ #20 )
but from where can I download KDZ? If from SALT than it is not downloading.
Click to expand...
Click to collapse
I have some basic backups (before and after usu)
I could upload a backup if you need it

steadfasterX said:
if it doesnt boot after 15 min something is wrong
-
Click to expand...
Click to collapse
I cannot boot any AOSP in H810. I did flash after USU unlock.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
steadfasterX said:
if it doesnt boot after 15 min something is wrong
-
Click to expand...
Click to collapse
Also I tried LOS 15.1 for H810. This boots to recovery back. Please help.
---------- Post added at 05:23 PM ---------- Previous post was at 05:23 PM ----------
steadfasterX said:
if it doesnt boot after 15 min something is wrong
-
Click to expand...
Click to collapse
Also I tried LOS 15.1 for H810. This boots to recovery back. Please help.

Related

[Guide / Tool][10/15/12] - Update to Official Jellybean Then Root or Custom ROM!

I wrote this guide do to the general lack of information for users about the Jellybean update. This guide is basic in nature and will provide you with all the tools and links you need to update from an ICS based ROM to the official JB ROM then re-root or prepare for custom ROM.
If you already have the Official JB Update simply unlock it and proceed to Section #2. This guide was intially intended for those who cannot update because of Asus stupid lock out program once you unlock.
Warning
I have tested this guide on my device multiple times and never have one single issue. I cannot say it will work perfect for you! I am not responsible for anything that goes wrong including but not limited to; A $500 brick! The economy imploding worse, Nuclear war, End of the world on 12/12/12!
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
Windows 7 or Windows 8 PC
General Overview
Flash Asus JB update
Flash TWRP 2.2.3
Flash SuperSU or Custom ROM
Profit!
Please do not be afraid to ask for help!
This guide was written for people who need help. I didint write it for myself because I already know how to do it, lol
Donations gratefully accepted but never expected!
Please hit Thanks and Rate the thread 5 Stars
Click to expand...
Click to collapse
-Scott

Section 1 - Flash Asus JB update
Obtain the appropriate Jellybean update from the Asus Support Site HERE
Go to Downloads and pick the local / region specific update file for your device. For the intent of this guide I will focus on the US Based variant but all other devices will follow the exact same steps.
{
"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"
}
After you download the Jellybean update you must extract the zip file in the zip (I dont know why they did this!). The name of the first zip file will be "US_epad_user_10_4_4_16_UpdateLauncher.zip"
The zip file inside of that will be "US_epad-user-10.4.4.16.zip" This is the file we will flash to update to JB!
To do this open the first zip file with your zip [rogram of choice, (as you can see I use 7zip) and pull out the only other zip file in there (US_epad-user-10.4.4.16.zip).
Once you have that file copy it to you internal SD card. Although, untested, external SD should work too.
Now.... Reboot to recovery. To do this power down the device, and then Hold Volume Down and then press power untill you get a menu that says press XX key to boot to recvoery.
Once in recovery you MUST wipe data before you continue!
Now flash the ROM file you just copied like it was a plain old fashioned custom ROM or Root.zip. Just select it and flash!
Once the flash is done reboot. Dont be scared... This will take a LONG time... Maybe in upwards of 3 to 5 minutes. This is normal. Its completely rebuilding the device!
Once the device is all booted up and you are at your desktop we can proceed to Section 2.

Section 2 - Flash TWRP 2.2.2.3
First we need to obtain TWRPREcovery. You are free to use any version you want, including ClockworkMod (although I highly discourage CWM and recomend TWRP).
You can find TWRP HERE. Remember I recommend the 2.2.2.3 version. 2.3.0.0 gave me some issues.
Now that you have the file download you need to rename it to "recovery.blob" for use with my tool!
Now download the attached tool and unzip it. It contains the fastboot and ADB files you will need to flash the recovery.
Next place the recovery.blob in the folder
Turn on USB Degging in the developer menu of the device. This is very important otherwise you will be just sitting there forever, lol
Now initiate the "Recovery Install Tool.bat" file. This will reboot you to bootloader and flash the recovery for you ;c)
Done!

Section 3 - Flash SuperSU or Custom ROM
Needless to say I am partial to custom ROMS ;c) But I know some may be content with just flashing root so I will show you how to obtain the correct root file and or ROM and give a brief over view on how to flash them. This section will be pretty routine and will not contain a lot of new info for most of you!
Obtain my favorite root app, SuperSU, from HERE
Copy to storage
Reboot to recovery
Flash and Be rooted!
Same steps for a custom ROM. The best Custom ROM can be found HERE! ;c)

Section 4 - Thanks!
Thanks to Dess_troy for making TWRP for our devices!
Thanks to Chainfire for the root app!
Thanks to all the Developers on XDA that have taught me (in one way or another) everything I know!
Special Thanks to all the CleanROM users who have inspired me to push CleanROM to be the premier custom ROM for your Android Device!

Please feel free to rebuild this for the Linux or Mac platform and re-distrubute!

So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app

scrosler said:
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
-Scott
Click to expand...
Click to collapse
A number of people have asked and I have usually replied that it is possible to use the Asus provided UnLock tool - the one on the website that says is only compatible with ICS - with a tablet that has been updated to JB.
In short the Unlock tool works in Jellybean!
You might want to add this as an addendum to your original post.
Cheers,
Eric

i apologize for my beligerant question but if i want to try the new cwm touch recovery, do i just rename it to recovery.blob? when i downloaded it it was the usual iso. when renamed it didnt change anything so i dont wanna brick my tab. figured id ask first. thanks for the awesome walk through tho man. i really apreciate it. loving your roms. have 2.0 downloaded already. also can you pm the link to your tf300 kernel you used? i need to show off some high quadrant numbers lol

Confused...
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?

BlastTyrantKM said:
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
Click to expand...
Click to collapse
BlastTyrantKM said:
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This guide is for people who have already unlocked there device any may have had a custom ROM installed pre-JB.
You fall into a unique and rather off situation. I have never heard of some one not getting the OTA.
You could follow these steps but as a pre-step...
Download and unlock with the Asus unlock tool. Its on the same download page.
Download an ICS based recovery and use that in in place of the one noted for now. And then just start at Section 2. Then start back over at Section 1.
Basically we will put a recovery on your device in Section 2. Then start over at step 1 by applying the JB build then put a recovery back on, as it gets wiped off by Asus builds and your all set.

So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
The stock recovery will only flash firmware zips with a certain name. Rename the zip to EP201_768_SDUPDATE.ZIP and try again.

I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.

yes you lose root. this will make your tf700 like the factory jellybean firmware which is not rooted. go back to op and keep reading. each section builds on the previous. first get the jellybean firmware. im still playing with mine stock its so damn smooth. then you flash a custom recovery using his tool. then you flash the zip which gives you root. then i would make a back up so you can always get back to that point. then you can look into custom roms like scotts sweet clean rom for tf700 series
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
To me it looks like you are trying to run the batch file without extracting the contents.

Thank you for this guide! Although it took me some time to understand it as I was on non-rooted/locked JB stock rom.
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually had similar problem as this guy. I was already on JB and the guide is made for people that are on ICS.

scrosler said:
To me it looks like you are trying to run the batch file without extracting the contents.
Click to expand...
Click to collapse
I am using a borrowed PC. I am a Mac user so forgive my ignorance. But when I look at the folder with Scott's Tool in it it looks like everything is extracted.

scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually tried this last night with no luck. I guess it was something funny with my desktop in that it couldn't connect using fast boot. Anyway I brought it in to work and ran it here and everything is fine. I am going to throw your stock/root rom on it now. Thanks for your help!

CWM-SuperSU-v0.96.zip
Hello,
thanks a lot for the guide, it is really clear and detailed.
My question is something I did not find on the previous question and it is more a double check to be sure I am not doing something I should not.
You say to install SU with the package copied on the internal SD, and you added a link to the SU thread. in this thread, the only SU as a package you can find is CWM-SuperSU-v0.96.zip, as it is CWM, will it work if I install it with TWRP? or there is special settings in this package that will not be recognised by TWRP?
Thanks in advance for your help
Regards

[GUIDE][HUAWEI TAG-Lxx] P8 lite smart/GR3/Enjoy 5S Modding (unlock, root ecc...)

INFO
This device have different names in different countried (TAG-L01/L03/L13/L21/L22/L23 ecc..), but they are the same, everything writed in this post work on every TAG-Lxx device.
DISCLAIMER FOR ANDROID 6.0
A lot of people asked me to port android 6 or 7, so i answer once and for all:
I have alredy tryed but kernel needs some changes, the problem is that kernel source code they provided is simply incomplete! Compiled kernel without any mods don't boot at all
I've checked and i found that the first problem that cause this is missing/wrong lcd driver(this is the first but i think there are a lot of other driver missing)
So this are the options:
-fix it myself and add drivers from other device(already tried, risked to damage my device, i won't do anymore)
-ask huawei for correct source(i will try)
-find a way to bypass this changing android source(if kernel is not compatible by android, i can make android compatible with kernel), but its not easy
STOCK ROM
Single sim version(system dump of TAG-L01)
I can't find it on internet, so i have created a flashable zip that contains system and boot dumped from my device(using TAG-L22 offical one, because this is the only firmware i have found)
update.zip
if something goes wrong place it into your sdcard, reboot into recovery and flash it, your device is now fully working
-build: TAG-L01C212B123
-brand:TIM
-rooted:yes
this is my dump:
https://www.androidfilehost.com/?fid=24591000424961455
This zip contains boot recovery and system image of my device.
Dual sim version(offical TAG-L22, work on every dual sim variant)
official download link
UNLOCKING BOOTLOADER
Unlock bootloader is the same for all huawei devices:
-enable developer options(7 tap on build number)
-enable "oem unlock"
-go into http://emui.huawei.com/en/plugin.php?id=hwdownload and register an account
-select chinese language (is important, otherwise you can't access bootloader unlock page)
-click on the green lock and select first choice
-accept
-you are now into bootloader unlock page
{
"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"
}
-serial number can be found in settings/about phone/state
-IMEI have to be in the phone box
-product id can be found writing *#*#1357946#*#* in phone dialer
-solve captcha and click on the blue button
-you have bootloader unlock code
-MAKE A BACKUP, BECAUSE WHEN YOU UNLOCK YOUR DEVICE WILL BE FACTORY RESET
-put your indevice in bootloader mode(by using "adb reboot bootloader" or by volume up+power and selecting fastboot mode)
-type "fastboot oem unlock yourcode" (i suggest to write code letter by letter, copy-paste has not worker for me)
-type "fastboot oem get-bootinfo" and you have to see unlocked:yes
-type "fastboot reboot" to reboot into android
ROOT
recommender method(need an unlocked bootloader):
-Install twrp(look under for the link)
-download supersu
-reboot into recovery and flash it
phone can be rooted also without unlocking bootloader, but if something goes wrong to fix you need an unlocked bootloader, and i'm receveing a lot of report of people who have bricked, so i won't show how to do it anymore.
Restore huawei bootlogo(for branded devices)
Thanks a lot @ervius !
download
simply run logo_huawei.bat (or, if you are on linux read that and run all commands inside)
If SIM card is not recognised:
Sometimes, if you wipe data or change rom you will face this problem, fix is easy(but need root):
-go into / and delete nvdata folder(you will see a "read-only filesystem" message, ignore it)
-reboot(not soft reboot, normal reboot)
CUSTOM RECOVERY
TWRP 3.0.2-0
CUSTOM ROMS
Cyanogenmod 12.1
XPOSED
Official thread
-download Xposed for EMUI 3.1 Android 5.1.1 arm64 version
-flash it using twrp
-download and install this apk
NOTE:some module won't work because this device have emui

Thanks, I've been waiting weeks for this!
Can confirm TWRP works on my GR3 (TAG-L13) and was able to SuperSU from there.

felzam said:
Thanks, I've been waiting weeks for this!
Can confirm TWRP works on my GR3 (TAG-L13) and was able to SuperSU from there.
Click to expand...
Click to collapse
Good
Now you can also install xposed and other mods, i'm uploading a zip that fully re-stock this device, so if something goes wrong you can easily restore (some kind of "official firmware" but based on my dump, because official does not exist)
edit: ah ok, you have a TAG-L13, so probably with this firmware your sim wont work

what about tag l21

MedNour said:
what about tag l21
Click to expand...
Click to collapse
This guide will work and TWRP also, TAG-L01 and TAG-L21 are identical, the only problem is dual sim(so if i will succed compiling cyanogenmod, you probably can't use your sim)

mac12m99 said:
This guide will work and TWRP also, TAG-L01 and TAG-L21 are identical, the only problem is dual sim(so if i will succed compiling cyanogenmod, you probably can't use your sim)
Click to expand...
Click to collapse
good news then but i will be able to use 1 sim and micro sd ????

mac12m99 said:
This guide will work and TWRP also, TAG-L01 and TAG-L21 are identical, the only problem is dual sim(so if i will succed compiling cyanogenmod, you probably can't use your sim)
Click to expand...
Click to collapse
Cyanogenmod would be wonderful! I have major push notification problems while on WiFi and would love to move away from EMUI. Would it work on different versions though (on any TAG-LXX)?

MedNour said:
good news then but i will be able to use 1 sim and micro sd ????
Click to expand...
Click to collapse
Micro sd not, but probably all sims will not work
felzam said:
Cyanogenmod would be wonderful!
Click to expand...
Click to collapse
Yes
I have compiled succesiful, but don't boot, i need more time...
felzam said:
I have major push notification problems while on WiFi and would love to move away from EMUI.
Click to expand...
Click to collapse
Settings, protected apps, allow all apps that you want notification
felzam said:
Would it work on different versions though (on any TAG-LXX)?
Click to expand...
Click to collapse
Yes, but in dual sim devices proably sim will not work

Just wanted to say i'm also looking forward to see if an update to Android 6 is possible.

TheEversor said:
Just wanted to say i'm also looking forward to see if an update to Android 6 is possible.
Click to expand...
Click to collapse
There is only a stock rom on internet and is android 5.0(for TAG-L22), so for now no 6.0
My goal is compiling cyanogenmod 13(whitch is based on android 6), but it will take a lot of time.

mac12m99 said:
There is only a stock rom on internet and is android 5.0(for TAG-L22), so for now no 6.0
My goal is compiling cyanogenmod 13(whitch is based on android 6), but it will take a lot of time.
Click to expand...
Click to collapse
I'm absolutely new to this kind of things, but would it be theoretically possible to cook the huawei rom for the Honor 5X (also known as GR5) that is Android 6, adding the drivers of the official Android 5 huawei rom of the GR3 or TAG-L01 ?

TheEversor said:
I'm absolutely new to this kind of things, but would it be theoretically possible to cook the huawei rom for the Honor 5X (also known as GR5) that is Android 6, adding the drivers of the official Android 5 huawei rom of the GR3 or TAG-L01 ?
Click to expand...
Click to collapse
No, because has different hardware, i have to found a device that have the same processor whitch have android 6.0, but i will do late, first i have to build cm12.1(based on the same android version that have this device)

Hang on boot and adb driver problem
Dear friends, I made a little mess and I need your help.
I followed the guide by mac12m99, but I did some mistakes. A little recap:
1) I became developer (7 taps on build) -> OK
2) I enabled ADB debug, OEM unlock -> OK
3) Connected the phone while OS was running and did "adb reboot bootloader" -> OK
the phone booted in "fastboot mode". Now I had a problem: I cannot connect the phone anymore: if I tried "adb devices" no device was found. I think this is a driver related problem (I use Win 7 64bit). I googled a lot, but I wasn't able to find a working driver to solve this issue.
And now I made my BIG mistake! Since I couldn't connect the phone correctly to unlock the bootloader, I tried Kingroot -> success. But I don't like Kingroot much, due to many permissions requested. So I switched Kingroot with superSU using a guide from another forum (sorry I cannot post links).
During the process superSU asked for upgrading and I did -> success, but... after reboot the phone hung on boot.
Panic! tried to factory reset it, but after boot still hung.
Now I don't know how to proceed.
So I need your help:
1) Where can I find the correct driver to connect Win7 64 bit to the phone in fastboot mode ?
2) How could I revive the phone ? I thought if I successfully connect the phone in fastboot mode, maybe I could unlock the bootloader and see if the boot proceeds.
Thank you for your help, and sorry form my English and my ignorance.

mac12m99 said:
INFO
...
I can't find it on internet, so i have created a flashable zip that contains system and boot dumped from my device(using TAG-L22 offical one, because this is the only firmware i have found)
[ mediafire URL ]
if something goes wrong place it into your sdcard, reboot into recovery and flash it, your device is now fully working
-build: TAG-L01C212B123
-brand:TIM
-rooted:yes
Click to expand...
Click to collapse
Sorry but this content has been removed from Mediafire. Could you upload it again? Thankyou

Hang on boot and adb driver problem - update
OK I solved the first problem: it was a driver related problem as suspected. I succeeded to flash recovery and from there superSU, but after reboot still hang. So I need the stock image to revert the situation. I didn't understand well which image I should use: the first one from Mediafire (not available) or the second one: dumped from your device ? If I should use the second one: what is the procedure? Thank you

Triglia said:
OK I solved the first problem: it was a driver related problem as suspected. I succeeded to flash recovery and from there superSU, but after reboot still hang.
Click to expand...
Click to collapse
Did you unlocked the bootloader?(i guess yes, because twrp booted)
If yes, you have done a factory reset, so it needs 3-4 minutes to re-create cache and then will be working
Triglia said:
So I need the stock image to revert the situation. I didn't understand well which image I should use: the first one from Mediafire (not available) or the second one: dumped from your device ? If I should use the second one: what is the procedure? Thank you
Click to expand...
Click to collapse
They have blocked it
If waiting don't work, for now do this:
-go here
-search for gr3
-download firmware
-flash it using twrp
If you have a TAG-L01 SIM will not work, but device is usable.
If you use the second one you can only flash stock recovery, because system partition is refused by bootloader , but i think you can flash it using adb and twrp(an advanced method, i you want i can explain )

mac12m99 said:
Did you unlocked the bootloader?(i guess yes, because twrp booted)
If yes, you have done a factory reset, so it needs 3-4 minutes to re-create cache and then will be working
They have blocked it
If waiting don't work, for now do this:
-go here
-search for gr3
-download firmware
-flash it using twrp
If you have a TAG-L01 SIM will not work, but device is usable.
If you use the second one you can only flash stock recovery, because system partition is refused by bootloader , but i think you can flash it using adb and twrp(an advanced method, i you want i can explain )
Click to expand...
Click to collapse
Since I'm using TAG-L01 TIM branded, I think I should use your dump. Please explain me how to do. Meanwhile I'm downloading your image.
What do you mean that the SIM won't work? I cannot use it as a telephone anymore???!!!
Thank you.

Triglia said:
Since I'm using TAG-L01 TIM branded, I think I should use your dump.
Click to expand...
Click to collapse
So waiting have not worked?
Triglia said:
Please explain me how to do. Meanwhile I'm downloading your image.
Click to expand...
Click to collapse
-boot into twrp
-place system.img in internal sdcard
-type this:
Code:
adb shell
dd of=/sdcard/system.img if=/dev/block/mmcblk0p22
-flash boot.img using the recovery method(install-install image ecc..)
-reboot and wait 3-4 minutes
But if my firmware wasn't deleted, you can restore by easily flash the zip
Triglia said:
What do you mean that the SIM won't work? I cannot use it as a telephone anymore???!!!
Click to expand...
Click to collapse
Because my firmware was deleted, i've linked to you the only "official firmware", that is for the TAG-L22, i've tested it on TAG-L01 and everything work but SIM not(this firmware is not branded), it means that using this will not work, but if you install another that work, SIM will work
Triglia said:
Thank you.
Click to expand...
Click to collapse
Welcome

mac12m99 said:
So waiting have not worked?
-boot into twrp
-place system.img in internal sdcard
-type this:
Code:
adb shell
dd of=/sdcard/system.img if=/dev/block/mmcblk0p22
-flash boot.img using the recovery method(install-install image ecc..)
-reboot and wait 3-4 minutes
But if my firmware wasn't deleted, you can restore by easily flash the zip
Because my firmware was deleted, i've linked to you the only "official firmware", that is for the TAG-L22, i've tested it on TAG-L01 and everything work but SIM not(this firmware is not branded), it means that using this will not work, but if you install another that work, SIM will work
Welcome
Click to expand...
Click to collapse
Waited for about 15 min. but still hang.
In the file image "zt...G-L01_stock.gz", there is only 1 file "HUAWEI TAG-L01 stock" about 3.8Gb uncompressed. There is no "system.img " file.
I cannot restore a different ROM, I need to use the phone. Please could you send me the correct file? I sent you a private message with my direct contacts.

[SOLVED] hang at boot after Kingroot to superSU switch
After 2 days of test, and with the essential help of mac12m99 :highfive:,
I succeeded to revive my phone. It was necessary to flash the "update.zip" from the first post (but unavailable in the last days) and my phone was back, then I started again from scratch.
A suggestion: DO NOT try to switch from Kingroot to superSU using "superSUME", because you'll end in soft brick as I did.
If you gained root access through Kingroot and you want to switch to superSU, you should do the following:
1) Be sure that Kingroot is installed and working
2) Disable root from Kingroot itself, and uninstall Kingroot (you can do everything within Kingroot's options)
3) reboot in recovery (TWRP)
4) install superSU from TWRP
5) reboot: you are rooted again but with superSU and the phone is still working :good:
So, a big THANK YOU to mac12m99, for his precious help and patience and happy modding to everyone.

[RS988][RECOVERY][UNOFFICIAL] TWRP 3.2.1-0 for LG G5 RS988

{
"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 @jcadduono for your RS988 TWRP tree!
This is an unofficial TWRP v3.2.1-0 build for the RS988 to go along with the LineageOS build that I made. This is my first build of a recovery. Use at your own risk.
Installation from Stock:
**If your bootloader isn't already unlocked, go to the LG Developer website. You'll need to create an account. You can get the necessary ADB and fastboot tools from the Android SDK Platform Tools.**
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
1. Reboot into the bootloader with the command "adb reboot bootloader" and issue the command "fastboot flash recovery twrp-x.x.x-x_rs988.img", replacing "twrp.x.x.x..." with the location of the TWRP image on your drive.
2. Once it is done writing the image and says "finished," detach all power sources and remove the battery. This step is important—if you reboot into the system instead, TWRP will be overwritten by the stock recovery.
3. Reinsert the battery. Then start the phone, holding down both the Volume Down and Power button. When the LG logo appears, quickly release and re-press the Power button, continuing to hold Volume Down. This should bring you to a Factory Data Reset screen.
4. Confirm "Yes" on the two prompts (don't worry, no data will be deleted—we've overwritten the stock recovery) and you will be in TWRP.
Make sure to follow these steps as written, and make backups if necessary. You wouldn't want to risk saying "Yes" and actually wipe your data, right?
Click to expand...
Click to collapse
Working:
It works. If there are any problems, tell me.
Downloads:
v3.2.1-0-v5: MD5: 77501db1b7c551b1fd33407e0485d430
Update: Should fix flashing issues from v4.
Android File Host
v3.2.1-0-v4: MD5: 1600fbde74b2907c6f4e773e8dfd6f0d
Update: Added updated kernel, which fixes time and date, fast charging, etc. while in recovery.
Android File Host
v3.2.1-0-v3: MD5: 42714c19ccad6a29626aa81251bc984c
Update: Added extra languages (I use Japanese, so I need it).
Android File Host
v3.2.1-0-v2 (Fixed): MD5: b122eed990837936d113c9c780413c10
ALERT:
IF USING FIRST v3.2.1-0 BUILD, UPDATE IMMEDIATELY. ROMS WILL FAIL TO FLASH!
Update: Re-added cache partition to fstab.
Android File Host
v3.2.1-0: MD5: af7c9ebe4b78ed50f2cf45d81c3fbac9
Android File Host Use fixed build.
v3.1.1-0: MD5: 07e56018305edf54e92b2db8ebf6e05a
Android File Host
Click to expand...
Click to collapse
For all other information, refer to @jcadduono's TWRP Project page for the G5. I'm compiling his original work.
XDA:DevDB Information
[RS988][RECOVERY][UNOFFICIAL] TWRP 3.2.1-0 for LG G5 RS988, Tool/Utility for the LG G5
Contributors
NextDroid, shunjou, jcadduono
Source Code: https://github.com/imasaru/android_device_lge_rs988
Version Information
Status: Testing
Created 2018-02-04
Last Updated 2018-06-10

Everything works! Thank you for an updated recovery!

Awkydee said:
Everything works! Thank you for an updated recovery!
Click to expand...
Click to collapse
Phew. I was kind of unsure... I couldn't get Magisk to stick, so I was unsure whether it was problem with the recovery or not.
Thank you!

NextDroid said:
Phew. I was kind of unsure... I couldn't get Magisk to stick, so I was unsure whether it was problem with the recovery or not.
Thank you!
Click to expand...
Click to collapse
Magisk sticks!

Awkydee said:
Magisk sticks!
Click to expand...
Click to collapse
All right. It may just be an issue with my Lineage build then.
Also @Awkydee have the battery levels been reported accurately? I'd had this issue where it always reported 50%, and even a full reboot didn't solve it. I'm pretty sure I did a battery re-plug and it didn't help either.

No.. it almost always reports as 50%.

I might just buy a rs988 now that's it's got a new recovery and lineage os thanks!

On the subject of the battery percentage reported, the percentage always seems to start at 50% and then change to the correct percentage after about a minute or so. I'm not sure if this just means it checks battery percentage on a long timer or if its something else.

I need some help here I went ahead and unlocked my bootloader and I attempted to flash TWRP via the fastboot flash recovery command everything was successful but when I reboot my phone and try to type in ADB reboot recovery it just brings me 2 a stock looking Android recovery screen. With a little bit of research I discovered that I needed to apparently power down the phone after flashing TWRP then hold the power and volume down button until the logo appears and quickly release them and hold down again while the logo is still showing to get into TWRP for the first time but when I do this the phone just proceeded to show me the security warning due to the bootloader being unlocked and then it boots normally every single time I'm very confused am I doing something wrong?

TeChNoC4AzY said:
I need some help here I went ahead and unlocked my bootloader...
Click to expand...
Click to collapse
Yes, I agree, some instructions given on various sites are obscure. This is what you need to do:
1. Re-flash the recovery via TWRP.
If you're running stock, I believe that the recovery partition is overwritten on boot.
2. After it's done flashing (be EXTRA sure that it is), detach all power sources and remove the battery.
3. Start up the phone, holding both Volume Down and the Power button. When the LG logo appears, quickly release and re-press the Power button, continuing to hold Volume Down. This should bring you to a "stock-like" screen.
4. On the two prompts, select "Yes" on each one. You should then be taken to TWRP. Your data will not be overwritten, as TWRP should have replaced the stock recovery.
Personally, if I were to miss #3, I would reflash TWRP and then start over. I wouldn't want to risk the recovery partition being overwritten and saying "Yes" to actually wipe my data.
Make sure to corroborate with other sources to be sure that this is correct. This is coming off the top of my head.

I finally remembered to say this: instructions have been added to the main post.
Also, I have updated to TWRP v3.2.1-0! Download will soon be available in the main post as well.

Two announcements!
1. Installation instructions have been added to the main post. I have forgotten at least five times to say this, sorry ><
2. New build of TWRP available! A download for v3.2.1-0 has been added to the main post as well.

When I reboot into recovery mode and go to wipe> advanced wipe there's no option to wipe the cache in version 3.2.1-0

Awkydee said:
When I reboot into recovery mode and go to wipe> advanced wipe there's no option to wipe the cache in version 3.2.1-0
Click to expand...
Click to collapse
Sorry, I didn't see your post until now... I can reproduce this. I will look into it.

NextDroid said:
Sorry, I didn't see your post until now... I can reproduce this. I will look into it.
Click to expand...
Click to collapse
It's no big deal it's easy to flash back to a previous version. 3.1.1-0 works just fine!

Awkydee said:
It's no big deal it's easy to flash back to a previous version. 3.1.1-0 works just fine!
Click to expand...
Click to collapse
I like your patience haha. Luckily this time I was able to find a solution. The cache partition is now selectable in my latest build. I will upload it in a second.
UPDATE: Fixed build has been uploaded and is available in main post.
UPDATE II: @Awkydee This issue was worse than I thought.
UPDATE: MAKE SURE TO UPDATE TO FIXED v3.2.1-0 BUILD. ROMS WILL FAIL TO FLASH!

NextDroid said:
I like your patience haha. Luckily this time I was able to find a solution. The cache partition is now selectable in my latest build. I will upload it in a second.
UPDATE: Fixed build has been uploaded and is available in main post.
UPDATE II: @Awkydee This issue was worse than I thought.
UPDATE: MAKE SURE TO UPDATE TO FIXED v3.2.1-0 BUILD. ROMS WILL FAIL TO FLASH!
Click to expand...
Click to collapse
Thank you for all your effort on this device!

NextDroid said:
I like your patience haha. Luckily this time I was able to find a solution. The cache partition is now selectable in my latest build. I will upload it in a second.
UPDATE: Fixed build has been uploaded and is available in main post.
UPDATE II: @Awkydee This issue was worse than I thought.
UPDATE: MAKE SURE TO UPDATE TO FIXED v3.2.1-0 BUILD. ROMS WILL FAIL TO FLASH!
Click to expand...
Click to collapse
Just out of curiosity: Does your version of TWRP have the correct date/time or is it like ours (H850) with a date from last year and a wrong time no matter what you do?

Nimueh said:
Just out of curiosity: Does your version of TWRP have the correct date/time or is it like ours (H850) with a date from last year and a wrong time no matter what you do?
Click to expand...
Click to collapse
Oh boy... That one has driven me crazy. Having all of my NANDroid backups dated to the 1st of January 2016... Yep, like the H850 problem. I'm not sure how to fix that one :/
I've read that a couple reboots solve the issue, but that doesn't seem to work in this case.

NextDroid said:
Oh boy... That one has driven me crazy. Having all of my NANDroid backups dated to the 1st of January 2016... Yep, like the H850 problem. I'm not sure how to fix that one :/
I've read that a couple reboots solve the issue, but that doesn't seem to work in this case.
Click to expand...
Click to collapse
I've had my H850 for almost 2 years now and can't even count how often I've rebooted it - no fix there :laugh:
Every time I update TWRP or change the splash screen the date resets to Jan. 1st 2016 ... I rename every nandroid manually but it sure is a pain in the ... well you know :angel:
I was hoping you might have a solution ... oh well, just 1 more reason to ditch the phone and get a new one when the contract runs out in 3 months

TWRP for LG Aristo 2

{
"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"
}
Warning: Make a backup of your current stock recovery and data! As always I'm not responsible for bricks.
This is twrp version 3.2.1-0 and has finally been ported to the LG Aristo 2!
To flash:
1. Make sure your bootloader is unlocked
2. Download recovery.img from below
3. Boot phone into fastboot mode using "adb reboot bootloader" without quotations
4. Flash using "fastboot flash recovery recovery.img" without quotations
5. Once it is done, disconnect the phone and reboot into recovery
6. Wipe /data and /cache
7. Flash no verity zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ (Get latest version)
8. Flash magisk zip from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
9. Reboot and Enjoy!
Thanks to @brad2192 for flashing experimental builds for me!
*UPDATE 2-Fixed time bug, so now backups can be identified by date: https://www.androidfilehost.com/?fid=5862345805528064784*
TWRP DEVICE TREE: https://github.com/armandopartida0/android_device_lge_cv1
Donate here --------> https://paypal.me/APartida332

Works great, was a fun night of figuring this out together glad it worked out! Everything is functioning properly!
Just remember when you first load into TWRP you will need to go to wipe > format data and type yes.
This will erase all data so be sure to backup all your personal files to your SD card using the phone before you format. Then proceed to use the above instructions!

I got it flashed successfully and can get to it but it's asking for a decrypt password. I never set one up, so I'm not sure what to do. I still tried to format but it gives an error about inability to mount.
Edit - even with the error, it still has me set up Android again but it still wants a decrypt password and I can't mount.

tge101 said:
I got it flashed successfully and can get to it but it's asking for a decrypt password. I never set one up, so I'm not sure what to do. I still tried to format but it gives an error about inability to mount.
Edit - even with the error, it still has me set up Android again but it still wants a decrypt password and I can't mount.
Click to expand...
Click to collapse
hmmm. Can you provide a picture of the error please?

armandop_ said:
hmmm. Can you provide a picture of the error please?
Click to expand...
Click to collapse
I got it figured out. I rebooted directly back to TWRP after formatting the data and it mounted.

tge101 said:
I got it figured out. I rebooted directly back to TWRP after formatting the data and it mounted.
Click to expand...
Click to collapse
ah ok. Thanks for letting me know

Its normal. look at the other threads for twrp they always say to format the data after a reboot. Maybe add it to your tutorial thingy.
Edit: Thanks a lot guys its a lot more fun with root and TWRP. (>^.^)>

armandop_ said:
Warning: Make a backup of your current stock recovery and data! As always I'm not responsible for bricks.
This is twrp version 3.2.1-0 and has finally been ported to the LG Aristo 2!
To flash:
1. Make sure your bootloader is unlocked
2. Download twrp.img from below
3. Boot phone into fastboot mode using "adb reboot bootloader" without quotations
4. Flash using "fastboot flash recovery twrp.img" without quotations
5. Once it is done, disconnect the phone and reboot into recovery
6. Wipe /data and /cache
7. Flash no verity zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ (Get latest version)
8. Flash magisk zip from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
9. Reboot and Enjoy!
Thanks to @brad2192 for flashing experimental builds for me!
TWRP 3.2.1-0 (tested and working): https://drive.google.com/open?id=1XDQ01-OTloDd1e-uhfU3La5XzsVbPZmH
Click to expand...
Click to collapse
Thank you for this! Once my sata cables come in the mail and I get my Windows copy up and running on my second hard drive I need to create an ISO .img from the KDZ file you gave me. Need to get my phone back to stock, and im thankful you guys got TWRP working on this great phone.

Create a IMG from kdz? Don't you just use the kdz in lg up or something to reflash?

teknoweanie said:
Create a IMG from kdz? Don't you just use the kdz in lg up or something to reflash?
Click to expand...
Click to collapse
That sounds like allot less pain in the ass. Can you give me a quick breakdown of how to reset into stock using the KDZ. Dont need go type paragraps or anything just a brief summary this is all new to me.

Heres a tutorial. Its made for the aristo 1 but im sure it should work with the aristo 2. Use the lg up program.here
Just make sure to use the kdz made for the aristo 2 that you already have.
Forgot you may need uppercut aswell. here sometimes it gives a error which uppercut fixes.

Has anyone tried any other cameras with this phone? I was thinking of trying to flash CameraNext or SnapDragon but I've never tried either on a stock rom, so I'm not sure whether I'd bootloop.

tge101 said:
Has anyone tried any other cameras with this phone? I was thinking of trying to flash CameraNext or SnapDragon but I've never tried either on a stock rom, so I'm not sure whether I'd bootloop.
Click to expand...
Click to collapse
I don't have the phone so I can't test that. Mabe someone here with the phone can test?

tge101 said:
Has anyone tried any other cameras with this phone? I was thinking of trying to flash CameraNext or SnapDragon but I've never tried either on a stock rom, so I'm not sure whether I'd bootloop.
Click to expand...
Click to collapse
I love the Google Camera, just sucks that it saves strictly to Internal.

brad2192 said:
I love the Google Camera, just sucks that it saves strictly to Internal.
Click to expand...
Click to collapse
It only works up to be version 3 right? That's the last one I could find for non arm64.

tge101 said:
It only works up to be version 3 right? That's the last one I could find for non arm64.
Click to expand...
Click to collapse
Yeah, exactly. But it records really nicely

i have trouble booting in to recovery.... it takes me back to fastboot... Also I tried to revert to flash the root_boot and that does not work for me... pls help

Hey guys quick question... So I accidentally wiped system and didn't make a backup. I can get into twrp but have no os to flash. What can I do to get my phone working again? Sorry and thanks!

tge101 said:
Has anyone tried any other cameras with this phone? I was thinking of trying to flash CameraNext or SnapDragon but I've never tried either on a stock rom, so I'm not sure whether I'd bootloop.
Click to expand...
Click to collapse
I am trying to find good camera apps for this phone because the stock one is not that good. I will try those two that you have just posted.

Xsavi said:
I am trying to find good camera apps for this phone because the stock one is not that good. I will try those two that you have just posted.
Click to expand...
Click to collapse
I've tried finding other LG camera apps but none would work. Let me know how CameraNext works (if it does).
OpenCamera is giving me terrible quality.
Bacon Camera seems ok.
Google Camera is ok, but limited.
That's all I've tried. I know this camera should be capable of some good pictures.
Edit - I found an APK only install for CameraNextMod v10. This might be the best we can get with this camera unless the zip versions are compatible. Here's a link https://drive.google.com/file/d/1aLdiT1B2TcDFL0vfcmwYz6L7EdxqgFKj/view?usp=sharing
---------- Post added at 07:09 PM ---------- Previous post was at 06:26 PM ----------
armandop_ said:
ah ok. Thanks for letting me know
Click to expand...
Click to collapse
So, I just went back into TWRP for the first time since and it's still asking for a password to decrypt. I don't want to wipe everything again. Any ideas? Nothing is mounted and I can't mount without the password.

[Blu B130DL Unlock/Recovery/Root RELEASE]

{
"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"
}
Proudly Presents
Another Exclusive Release
Supported Model
Blu View 2
B130DL
Recoveries
TWRP_10 Recovery
Roms
GSI Roms ?
Info
Patched-lk.img contains the Orange State Boot warning Patched out
Patched-boot.img & Patched-vbmeta.img Are Pre-Rooted Images
BootLoader Unlock
MtkClient
Recovery Download & Device Tree
Device Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions
Contributors
Thanks to @bkerler for MtkClient

orb_selektor said:
Please read and respect the rules, no duplicated threads
Thanks
Click to expand...
Click to collapse
I'm sorry what ??

PizzaG said:
I'm sorry what ??
Click to expand...
Click to collapse
Sorry my bad, nevermind

I’m sorry, but, where are the patched images? Are they on GitHub?
Also, are they stock or TWRP?

Jakefusion said:
I’m sorry, but, where are the patched images? Are they on GitHub?
Also, are they stock or TWRP?
Click to expand...
Click to collapse
TWRP_10 is on github in the release section. I'll have to see what I did with the other images and get them up

Jakefusion said:
I’m sorry, but, where are the patched images? Are they on GitHub?
Also, are they stock or TWRP
Click to expand...
Click to collapse
I made my own image files from Firmware with build number QP1A.190711.020
And build version
V10.0.05.05.05.02
at the moment twrp isn't exactly functional so you need to install with mtkclient. Also it's not exactly apparent but you need to do this with the battery removed. If anyone wants I can make a guide better detailing the bootloader unlock process.
Put the attachments in the mtkclient folder.(vbmeta is included with mtkclient)
Backup your existing partitions using
python mtk r boot,lk,vbmeta boot.img,lk.img,vbmeta.img
Write new partitions using
python mtk w boot,lk,vbmeta boot.p.img,lk.p.img,vbmeta.img.empty
(If python fails try just using py)
install patched magisk from here
https://raw.githubusercontent.com/v...9e22fa276698f6c03bc1168df2c10/app-release.apk
Thanks PizzaG for the unlock process.

Before someone installs twrp can they make a backup of their recovery for me?
python mtk r recovery recovery.img
Could be python or py depending on your system
Also I am working on getting gsis or other custom ROMs on the device. Lack of fastboot and fastbootd make it a pain but I got one gsi to boot (network issues though)

i dont get it.

matthewdwheelersr said:
i dont get it.
Click to expand...
Click to collapse
got that little booger tho!

matthewdwheelersr said:
got that little booger tho!
Click to expand...
Click to collapse
i LOVE YALL CODE HEADS!!! I did soft brick it once, soft brick tho. big difference between a soft and a hard brick... If it wasn't for y'all code heads I wouldn't be able to live like I do. I love y'all man. this phone i had fun with its janky shtanky buttheads! Turning phones into GANGSTERS!!!

Technically maybe two soft bricks. bootloop with no logo tho... im just so happy guys...ya know it?

Hi, so I got this phone as a backup.
I tried putting in another sim card, but it said invalid.
Any idea if rooting would help? Or is this more of a hardware incompatibility?

zph0eniz said:
Hi, so I got this phone as a backup.
I tried putting in another sim card, but it said invalid.
Any idea if rooting would help? Or is this more of a hardware incompatibility?
Click to expand...
Click to collapse
SIMLock. Nothing you can do besides use it on TracFone for a year. I've seen GSIs remove sim locks before but it's been a while,and it was on Kroger Wireless in the Sprint days. Maybe it will work maybe it won't.

mateo121212 said:
I made my own image files from Firmware with build number QP1A.190711.020
And build version
V10.0.05.05.05.02
at the moment twrp isn't exactly functional so you need to install with mtkclient. Also it's not exactly apparent but you need to do this with the battery removed. If anyone wants I can make a guide better detailing the bootloader unlock process.
Put the attachments in the mtkclient folder.(vbmeta is included with mtkclient)
Backup your existing partitions using
python mtk r boot,lk,vbmeta boot.img,lk.img,vbmeta.img
Write new partitions using
python mtk w boot,lk,vbmeta boot.p.img,lk.p.img,vbmeta.img.empty
(If python fails try just using py)
install patched magisk from here
https://raw.githubusercontent.com/v...9e22fa276698f6c03bc1168df2c10/app-release.apk
Thanks PizzaG for the unlock process.
Click to expand...
Click to collapse
Finally by booting the livedvd directly on my computer instead of in VirtualBox I got mtkclient to work and stop getting the EMI 12 byte error.
Then I made a successful backup and proceeded to flash the two files you attached. The third I assumed should be an empty file so I touched an empty file into existence before writing.
I assumed I need to boot up the phone in order to flash the patched magisk you provided. The phone screen stayed black. Using lsusb shows that the phone is in a bootloop since it appears and disappears from the list of devices.
I flashed back the backup images and the phone, as expected, boots up but is not unlocked or rooted.
What am I missing here to get my B130DL rooted?

BluPhoneHome said:
Finally by booting the livedvd directly on my computer instead of in VirtualBox I got mtkclient to work and stop getting the EMI 12 byte error.
Then I made a successful backup and proceeded to flash the two files you attached. The third I assumed should be an empty file so I touched an empty file into existence before writing.
I assumed I need to boot up the phone in order to flash the patched magisk you provided. The phone screen stayed black. Using lsusb shows that the phone is in a bootloop since it appears and disappears from the list of devices.
I flashed back the backup images and the phone, as expected, boots up but is not unlocked or rooted.
What am I missing here to get my B130DL rooted?
Click to expand...
Click to collapse
Did you follow the instructions on the mtkclient github to unlock the bootloader first? Does your firmware match the files I posted? The blank vbmeta is in the download of mtkclient no need to make one. If your firmware does not match mine I can patch the files manually if you attach them and make sure to let me know what firmware or I can walk you through doing it yourself.
Useful links
Creating your own patched boot.img guide.
https://topjohnwu.github.io/Magisk/install.html
Creating your own patched lk.img (the orange state is what you need to remove)
https://www.getdroidtips.com/orange-yellow-red-state-warnings-mediatek/

mateo121212 said:
Did you follow the instructions on the mtkclient github to unlock the bootloader first? Does your firmware match the files I posted? The blank vbmeta is in the download of mtkclient no need to make one. If your firmware does not match mine I can patch the files manually if you attach them and make sure to let me know what firmware or I can walk you through doing it yourself.
Click to expand...
Click to collapse
Custom build version is BLU_B130DL_V10. 0.05.05.05.02_FSec
Build number QP1A.190711.020
This appears to match yours.
I'll need to reread the unlock bootloader part.
Thanks for the super fast reply!

BluPhoneHome said:
Custom build version is BLU_B130DL_V10. 0.05.05.05.02_FSec
Build number QP1A.190711.020
This appears to match yours.
I'll need to reread the unlock bootloader part.
Thanks for the super fast reply!
Click to expand...
Click to collapse
https://github.com/bkerler/mtkclient#unlock-bootloader

mateo121212 said:
Did you unlock the bootloader first
Click to expand...
Click to collapse
No I did not. And it appears I first need to backup boot and vbmeta, reboot phone, install patched magisk, adb push boot.img and install boot.img using magisk, pull boot.img back off phone and save as boot.patched before unlocking bootloader. Or do I just skip to the unlock bootloader section?

BluPhoneHome said:
No I did not. And it appears I first need to backup boot and vbmeta, reboot phone, install patched magisk, adb push boot.img and install boot.img using magisk, pull boot.img back off phone and save as boot.patched before unlocking bootloader. Or do I just skip to the unlock bootloader section?
Click to expand...
Click to collapse
Since you have same firmware you don't need to do magisk first. Just follow unlock procedure then flash the 2 modified files and blank vbmeta and reboot and install patched magisk apk. If your interested I created a magisk module that enables gesture navigation. Working on a debloat module as well.

Hey just wanted to say thanks to all that worked to get this going, y'all got my Alcatel tetra rooted, or some of y'all were in on that project and now my view 2, and I was just curious to see if it would work, so I attempted this whole process, on tcl a3 a509dl, took out the boot lk vbmeta, from mtkclient, and backed up those files for tcl then created magisk patch and lk patch and reflashed and it work, anyway again thank you

Database Info

welcome