Database Info

Ulefone Future - Development & Support (GearLabs CM13 Available!)

In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.​
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Custom ROM (based on Android 6.0)
- LineageOS/CyanogenMod 13 by GearLabs ( @Alberto96 ) : http://forum.xda-developers.com/showpost.php?p=69543058&postcount=458
- based on alps-mp-m0.mp7-V1.18_nb6755.66.m_P16 with Root, Busybox & init.d support - by GearLabs: https://mega.nz/#!JAciHZwC!2G-dZlgvLJA99v723oXMuRp3rzQXz2fRZVVb_OytETk
I recommend you to flash P16 Stock ROM using SP Flash Tool first so that you will have a complete upgraded base.​
Stock (Android 6.0)
- alps-mp-m0.mp7-V1.18_nb6755.66.m_P16 - 20160721 (latest, provided by Ulefone Tech. Support): https://docs.google.com/uc?id=0BxhU4oDpvylvamRwc2Z1S3d1YmM&export=download | Mirror
- Official Stock ROM & Flash Tools: http://ulefone.com/download/future.html
- SP Flash Tool for Windows & Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Download Only" instead.
Previous Releases:
- alps-mp-m0.mp7-V1.18_nb6755.66.m_P9 / 2016.06.08 01:02:34 CST : https://mega.nz/#!AZFmWRjA!eN2bHSLxZkpUK9WLw9UkA5S_3LvojgUo1u0WVo6l8y0
Flash Tool
- SP Flash Tool v5.1628 for Windows & Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A​
Recovery:
GearRecovery based on TWRP
- Check the GearCM 13 post: http://forum.xda-developers.com/showpost.php?p=69543058&postcount=458​
TWRP 3.0.2 by "jemmini" from 4PDA Forum. Tested by @beruppino (thank you for the huge amount of tests you are doing for me)
- Based on alps-mp-m0.mp7-V1.18_nb6755.66.m_P7 / 2016.05.21 14:26:51 CST : https://mega.nz/#F!wMMQ2KwS!GSVeGPp7k1_H1UPREB8qSg
- Based on alps-mp-m0.mp7-V1.18_nb6755.66.m_P9 / 2016.06.08 01:02:34 CST : https://mega.nz/#F!NJ9ygBzJ!xRN9NHv1WCeHoqXriKkXpQ​
Remember that there is no direct recovery boot (Volume Up + Power), and if you flash the recovery it gets overwritten every time you reboot the device. Check post #18 for more information.
Root:
insecure boot image <= Required otherwise you won't be able to use root permissions and you will lose recovery access on reboot
- based on alps-mp-m0.mp7-V1.18_nb6755.66.m_P16 - Flashable using TWRP, or SP Flash Tool if you extract the boot.img image from the archive: https://mega.nz/#!sckyRBzb!PwkFr4HDYFyXWj6ByrUgFzYZ1IhpNkQWHGXi8swHp6c
Previous Releases
- based on alps-mp-m0.mp7-V1.18_nb6755.66.m_P9 - Flashable using SP Flash Tool: https://mega.nz/#!NVUmDDKA!97J7A98LhzZtM6wcI7FyY9_uW87K2hnf7Xo-Ne8tqdo
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu​
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811​
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en​

It seems that "needrom" managed to get Ulefone Future's ROM even before its official release.
Just Google for it.

vijay2 said:
please ulfone future stock rom....please link
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
thanks
Click to expand...
Click to collapse
Next time read the whole thread before posting something,

Alberto96 said:
Next time read the whole thread before posting something,
Click to expand...
Click to collapse
Alberto you recive your ulefone future?

beruppino said:
Alberto you recive your ulefone future?
Click to expand...
Click to collapse
Not yet. I have already contacted Ulefone to know when they will send me the device, but i still have to receive a reply.

I keep the topic on the root for ulephone future and puts it here (theme more suited). (started here : http://forum.xda-developers.com/gen...-future-5-5-mtk6755-64bit-4gb-t3293477/page16)
SO :
I have tested all "one click root" application with same résult : Root failed. (Kingoroot, king root, one click root, and more...)
We must find the right TWRP to flash the recovery. But it is not present anywhere.
For the elephone P9000, the root procedure was put online the same day of the first deliveries .. But with ulephone : Nothing.
So I looked at the addresses of the Rom for the P9000 which has the same processor. And this is result :
for the P9000 recovery adress start at 0x000000000008000 and end at 0x0000000000EE37FF
butFor Future recovery adress start at 0x000000000008000 and end at 0x00000000009BC37F (unconfirmed because rom comes from needrom.com and no from official ulephone site).
So I think we can not use the same tutorial and the same files.
If someonehave an idea, or if someone has succeeded root it, it would be great to share ..

Guys i recommend you to not mess up with your device, because the only ROM available (needrom) doesn't seem to work.
So, if you damage something in the /system partition, you won't be able to recover the device until Ulefone releases the Stock ROM.

I had the intuition that the Rom of needrom was not good because the reference did not correspond with that mine at any point in my phone ...
I did well to not try then ..
But you must admit that it is still exaggerated that all ulphone models have their firmware on the official site, and not the Future. Same way for rooting process... All models have their root procedures except the future..

TWRP 3.0.2 by "jemmini" from 4PDA Forum
- alps-mp-m0.mp7-V1.18_nb6755.66.m_P7 / 2016.05.21 14:26:51 CST : https://mega.nz/#F!wMMQ2KwS!GSVeGPp7k1_H1UPREB8qSg
- alps-mp-m0.mp7-V1.18_nb6755.66.m_P9 / 2016.06.08 01:02:34 CST : https://mega.nz/#F!NJ9ygBzJ!xRN9NHv1WCeHoqXriKkXpQ

thanks alebrto! did anyone already test it?
update: my version is alps-mp-m0.mp7-V1.18_nb6755.66.m_P12

I have Just tested it :
I have alps p9 version but
with TWRP P9. Even after flashing, I still have Chinese markings by power + vol-
---------- Post added at 02:09 AM ---------- Previous post was at 01:59 AM ----------
flashed three times with spflashtools V5.1552 and nothing .. No TWRP recovery in the phone ..

what do you mean with "Chinese markings by power + vol-"?

oliversum said:
what do you mean with "Chinese markings by power + vol-"?
Click to expand...
Click to collapse
the chinese recovery
to enter recovery, i have tested with power button and vol+ button, and tested with power button + vol- button.
Same way : No twrp but chinese application
now tested with spflashtools V5.1616 : Same way
No twrp recovery installed.. I don't understand why.. Flash is ok, green logo after flashing..
With the image P9 :
Power and Vol+ go to nothing and android is loading
Power and vol - go to a chinese application
With the recovery stock : two possibilities (vol+ or vol-) go to chinese application..
If i force to go in recovery mode in adb, phone reboot, and the yellow robot come with the phrase "no command". No twrp
I stop my test for the moment.. I have tested all possibilities and nothing.. Wait and see...

Alberto96 said:
TWRP 3.0.2 by "jemmini" from 4PDA Forum
- alps-mp-m0.mp7-V1.18_nb6755.66.m_P7 / 2016.05.21 14:26:51 CST : https://mega.nz/#F!wMMQ2KwS!GSVeGPp7k1_H1UPREB8qSg
- alps-mp-m0.mp7-V1.18_nb6755.66.m_P9 / 2016.06.08 01:02:34 CST : https://mega.nz/#F!NJ9ygBzJ!xRN9NHv1WCeHoqXriKkXpQ
Click to expand...
Click to collapse
Thank you for this img but this twrp not work in our ulephone.
Have you the link of the topic in 4PDA Forum ?

Recovery Mode hasn't been enabled, so if you send the "adb reboot recovery" command after the system boot-up, it won't be there because as soon as the system boots the recovery gets overwritten with the stock. (that's a security feature)
Unfortunately the same happened on the Ulefone Vienna, so it seems that starting from the Vienna Release they choose to disable direct recovery boot from the bootloader.

oooohh ok, so how can we do? There is a solution ?
if i do :
adb reboot bootloader
fastboot flash recovery c:\recovery.img
power and vol+
it will be the same problem, right ?
I do not know how I will succeed to root this device. Yet it is an obligation for me ... I am damned with this phone

Well, I tried lots of ways to try to start the recovery after flashing, but I still haven't succeeded : After flashing with SP-Flashtools ...
if not reboot, adb not working so we can't start TWRP.
If we start order after the reboot we have the little green robot.
If we made the combinations Power and Vol+ we have nothing
So we have the file of twrp but we have no way to start it, if I understood. Thank you Ulephone
Or, perhaps, just perhaps, ...... another way and another idea to work: Are we sure this TWRP really work? If no one inthe world has yet succeeded to start, how to be sure ?

fanfan7110 said:
oooohh ok, so how can we do? There is a solution ?
if i do :
adb reboot bootloader
fastboot flash recovery c:\recovery.img
power and vol+
it will be the same problem, right ?
I do not know how I will succeed to root this device. Yet it is an obligation for me ... I am damned with this phone
Click to expand...
Click to collapse
fanfan7110 said:
Well, I tried lots of ways to try to start the recovery after flashing, but I still haven't succeeded : After flashing with SP-Flashtools ...
if not reboot, adb not working so we can't start TWRP.
If we start order after the reboot we have the little green robot.
If we made the combinations Power and Vol+ we have nothing
So we have the file of twrp but we have no way to start it, if I understood. Thank you Ulephone
Or, perhaps, just perhaps, ...... another way and another idea to work: Are we sure this TWRP really work? If no one inthe world has yet succeeded to start, how to be sure ?
Click to expand...
Click to collapse
At every reboot the recovery partition gets overwritten so you have to:
1.A) Backup your boot.img image (without root it isn't possible though, you would need to use the SP Flash Tool readback feature together with the correct Scatter file in order to do it) <- Required for the fourth (4) step
or (choose the one you prefer or you find easier)
1.B) Keep safe the boot.img image from an available Stock ROM package (latest one is preferred) <- Required for the fourth (4) step
2) Flash recovery.img as boot.img (just rename the file or select it manually) so that the device will boot to recovery by default. (basically you flash the recovery image in the boot partition)
3) Remove "recovery-from-boot.p" from /system using the built-in TWRP File Manager. Remember to mount /system before doing it otherwise the system folder will be empty
4) Restore your boot.img image (using SP Flash Tool or by flashing a boot image using a flashable TWRP package) so that you can use the device again, and the recovery partition won't get anymore overwritten​
Done!
You can now access to the custom recovery but you will need to reboot manually into it using adb commands (adb reboot recovery), or by using some third-party apps such as "Quick Boot" or similar. There is no other way to do so unless Ulefone unlocks the key combination.

wouaho... OK ! Not very simple
So, because there is no official firmware a this moment (aberrant thing because ulefone need only to make a backup in their technical local and post it on the blog .. everything will be done in less than 5 minutes .. But..) , we need to wait to have a correct boot.img..
Thank you for this response. Thanks a lot

Good evening, thank you for the discussion to Alberto, are pending future ulefone, I will come on Monday or Tuesday, I read that there is a working firmware for ulefone, I wonder if you have seen this and if it is good? http://firmwarefile.com/ulefone-future
Thanks
Inviato dal mio Nexus 5X utilizzando Tapatalk

Qualcomm SG9350 snapdragon 820 Root guide for rookies

This thread is based on these two post, but for rookies like me.
http://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969 by @davecotefilm
&
http://forum.xda-developers.com/s7-edge/samsung-galaxy-s7-edge-snapdragon-roms-kernels-recoveries--other-development/rom-kernel-sm-g9350-s7-edge-debloated-t3482804 by @travis82
before we start, here's some basic requirement:
1. your S7 Edge must be Qualcomm snapdragon 820 CPU, SG-9350 model better HK version (Mine is Chinese version, but I flashed to HK stock rom, no need to oem unlock, if you need this part, please search online. be-aware, flash to HK verison from Chinese, you must select re-partion option for the first time in odin)
2. developer option has been enabled already (go to settings->about devices->software info->tap build number more than 5 or 6 times)
3. in settings ->developer options -> USB debugging is on, and OEM unlock is on
4. go to samsung store, download crom and run it. (this will unlock your bootloader, lost warranty. so your choice, don't blame on me)
5. back up your data of internal storage and external SD card
6. Samsung drivers has been installed on your computer
7. know how to enter download mode on your s7e: power off your phone then, press and hold vol down + home + power
8. know how to enter recovery mode on your s7e: power off your phone then, press and hold vol up + home + power when you see recovery booting blue little letters on top of your screen, release them all
Here's the files you will need:
1. Customized Odin https://www.androidfilehost.com/?fid=24588232905724860
2. TWRP 3.0.1 with SuperSU G9350.TWRP.SuperSU.tar
this is 3.0.1 version twrp, if you directly flash the 3.0.2 version downloaded from @travis82's post, it will not work, you have to flash the above one then update to 3.0.2
3. The following files you need to download is optional, just incase your phone need to be restored to stocked rom (Warranty can't be restored anyway). (Update 11/6/2016: base on @travis82's suggestion, put the SM-G9350_G9350ZHU2APE3-TGY firmware link below, so you can easily flash forward or backward)
AP https://www.androidfilehost.com/?fid=24588232905724857
BL https://www.androidfilehost.com/?fid=24588232905724854
CP https://www.androidfilehost.com/?fid=24588232905724856
CSC https://www.androidfilehost.com/?fid=24588232905724855
SM-G9350_G9350ZHU2APE3-TGY
4. No verity opt encrypt v3.2 https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-3.2.zip
all above files are from this post http://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969
5 TWRP 3.0.2 update
unofficial TWRP by @travis82 updated on 11/6/2016 Check second floor
6. @travis82 debloated rom of October https://www.androidfilehost.com/?fid=529152257862670418
7. and kernel of latest from @travis82 in this post, please go there download the latest Kernel
Now here we start.
1. enter download mode and connect to your computer
2. launch customized odin put G9350.TWRP.SuperSU.tar in AP and flash it. (after this, your twrp interface will be chinese by default, you can change to english ofcoz, however if you totally can't read it, go to flash the below step's update, it will change the twrp's interface to english by default.
3. launch customized odin again and put TWRP 3.0.2 update Unofficial TWRP updated 11/6/2016 by @travis82 in AP and flash it again. (Sure, you have to put your phone to download again and connect to your computer)
4. enter recovery -> wipe->fomat data ->reboot (This step will make twrp able to mount your data partion)
5. enter reocvery -> install -> select the No verity opt encrypt v3.2 and flash it. (you have to put it on your internal or external sd card)
after above steps, your stocked rom has been rooted, and if you like that, you don't need to go through below steps. below is to flash @travis82 optimized rom and kernel
6. put the downloaded debloated rom to your sd card
7. enter recovery -> install-> select the debloated rom file and flash ->reboot after finished successfully
8. the Samsung post screen will be there for several minutes, mine was about 5 minutes
9. put your downloaded latest kernel from @travis82 to your sd card
10. enter recovery -> install -> select the latest kernel and flash ( I didn't wipe the cache, works fine for me)
11. if there's a newer kernel published out, just put it on your sd card and repeat step 10 again, then you will be on the latest kernel ( I didn't wip the cache as well)
End
thanks to @travis82 and @davecotefilm

Unofficial TWRP: https://drive.google.com/open?id=0B6...Wo0M2FvU3VVRGs or https://www.androidfilehost.com/?fid=457095661767112021
Changelog: https://github.com/travismills82/twr...commits/master
Short version:
Update kernel and dtb for recovery
update fstab
added modem as backup (so we can restore modems without odin)
fixed decryption (no messages yet)
Noticed now I can use compression without my phone getting so hot it wants to explode or freezing.
PS: I don't think you need custom odin anymore. Also here is the crom.apk : https://www.androidfilehost.com/?fid=385035244224394932
Samsung likes to prevent os reverts ie marshmallow to kitkat. So I suggest you flash SM-G9350_G9350ZHU2APE3-TGY firmware via odin as stock before you just automatically jump to the latest version officially. Here is a link for that also. https://www.androidfilehost.com/?fid=312978532265363995 Than you can just flash zips via twrp and rollback for jump forward and not be stuck because you have a bootloader that can't load XXX rom.

travis82 said:
Unofficial TWRP: https://drive.google.com/open?id=0B6...Wo0M2FvU3VVRGs or https://www.androidfilehost.com/?fid=457095661767112021
Changelog: https://github.com/travismills82/twr...commits/master
Short version:
Update kernel and dtb for recovery
update fstab
added modem as backup (so we can restore modems without odin)
fixed decryption (no messages yet)
Noticed now I can use compression without my phone getting so hot it wants to explode or freezing.
PS: I don't think you need custom odin anymore. Also here is the crom.apk : https://www.androidfilehost.com/?fid=385035244224394932
Samsung likes to prevent os reverts ie marshmallow to kitkat. So I suggest you flash SM-G9350_G9350ZHU2APE3-TGY firmware via odin as stock before you just automatically jump to the latest version officially. Here is a link for that also. https://www.androidfilehost.com/?fid=312978532265363995 Than you can just flash zips via twrp and rollback for jump forward and not be stuck because you have a bootloader that can't load XXX rom.
Click to expand...
Click to collapse
thanks. yeah, you are right, no special reason for customized odin, just because it's in that post, easier got the link, and it works anyway. :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

Just trying to help keep the main post KISS style. Keep It Stupidly Simple

travis82 said:
Just trying to help keep the main post KISS style. Keep It Stupidly Simple
Click to expand...
Click to collapse
@travis82 one more questions, in your post, there's video fix, what is that for?
thanks,

I'm trying to get my chinese version rooted. I flashed HK stock rom, but couldn't get pass the crom unlock. I downloaded crom from Samsung store, ran it, and it gave me "unable to open application, an unkown error has occurred. try again later". Anyone knows why? I have oem unlock and usb debug on in developer settings.

What's the phones model #?

travis82 said:
What's the phones model #?
Click to expand...
Click to collapse
I got it working with s6-crom

travis82 said:
What's the phones model #?
Click to expand...
Click to collapse
Hi travis82, I'm trying to root another s7 edge for my gf, but this time not even s6-crom works. It's showing the same error. The phone is a China version of sg9350, I flashed two different HK roms with odin, but can't get S6-crom working. Oem unlock and usb debug are both on in developer settings. Do you have any idea?
---------- Post added at 02:12 PM ---------- Previous post was at 02:04 PM ----------
ioneng said:
Hi travis82, I'm trying to root another s7 edge for my gf, but this time not even s6-crom works. It's showing the same error. The phone is a China version of sg9350, I flashed two different HK roms with odin, but can't get S6-crom working. Oem unlock and usb debug are both on in developer settings. Do you have any idea?
Click to expand...
Click to collapse
Sorry, false alarm. I got it working by turning wifi off and ran it over data network. Strange that crom app didn't complain about internet problem while wifi was on.

boot loop
hiya i did up to step 3 and keep getting boot loop any idea what went wrong? 1st time im doing this i have device samsung galaxy s7 edge sm-g9350

[RECOVERY][BOOT][ROOT][VFD-1400] Vodafone Prime Tab 7

DISCLAIMER: I WILL NOT BE HELD LIABLE FOR ANY DAMAGE TO YOUR DEVICE BY USING THIS METHOD
Warning: this will only work with the older firmware (Android 6.0.1/1BEBFDB1 )
What this will achieve:
You will flash a modified boot image that runs selinux in permissive mode.
You will flash a custom recovery that allows you to root the device.
After you are done, your userdata will most likely not be encrypted anymore. You can re-enable encryption in the system settings.
DOWNLOAD
1. Install the usb drivers that come with the device, in /system/etc/USBDriver.iso.
They are also in the download package, in USBDriver/.
Run Setup.vbs.
Also install SUGAR QCT_SP v11.1.2 Setup.exe from the download package.
2. Connect your device to your computer and boot it into EDL mode (enable usb debugging).
adb.exe reboot edl
3. Run SUGAR QCT_SP (use credentials from download package), select VF1400 device and click on the upgrade button.
It will download the latest official firmware update into "C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\VF1400-2AVXXXX" (VF1400-2AVDDE1, for me).
After the download is done and the flashing started, make a copy of the VF1400-2AVXXXX folder to your Desktop.
4. While the flashing is going on, we can start to modify out copy of VF1400-2AVXXXX.
In it should be a folder, most likely called 1BEBFDB1 (version number of the update).
Inside that folder should be the .mbn files we care about: B1BEB0B0CD00.mbn (boot image) and R1BEB0B0CD00.mbn (recovery image).
Possibly they will be called differently, but I assume the boot image always starts with B and the recovery with R.
You can check "C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\tool\logs\Sugar_XXXXXXXX.log" to make sure which file is which.
Replace B1BEB0B0CD00.mbn with boot.img from the download and R1BEB0B0CD00.mbn with recovery.img.
5. After the flash is done and the device rebooted, put it in edl mode again (after enabling usb debugging).
adb.exe reboot edl
6. Now, *before* we start SUGAR QCT_SP again, copy the VF1400-2AVXXXX into "C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin"
7. Start SUGAR QCT_SP, select VF1400 device and hit upgrade.
Congratulations! After flashing and after the next reboot you are running with selinux in permissive mode and you can flash SuperSU from the recovery.
Now copy the latest SuperSU flashable zip into your internal storage and install it from recovery.
The recovery used is CM-13.0, device tree based on https://github.com/zwliew/android_device_xiaomi_land
Being compiled with prebuilt kernel from boot.img.

Works great! Thank you

Cool! Thanks alot!

Hi fused#1,
thanks for this, have you tried to install Xposed on this device after rooting it?
Best regards,
misterfx

Hi,
i've now tested and installed xposed.
You need this files: xposed-v87-sdk23-arm.zip, XposedInstaller_3.1.1.apk and for safety the xposed-uninstaller-20160829-arm.zip.
Install the xposed-v87-sdk23-arm.zip with recovery, after reboot install the XposedInstaller_3.1.1.apk.
Best wishes,
misterfx

TWRP recovery
Hello.
All work as expected, thanks a lot for that.
I wonder if someone have manage to install TWRP recovery.
I mainly interesting of NANDroid Backup i can take with TWRP recovery.
How can i do that?
Thanks at advance.

Hello,
is there any way to get ntfs oder exfat support on the vodafone tab prime 7 ?
at the moment, it is original, without rom changes.

Hi, I tried your guide today, but it failed at flashing the alternative bootloader and recovery. System was not able to boot anymore after flashing the second time with your altered files.
Display only showed "powered by android" and nothing else happened. Luckily I found out that you are able to switch back into EDL mode when this happens:
- Shut down device (disconnect any cable and press power until display switches off)
- Press Vol+ AND Vol- for about 10 seconds and then insert USB cable
-> "powered by android" label flashes up and then display goes black and voila you are in EDL mode again
---------------------
Here comes my question:
Is it possible that your bootloader and/or recovery are incompatible with latest FW version? Could you have a look at the current bootloader and recovery to get selinux in permissive mode again? I attached the original bootloader and recovery that was downloaded with SUGAR QCT_SP.

Hi,
quite possible.
I wasn't even aware of the new firmware version. Obviously this only works with the old firmware. I will make that clear in the original post.
What firmware/android version is it? Maybe I'll look into that today or tomorrow.
Cheers
edit: I'm not even being offered the new firmware. Can you upload all of it somewhere?
gandharva said:
Hi, I tried your guide today, but it failed at flashing the alternative bootloader and recovery. System was not able to boot anymore after flashing the second time with your altered files.
Display only showed "powered by android" and nothing else happened. Luckily I found out that you are able to switch back into EDL mode when this happens:
- Shut down device (disconnect any cable and press power until display switches off)
- Press Vol+ AND Vol- for about 10 seconds and then insert USB cable
-> "powered by android" label flashes up and then display goes black and voila you are in EDL mode again
---------------------
Here comes my question:
Is it possible that your bootloader and/or recovery are incompatible with latest FW version? Could you have a look at the current bootloader and recovery to get selinux in permissive mode again? I attached the original bootloader and recovery that was downloaded with SUGAR QCT_SP.
Click to expand...
Click to collapse

Hi,
it seems there is again a new fw, files named like R1BEJ0J0CD00.mbn, with security patch level of April 2017. A user flashed this with the root-patch, but he has no wifi anymore.
Thanks for a update
Best wishes,
MrFX

The procedure works, but I can not install from Supersu.zip recovery mode. I tried many versions but I always get this error:
E:filed to veryfy whole-file signature
E:signature verification failed
Istallation aborted.
Can someone help me

Hey @fused#1 , i have a problem. after flashing and rooting my wifi does not work. do you know why?

x.0ldB0y.x said:
Hey @fused#1 , i have a problem. after flashing and rooting my wifi does not work. do you know why?
Click to expand...
Click to collapse
I don't think this is compatible with the latest update for the device. If you are running thatthat could be the reason. It's possible they updated the radio firmware or whatever the **** it's called these days...

Hi fused#1,
have you a hint, i've now a 2nd device with the old fw (and saved old firmware files), but sugar_qct always do a update and downloads the new firmware... is it possible to flash the old, saved files?
Update: got it, renamed all old fw files to the new names, copied they to the new created directory (replaced new fw), and sugar_qct installed the old fw with the new file names.
Thanks,
MrFX

Hey misterfx,
can u do an tutorial, how u did it to flash the old fw?
I tryed many things but he doesnt accept the old files (and i dont know the new folder-name).
Would help many guys i think, thanks ^^

Hi,
you can download the new fw with sugar_qct (but while downloading, unplug the tab)... you now have the new folder name and the files inside it.
Rename ALL old firmware files (from backup) to the new names and copy they to the new fw folder and replace all files.
Then exit sugar_qct and start it again, it will find the "new" files... make upgrade.
Good luck,
MrFX
Neeschar said:
Hey misterfx,
can u do an tutorial, how u did it to flash the old fw?
I tryed many things but he doesnt accept the old files (and i dont know the new folder-name).
Would help many guys i think, thanks ^^
Click to expand...
Click to collapse

df
thank you

TWRP
Someone can find TWRP for VFD1400?

Vdf 1400 Old firmware
Would someone please upload the vdf1400 old firmware before the update of April 2017!!
I would like to install that Rom instead..
WiFi is not working while using this method for the new firmware..
Thanks

Vdf 1400 Old firmware
Anyone has a link for the old firmware VF1400-2AVDDE1 ....
Thanks in advance

Wileyfox Spark X

Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !

@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.

I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA

HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?

TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.

Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.

Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?

Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs

Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?

johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?

TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.

johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs

johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.

[SM-A750FN/DS] Unofficial LineageOS 17.1 GSI

Hi everyone,
I had dozen of problems getting my SM-A750FN/DS with the newest Stock Rom to run any GSI Rom, until I tried something that did the trick. Since there are a couple people here, who can't get it running, too, I decided to write a little Guide. Do all things in the right order and it should work. Since I only have the SM-A750FN/DS, I can't promise, that it will work on other SM-A750X devices.
First of all: I am not responsible for anything you do to your device. This guide worked for me, it doesn't have to work for you.
Working so far:
- Calling
- WIFI
- Sensors (All)
Working partially:
- Cam
Doesn't work so far:
- Bluetooth
- Memory Card
- USB File Transfer
Before you start with anything, get this things on your SD-Card:
1. Quantum Stock 2.5 Latest Release (OneUI edition, not the GSI!)
2. LineageOS 17.1 Arm 64 BvS (Extract the XZ and copy the IMG to the SD)
EDIT: Updating to the newest GSI Rom works through TWRP! Just choose the newest LineageOS BvS, extract it and copy it on your device. Install the Image and choose ONLY System. After the reboot you will be up-to-date. Tested with LineageOS 17.1 15.06.2021 GSI Rom (AllArch).
Good, now we need to make sure, that you have the STOCK ROM running on your Phone. If not, download the newest Samsung Stock and flash it with ODIN 3.14.4.
1. Download ODIN 3.14.4
2. Start ODIN.
3. Click on AP and choose the Samsung Stock Image (DO NOT CLICK ANYTHING ELSE!)
4. Start on your phone the bootloader (normally it is VOLUME DOWN + POWER button, when you phone is off).
5. If that didn't start the bootloader, try VOLUME UP + POWER and choose Start Bootloader in the menu.
6. Connect your phone to your computer through a USB cable.
7. Click Start in Odin (on your computer).
8. Wait for the phone to start into Android.
9. Close ODIN
10. Connect your phone to the internet and put a SIM inside (without this your OEM Unlocking option won't appear)
11. Enable Developer options in settings. Normally found after click about 10 times on Build in Settings ---> About Phone. (Here you can also see, that your phone uses OneUI 2.0.)
12. In the developer options you enable OEM Unlocking (this will delete everything on your phone - like a factory wipe).
13. Restart your phone and check if OEM Unlocking is enabled. If it doesn't appear, you are not connected to the internet and your sim card is not unlocked.
Now you are ready to start the flashing of the new ROM.
1. Download TWRP by ashyx.
2. Power Off your phone and load it into bootloader/download mode.
3. Start ODIN, click on AP, choose the ZIP file containing TWRP, click on Options and DISABLE Auto-Reboot (VERY IMPORTANT!).
4. Click on Start in ODIN and wait until it shows PASS.
5. On your phone hold VOLUME DOWN + POWER, until the phone shuts off, IMMEDIATELY hold VOLUME UP + POWER, so the phone can start TWRP.
6. In TWRP go on WIPE, FORMAT DATA and type yes.
7. When it is done, go on the Menu button (arrow showing up), go on Reboot and on Recovery. DO NOT POWER OFF THE PHONE OR RESTART IT TO SYSTEM!!!
8. After the phone rebooted into TWRP go on Install.
9. Click on INSTALL IMAGE.
10. Choose lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS.img.
11. Flash it.
12. After flashing is done, go back to menu (DO NOT RESTART THE PHONE YET!)
13. Go on Install and choose Quantum-Quack-A750F-V2.5-ONEUI.zip and flash it.
14. Wipe Dalvik Cache and restart the phone to system.
15. The phone will restart twice, on the second restart LineageOS will start.
You don't need magisk, since the Quantum Kernel is prerooted. If you wish to, try to install Magisk. DO NOT WIPE THE STOCK ROM!
For anyone ending up with problems:
ERROR: Download Mode shows "Only original firmware..."
Solution: You didn't check, if OEM Unlocking is enabled. IT IS NECESSARY TO CONNECT THE INTERNET AND SIM CONNECTION!
ERROR: Bootloop
Solution: Reflash the stock rom from Samsung and try the tutorial again. This time read more careful and don't miss anything. It is important, that your ABOUT PHONE says, that you have ONEUI.
ERROR: LineAgeOS doesn't boot.
Solution: Be sure, that it says BvS in the filename. AvS doesn't work, since Samsung changed the phone from a-only to A/B. Be sure to check if it is ARM64!
Special Thanks to:
@prashantp01 for the great Quantum Kernel 2.5!
@ashyx great working TWRP build!
@AndyYan for the unofficial ALLARCH LineAgeOS GSI. Works great so far.

Nice U took your time to write that long post... However 3/4 of that is copy-pasted from elsewhere...
I would like to suggest something to solve aome of your issues (especially those from DOESN'T WORK) and also TO WARN other users of following such guides.
Bluetooth and USB transfer - man, U simply use wrong kernel! It is not @prashantp01 fanaberie to provide 2 kernel versions, it is done for the purpose. OneUI contains a lib which breaks bluetooth....... GSI version contains file which is needed for USB thing...... Regarding Magisk - U should not use official Magisk which is included in Quantum kernel for GSI roms, please take some research to find correct version dedicated to GSIs... U took (or actually waste) plenty of time for this post as it NOT NECESSARY to do all mention above steps... As simple as:
from OneUI 2.0 - wipe data, dalvik/art and cache, flash gsi system.img, flash Quantum GSI kernel, flash CORRECT Magisk. IMPORTANT: DON'T WIPE SYSTEM OR MOSTLY LIKE U FACE BOOTLOOP.
from any gsi - wipe dalvik/art and cache, flash choosen gsi system.img, flash CORRECT Magisk, done.
That works for 4 months to most users - those who can't successfully boot makes a mistake on some stage.
Please have in mind U share your thoughts to few millions of people and by saying 'You take no responsibility' doesn't mean U are allowed to post ANYTHING.
I hope A750xx Users can take this as a lesson and will use their brains before following any random guide.
Have a nice day!

PS. USE UNOFFICIAL ORANGEFOX FOR FLASHING ON SAR DEVICE, AS MENTIONED TWRP IS PIE SOURCE AND DOESN'T WORK CORRECT ANYMORE ....

Besides the Filesystem (USB + SDCard) and Bluetooth everything works fine. Even Magisk works like it should.
So where is the problem with this way?

Wolve-San said:
Hi everyone,
I had dozen of problems getting my SM-A750FN/DS with the newest Stock Rom to run any GSI Rom, until I tried something that did the trick. Since there are a couple people here, who can't get it running, too, I decided to write a little Guide. Do all things in the right order and it should work. Since I only have the SM-A750FN/DS, I can't promise, that it will work on other SM-A750X devices.
First of all: I am not responsible for anything you do to your device. This guide worked for me, it doesn't have to work for you.
Working so far:
- Calling
- WIFI
- Sensors (All)
Working partially:
- Cam
Doesn't work so far:
- Bluetooth
- Memory Card
- USB File Transfer
Before you start with anything, get this things on your SD-Card:
1. Quantum Stock 2.5 Latest Release (OneUI edition, not the GSI!)
2. LineageOS 17.1 Arm 64 BvS (Extract the XZ and copy the IMG to the SD)
Good, now we need to make sure, that you have the STOCK ROM running on your Phone. If not, download the newest Samsung Stock and flash it with ODIN 3.14.4.
1. Download ODIN 3.14.4
2. Start ODIN.
3. Click on AP and choose the Samsung Stock Image (DO NOT CLICK ANYTHING ELSE!)
4. Start on your phone the bootloader (normally it is VOLUME DOWN + POWER button, when you phone is off).
5. If that didn't start the bootloader, try VOLUME UP + POWER and choose Start Bootloader in the menu.
6. Connect your phone to your computer through a USB cable.
7. Click Start in Odin (on your computer).
8. Wait for the phone to start into Android.
9. Close ODIN
10. Connect your phone to the internet and put a SIM inside (without this your OEM Unlocking option won't appear)
11. Enable Developer options in settings. Normally found after click about 10 times on Build in Settings ---> About Phone. (Here you can also see, that your phone uses OneUI 2.0.)
12. In the developer options you enable OEM Unlocking (this will delete everything on your phone - like a factory wipe).
13. Restart your phone and check if OEM Unlocking is enabled. If it doesn't appear, you are not connected to the internet and your sim card is not unlocked.
Now you are ready to start the flashing of the new ROM.
1. Download TWRP by ashyx.
2. Power Off your phone and load it into bootloader/download mode.
3. Start ODIN, click on AP, choose the ZIP file containing TWRP, click on Options and DISABLE Auto-Reboot (VERY IMPORTANT!).
4. Click on Start in ODIN and wait until it shows PASS.
5. On your phone hold VOLUME DOWN + POWER, until the phone shuts off, IMMEDIATELY hold VOLUME UP + POWER, so the phone can start TWRP.
6. In TWRP go on WIPE, FORMAT DATA and type yes.
7. When it is done, go on the Menu button (arrow showing up), go on Reboot and on Recovery. DO NOT POWER OFF THE PHONE OR RESTART IT TO SYSTEM!!!
8. After the phone rebooted into TWRP go on Install.
9. Click on INSTALL IMAGE.
10. Choose lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS.img.
11. Flash it.
12. After flashing is done, go back to menu (DO NOT RESTART THE PHONE YET!)
13. Go on Install and choose Quantum-Quack-A750F-V2.5-ONEUI.zip and flash it.
14. Wipe Dalvik Cache and restart the phone to system.
15. The phone will restart twice, on the second restart LineageOS will start.
You don't need magisk, since the Quantum Kernel is prerooted. If you wish to, try to install Magisk. DO NOT WIPE THE STOCK ROM!
For anyone ending up with problems:
ERROR: Download Mode shows "Only original firmware..."
Solution: You didn't check, if OEM Unlocking is enabled. IT IS NECESSARY TO CONNECT THE INTERNET AND SIM CONNECTION!
ERROR: Bootloop
Solution: Reflash the stock rom from Samsung and try the tutorial again. This time read more careful and don't miss anything. It is important, that your ABOUT PHONE says, that you have ONEUI.
ERROR: LineAgeOS doesn't boot.
Solution: Be sure, that it says BvS in the filename. AvS doesn't work, since Samsung changed the phone from a-only to A/B. Be sure to check if it is ARM64!
Special Thanks to:
@prashantp01 for the great Quantum Kernel 2.5!
@ashyx great working TWRP build!
@AndyYan for the unofficial ALLARCH LineAgeOS GSI. Works great so far.
Click to expand...
Click to collapse
Bro plz help. I instal lineagos arm64 ab gsi using twrp with gsi kernal phone restarting at samsung a7 2018 logo why not booting any android 11 rom i tried also arm64 a also arm try all gsi i also use boot fix zip but same problem plz bro rply me what is this problem plzz fix

Farhansolangi said:
Bro plz help. I instal lineagos arm64 ab gsi using twrp with gsi kernal phone restarting at samsung a7 2018 logo why not booting any android 11 rom i tried also arm64 a also arm try all gsi i also use boot fix zip but same problem plz bro rply me what is this problem plzz fix
Click to expand...
Click to collapse
Sorry for the late reply. Sounds like you got a bootloop. Just read the guide. I gave a solution to any problem I encountered.

Voytec83 said:
PS. USE UNOFFICIAL ORANGEFOX FOR FLASHING ON SAR DEVICE, AS MENTIONED TWRP IS PIE SOURCE AND DOESN'T WORK CORRECT ANYMORE ....
Click to expand...
Click to collapse
Can you PM me the link?

What is the link?

Voytec83 said:
flash CORRECT Magisk
Click to expand...
Click to collapse
What is the link for correct Magisk?

Voytec83 said:
flash CORRECT Magisk
Click to expand...
Click to collapse
Where to find CORRECT Magisk, any clues?

Thank you so much for this tutorial! Was looking for a long time.

ludemon said:
Where to find CORRECT Magisk, any clues?
Click to expand...
Click to collapse
Use Magisk 21.4. Newer versions bricked my device!

Wolve-San said:
Hi everyone,
I had dozen of problems getting my SM-A750FN/DS with the newest Stock Rom to run any GSI Rom, until I tried something that did the trick. Since there are a couple people here, who can't get it running, too, I decided to write a little Guide. Do all things in the right order and it should work. Since I only have the SM-A750FN/DS, I can't promise, that it will work on other SM-A750X devices.
First of all: I am not responsible for anything you do to your device. This guide worked for me, it doesn't have to work for you.
Working so far:
- Calling
- WIFI
- Sensors (All)
Working partially:
- Cam
Doesn't work so far:
- Bluetooth
- Memory Card
- USB File Transfer
Before you start with anything, get this things on your SD-Card:
1. Quantum Stock 2.5 Latest Release (OneUI edition, not the GSI!)
2. LineageOS 17.1 Arm 64 BvS (Extract the XZ and copy the IMG to the SD)
EDIT: Updating to the newest GSI Rom works through TWRP! Just choose the newest LineageOS BvS, extract it and copy it on your device. Install the Image and choose ONLY System. After the reboot you will be up-to-date. Tested with LineageOS 17.1 15.06.2021 GSI Rom (AllArch).
Good, now we need to make sure, that you have the STOCK ROM running on your Phone. If not, download the newest Samsung Stock and flash it with ODIN 3.14.4.
1. Download ODIN 3.14.4
2. Start ODIN.
3. Click on AP and choose the Samsung Stock Image (DO NOT CLICK ANYTHING ELSE!)
4. Start on your phone the bootloader (normally it is VOLUME DOWN + POWER button, when you phone is off).
5. If that didn't start the bootloader, try VOLUME UP + POWER and choose Start Bootloader in the menu.
6. Connect your phone to your computer through a USB cable.
7. Click Start in Odin (on your computer).
8. Wait for the phone to start into Android.
9. Close ODIN
10. Connect your phone to the internet and put a SIM inside (without this your OEM Unlocking option won't appear)
11. Enable Developer options in settings. Normally found after click about 10 times on Build in Settings ---> About Phone. (Here you can also see, that your phone uses OneUI 2.0.)
12. In the developer options you enable OEM Unlocking (this will delete everything on your phone - like a factory wipe).
13. Restart your phone and check if OEM Unlocking is enabled. If it doesn't appear, you are not connected to the internet and your sim card is not unlocked.
Now you are ready to start the flashing of the new ROM.
1. Download TWRP by ashyx.
2. Power Off your phone and load it into bootloader/download mode.
3. Start ODIN, click on AP, choose the ZIP file containing TWRP, click on Options and DISABLE Auto-Reboot (VERY IMPORTANT!).
4. Click on Start in ODIN and wait until it shows PASS.
5. On your phone hold VOLUME DOWN + POWER, until the phone shuts off, IMMEDIATELY hold VOLUME UP + POWER, so the phone can start TWRP.
6. In TWRP go on WIPE, FORMAT DATA and type yes.
7. When it is done, go on the Menu button (arrow showing up), go on Reboot and on Recovery. DO NOT POWER OFF THE PHONE OR RESTART IT TO SYSTEM!!!
8. After the phone rebooted into TWRP go on Install.
9. Click on INSTALL IMAGE.
10. Choose lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS.img.
11. Flash it.
12. After flashing is done, go back to menu (DO NOT RESTART THE PHONE YET!)
13. Go on Install and choose Quantum-Quack-A750F-V2.5-ONEUI.zip and flash it.
14. Wipe Dalvik Cache and restart the phone to system.
15. The phone will restart twice, on the second restart LineageOS will start.
You don't need magisk, since the Quantum Kernel is prerooted. If you wish to, try to install Magisk. DO NOT WIPE THE STOCK ROM!
For anyone ending up with problems:
ERROR: Download Mode shows "Only original firmware..."
Solution: You didn't check, if OEM Unlocking is enabled. IT IS NECESSARY TO CONNECT THE INTERNET AND SIM CONNECTION!
ERROR: Bootloop
Solution: Reflash the stock rom from Samsung and try the tutorial again. This time read more careful and don't miss anything. It is important, that your ABOUT PHONE says, that you have ONEUI.
ERROR: LineAgeOS doesn't boot.
Solution: Be sure, that it says BvS in the filename. AvS doesn't work, since Samsung changed the phone from a-only to A/B. Be sure to check if it is ARM64!
Special Thanks to:
@prashantp01 for the great Quantum Kernel 2.5!
@ashyx great working TWRP build!
@AndyYan for the unofficial ALLARCH LineAgeOS GSI. Works great so far.
Click to expand...
Click to collapse
Thank you for your post! I have successfully installed LineageOS on my device. I want to add - when someone wants to download LineageOS, it must be Android 10 (with One UI 2.0) with firmware version from November 2020. How to choose correct firmware for your device is explained here: https://www.xda-developers.com/how-to-update-samsung-galaxy-smartphone/

Now I cannot transfer USB files to PC. Windows doesnt detect phone, Linux can (sometimes) but I can do nothing with it. USB debugging is on and Transfer Files options is enabled. I tried different ports, but it happens nothing. Does someone have an idea what I should do?