Database Info

[SCRIPT] Moto E XT1023 super easy ROOT, RECOVERY, & RESTORE

This is a little script tool I made up for the Moto E XT1023 The Firmware restore will only work on the XT1023 but all other options should work on all the variants of the Moto E
It is really simple. But requires a unlocked bootloader video HERE If you need help with bootloader unlock
{
"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"
}
Download the Moto E Super Tool
extract the tool to your desktop
Turn on usb debugging mode on the device
install the Motorola drivers
Run the Moto E 1 Moto-E-Restore-XT1023.bat file
then just select what you want to do
1. Root your Moto E
2. Flash TWRP Recovery
3. Flash Stock Android Recovery
4. Flash CWM recovery
5. Remove the unlocked bootloader warning
6. Fully restore the Moto E to stock
7. Fully restore plus Relock the bootloader
Newest release V2
Change Log
Vision 1 first release
Version 2
updated TWRP
Updated Supersu.zip
DOWNLOAD SUPER TOOL
WIll add more to this if i have time
Hope this will help out some noobs

Is it for all the models like xt1021 nd xt1022??

zoneofSAM said:
Is it for all the models like xt1021 nd xt1022??
Click to expand...
Click to collapse
the first line of thread answers your question. variants=models

zoneofSAM said:
Is it for all the models like xt1021 nd xt1022??
Click to expand...
Click to collapse
I have tested it on the xt1023 but from what i am told it should work on all models because supersu.zip is universal and same with TWRP if i am not mistaken.

doesn't reboot into recovery
Everything seems ok during the process but when the phone reboots it stays in the Motorola logo/Android screen, never moving on to TWRP. This also happened when I tried the normal Fastboot method. Bootloader is unlocked and usb debugging is checked, of course.
Any ideas?
edit:
More info-
1. The only command that seems to work on my phone is when I install stock recovery.
2. When I go into bootloader and try to restart in any mode but normal restart I get a blank screen
3. I previously bricked my phone by doing something stupid so I reflashed one of the factory firmwares-
RETUAWS_XT1023_4.4.2_KXC20.82-15_cid9_CFC.xml
Could this be the source of my problem?
Thanks in advance!

Hi,
Thanks for your script, mate...just used it for SuperSu installation and made the rest by other way, but worked flawlessly for that, and that's the point !!! :good:
Cheerz

satanas17 said:
Hi,
Thanks for your script, mate...just used it for SuperSu installation and made the rest by other way, but worked flawlessly for that, and that's the point !!! :good:
Cheerz
Click to expand...
Click to collapse
updated tool with newest twrp and supersu

Cannot upgrade to 4.4.4
Thanks for the nice video; however I just have a problem when trying to go back to stock recovery to install the 4.4.4 update that is recently pushed to Moto E devices; I want to go back to stock recovery as it does not gets installed with any custom recovery.
I tried the said method 4-5 times but it gives me with a dead android icon when trying to get to stock recovery..
Please help me to get 4.4.4 on my device.

Yeah that is normal you have to press volume up and power on that screen to get to options

Tomsgt said:
Yeah that is normal you have to press volume up and power on that screen to get to options
Click to expand...
Click to collapse
Thanks!! it worked for me and I see the options now.. however the update still does not work :crying:
and searching and experimenting to get 4.4.4

_SGY said:
Thanks!! it worked for me and I see the options now.. however the update still does not work :crying:
and searching and experimenting to get 4.4.4
Click to expand...
Click to collapse
Update won't work if you have modded system partition in any way. Even if its just blotware uninstalled. Just flash system partition only and it should work. The .1 .2 .3 file extension files I mean

Deadly said:
Update won't work if you have modded system partition in any way. Even if its just blotware uninstalled. Just flash system partition only and it should work. The .1 .2 .3 file extension files I mean
Click to expand...
Click to collapse
You mean system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 right??
Done that already with no success.. I don't know what I am doing wrong here

No more wallpaper crashes after wipe data and cache

_SGY said:
You mean system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 right??
Done that already with no success.. I don't know what I am doing wrong here
Click to expand...
Click to collapse
Updated Yippeeeeee...
The issue was my rooted device, I had to unroot, install stock ROM as I had removed plenty of bloatware..update success, re-root and enjoy!!!!
Posting steps to benefit someone who may be facing the same issue as I was..

Hey guys. My little brother just got a Moto E, and I'm trying to get it rooted/Recovery'd.
I'm using your toolkit, but so far, no luck. Doesn't want to root, nor install recovery. It's stuck on "waiting for device".
I don't know what's wrong. I checked that USB debugging was on, and he unlocked his bootloader earlier. Everything should be fine.
But, it doesn't work.
Could someone provide some help, please ?
Thanks.

Did you extract the zip to your desktop? And are the right drivers installed also try using a different USB cable or port.

Demonseye said:
Hey guys. My little brother just got a Moto E, and I'm trying to get it rooted/Recovery'd.
I'm using your toolkit, but so far, no luck. Doesn't want to root, nor install recovery. It's stuck on "waiting for device".
I don't know what's wrong. I checked that USB debugging was on, and he unlocked his bootloader earlier. Everything should be fine.
But, it doesn't work.
Could someone provide some help, please ?
Thanks.
Click to expand...
Click to collapse
Did u connected mobile in bootloader ? Try t

sham4u2sam said:
Did u connected mobile in bootloader ? Try t
Click to expand...
Click to collapse
Yeah, I tried it. Weird thing is that we reconnected it to his computer, and the script recognized his phone, while my PC did not. Everything went smooth. Thanks.

Recovery.img is for 4.2(for option stock recovery)
But my moto e is 4.4.4
Will it work???
And also
One advice
Plz include flash stock firmware to your your script
And don't add drivers to in your zip file make a separate link for driver.
Hope you like my suggestions and include it in your next update
Any how i looked your bat file
You looks a good programmer
---------- Post added at 11:01 PM ---------- Previous post was at 10:20 PM ----------
Request for new menu
1.root your phone
2.flash twrp
3.flash stock recovery 4.4.4
4.unlock boot loader(where it only ask to enter unlock key)
5.remove bootloader unlocked warning
6.install stock firmware or rom(where it flash frimware placed in frimware folder)
7.lock your boot loader and install orignal 4.4.4 recovery to get warranty back
Hit thanks if you like to include these options in next update

hard91 said:
Recovery.img is for 4.2(for option stock recovery)
But my moto e is 4.4.4
Will it work???
And also
One advice
Plz include flash stock firmware to your your script
And don't add drivers to in your zip file make a separate link for driver.
Hope you like my suggestions and include it in your next update
Any how i looked your bat file
You looks a good programmer
---------- Post added at 11:01 PM ---------- Previous post was at 10:20 PM ----------
Request for new menu
1.root your phone
2.flash twrp
3.flash stock recovery 4.4.4
4.unlock boot loader(where it only ask to enter unlock key)
5.remove bootloader unlocked warning
6.install stock firmware or rom(where it flash frimware placed in frimware folder)
7.lock your boot loader and install orignal 4.4.4 recovery to get warranty back
Hit thanks if you like to include these options in next update
Click to expand...
Click to collapse
challenge excepted LOL Moto E Super Tool
Your Option 4 isnt going to happen

Temp Root Question

Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)

coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.

robocuff said:
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.
Click to expand...
Click to collapse
Thank you, then I'll have to buy the full version of app

coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?

cntryby429 said:
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?
Click to expand...
Click to collapse
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.

coderch123 said:
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.
Click to expand...
Click to collapse
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.

cntryby429 said:
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.
Click to expand...
Click to collapse
Here's a picture
{
"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"
}

Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?

cntryby429 said:
Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?
Click to expand...
Click to collapse
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.

coderch123 said:
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.
Click to expand...
Click to collapse
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk

dottat said:
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay. I checked it with fastboot getvar all and it is stock, there's nothing wrong with it. S-ON and locked bootloader.

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.

[recovery][lm-g710em]twrp 3.2.1[persistent]

[UNOFFICIAL] TWRP 3.2.1 for LM-G710EM ONLY
{
"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"
}
​
NOTE
There are 2 versions for this recovery, SEMI-PERSISTENT & PERSISTENT.
1. Semi-Persistent Recovery
[Works on stock rom and custom rom] Not permanent, requires command in order to boot and needs to reflash it every time you need it and then reflash stock boot.img after using it in order to avoid bootloop.
2. Persistent Recovery
[Works only on custom rom] Permanent, you can boot on it anytime without a command and doesn't need to reflash it and stock boot.img.
Flashing TWRP Recovery
Downloads:
[SEMI-PERSISTENT] TWRP 3.2.1
[PERSISTENT] TWRP 3.2.1
1. You need to be rooted first. Root Guide: Magisk
2. Flash TWRP image (Download link above) using the following command:
Code:
fastboot flash boot_a pathtoimghere
and
Code:
fastboot flash boot_b pathtoimghere
Note: In this state, you will encounter bootloop when you restart your device and proceed to OS. So please, don't.
3. Boot to recovery using the button combination (VOLUME DOWN + POWER BUTTON).
4. Once you are booted in TWRP, you might notice that /date doesn't work. To fix it, you need to decrypt your phone.
For now, flash the vendor.img found here.
5. After step #4, Hit Wipe and Format Date on TWRP, type yes in the dialog, and then reboot to recovery (not system). TWRP will now be useful.
6. If you are on 10f or 10h stock rom download this TWRP then mount vendor and system, flash the zip through TWRP to enable semi-persistant.
SUPPORT
If you need any help for this or in general or if you just want to have a chit chat, feel free to join our Telegram Group:
LG G7 ThinQ XDA Community Telegram Group
Others:
Official LG G7 Subreddit
LG Community Discord
CREDITS
Me (for the initial G7 TWRP device tree)
Rashed97 (for his great help to make me understand how recovery works on a/b devices)
Skullpluggery (for polishing the thread)
I hope i didn't forgot anyone , if i did im sry , hit me up and i will add you here.

Why is this TWRP semi persistent
So The g7 is a a/b device meaning it has 2 system paritions etc , but it doesnt have a recovery parition anymore so recovery is now a binary inside of boot.img which gets executed when hitting the button combo , but to have to you need to flash the boot.img containing it , and thats the point the boot.img containig twrp isnt compatible neither to aosp nor to stock meaning your phone would probably stuck in a bootloop or a reboot loop , so only thing we can do for now is flashing back our boot.img after were done with twrp, im working on it and i was able to smack twrp into the stock boot.img but it doesnt work correctly anymore then , I've finished my work on a variant that works without a pc needed

Persistance reached us , YAY
This is ONLY for AOSP OREO AND PIE flash this bootimage using fastboot flash boot_a pathtoimg or fastboot flash boot_b pathtoimg
Then TWRP will be always present no annoying flashes anymore

Can I flash normal zip files with recovery? because not everything is supposed to go.

Sony92 said:
Can I flash normal zip files with recovery? because not everything is supposed to go.
Click to expand...
Click to collapse
yes you can do everything once your decrypted , this twrp just wont stick

can someone please tell me if i have the buttons before warning that the bootloader is unlocked or after the warning? it's about booting to recovery after flashing the recovery.img. Unfortunately, I did not manage it yesterday.
should you flash at step 4 the file on the recovery, or via adb sideload?

hello mate long time no chat lol thinking of getting the g7 got one plus 6 at min will the fix for the one plus that makes the recovery stick work on this ?

will the error be corrected over time? because after the first reboot into the system the recovery disappeared again. I would like to boot again into recovery after being in the system, it no longer exists. I followed everything according to instructions

strikerdj2011 said:
hello mate long time no chat lol thinking of getting the g7 got one plus 6 at min will the fix for the one plus that makes the recovery stick work on this ?
Click to expand...
Click to collapse
damn youre still alive good to talk again , no that is only for the op6 , but this is my first work for a/b but meanwhile i got a main idea what to do , all i need rn is a linux machine

Sony92 said:
will the error be corrected over time? because after the first reboot into the system the recovery disappeared again. I would like to boot again into recovery after being in the system, it no longer exists. I followed everything according to instructions
Click to expand...
Click to collapse
thats what non persisrant mean youi always have to flash the recovery boot.img first

Great to know development is picking up on this device. Waiting for supplies to hit the rest of the world so I can get an European variant. ** Thumbs Up **

stupid question but does the locked bootloader on usa versions disallow booting unsigned images over "fastboot boot" command also?

just got a g7 what we going to cook up this year

strikerdj2011 said:
just got a g7 what we going to cook up this year
Click to expand...
Click to collapse
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do

J0SH1X said:
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do
Click to expand...
Click to collapse
**** that mate
---------- Post added at 07:49 PM ---------- Previous post was at 07:34 PM ----------
strikerdj2011 said:
**** that mate
Click to expand...
Click to collapse
J0SH1X said:
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do
Click to expand...
Click to collapse
whats going rate for a linux server

J0SH1X said:
Not much afaik, im missing a linux server to build stuff and noone is pickung up g7 for development exept me till now so there is not much to do
Click to expand...
Click to collapse
Hi.
As a developer, do you think it is possible enable HDMI out via kernel update?
https://forum.xda-developers.com/lg-g7-thinq/help/usb-c-to-hdmi-t3809408
Thanks.
Sent from my LM-G710 using Tapatalk

ricxgp said:
Hi.
As a developer, do you think it is possible enable HDMI out via kernel update?
https://forum.xda-developers.com/lg-g7-thinq/help/usb-c-to-hdmi-t3809408
Thanks.
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
no i cant build any kernel im no kernel dev also g7 kernel sources are badly broken they dont boot and give no logs so were out of luck

J0SH1X said:
no i cant build any kernel im no kernel dev also g7 kernel sources are badly broken they dont boot and give no logs so were out of luck
Click to expand...
Click to collapse
another year another ****ed up source from lg

J0SH1X said:
no i cant build any kernel im no kernel dev also g7 kernel sources are badly broken they dont boot and give no logs so were out of luck
Click to expand...
Click to collapse
Thanks.
It is a shame what LG does...
I am really thinking about sell the LG G7, I really like the phone but this kind of thing are shamelessl...
Sent from my LM-G710 using Tapatalk

ricxgp said:
Thanks.
It is a shame what LG does...
I am really thinking about sell the LG G7, I really like the phone but this kind of thing are shamelessl...
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
exactly my thought awesome device but zero support from lg even q6 with is mid/low got 8.1

[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