Develop Bugs

BLU Life One X 2016

My goal for this thread is to gather as much info for the BLU Life One X 2016.
Specs
Screen: 5.2", 1080 x 1920 pixels, ~424 ppi, Gorilla Glass 3
Memory: 2 GB RAM, 16 GB storage, microSD slot (up to 64GB)
Camera: 13 MP rear, 5 MP front, LED flash front & rear, [email protected] video
Battery: Li-Ion 2900 mAh
Chipset: Mediatek MT6753
CPU: Octa-core 1.3 GHz Cortex-A53
GPU: Mali-T720
Model: L0070UU
Links & Other General Resources
BLU Products
Amazon: Black - White
GSMArena
BLU Products Development Team (Google+)
L0070UU User Manual
ClanGSM claim to have firmware files for our phone but it would cost $$$ to download: / mnt / data / ftp / Flashes / BLU / Life One X / L0070UU /
Similar Phones
Wiko Fever (GSMArena)
Micromax Canvas 5 (GSMArena)
XOLO Black 1X (GSMArena)
Elephone P8000 (CM12.1) and P6000 Pro
Quantum Go 4G (PhoneMore)

WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Note: While I use a variety of operating systems on a regular basis everything here will be Windows 10 focused.
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
Drivers
I recently setup a 5th gen Kindle Fire 7" tablet on my Windows 10 desktop. Because the BLU Life One X 2016 and the Kindle Fire are similar enough it just worked. To use the Amazon drivers you can find them on this page: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing. The direct link is https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip. Extract the zip file and then run KindleDrivers.exe.
Unlock Bootloader, Install Custom Recovery, and Install Root
Note #1: All credit for this guide goes to manos78's post for rooting the Wiko Fever!!! You can check it out here.
Note #2: I use Windows 10 on every PC I own. I assume Windows 7 and 8 should work just fine but cannot test that.
Note #3: The following assumes you have setup ADB and the proper drivers before beginning. I will try to detail that at a future time.
Note #4: Your phone will be completely erased. If there is anything you want to save do so beforehand.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
2) Install Custom Recovery
Note #1: We will flash a version of CWM or TWRP that was built for a Wiko Fever as they appear to be fully compatible with the BLU Life One X 2016. Go to this thread and download the latest CWM (http://www.sendspace.com/file/4g87bj) or TWRP (http://www.sendspace.com/file/y4jel8). Extract the img file. Again, many thanks to manos78 for CWM and hanuma for TWRP!!!
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img
Type fastboot reboot
Note: If your phone does not reboot then just hold the power button until it turns off. Hold the power button again until it turns back on.
3) Install Root
Note: While there are newer beta versions of the SuperSU app I am not sure if they will work properly on our stock rom. You can test one of those out and report back but I would recommend you do a full backup beforehand.
Download BETA-SuperSU-v2.52.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in CWM. Go to Install zip, find BETA-SuperSU-v2.52.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Xposed
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Mine rebooted like five times during the "Android is starting" step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
ViPER4Android
ViPER4Android adds audio effects to your Android device and is beloved by many. First we will install SELinuxModeChanger and then ViPER4Android. Special thanks to Tha Watcher for his original write-up here.
1) SELinuxModeChanger
Go to the SELinuxModeChanger page on F-Droid, download the latest version (3.2 as of this writing) or use this direct link, and save it to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\com.mrbimc.selinux_42.apk
On the phone you may see a prompt saying Installation Blocked. If so, click the little triangle and tap Install anyway (unsafe). If you see a failure just do it again and it should work.
Launch the SELinuxModeChanger app on your phone, grant it root permissions, and click Permissive
Note: If you have any issues with SELinuxModeChanger then head over to the XDA thread.
2) ViPER4Android
Download the latest version in zip format from here and extract ViPER4Android_FX_A4.x.apk to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\ViPER4Android_FX_A4.x.apk
Launch the ViPER4Android app on your phone, click Yes when prompted, click Super Audio Quality, and then click OK
Grant root access when prompted
Click OK
Reboot your phone
Note: Once your phone reboots you can start configuring ViPER4Android. I cannot really help much with that but feel free to look over the official XDA thread or their Settings Explained page on the official website.
Engineering Mode
Note: If I were you I would not change anything unless you absolutely know what you are doing!
I cannot seem to get the phone codes to work. You can install the MTK Engineering Mode app from the Google Play Store.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!

Frequently Asked Questions
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
MTK Droid Tool
MTK SP Flash Tool
Latest Version: 5.1548.00.000
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!

WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Q: How can I tell if my model is the BLU Life One X 2016?
A: Go here and see if it is the same model.
Q: When I try to use adb root I get the following error: adbd cannot run as root in production builds
A: You can purchase and install [root] adbd Insecure by Chainfire. Once installed, launch the app, grant it root access, and then check Enable insecure adbd and Enable at boot
Q: How do I (re)mount /system as read-write?
A: Install [root] adbd Insecure as mentioned above, open a Command Prompt, type adb root, and then adb remount rw
Q: How can I disable the audio that plays when starting up or shutting down my phone?
A: Using a file explorer with root access, or an adb shell, delete or rename (with .bak at the end) /system/media/bootaudio.mp3 and /system/media/shutaudio.mp3 and then reboot your phone.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!

Reserved #4

Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.

Has anyone been brave enough to try this yet?
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
I'm receiving my phone tomorrow so i might be the guinea pig...lol

Did this last night on my phone. Most difficult part for myself was finding the correct drivers as this is my first mediatek device. Ended up being my fifth attempt that had the correct set.
After I had the drivers it was extremely similar to a nexus process.

Do you have a link to the drivers
Sent from my 6045X using Tapatalk

I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.

OK thanks
Sent from my 6045X using Tapatalk

I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.

SCrid2000 said:
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Click to expand...
Click to collapse
Unfortunately the guy that was bringing up the elephone p8000 has sold it and subsequently not be supporting it any longer. I'm happy enough there is custom recovery options and root. An AOSP ROM would be nice, but naturally the custom gestures would be lost.

jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.

hottcakes said:
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
Click to expand...
Click to collapse
I was trying to using the link to download the driver, but the mega site asked for "decryption key" before I can download. Is there a key available to share? Thanks,

Tha Watcher said:
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
Click to expand...
Click to collapse
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,

clu1688 said:
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
Click to expand...
Click to collapse
I appreciate that but the only way I'd post it in this thread is if the OP says it's fine. I do not like hijacking or taking over other people's threads.
It sounds like ADB is actually not loaded or working on your computer or otherwise you wouldn't get that message. I could be wrong, though. To test to see if it is indeed working and drivers are properly loaded, what does it respond when you type: adb devices

SCrid2000 said:
Have you tried porting the Elephone rom for the Blu?...
Click to expand...
Click to collapse
Not yet, but I do plan to try to start with that. It's nice that Elephone released the source code for the P8000 so that could help as well. If I ever get to this I will need lots of help.

jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
Everything that *I* post in the OP will be something that I tested on my own device first unless I specifically mention otherwise.

hottcakes said:
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
Click to expand...
Click to collapse
I will add a note about that but some of us had issues so I chose the alternate method that has worked for me the first time every time.

Root and Install TWRP on Moto G4 Plus

Hello everyone.... There is no specific post on rooting and unlocking the bootloader here so I thought I'd rather post it....
So let's begin....
mod edit as per original author

Have U Tested it ?????
Does it Work ????
or Just Posting without results ?

Bootloader unlock works.... but I'm still working trying to make Lucky patcher work to confirm root access

cool_sid said:
Bootloader unlock works.... but I'm still working trying to make Lucky patcher work to confirm root access
Click to expand...
Click to collapse
Dont Post Threads which leads to disasters !!!
confirm first and make it live. !!!

No disaster buddy.... you don't understand.... it all works but since I don't have busy box.... it doesn't work for lucky patcher... I'll just install it n also send screenshots of my root access with Root Checker.....
OK?

cool_sid said:
No disaster buddy.... you don't understand.... it all works but since I don't have busy box.... it doesn't work for lucky patcher... I'll just install it n also send screenshots of my root access with Root Checker.....
OK?
Click to expand...
Click to collapse
install root checker nd send it. !!
they dnt need busybox.
and y care for luckypather btw ?

It doesn't work with supersu. Already tested by @yeshwanthvshenoy and phone bootlooped.
Sent from my Moto G (4) using Tapatalk

I don't understand why you people say it.... it booted on my Moto G4 Plus.....

cool_sid said:
I don't understand why you people say it.... it booted on my Moto G4 Plus.....
Click to expand...
Click to collapse
cause after 6.0+ need modifided boot.img

Bootloader unlocked, TWRP done..
Now im doing backup for in case of someting goes wrong... im about to flash superSU and i will tell you if yes or no.. im doing the sacrifice !! LOL

cool_sid said:
Hello everyone.... There is no specific post on rooting and unlocking the bootloader here so I thought I'd rather post it....
So let's begin....
What you need:
1) Laptop/PC with Internet running Windows
2)Moto G4 and Moto G4 Plus USB driver,?*Minimal ADB, and Fastboot tool driver.
3) USB cable
4) Patience
How to unlock the?*bootloader of Moto G4 and Moto G4 Plus
a) Before proceedings make sure that your device is at least 70% charged.
b) Enable USB Debugging by going into Setting> About Phone and tap on build number for 8 times. This should unlock Developer Options. Now get into Developer Options and enable USB Debugging.
c) Install?*Minimal ADB,?*Fastboot Tools, and?*Moto G4 or Moto G4 Plus Driverson your PC.
d) Now go to the folder where Minimal ADB & Fastboot Tools are present (must be somewhere in C drive). Now open Command Prompt by pressingShift Key + Right Mouse Button?*and select Open Command Window here.
e) Now switch off your phone. Then press Volume up + Power Key together. You will get into Fastboot Mode. Now connect it to the PC via USB cable.
f) Now type the following command into the Command Window to check if your phone is properly connected and is detected by PC or not.
fastboot devices
g) Now you need the unlock data to unlock the bootloader. Type the following command into the Command Window
fastbootoemget_unlock_data
h) It will display a long string which you need to copy into notepad, remove all the spaces which are present and save it somewhere.
i) Now go to?*Motorola official website. Create an account if you don’t have any. Log in to the account and go to the Unlock Bootloader option and paste the string which you copied in the notepad earlier.
j) Now click on Can my device be unlocked. Select I Agree and then Request Unlock Code. You should receive a mail from Motorola with similar codes within few minutes.
k) Now copy those codes, open Command Window and type the following commands
fastboot OEM unlock (insert the code without braces)
l) Now you have successfully unlocked the bootloader and now you can install recovery.
Though it's pretty much sufficient but if you ask... I'll post some screenshots of the process as well......
Don't hesitate to ask if stuck anywhere....
???????? Install TWRP ON MOTO G4 PLUS
To install TWRP on moto G4 Plus... Refer to this XDA link
https://www.google.co.in/url?sa=t&s...mQxu4hgzMGQnN1dQQ&sig2=BEagC-mbHleWiRHg85zLyA
How to root Moto G4 And Moto G4 Plus
a) Download?*BETA-SuperSU.zip ?*file and place it into the root of your memory card (Attached along)
b) Get into recovery mode by pressing Power + Volume Down button.
c) Once you are in recovery select Install from SD card option and browse the SuperSU.zip file. Select Yes to install and wait until the flashing is done.
d) Now select Restart option from the recovery and wait for the device to boot up.
Go to Google Play and download the Root Checker app to check the root status. If root checker app says root access available then Enjoy you have rooted your Moto G4 and Moto G4 Plus.
Now you have ROOTED and have installed a custom recovery on your Moto G4 Plus....
Just Hit the thanks if you like the post
Ask me for screenshots if you want them (forgot to take them but will get them u want).......
Click to expand...
Click to collapse
I have no idea how this thread is different from the one over here : http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584/
If you have found the way to root, post it there itself or in the Chainfire's thread, why bother creating a new thread to teach people the same thing again and again? Please try searching before posting.
And these lines my friend clearly say you didn't even attempt to search through :
cool_sid said:
Hello everyone.... There is no specific post on rooting and unlocking the bootloader here so I thought I'd rather post it....
So let's begin....
Click to expand...
Click to collapse

Aaaand it doest work.. my phone was frozen on the motorola logo ..

Sorry m8.... considered...... I didn't know that there was another similar post about moto g4 plus

Is this same for 16 and 32gb versions?

yash989 said:
Is this same for 16 and 32gb versions?
Click to expand...
Click to collapse
both version r same.
but this is risk.
do it on ur own risk.

Closing down thread. Please don't make anyone here as a guinea pig.. Prove it yourself first before releasing the tutorial to the public. You are just causing too much harm..

{Help} Adding Dual boot patcher support

Being an avid user of Multirom with TWRP on my now dead LG Optimus G, I couldn't deal with the fact there is no multi boot option for my Honor 8 pro. So, I did some research and came to know that "Dual boot patcher" is the preferred solution to boot multiple roms at the moment. Thankfully, the project turned out to be open source and the developer has a well documented Git with information required to add support for new devices. I tried following the dev's guide found here https://github.com/chenxiaolong/DualBootPatcher/wiki/How-to-add-new-Devices-to-DualBootPatcher%3F by flashing the provided zip file. But it did not create any log files in the internal storage. So, if any of you happen to be in stock rom and are willing to help, kindly flash the file found in the above URL and upload the results. I'll proceed with the further steps. Thanks.

Will be glad to help. Can you explain in step-wise format on what to do. Any prerequisites other than a twrp recovery.

NIKHIL JOHN said:
Will be glad to help. Can you explain in step-wise format on what to do. Any prerequisites other than a twrp recovery.
Click to expand...
Click to collapse
Thanks for taking interest in this. To test it out, you will need a device with unlocked bootloader with twrp recovery installed. Also, I believe (not sure though) that file encryption needs to be disabled for this to work. To check file encryption state, go to
Settings → Security & Location → Encryption & Credentials & it shows phone encrypted
or
Use adb command
Code:
adb shell getprop ro.crypto.state
( works on unrooted devices also) returns encrypted or unencrypted
As far as flashing is concerned, it is pretty straight forward. Just download the zip file mentioned in the above post and transfer it to either internal storage or SD card. Boot into TWRP recovery and flash the zip file. If you need any help during the process, feel free to ask.

Andromann said:
Thanks for taking interest in this. To test it out, you will need a device with unlocked bootloader with twrp recovery installed. Also, I believe (not sure though) that file encryption needs to be disabled for this to work. To check file encryption state, go to
Settings → Security & Location → Encryption & Credentials & it shows phone encrypted
or
Use adb command
Code:
adb shell getprop ro.crypto.state
( works on unrooted devices also) returns encrypted or unencrypted
As far as flashing is concerned, it is pretty straight forward. Just download the zip file mentioned in the above post and transfer it to either internal storage or SD card. Boot into TWRP recovery and flash the zip file. If you need any help during the process, feel free to ask.
Click to expand...
Click to collapse
Hey buddy sorry for the late reply. My phone was bricked so had to get it fixed. Now my phone is updated to Andriod Oreo. Will try to root again and Follow the procedure. It would be helpful if you can give me your whatsapp number because i kind of mess things up and it takes a long time for me to get my phone back up and going. It would be helpful if you can assist on the way.

[GUIDE] LineageOS 17.1 ROM for Galaxy A50 Android 10 Q

The phone must be installed TWRP Recovery. Use at your own risk, I'm not responsible for bricking your device.
Installation Instructions:
1. Enter TWRP Recovery Mode: Turn power off; Press and hold Volume Up key + Power key, when samsung logo appears release power key only, keep pressing volume up until TWRP recovery appears
2. Select Wipe - Format Data - type "yes" and confirm
3. Copy GSI ROM to your phone
4. Install - Install Image - select lineage-17.1-20200413-UNOFFICIAL-treble_arm64_bvN.img - select System Image and Confirm to flash.
5. Select Reboot - System ( boot without magisk )
6. Setup the Phone
7. INSTALL GAPPS: Enter TWRP Recovery Mode
8. Copy GAPPS zip file from PC to Phone
9. Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize.
10. Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
11. Reboot - System
12. ROOTING: Enter TWRP Recovery Mode
13. Copy magisk manager apk from pc to phone
14. Reboot to Recovery ( boot with magisk )
15. Connect the phone to internet
16. Install magisk manager
Done!
Download:
LineageOS 17.1 ROM
Open Gapps
WATCH VIDEO HOW TO INSTALL IT: https://youtu.be/u9gDx6VEORo

Thanks. So this is GSI? Bugs?

Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN

Hello everyone
iam in the Process of considering to put LOS on my device.
But the i saw the remarks from InFam0us-1985
Is it therefor not adviceable to use this on a Samsung Galaxy A505FN because this is exactly what i have
Saludos from Spain

DId i Brick my Samsung Galaxy A505FN?
Hello one Question:
"did i Brick my device if for some reason after Trying to flash TWRP it fell back in to OEM-locked and i’ am now in a Boot Loop, ore is the any Hope?
I used Heimdal and at first it did the Job but then it would not start again as expected.
After some attempts to flash it Properly it suddenly fell back in to OEM-Locked!
Pleas if you now some advice it be greatly aprichiatet
My device is a Samsung Galaxy A505FN (Spain)

I found a way to Unbrick my device
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans

hans2020 said:
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
Click to expand...
Click to collapse
AFAIA, OEM locked you can always flash stock?

I’ am not sure if thats True
InFam0us-1985 said:
AFAIA, OEM locked you can always flash stock?
Click to expand...
Click to collapse
All i know in case of my Samsung Galaxy A50 it is Possible!
To lift the OEM-Lock mode again.
i do not know if that is true for every Device.
Ultimately i was successful to install full Root-access!
I had great difficulty tho to use Heimdall ore any tool on Linux so i ended up using Odin in a VirtuelBox with WinXPpro
but do to no support of Long file names i had to trick there, to to make it work.
I just shorten the Names of every .tar to the first 2 letters.
I was able to successfully flash TWRP with Heimdall but not the Android ROM for my Phone.
I still wonder how to make it work!
There was one Thing i Noticed when Using Odin it seams in the Process he flashes vbmeta.img twice.
That impossible with Heimdall it creates a error message.
Well if anyone - that passes here - knows how to flash a Android 10 ROM of a Samsung Galaxy A50 using Heimdall let me know i tried very very hard to no avail.
I was surprised to learn there is no Good Tool for Linux-user doing this Task.
i only found Old Tutorials!
Is it truly possible that Heimdall dose not support modern Phone-flashing anymore properly?
As of now if a Linux-user ask me about Rooting i would advice him/her to do it in a VritualBox with windows installed.
If you have a License of a Windows Version Higher then XP good otherwise you have to Shorten File names if the very long to make it work.
I scarcely use windows anymore that why i only have a old WinXPpro legally in my Possession.
Unbelievable that the Linux-Community should not have a modern Flash Tool!???
Saludos
Hans
---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------
Hello to @everyone
I had great difficulty to do this as a Linux User using Heimdall and eventually had to give up (after trying for 3 full days)!
I ended up doing it using Windows out of a VirtualBox!
It was Possible tho to successfully flash TWRP using Heimdall!
It also showed Success when Flashing Android 10 Version for my Phone but would not work.
Using the same Firmware with Odin it worked just fine.
When i compared the Flash-Protocol of Odin with what i did i only Noticed that Odin would flash vbmeta.img twice in the Process something that cant be done with Heimdall as it produces the duplicate error.
I wonder if this is the Reason it would not work.
I was also surprised to Learn, that there is virtual now Tutorial out there using Heimdall on a Modern Phone (last 12 Month ore less).
Is it truly Possible that There is now good solution for Linux Users?
I also Looked in to Fastboot and ADB and other Tools for Linux Platform and they all seam to be outdated!
Also all this Tools could not accomplish the task at hand.
Now if its me and anyone knows how to make it Work on Heimdall let me know as it is a Pretty good tool after all and by now i know it well. I would gladly start to make a tutorial and provide it here for free if i know how to make it work.
I have a txt file where i made a complete Protocol of all i tried if someone is curious ill send it to you.
Saludos Hans
##################################################################
I send some more Details of my Challenge in hope someone my know what it is i have to change!
My Device:
Samsung Galaxy A505FN
I created a .txt file protocol of all i did, i gladly provide it if someone ants to see it.
I analyzed the Whole Firmware-archive and the Pit file of my Phone to eventually find the Problem.
Note:
The Firmware was the correct one as it worked just fine using Odin!!
Analyzing all this, i only noticed two things:
First:
There are 3 seemingly identical files in the Archive and two so called
fota.zip files witch are not Identical
(one in the AP-Packet and one in the CSC-Packet)
Those where:
– cache.img one in the AP-Packet and one in the BL-Packet
– vbmeta.img one in the AP-Packet and one in the BL-Packet
– product.img one in the AP-Packet and one in the BL-Packet
Second:
Once i used Odin to finally flash successfully i noticed that in the Flash-protocol of Odin it seams Odin flashes the vbmeta.img twice in the process!?
Heimdall would not allow me to do so giving me the “Duplicate Error message”
Furthermore i tried one more thing in my desperation to make it work:
i thort: “maybe the order in wish the files a flashed chronologically matters”
So i did exactly that, trying to flash in the same chronological sequence as Odin did.
Note:
Every time i flashed, Heimdall would successfully finish the process but the Phone would not start with android
no matter what i tried.
ALSO i did successfully flash TWRP to my Phone using Heimdall
SO Heimdall works just fine on my system!
I spend a Long Time searching the Internet for a workable Tutorial or glue’s as to what is missing and how i could make it work.
I really want to succeed doing this, as i want to provide my folks offer her in Germany and also English and Spanish speaking Linux-Community with a Tutorial to do this!
I did also drop this Question and Challenge i face in some other Forums no useful answer returned so far
The latest Governmental Abuses and infringement on Peoples Privacy using Corona as excuse, makes it abundantly clear how important this kind a work is!
As for now i think, the only true option for a Linux-User is to run Odin from a Virtual-Box Windows installation, given
you have a legal copy in you're possession and have higher then Windows XP
(else you must change the Filenames of the .tar archives as WIndows XP and lower did not support excessively long filenames.)
Also you have to Install you're Phone USB drivers and have them up and running properly!
Internet access to you're VB makes it all more comfortable, but you can also use Shared folders with the Host-System to do the job.
Note:
I did indeed tried the "WINE-plugin-environment" (Windows 10) under Linux. i could not get it to work.
It was to much messing around make it recognize the USB-connection to the Phone!
I could not get it to work, I don't know if you can?
I guess that would be a nice way for Linux-users if it could be made to work!
What do you guys think, can this be solved?
Pleas let me know if you know the answer to my Challenge!
You're help is not only needed but would be greatly appreciated
Sincerely yours
Hans from Germany

well I Found this from 2017;
Yes you can do fastboot and adb cmd in Linux but you have to install adb and fastboot drivers to Linux by using
1) sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
2) sudo apt-get install android-tools-adb android-tools-fastboot
That's it you get your fastboot and adb cmd’s all the cmds are same just as windows just you need to add sudo in front if not in root
Click to expand...
Click to collapse
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/

Well i do know
Of course i know how to Install a Software on Linux and i did indeed installed those Two
But both of them would not even Detect my device jet Heimdall and Odin had no problem doing that.
Anyhow i might go about and try those Two harder.
And no Iam not confused
thank you anyway
Saludos Hans
InFam0us-1985 said:
well I Found this from 2017;
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Click to expand...
Click to collapse

I cant call or receive call and send and receive messages via sim
Please help
I cannot call and receive calls
Cannot send and receive messages ,one time passwords, through message
Cannot login through whatssapp .
volte is not enabled
And no option for it to enable
I am from India using jio sim card .
Please help.
If any custom rom is used in my SM-A505F i cant do calls or receive calls nor send or receive messages.
country id : INS
Original firmware of A50 : Atb6

Will this image work with the SM-A505G version?

USB File Transfer Does Not Work
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?

OmariCelestine said:
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
Click to expand...
Click to collapse
This is what you get with a GSI, finger print wont work either.

InFam0us-1985 said:
This is what you get with a GSI, finger print wont work either.
Click to expand...
Click to collapse
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.

OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
Try with a custom kernel

the project is down? Because I love LineageOs, but the A50 is abandoned :/
---------- Post added at 06:06 AM ---------- Previous post was at 05:57 AM ----------
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
you need to run into Twrp and it work. But only in TWRP

hey man, the project is being upgraded? Tanks for your time

InFam0us-1985 said:
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Click to expand...
Click to collapse
Got the same problem here. i guess i'm staying on the stock firmware

I have installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_bvS.
Fingerprint and MTP working.

[YT-X705F,X,L]Unlock bootloader of Lenovo Yoga Smart Tab and root it

DISCLAIMER​* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.​PRE REQUIREMENTS:​- SDK Platform-tools (Get it here)
-boot.img from Stock Rom
-Patience
LET'S BEGIN!
Extract the SDK Platform tools folder to an easily accessible directory
UNLOCKING THE BOOTLOADER​NOTE: THIS WILL ERASE ALL DATA FROM YOUR DEVICE SO MAKE SURE TO TAKE A BACKUP IF NECESSARY
-Extract the SDK Platform tools folder to an easily accessible directory
- Go to Settings > About Tablet > Tap build number 7 times. Go back to main page of Settings > System > Developer
options and enable OEM unlocking and USB Debugging
- Reboot the system to bootloader (Press Vol - and Power key or type "adb reboot bootloader" by opening a command prompt window in Platform tools directory)
- To unlock bootloader type the below code
fastboot flashing unlock
- The device will do a factory reset and restart itself
-After Setting up your device install the magisk app from here
ROOTING [MAGISK]​METHOD-1 (FASTBOOT)​- Transfer your boot.img to Internal Stroage
- After installing the magisk app Go to Install > Select and Patch a File
- Select the boot.img you transferred to Internal Storage. Magisk will patch your boot.img and display the output folder after the process.
- Transfer the Patched boot.img to SDK Platform tools folder and rename it to boot.img
- Reboot to Bootloader and type the below command:
fastboot flash boot boot.img
-Reboot the device by typing:
fastboot reboot
-Check Magisk manager and the device must be rooted now
METHOD-2 (TWRP)​- Install TWRP by following this guide
- Download the magisk apk. Transfer it to SD-Card and flash it from twrp
- Reboot your device
CREDITS​@topjohnwu Magisk
@adazem009 For TWRP recovery
Press Thanks button if this guide was useful to you!

@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.

PATCHED BOOT IMAGE FROM YT-X705F​This is a magisk patched boot.img from the latest firmware for YT-X705F. Please don't use it for other models (YT-X705L, YT-X705X)

TNSMANI said:
@Johannj22
We would appreciate if you provide all help in the open on the thread itself. Please do not post Telegram links and request users to visit you there for help. TG links can only be posted by Devs on Development threads in the OP only. Please read THIS.
Click to expand...
Click to collapse
Noted sir. It won't happen again

what version of ROM you use .
the last one is not work with magisk

I use this version YT_X705F_S001135_210909_ROW

yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?

Loserintheend said:
yes this one is the last one see date from post yet,
but magisk will not work with this version anymore.
i collect from earlier version this "boot.img" does it match with a android roms 10 from lenovo ?
Click to expand...
Click to collapse
You just have to make sure you use the boot.img from the exact firmware you are on now. Let me know if it worked.

Johannj22 said:
I use this version YT_X705F_S001135_210909_ROW
Click to expand...
Click to collapse
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release OTA-Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install OTA Update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS

Loserintheend said:
so S001135 was last Offizial ROM from Lenovo , just was waiting to install this one as root.
because every three month Lenovo release Update for some Update and get worse.
After rooting tablet and lenovo release update, " boot.img" must be change back to install update from lenovo .
Now it seams this OS will be stable on Lenovo YT_X705F SMART TAB.
But still probs on running differnt APPS on this doomed crap tablet, for this issue i'm looking on LineageOS
Click to expand...
Click to collapse
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.

Johannj22 said:
If you are on the same firmware S001135 then just use the boot.img I posted above. It should work. Also It would be better to disable system updates. I am creating a seperate post for running GSI of LineageOS and other ROMS.
Click to expand...
Click to collapse
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .

Loserintheend said:
No way to disable updates , after every reboot this tablet ask you again. Only mark, i will update rom manuell.
BTW im also switch off all this spying GOOGLE Apps , and a lot of this junk apps from google .
Click to expand...
Click to collapse
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img

Johannj22 said:
SO you are not able to root the device?. I am on latest update and I rooted it. You can install the latest firmware from Rescue and Smart assistant. Just flash it onto your device. The downloaded ROM should be saved in C:\ProgramData\RSA\Rom files\YT-X705Fxxxx\.......There you should fine boot.img
Click to expand...
Click to collapse
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9

Loserintheend said:
i told you i do it twice , but by the last ROM i was waiting .. read my issue #9
Click to expand...
Click to collapse
Waiting?. I am sorry I think its the language barrier ..I don't understand certain things you say.

Any help provided for X705X tab,It got A10 update.How can I get stock rom and boot image for the latest update?

Finally I find out RSA mentioned in this threads and able to download stock firmware

vygavedha said:
Finally I find out RSA mentioned in this threads and able to download stock firmware
Click to expand...
Click to collapse
Yes use RSA and flash the stock firmware. This stock firmware you flashed should be saved in your system's C:\ProgramData\RSA\Rom Files folder. Just get the required image files from there/

I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?

vygavedha said:
I did not flashed. I just downloaded the firmware. But it seems it is downloaded with some extension(.bmp Or pac which I did not check well).
How can I extract boot img from this?
I renamed to zip and extracted. But could not find any image files.
Can you help how did you do the extraction?
Click to expand...
Click to collapse
Send me a screenshot

Johannj22 said:
Send me a screenshot
Click to expand...
Click to collapse
Sure. I have deleted the downloaded file. I will redownload the same and update the screen shot tomorrow