{
"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
Related
I made advanced stock kernel and TWRP for Xperia X Compact.
I don't have X Compact, so there will be no further update.
Please don't ask for update.
Advanced stock kernel
-For 34.1.A.1.198
-ric, dm-verity disabled
-DRM patch from tobias.waldvogel
-SELinux Permissive
-Load recovery from recovery (FOTAKernel) partition
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8bl9xbEFxN1N1Vkk
TWRP 3.0.2
-Fully supports decryption
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
1. Reboot into recovery or bootloader
2. Extract boot.img from zip and run this command in fastboot mode:
fastboot flash boot boot.img
If you have no recovery, you also need to flash recovery by this command:
fastboot flash recovery TWRP-3.0.2-2-F5321.img
3. Reboot
4. Done!
* Press volume up or down key when LED is orange to enter into recovery
Kernel source:
https://github.com/AndroPlus-org/android_kernel_sony_msm8956/tree/34.1.A.1.198
Device tree for TWRP:
https://github.com/AndroPlus-org/android_device_sony_kugo
PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S2LALLRARKTKC
Credit:
tobias.waldvogel for awasome DRM patch,
nilezon for boot script
Snow_Basinger for testing
and big thanks to other people involved including Sony and TeamWin
AndroPlus said:
I made advanced stock kernel and TWRP for Xperia X Compact.
I don't have X Compact, so there will be no further update.
Please don't ask for update.
Advanced stock kernel
-For 34.1.A.1.198
-ric, dm-verity disabled
-DRM patch from tobias.waldvogel
-SELinux Permissive
-Load recovery from recovery (FOTAKernel) partition
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8bl9xbEFxN1N1Vkk
TWRP 3.0.2
-Fully supports decryption
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8YWJsVGZTc0ZhZUE
1. Reboot into recovery or bootloader
2. Extract boot.img from zip and run this command in fastboot mode:
fastboot flash boot boot.img
If you have no recovery, you also need to flash recovery by this command:
fastboot flash recovery TWRP-3.0.2-2-F5321.img
3. Reboot
4. Done!
* Press volume up or down key when LED is orange to enter into recovery
Kernel source:
https://github.com/AndroPlus-org/android_kernel_sony_msm8956/tree/34.1.A.1.198
Device tree for TWRP:
https://github.com/AndroPlus-org/android_device_sony_kugo
PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S2LALLRARKTKC
Credit:
tobias.waldvogel for awasome DRM patch,
nilezon for boot script
Snow_Basinger for testing
and big thanks to other people involved including Sony and TeamWin
Click to expand...
Click to collapse
this is only for unlocked bootloader?
x10isrooted said:
this is only for unlocked bootloader?
Click to expand...
Click to collapse
yes.
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
mesajoejoe said:
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
Click to expand...
Click to collapse
To root, just install SuperSu zip in TWRP (search it)
mesajoejoe said:
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
Click to expand...
Click to collapse
So I think you unlocked the boot loader using the service delivered by Sony, correct? Okay...
But how did you deal with the DRM security keys (TA partitions)? If I get that right within the TA partition there might be some key information which could affect advanced camera functionality? Did you get a backup of the TA partition before unlocking the bootloader?
Thank you for support!
fl3xx said:
So I think you unlocked the boot loader using the service delivered by Sony, correct? Okay...
But how did you deal with the DRM security keys (TA partitions)? If I get that right within the TA partition there might be some key information which could affect advanced camera functionality? Did you get a backup of the TA partition before unlocking the bootloader?
Thank you for support!
Click to expand...
Click to collapse
You don't need to backup TA (at least when you are using) since DRM patch solves camera functionality problem.
has anyone tested this? It basically means we can:
1. unlock the bootloader
2. flash twrp recovery
3. flash this kernel
4. flash superuser
and we have a rooted x compact with working drm (at least some of it).
Is that correct?
charliebigpot said:
has anyone tested this? It basically means we can:
1. unlock the bootloader
2. flash twrp recovery
3. flash this kernel
4. flash superuser
and we have a rooted x compact with working drm (at least some of it).
Is that correct?
Click to expand...
Click to collapse
In theory yes. Though I cannot flash the superuser zip, nor can I mount anything in TWRP at the moment. Before unlocking boot loader and flashing this, I flashed UK for fingerprint sensor so that may be the reason. Tomorrow I plan on testing more.
Sent from my HTC 10
mesajoejoe said:
In theory yes. Though I cannot flash the superuser zip, nor can I mount anything in TWRP at the moment. Before unlocking boot loader and flashing this, I flashed UK for fingerprint sensor so that may be the reason. Tomorrow I plan on testing more.
Sent from my HTC 10
Click to expand...
Click to collapse
Good luck and keep us posted!
charliebigpot said:
Good luck and keep us posted!
Click to expand...
Click to collapse
No luck. It won't install the superuser.zip. In TWRP everything is red, can't mount anything. Can't see internal SD from TWRP, can't format anything. I went back to Customized US from xperifirm and re-flashed kernel and TWRP. Not sure what to do.
{
"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"
}
mesajoejoe said:
No luck. It won't install the superuser.zip. In TWRP everything is red, can't mount anything. Can't see internal SD from TWRP, can't format anything. I went back to Customized US from xperifirm and re-flashed kernel and TWRP. Not sure what to do.
Click to expand...
Click to collapse
hmm, can you upload full log (tmp/recovery.log)?
I confirmed this works on F5321 but maybe there's some difference in US.
AndroPlus said:
hmm, can you upload full log (tmp/recovery.log)?
I confirmed this works on F5321 but maybe there's some difference in US.
Click to expand...
Click to collapse
Here ya go.
mesajoejoe said:
Here ya go.
Click to expand...
Click to collapse
Can you check if there is /dev/block/platform/soc/7824900.sdhci ?
e.g.
Code:
ls -l /dev/block/platform/soc/7824900.sdhc
AndroPlus said:
Can you check if there is /dev/block/platform/soc/7824900.sdhci ?
e.g.
Code:
ls -l /dev/block/platform/soc/7824900.sdhc
Click to expand...
Click to collapse
Two things exist there. 7824900.sdhci and 7864900.sdhci Thank you BTW for looking into this. Root access is the only thing holding me back from using this device.
Sent from my HTC 10
mesajoejoe said:
Two things exist there. 7824900.sdhci and 7864900.sdhci Thank you BTW for looking into this. Root access is the only thing holding me back from using this device.
Sent from my HTC 10
Click to expand...
Click to collapse
Thank you, I'll rebuild TWRP later with "7864900.sdhci".
I don't know why there are two path, but 7864900.sdhci should be right path for your device.
oops it was for sdcard...
AndroPlus said:
Thank you, I'll rebuild TWRP later with "7864900.sdhci".
I don't know why there are two path, but 7864900.sdhci should be right path for your device.
oops it was for sdcard...
Click to expand...
Click to collapse
Let me know if there's anything I can assist with.
mesajoejoe said:
Let me know if there's anything I can assist with.
Click to expand...
Click to collapse
Can you try this version?
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
AndroPlus said:
Can you try this version?
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
Click to expand...
Click to collapse
Appears to be working. I have mounting access in TWRP, flashed superuser.zip without issue. Thanks!
Well it was kind of working. On US firmware root was functioning but when switching over to UK it stopped. Since then I have not been able to regain root access on US or UK. After flashing the superuser.zip it just hangs on the Sony logo. I've gone back and forth between US and UK, but no luck. TWRP is having issues unmounting /system... not sure if that gives anyone any insight. I'm probably just going to leave it without root access for now. Appreciate your help!
Does it work on CE version
Hey everyone
Can anyone confirm that it works on CE software Version.
Unlock BL is allowed.
Thanks in advance.
{
"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.
[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
This is the Xiaomi Mi A2 Lite's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Yay ^_^ Thanks for the efforts Respected devs. Hope it makes life way easier for people here at the community ^_^
unlock bootloader and root still delete all of my files right?
machine1104 said:
unlock bootloader and root still delete all of my files right?
Click to expand...
Click to collapse
Yes
Xiaomi Mi A2 Lite got messed up
Hi there!
I have just received my new Xiaomi Mi A2 Lite phone and wanted to pass all of my data from my old phone to it in a way that it was required to be rooted.
KingRoot didn't work on this new phone, so I unlocked bootloader and tried to install TWRP recovery on my phone.
Installing to the recovery partition did not work. I searched the error it gave me and found a thread saying that flashing it to the boot partition worked for them. So I did. Next thing that happened is that my phone did not boot into the OS (operating system) ever again. It only booted TWRP.
I have since been able to remove TWRP (though I made a back up of it) but the phone still stays on just the loading part before going to the OS.
I have since been able to get back the fastboot and stock recovery, but the phone will not start into the OS anymore.
How can I fix this?
I have been searching for ways to restore my android to the 8.1 Oreo version that it was.
Can I do it with this Tool All In One? Please help! Thank you in advance!! Much appreciated!!
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
chillout23 said:
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
Click to expand...
Click to collapse
If you need to flash twrp and root.no, you will not lose data
Ok. Thank you very much for answer
Then will try
chillout23 said:
Ok. Thank you very much for answer
Then will try
Click to expand...
Click to collapse
I would suggest using the root method mentioned here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Twrp does not have good results for most people.
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
chillout23 said:
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
Click to expand...
Click to collapse
If your bootloader is unlocked, you should not lose any data just installing magisk
Yes...my fault. My BL is unlocked already.
But I posted in that thread...because of some reason does not work. But this is not thread about it
Thanks for help
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
chillout23 said:
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
Click to expand...
Click to collapse
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
uptowner said:
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
Click to expand...
Click to collapse
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
uptowner said:
Because your not supposed to install the twrp image just boot from it
Click to expand...
Click to collapse
Installed TWRP image. I know what is .img
mauronofrio said:
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
Click to expand...
Click to collapse
oops sorry i should check what thread this is before trying to answer a question i blame alcohol .
Thing is there are posts out on the net that advices people with the a2 lite to install the twrp image to their inactive slot and not to just boot it and that's where things seem to start going wrong.
This has absolutely nothing to do with this tool and sorry i just dived in here and confused people.
maybe some kind passing mod will get rid of the post apologies again
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
mesuahas said:
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
Click to expand...
Click to collapse
Read the op follow it exactly how it says if u don't know something research it.i have root with no problems if u do as the op says u shouldn't have no problems
Will this work on pie at all?
I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well looks like I can go into the bootloader but if I choose recovery mode it just goes back to the "Device is corrupt screen".
toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I don't have a backup of the tmobile rom :/ I think we ned the modem files from the tmobile version, which would be on my phone yet if I could acess them? The last time I did anything with a phone was the OP6 I'm out of my depth...
hiryupd said:
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I dont have a backup of the tmobile rom :/ The last time I did anything with a phone was the OP6 Im out of my depth...
Click to expand...
Click to collapse
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom
toyanucci said:
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom
Click to expand...
Click to collapse
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/
hiryupd said:
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/
Click to expand...
Click to collapse
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember
toyanucci said:
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember
Click to expand...
Click to collapse
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....
hiryupd said:
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....
Click to expand...
Click to collapse
I got it done with the 7T so it can be done and if you had restored the stock boot image with magisk before you uninstalled it then you are stock, just with an unlocked bootloader.
Re updates, again if you have the stock boot.img restored you'll get Ota updates just fine.
hiryupd said:
I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.
Click to expand...
Click to collapse
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.
inspron said:
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.
Click to expand...
Click to collapse
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?
hiryupd said:
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?
Click to expand...
Click to collapse
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.
hiryupd said:
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.
Click to expand...
Click to collapse
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Well system update always comes back saying it has a problem and cant update. Also yea after I relocked It has a dialogue asking if im sure because it will do a full wipe, just like when I unlocked it. But instead of doing the full wipe it booted into that red text about being corrupt. So right back here again
toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
I wish I had seen this part prior. I flashed img about 3 weeks ago prior to this method was known to me.
toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.
inspron said:
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.
Click to expand...
Click to collapse
I exported them a while ago on a thread, we just moved our company so i dont have those systems and drives set up for me to get on server. We unbrick and all that fun stuff. If you have a telegram send me the info. & ill add you to try to resolve your issue.
Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...
oh
hiryupd said:
Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...
Click to expand...
Click to collapse
if that's the case you can flash with official build, and then you can add the t-mobile bloatware if you want.. Which i take it off most phones by request.
Official Build (Direct DWLOAD)
(Stock - Boot.img (Direct DownL)) Instead if easier...
If you really want the bloatware back that makes T-Mobile T-Mobile then.. here ya go..
pm install -k --user 0 com.mobitv.client.tmobiletvhd
pm install -k --user 0 us.com.dt.iq.appsource.tmobile
I want T-Mobile Boot Up Animation! I Want People to know im using T-Mobile!!
Here ya go, "https://www.hongkiat.com/blog/change-android-boot-animation/" - Add Sound even
{
"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"
}
I Hope this helps ya mate ..
You can also use these files I built to follow this post too if you need more help.
BACK TO STOCK 1+9