Related
I've heard people claim it's 64bit. zcpu isn't saying, and antutu benchmark says 64bit. Wikpedia and motorola/lenovo sites aren't saying. Who are saying it's 32bit and what's their source for this?
If it's true, does that mean that there has to be a full wipe of the apps/data during an upgrade to oreo, or would that only be true if the version of oreo was 64 bit, and that a 32bit upgrade from nougat to orea would be ok?
Please post a reasonable source when replying; i've seem talk either way, and i'm interested in THE answer, not AN answer.
Webern said:
I've heard people claim it's 64bit. zcpu isn't saying, and antutu benchmark says 64bit. Wikpedia and motorola/lenovo sites aren't saying. Who are saying it's 32bit and what's their source for this?
If it's true, does that mean that there has to be a full wipe of the apps/data during an upgrade to oreo, or would that only be true if the version of oreo was 64 bit, and that a 32bit upgrade from nougat to orea would be ok?
Please post a reasonable source when replying; i've seem talk either way, and i'm interested in THE answer, not AN answer.
Click to expand...
Click to collapse
Our phones are 64 bit. Stock software runs in 32 bit mode for Sanders. Oreo custom roms are 64bit for our phone for what's currently available.
Sent from my XT1806 using Tapatalk
treyweez11 said:
Our phones are 64 bit. Stock software runs in 32 bit mode for Sanders. Oreo custom roms are 64bit for our phone for what's currently available.
Click to expand...
Click to collapse
Ok, so there'd be no reason to wipe the user data even if we upgrade to a 64 bit version of Oreo, right? Data structures etc in saved data presumably don't need to be concerned with the architecture.
Webern said:
Ok, so there'd be no reason to wipe the user data even if we upgrade to a 64 bit version of Oreo, right? Data structures etc in saved data presumably don't need to be concerned with the architecture.
Click to expand...
Click to collapse
it's a bad idea to switch rom without a full wipe, i never managed to get a working installation without that
if you wait for motorola's official update instead, that will probably work and keep your data
Webern said:
Ok, so there'd be no reason to wipe the user data even if we upgrade to a 64 bit version of Oreo, right? Data structures etc in saved data presumably don't need to be concerned with the architecture.
Click to expand...
Click to collapse
That my friend is a food question. You should do clean flash any way when flashing different ROMs but you won't know until you try. Some people restore their data that way.
Sent from my XT1806 using Tapatalk
My question is about the stock Oreo update only.
Webern said:
My question is about the stock Oreo update only.
Click to expand...
Click to collapse
there is no stock oreo update at the moment, and nobody knows when it will be released
as it is not out yet, you question cannot have an univocal answer
apparently it will eventually be released as motorola declared about one year ago, but some people, including myself, start to doubt it
btw, normally, no further or previous actions (such as wiping data) are required when installing an official update
i'd rather back up all my files anyway before upgrading, just in case
ElKorki said:
there is no stock oreo update at the moment, and nobody knows when it will be released
as it is not out yet, you question cannot have an univocal answer
apparently it will eventually be released as motorola declared about one year ago, but some people, including myself, start to doubt it
btw, normally, no further or previous actions (such as wiping data) are required when installing an official update
i'd rather back up all my files anyway before upgrading, just in case
Click to expand...
Click to collapse
I know that normally you don't have to wipe/reset the device when updating stock, and I know that normally you wipe when flashing different hobbyist roms, and I know there's no release date for Oreo yet. All great facts and I really appreciate the attempt at helping but none of this addresses my question. I'll try again as I obviously wasn't clear enough:
1) Is this device running 32 bit Nougat?
2) Does/Can there exist anywhere a 32 bit Oreo?
3) If the answers are Yes and No respectively, does that mean that in order to upgrade from 32 bit Nougat to 64 bit Oreo a full wipe of app and user data is required?
Webern said:
I know that normally you don't have to wipe/reset the device when updating stock, and I know that normally you wipe when flashing different hobbyist roms, and I know there's no release date for Oreo yet. All great facts and I really appreciate the attempt at helping but none of this addresses my question. I'll try again as I obviously wasn't clear enough:
1) Is this device running 32 bit Nougat?
2) Does/Can there exist anywhere a 32 bit Oreo?
3) If the answers are Yes and No respectively, does that mean that in order to upgrade from 32 bit Nougat to 64 bit Oreo a full wipe of app and user data is required?
Click to expand...
Click to collapse
ok, i'll try to be more schematic
1) yes it is
2) yes, oreo can be 32 or 64 bit. ATM there are no 32 bit oreo custom roms for our device and nobody knows what version will be the official update
2b) all already oreo updated motorola phones run 64bit android, so probably also g5splus ore update will be 64bit
3) nobody can know the exact answer to your question because the update has not been released yet, so nobody could test it yet.
these are my thoughts on the subject:
- the architecture has nothing to do with data partition: only binaries are specific to a processor architecture, not data.
- a full wipe is strongly advised because between different roms there can have differences in folder structure.
- official update is expected to keep your data intact and to takes care of any possible data structure divergencies under the hood during installation
anyway, on lenovo official forum i found this thread
https://forums.lenovo.com/t5/Moto-G5S-Moto-G5S-Plus/Help-Android-Oreo-32-or-64-bit/td-p/3986111
which suggests that your fears are realistic
so i'm no longer very confident about the "taking care under the hood" possibility...
Here you go!
So, the processor is of x64 but stock latest Oreo rom is running on 32-bit mode.
Moto g5s plus is 32-bit
Yes Motorola Moto g5splus is a 32-bit. Checked now on antutu it does says 32-bit, one more proof is the fortnight installer. Fortnight you can't install on Moto g5splus and if you see installers requirements it says OS 64-bit so that's too a one more proof of that.
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about doing this to your device
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.
This is an Android 9.0 GSI (Generic system image ) specific for the Samsung A6!
WARNING: The GSI is unstable and some things are not working. Let me know what is not working please!
FLASHING GUIDE:
1. Formata Dalvik, System, Data and Cache.
2. Install the GSI and click on system image.
3. Reboot to recovery.
4. Install latest Magisk. (Not necessary)
5. Reboot.
BUGS:
No Storage and SD Card access. (On FN Variant)
FIXES
The SIM card reading has been fixed.
Download Link:
https://github.com/phhusson/treble_...9/system-arm32_binder64-aonly-gapps-su.img.xz
Telegram Group:
https://t.me/joinchat/AAAAAEWK3LnN80mnvcTUtA
My telegram username: Paxa202
Credits:
@BlackMesa123
@phhusson
IF THERE IS SOMEONE WHO WANTS TO HELP ME TO MAKE THE GSI STABLE, SEND ME AN PM ON XDA OR AN MESSAGE ON TELEGRAM.
Hello. Is there a thread where we can see how this prosses if done?
ariber14 said:
Hello. Is there a thread where we can see how this prosses if done?
Click to expand...
Click to collapse
The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
phhusson said:
The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
Click to expand...
Click to collapse
So is there a woring android p version for a6 plus or do we have to wait?
ariber14 said:
So is there a woring android p version for a6 plus or do we have to wait?
Click to expand...
Click to collapse
It probably works also with A6+
Shouldn't all GSI ROMs work with all devices with a or ab support or am I wrong?
DKzVeNgEnS said:
Shouldn't all GSI ROMs work with all devices with a or ab support or am I wrong?
Click to expand...
Click to collapse
Yeah but samsung A6 has something unusual, this commented phhusson earlier.
Phhusson: The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
Because the 64bits CPU runs 32bits OS is the reason that normal GSI's doesn't boot on Samsung A6
Working on j6 too
sd card and working is j6.
camera not working and sim not working...
DaanDH12 said:
Yeah but samsung A6 has something unusual, this commented phhusson earlier.
Phhusson: The only thing "unusual" with the A6 is that it's a 64bits CPU running 32bits OS, with 64bits binder.
But that's standard in Android Pie.
So if you build pure AOSP GSI, you just use aosp_arm target.
For my GSI, that would be treble_a64_xxx (like treble_a64_avS-userdebug) target
Because the 64bits CPU runs 32bits OS is the reason that normal GSI's doesn't boot on Samsung A6
Click to expand...
Click to collapse
That's pretty normal for Samsung devices, especially lower spec variants.
A 64bit cpu is backward compatible with 32bit architecture, so shouldn't be an issue as long as the rom supports 32bit, built for ARM target as mentioned above.
ashyx said:
That's pretty normal for Samsung devices, especially lower spec variants.
A 64bit cpu is backward compatible with 32bit architecture, so shouldn't be an issue as long as the rom supports 32bit, built for ARM target as mentioned above.
Click to expand...
Click to collapse
Guys i made a custom rom from stock rom oreo. Everything looks good.i installed it through twrp.it boots,passes the bootlogo and then asks for wifi. I connect to internet.on the next page as normally it searches for updates but is stays there forever.i don't know why. I did it a couple of times and still the same.Internet is ok.and i did not remove anything that could affect google apps or accounts. I would appritiate some advice
ariber14 said:
Guys i made a custom rom from stock rom oreo. Everything looks good.i installed it through twrp.it boots,passes the bootlogo and then asks for wifi. I connect to internet.on the next page as normally it searches for updates but is stays there forever.i don't know why. I did it a couple of times and still the same.Internet is ok.and i did not remove anything that could affect google apps or accounts. I would appritiate some advice
Click to expand...
Click to collapse
Seems you've possibly disabled/removed a component required to facilitate update checking.
ashyx said:
Seems you've possibly disabled/removed a component required to facilitate update checking.
Click to expand...
Click to collapse
But i didn't change anything to the rom
There are some questions that i'm still not sure what to do.like
1.should i choose sparse,raw or permissive?
2. Should i incloude vendorn, odm and cache folder inside the rom?
ariber14 said:
Guys i made a custom rom from stock rom oreo. Everything looks good.i installed it through twrp.it boots,passes the bootlogo and then asks for wifi. I connect to internet.on the next page as normally it searches for updates but is stays there forever.i don't know why. I did it a couple of times and still the same.Internet is ok.and i did not remove anything that could affect google apps or accounts. I would appritiate some advice
Click to expand...
Click to collapse
Skip the whole setup thing! IMPORTANT! skip everything and setup wifi later, if you connect to wifi he goes searching for updates, but if you not connected to wifi, it skips the update part!
DaanDH12 said:
It probably works also with A6+
Click to expand...
Click to collapse
Working on A6+ with sd card but sim card not working
DaanDH12 said:
Skip the whole setup thing! IMPORTANT! skip everything and setup wifi later, if you connect to wifi he goes searching for updates, but if you not connected to wifi, it skips the update part!
Click to expand...
Click to collapse
I did it. Rom is working good. Everything looks great. About the glitch during the setup i just install gapps 8 ARM after flashin Rom and it's ok.
Adb also work for me
The thing is i don't understand why something on google account breaks even though i dont make any changes at all from stock rom. I also get a difference at menu. T mobile, mobile networks and service provider are visible at custom rom menu like in the pic below. Another thing is that i used superr's kitchen 1.1.9.5 to do the job. When i use 2.0.0.5 the custom rom does not boot.
ariber14 said:
The thing is i don't understand why something on google account breaks even though i dont make any changes at all from stock rom. I also get a difference at menu. T mobile, mobile networks and service provider are visible at custom rom menu like in the pic below. Another thing is that i used superr's kitchen 1.1.9.5 to do the job. When i use 2.0.0.5 the custom rom does not boot.
Click to expand...
Click to collapse
I think you should post in a own thread. Otherwise people will confuse your post with the Treble Rom posts
nebkas said:
I think you should post in a own thread. Otherwise people will confuse your post with the Treble Rom posts
Click to expand...
Click to collapse
you are right. i will make a new thread for this
Codelyoko2409 said:
Working on A6+ with sd card but sim card not working
Click to expand...
Click to collapse
I think some proprietary binaries are missing in the rom. But shouldnt be so hard to figure out why sim is not working. What do you think @ashyx ? Should be to solve with tracking the log's?
Note:- Credits To this guide goes to {Diablosss}
GUIDE FOR UNLOCKING BOOTLOADER OF MEIZU PRO 7
(Sorry for the inconvenience, but there are some issues in posting pictures. Therefore requesting you to please check the attached files for images)
This guide can also work with many other Meizu devices. Checked on 15, 16 all options (s, t, x) and on Pro7I post the archive and instructions in pictures.
Step 1: Download. Unpack. Run meizublunlocker.exe
meizublunlocker:-https://drive.google.com/open?id=1yEm_vZo4rsqEtii279AU6l1mBajiSPQ2
See Image 1 in Attachments.
Step 2:-We connect the phone to the computer in fastboot mode (hold down the Vol. Down and power buttons), click refresh. The program must identify the device.
See Image 2 in Attachments.
Step 3ress CheckBL to check bootloader status.
See Image 3 in Attachments.
Step 4:-Click the Create Request button. This will create a file with the end of req.dat in the folder with this program
We send it to the e-mail [email protected] and wait for the response file to unlock the bootloader.
(This takes usually 1 week to receive the unlocked file, but you can donate to get the file within 3 hours)
See Image 4 in Attachments.
Step 5:- After we received the unlock file with the end of res.dat, click UnlockBL and select the resulting file.
See Image 5 in Attachments.
If the file is correct then get this answer
See Image 6 in Attachments.
That's It. We successfully Unlocked the Bootloader.
Now the next thing is to install the TWRP in our Device. ( Further credits goes to{ sergpolov} )
Step 1: Download and install "adb_run"
adb run:-https://drive.google.com/open?id=1y4wdL53-P7mybKsj5XeimHRoMSpokMkQ
Step 2:- Download the required Files.
Stock Recovery Pro 7:-https://drive.google.com/open?id=1e2tRdqLi5jsT8J854RMcIA-jvZyR7xhT
Twrp Pro 7:-https://drive.google.com/open?id=1uYOT9HGractYuoJvRidgAgh8IBLhzFtu
Step 3:-We load the phone into fastboot mode, flash through the fastboot the recovery you need.
Launch the application shortcut
Step 4:-Click "3" - go to fastboot mode
See Image 7 in Attachments.
Step 5:-Click "3" - recovery
See Image 8 in Attachments.
Step 6:-Here we select the recovery file: - in the window that opens, we throw the file itself and close the window with the file and press any button.
See Image 9 in Attachments.
The process has begun.
See Image 10 in Attachments.
Step 7:- Choose "Y" and "Enter"
See Image 11 in Attachments.
The recovery firmware process is over!
Next Few Steps are Extremely Important , so follow with caution!Step 8:-Reboot into Recovery Mode(hold down "Power" and hold, as soon as the screen goes blank, hold down the second button "Volume +" - hold it until vibration and release "Power", and after it release the button "Volume +")
Step 9:-To disable encryption of the "Data" section (who installs TWRP), we immediately flash the zip archive - tool-root_unlock-Testing-Pro7.zip
(disables encryption of the "Data" section, disables Boot and Recovery checks, installs Magisk and disables system root) and reboot into the system.)
tool-root_unlock-Testing-Pro7.zip:-https://drive.google.com/open?id=1a3Gyyuoo2Jv3EN7EWPwj389tXorSwkxT
Attention ! When installing custom recovery (TWRP) on your device, for the full TWRP functionality, you should format the internal memory (Data section) of the device using TWRP itself, since the "Data" section on Meizu smartphones is encrypted, I highly recommend it before installing custom recovery , on creating backups using the internal Flyme firmware (after creating the backup, it is located in the "backup" folder of the internal drive), as well as copying all the necessary data from the phone’s internal memory to the computer!
NOTE:-No One shall be responsible to any damage ocurring to your device
Doubts and queries are welcomed .
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
XRed_CubeX said:
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
Click to expand...
Click to collapse
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
adityadhage said:
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
Click to expand...
Click to collapse
But then for other MTKs like M5C it will never work?
XRed_CubeX said:
But then for other MTKs like M5C it will never work?
Click to expand...
Click to collapse
i know you have already tried this method with your device and it didnt worked. I am not sure that m5c will get another method in future or not. Bcoz we also got lucky with pro 7 that it got successful by the help of guide ported from Meizu 16TH a Qualcomm device.
its now per donation only.
spiramedia said:
its now per donation only.
Click to expand...
Click to collapse
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
cris2d2 said:
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
Click to expand...
Click to collapse
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
adityadhage said:
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
Click to expand...
Click to collapse
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
cris2d2 said:
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
Click to expand...
Click to collapse
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
adityadhage said:
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
Click to expand...
Click to collapse
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
cris2d2 said:
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
Click to expand...
Click to collapse
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
adityadhage said:
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
Click to expand...
Click to collapse
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
cris2d2 said:
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
Click to expand...
Click to collapse
basically you are right
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
deathbreath2010 said:
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
Click to expand...
Click to collapse
this guide is now updated and guranteed to work with x30 also
follow this
https://www.youtube.com/watch?v=Rnuf-uNBnYA&t=319s
adityadhage said:
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
Click to expand...
Click to collapse
its not 5$ its now 15$ its too mutch
sajib_ngage said:
its not 5$ its now 15$ its too mutch
Click to expand...
Click to collapse
try asking them for lower price, they will help u i think. Tell them its for pro 7 bcoz pro 7 requires less work. try ur luck
When I run a Treble Info app on my phone (nora), it displays that my CPU is ARM32. When I look at the device specification here, it claims to have a 64-bit CPU.
Does it mean that I can install any 64-bit GSI ROMs on my device or will it brick my phone?
Seems it is.
Because i have LineageOS 17.1 custom ROM installed on my Moto E5 (XT1944-3)
Also this ROM, isn't a GSI ROM. (But you still can use this ROM for flash an GSI one)
After install it, In Treble Info app, it displays that my CPU is now ARM64 (by the way, can use A/B operating system).
So which you can install an GSI ROM that can be named:
"system-arm64-ab.img.xz"
Notice that you can't install an GSI Rom from 32bit Recovery, you'll need to boot a 64bit recovery.
For last, most of Android 10 GSI ROMS can work well, Android 11 GSI ROMS you will find some bugs and also are heavy, and Android 8.1 or 9.0 GSI Roms won't boot. Like it is bricked.
If you going to install an 64bit GSI ROM, make sure of make backups, in case you're not used to have bugs.
WARNING
This device is an "advanced" tablet that requires a variety of commands and slightly advanced skills. If you don't know words like "adb", "fastboot", "QFIL" ,or "EDL V2 cable", we recommend avoiding customization and operating with ZUI. And I cannot guarantee any damage caused by reading this.
Legion Y700's Stock ROM, ZUI, initially did not support languages other than English and Chinese (I am Japanese) and there was some hassle with using GMS (the latest version, ZUI14, adds an option to use a Google account). So I therefore decided to use GSI to remedy this shortcoming to some extent.
I therefore decided to use GSI to remedy this shortcoming to some extent. This is the flashing process for nazim's crDroid GSI that I wrote about earlier, and the basics are still the same today.
①Unlock bootloader with SN.img. This procedure is the same as for other Lenovo tablets such as the Xiaoxin Pad, so I'll skip this step.
②Put the tablet in Fastboote"d" mode. I usually enter this mode by pressing and holding the volume down and the power button to activate fastboot mode, then selecting "Enter Fastboot" from the recovery menu.
③You have to download the arm64 version from the crDroid GSI link that the text my first post in this thread. I recommend arm64-BgN-vndklite.
④I will assume that you have already configured Android Studio. Start a command prompt and type the command fastboot flash system (the img file you downloaded and unzipped) You can also do this by dragging and dropping the img file into the window before flashing system.
⑤Operate the tablet; proceed to Enter recovery→Wipe data/factory reset to initialize the tablet's data. Otherwise, it will freeze at the title.
⑥Reboot system now and after a while crDroid will start.
Click to expand...
Click to collapse
I recommend crDroid for the following reasons.
This GSI is stable and has few crashes. Performance in games is also kept at a high level.
This GSI supports Face Unlock, which is important because the Y700 does not support fingerprint recognition.
Those who do not need facial recognition or do not want a landscape lock screen can try other ROMs such as LineageOS.
Android 13's GSI is also much more stable than earlier versions. I haven't used it yet because Lawnchair doesn't support it natively, but if you don't, I recommend this one as well. crDroid as well as Project Elixir, which is officially certified, seem to have good battery life.
By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Pixel Experience's Telegram Group.
It is also possible to return to ZUI by using QFIL.
https://smartasw.com/archives/15575
If Bricked by ROM flash, etc., it may be possible to use an EDL V2 cable (sold by Aliexpress, etc.) to make it ready to flash with QFIL.
I have a bit of writing to do, but I will end here. I will add more when I have more time.
These are perfotmance magisk module for Snapdragon 870
①Thermal Qualcomm 870 (recommended for v5.0)
②Adreno GPU Driver for SM8250 (need HuskyDG's overlayfs v1.13)
And now, Adreno 650 in the Snapdragon 870 is clock limited by Qualcomm to 683MHz. I would like to know if anyone knows how to unlock this.
FIERA03 said:
WARNING
This device is an "advanced" tablet that requires a variety of commands and slightly advanced skills. If you don't know words like "adb", "fastboot", "QFIL" ,or "EDL V2 cable", we recommend avoiding customization and operating with ZUI. And I cannot guarantee any damage caused by reading this.
Legion Y700's Stock ROM, ZUI, initially did not support languages other than English and Chinese (I am Japanese) and there was some hassle with using GMS (the latest version, ZUI14, adds an option to use a Google account). So I therefore decided to use GSI to remedy this shortcoming to some extent.
I therefore decided to use GSI to remedy this shortcoming to some extent. This is the flashing process for nazim's crDroid GSI that I wrote about earlier, and the basics are still the same today.
I recommend crDroid for the following reasons.
This GSI is stable and has few crashes. Performance in games is also kept at a high level.
This GSI supports Face Unlock, which is important because the Y700 does not support fingerprint recognition.
Those who do not need facial recognition or do not want a landscape lock screen can try other ROMs such as LineageOS.
Android 13's GSI is also much more stable than earlier versions. I haven't used it yet because Lawnchair doesn't support it natively, but if you don't, I recommend this one as well. crDroid as well as Project Elixir, which is officially certified, seem to have good battery life.
By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Telegram, so I share the link.
https://t.me/poncesgsi/98843
It is also possible to return to ZUI by using QFIL.
https://smartasw.com/archives/15575
If Bricked by ROM flash, etc., it may be possible to use an EDL V2 cable (sold by Aliexpress, etc.) to make it ready to flash with QFIL.
I have a bit of writing to do, but I will end here. I will add more when I have more time.
Click to expand...
Click to collapse
What do you mean by Project Elixir is officially certified?
gogitossj said:
What do you mean by Project Elixir is officially certified?
Click to expand...
Click to collapse
Project Elixir GSI is an "official" GSI because its maintainer, Mr. UGLYKID24, is certified by the Elixir development team. On the other hand, crDroid is an "unofficial" GSI because Mr. Nazim is not certified (Ancient OS, which is also certified under Nazim's ROM, is considered an official GSI).
FIERA03 said:
And now, Adreno 650 in the Snapdragon 870 is clock limited by Qualcomm to 683MHz. I would like to know if anyone knows how to unlock this.
Click to expand...
Click to collapse
I wonder if Konabess working for this
FIERA03 said:
These are perfotmance magisk module for Snapdragon 870
①Thermal Qualcomm 870 (recommended for v5.0)
②Adreno GPU Driver for SM8250 (need HuskyDG's overlayfs v1.13)
Click to expand...
Click to collapse
Hey FIERA03, I see you removed the LPDDR and Cache module. Did they have issue?
- can you show me how to install
"By the way, there seems to be a problem with Android 13 GSI where "Face Unlock" does not work. However, I found a module called biometric-restore in Pixel Experience's Telegram Group." ???
- No double taps, no lift to wake, always use the power button is not convenient
- thank you
Can I apply the Samsung ROM on the link to y700?
[CLOSED] One ui gsi to all samsung
updated 8 times One ui gsi to all samsung no boot loops all features are working now i'm using one ui 5 it's pretty fast For those who want, the best 3 game acceleration magisk modules are below, I've been using them for a long time, it's fine...
forum.xda-developers.com
you486jsm said:
Can I apply the Samsung ROM on the link to y700?
[CLOSED] One ui gsi to all samsung
updated 8 times One ui gsi to all samsung no boot loops all features are working now i'm using one ui 5 it's pretty fast For those who want, the best 3 game acceleration magisk modules are below, I've been using them for a long time, it's fine...
forum.xda-developers.com
Click to expand...
Click to collapse
I think the title said: to all samsung
Mrxyzl said:
제목에 이렇게 적혀 있었던 것 같아요: 모든 삼성에게.
Click to expand...
Click to collapse
I heard that this ROM can be installed and used on P11 and P12. Then, wouldn't it be possible on Y700? I don't have the skills, so I'm asking.
I can't seem to flash the system file, I get this error:
C:\Users\Mike\Desktop>fastboot flash system C:\Users\Mike\Desktop\crDroid-8.13-arm64_bgN-Unofficial.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
I unlocked my bootloader using the "fastboot oem unlock-go" command because I couldn't get the SN.img file to work. It does show my bootloader as unlocked. Could this be my issue? Also, my tablet is 12GB 256GB, not sure if that changes which crDroid file I should flash...any help is greatly appreciated.
I figured it out, I was using an outdated version of fastboot. Downloaded this and worked like a charm!