Related
i bricked my sgy last week
actually i installed a new kernal to overclock sgy
-i installed jellyblast rom
-installed creedsix rom
-installesd new kernal
-wipe data, cache, dalvik cache
problem
-stuck in samsung galaxy y logo
-flashed too many times, still stuck in samsung galaxy y logo
i flashed at least 30 times, with different firmwares.
but still no luck, still stuck there.
i had definitely no idea what to do.
help me. thanks.
Try Flashing the Stock Firmware with ODIN. Search for the Stock Firmware Thread in XDA. If you tried that and it didn't work, you may have to take it to the Service Centre....Here's a tutorial you could find help from--http://forum.xda-developers.com/showthread.php?t=1640668
mayank_saxena said:
i bricked my sgy last week
actually i installed a new kernal to overclock sgy
-i installed jellyblast rom
-installed creedsix rom
-installesd new kernal
-wipe data, cache, dalvik cache
problem
-stuck in samsung galaxy y logo
-flashed too many times, still stuck in samsung galaxy y logo
i flashed at least 30 times, with different firmwares.
but still no luck, still stuck there.
i had definitely no idea what to do.
help me. thanks.
Click to expand...
Click to collapse
Turn it on and leave it off for a day,then try again :good:
Status 7 stands for incorrect zip file.
Btw, i don't get it. Your title asks a question and your post says something else.
||I'm just a PM away for help||
anasdcool71 said:
Status 7 stands for incorrect zip file.
Btw, i don't get it. Your title asks a question and your post says something else.
||I'm just a PM away for help||
Click to expand...
Click to collapse
I am not able to start my phone.
Every time i switch on it .The phone gets stuck on the samasung galay y logo.
When I went in the Android System Recovery Mode (not in CWM) there were lines written in the end stating:
E:failed to mount/cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I went into the CWM tried to flash savie kernel #73 went to device information it stated as follows:
Your Device System and Partition Information
Brand : (didnt state any thing)
Model : (didnt state any thing)
Baseband : (didnt state any thing)
Build Number : (didnt state any thing)
Board Name : (didnt state any thing)
CPU : (didnt state any thing)
LCD Density : (didnt state any thing)
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
and when I started the installation of this kernel it stoped and stated
" assert failed:
getprop("ro.product.device") ==
"GT-S5360" "
and also stated
Installer Status:7
.
I tried to flash the stock rom and checked the device information and now it stated as follows:
Your Device System and Partition Information
Brand : samsung
Model : GT-S5360
Baseband : S5360DDLE1
Build Number : GINGERBREAD.DDLE1
Board Name : totoro
CPU : armeabi
LCD Density : 120
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
but when i started the installation of this kernel. Still the error was same.
Now please tell me what to do .
Please tell me via CWM
Help me asap.
Thanks
mayank_saxena said:
I am not able to start my phone.
Every time i switch on it .The phone gets stuck on the samasung galay y logo.
When I went in the Android System Recovery Mode (not in CWM) there were lines written in the end stating:
E:failed to mount/cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I went into the CWM tried to flash savie kernel #73 went to device information it stated as follows:
Your Device System and Partition Information
Brand : (didnt state any thing)
Model : (didnt state any thing)
Baseband : (didnt state any thing)
Build Number : (didnt state any thing)
Board Name : (didnt state any thing)
CPU : (didnt state any thing)
LCD Density : (didnt state any thing)
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
and when I started the installation of this kernel it stoped and stated
" assert failed:
getprop("ro.product.device") ==
"GT-S5360" "
and also stated
Installer Status:7
.
I tried to flash the stock rom and checked the device information and now it stated as follows:
Your Device System and Partition Information
Brand : samsung
Model : GT-S5360
Baseband : S5360DDLE1
Build Number : GINGERBREAD.DDLE1
Board Name : totoro
CPU : armeabi
LCD Density : 120
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
but when i started the installation of this kernel. Still the error was same.
Now please tell me what to do .
Please tell me via CWM
Help me asap.
Thanks
Click to expand...
Click to collapse
u need to flast stock rom via odin. go to this site it will surely help u http://s5360rom.blogspot.com/p/how-to-install-or-flash-stock-rom-on.html
please press thanks if i helped u.
mayank_saxena said:
I am not able to start my phone.
Every time i switch on it .The phone gets stuck on the samasung galay y logo.
When I went in the Android System Recovery Mode (not in CWM) there were lines written in the end stating:
E:failed to mount/cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I went into the CWM tried to flash savie kernel #73 went to device information it stated as follows:
Your Device System and Partition Information
Brand : (didnt state any thing)
Model : (didnt state any thing)
Baseband : (didnt state any thing)
Build Number : (didnt state any thing)
Board Name : (didnt state any thing)
CPU : (didnt state any thing)
LCD Density : (didnt state any thing)
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
and when I started the installation of this kernel it stoped and stated
" assert failed:
getprop("ro.product.device") ==
"GT-S5360" "
and also stated
Installer Status:7
.
I tried to flash the stock rom and checked the device information and now it stated as follows:
Your Device System and Partition Information
Brand : samsung
Model : GT-S5360
Baseband : S5360DDLE1
Build Number : GINGERBREAD.DDLE1
Board Name : totoro
CPU : armeabi
LCD Density : 120
System Size : -1 MB
Free : -1 MB
Data SIze : -1 MB
Free: -1MB
SD Card Size : 969MB
Free : 809MB
SD-EXT Size :-1MB
Free : -1MB
but when i started the installation of this kernel. Still the error was same.
Now please tell me what to do .
Please tell me via CWM
Help me asap.
Thanks
Click to expand...
Click to collapse
U will still be able to go into download mode
Down+home+Power
Get a stock rom from http://forum.xda-developers.com/showthread.php?t=1465800
And flash using odin
From where u got creed six rom...???
Sent from my GT-S5360 using xda app-developers app
Ritayan Roy said:
Try Flashing the Stock Firmware with ODIN. Search for the Stock Firmware Thread in XDA. If you tried that and it didn't work, you may have to take it to the Service Centre....Here's a tutorial you could find help from--http://forum.xda-developers.com/showthread.php?t=1640668
Click to expand...
Click to collapse
please tell me via CWM
anmolsharma1293 said:
From where u got creed six rom...???
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Didnt remember coz i switched to jellyblast after that.
U can view my problem above
I THINK U HAVE FLASHED ANOTHER PHONE ROM ON U R YOUNG THAT'S WHY IT IS HAPPENING I SUGGEST U TO FLASH STOCK ROM FROM ODIN OR TAKE IT TO SAMSUNG CENTRE
bY
-----------------------SS------------------------OO-----------------------------MM-------------------------KK------------------------LL
mayank_saxena said:
please tell me via CWM
Click to expand...
Click to collapse
Friend, I know you'd prefer CWM as you are a New User...Believe me, I too preferred CWM sometime ago..I bricked my phone atleast three times using CWM before I succesfully installed Merruk 2.5 Deluxe using ODIN(on first attempt)..you just follow the tutorial carefully.You'll get it done for sure..READ THIS AT FIRST-- http://forum.xda-developers.com/showthread.php?t=1640668
There's the ODIN section..Go through it and you'll find it much simpler...I did. Good Luck..!
mayank_saxena said:
please tell me via CWM
Click to expand...
Click to collapse
here u go .try this at your own risk.
Procedure to install Stock ROM in Samsung Galaxy Y GT-5360
1.First download the zip file (link https://hotfile.com/dl/164864526/e7ba5c1/clockworkmod.zip.html) in your computer,extract it. After extracting you will get a folder with three files i.e. Backup, Desktop.jpg, Thumbs.db. and then with the help of USB cable connect the Galaxy Y with computer to place the three files i.e. Backup, Desktop.jpg, Thumbs.db right away in the SD card inside clockworkmod folder. Do not place in any subfolder.
2.Detach the cable
3.Just check that in the backup files there is a folder DDLE1 and in that there is Nandroid.rsf.tar, System.rfs.tar, Cache.rfs.tar etc. if these are missing then again continue the process from beginning.
4.Now its time to turn off the Y to boot into Clockworkmod recovery by pressing the Volume Up key, Home and then power button together. In case you have install the creed ROM then press the power button and select the Clockwork Mod to boot the same.
5.Now wipe data and cache partition. After this select Backup & restore-> Restore-> DDLE1->Confirm-restore DDLE1 and wait for 10 minutes to flash the ROM.
6.When the installation is finished, select ‘Reboot system now’.
If this doesn’t work then you have use odin way.
PLZ PRESS THANKS
I hate to see the people getting their basics wrong and doing it all complicated.
1) First of all, DONT use Creed six ROM, its NOT an official one(not by creed series OP pratyush.creed), its outdated, way better ROMs out there now. Try USSRv8/ Jelly Blast/ Hyperion, they are way better than Creeds Six in every way.
2) Use only XDA posts/ROMs/Kernels to get the correct info, dont rely on 3rd party websites. If you cant find something in xda, you cant find anywhere!
3) Im assuming you are installing Merruk Kernel 2.5 (deluxe #206 kernel) which only supports overclock.
The error code you are getting there is due to the ext4 flashing. Merruk #206 involves the conversion of system,data and cache to ext4 and flashing the kernel in ext4, its a ALL-IN-ONE pack.
To get a perfect combo of flashing merruk dev #206 follow these steps:
1) Flash back to stock ROM (Refer to doky73 thread in development)
2) Flash any custom ROM you desire via CWM( Refer its thread for instructions)
3) Download and copy the latest merruk kernel package(#206 deluxe all-in-one pack) to SD card
4) Backup your ROM using nandroid backup option from CWM
5) Flash the merruk kernel zip via CWM
6) Now, Go to advanced restore in CWM and restore data,system, cache
7) Reboot..
Thats it, your phone is now installed with latest merruk kernel(which involves the overclocking capability).
its mean here is not any solution
its mean here is not any solution of real [Q] how to fix error status 7 in samsung galaxy y
we all know about odin packages on XDA...
i think here is cygwin software issue....... its not for all
or
is this solution?
extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again....
An unlocked bootloader is recommend for flashing custom Roms and kernels.
i think its solution..
There is a prob in ur updater script
Sent from my GT-S5360 using XDA
Kashif.Ali said:
its mean here is not any solution of real [Q] how to fix error status 7 in samsung galaxy y
we all know about odin packages on XDA...
i think here is cygwin software issue....... its not for all
or
is this solution?
extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again....
An unlocked bootloader is recommend for flashing custom Roms and kernels.
i think its solution..
Click to expand...
Click to collapse
hell_lock said:
There is a prob in ur updater script
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
Error 7 means error in updater script. But his query isnt that. The topic heading and the question he asked is completely different.
hitme987 said:
Error 7 means error in updater script. But his query isnt that. The topic heading and the question he asked is completely different.
Click to expand...
Click to collapse
cygwin automatic generating updater script u mean its issue of cygwin...
because u r saying right "its updater script error"
E:Can't mount cache/recovery.....
pustinjak said:
Turn it on and leave it off for a day,then try again :good:
Click to expand...
Click to collapse
Hi, i istalled JellyBlastV3 on Samsung Galaxy Y and it worked perfectly fine..but then I try to install a New Kernel smthng Marvk v2.0, i dnt remember exactly..and i did smthng wrong..it got stuck in bootloops.But Then i Flash Stock ROM with Odin..and it worked pretty good.But Now i am again try to install JellyBlast V3 ..abd When IN CWm when i try to wipe data/reset & Wipe Cache Partition..I Get
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
thsese errors..Nw i dnt know what is the problem ..when i try to wipe in Android Recovery ..it just worked fine...
Please help
Yudi
[email protected]
yudibakshi said:
Hi, i istalled JellyBlastV3 on Samsung Galaxy Y and it worked perfectly fine..but then I try to install a New Kernel smthng Marvk v2.0, i dnt remember exactly..and i did smthng wrong..it got stuck in bootloops.But Then i Flash Stock ROM with Odin..and it worked pretty good.But Now i am again try to install JellyBlast V3 ..abd When IN CWm when i try to wipe data/reset & Wipe Cache Partition..I Get
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
thsese errors..Nw i dnt know what is the problem ..when i try to wipe in Android Recovery ..it just worked fine...
Please help
Yudi
[email protected]
Click to expand...
Click to collapse
Flash ur stock rom by odin or take it to servic centr if ur phone is in waranty...
Press thnx if u got ur phone working back
Code:
/*
* 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 features included in this ROM
* before flashing it! 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.
*/
ROM IS ABANDONED
AospExtended 7.0
Properties
Selinux mode: Enforcing by default
Build type: user
Gapps: not included
Working features
MicroG
Magisk
JamesDSP
MAC randomization
Storage encryption
Known issues
Data partition cannot be backed up by the official TWRP right now
Notes
This ROM is in beta state and not tested well, use as daily driver at your risk and backup everything!
[*]This ROM encrypts storage by default, so far only official TWRP can decrypt storage, don't use OrangeFox!
[*]Follow installation instructions!
If you experience issues, try to change selinux to permissive first
Installation
Flash latest stock ROM from here
Install official TWRP by following instructions in this post
Flash ROM zip to both A/B slots
Flash TWRP zip installer
Reboot to recovery
Flash this patch to fix sim card issue
Flash Gapps (optional)
Flash Magisk (optional)
TWRP can't wipe data partition properly for this ROM and Mi A3 bootloader unfortunately doesn't support partition formatting, so you have to use following workaround to wipe data partition
Reboot to bootloader
Flash this empty image file to userdata partition with fastboot flash userdata userdata.img
fastboot reboot
Cross fingers
Update
Flash ROM zip
Flash TWRP installer zip
Flash this patch to fix sim card issue
Flash Gapps (optional)
Flash Magisk (optional)
Wipe dalvik cache
Reboot to system
Downloads
14.2.2020
Download
Checksum: 7c8c9149d627f03cd30976b164404b13
Older builds
Telegram group
Sources
ROM
Device tree
Kernel
Vendor
Credits
AospExtended team - ROM
@Harukey - device sources
XDA:DevDB Information
[ABANDONED][ROM][10][UNOFFICIAL][BETA] AospExtended 7.0, ROM for the Xiaomi Mi A3
Contributors
Golbinex
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: CrDroid
Version Information
Status: Beta
Created 2020-02-15
Last Updated 2020-03-17
Reserved
Changelog
14.2.2020
Initial public build
@Golbinex
Thank you man. It would be nice if you added some screenshots.
Onurnymr10 said:
@Golbinex
Thank you man. It would be nice if you added some screenshots.
Click to expand...
Click to collapse
Done.
https://forum.xda-developers.com/devdb/project/?id=37481#screenshots
Patch to fix sim card issue was uploaded: URL
Flash it with TWRP.
Thank you thank you thank you and a million times more! Finally a ROM I can use with MicroG. I've been stuck with the stock ROM (and google) since the fall after getting this phone. I'm free once again!
Hello everyone. I tried this rom today. I followed all steps for cleaning format data etc/ flash twrp on
a slot etc/ flash rom/ then install zip.twrp / Reboot recovery/ flash patch/flash gapps/flash magisk/ Reboot bootloader/ flash empty image/ fastboot Reboot..
followed all the steps and for no reason my phone space is almost full...
Anyone knows why?
Noexcusses said:
Hello everyone. I tried this rom today. I followed all steps for cleaning format data etc/ flash twrp on
a slot etc/ flash rom/ then install zip.twrp / Reboot recovery/ flash patch/flash gapps/flash magisk/ Reboot bootloader/ flash empty image/ fastboot Reboot..
followed all the steps and for no reason my phone space is almost full...
Anyone knows why?
Click to expand...
Click to collapse
That is currently bug. Solution should be disabling encryption like in other ROMs and not flashing userdata img at all. Or here is more complicated solution: https://forum.xda-developers.com/showpost.php?p=81782735&postcount=78
Do i need to re install everything thow?
Noexcusses said:
Do i need to re install everything thow?
Click to expand...
Click to collapse
Take a look at that link, you shouldn't lose any data by resizing partition, but definitely backup everything.
Bloo tooth bug - facebook bugs crashing all the time, low speaker... any solotuion guys?
Noexcusses said:
Bloo tooth bug - facebook bugs crashing all the time, low speaker... any solotuion guys?
Click to expand...
Click to collapse
Provide logs for developer I guess?
Bluetooth log
Can confirm, I have the same issue. Bluetooth device connects but no audio is sent to it. I have uploaded a logcat here: https://cloud.reekynet.com/s/ZLDbet9swwT9XFn.
During capturing this log I paired my bluetooth speaker and played music, which came out of the phone speaker.
EDIT: Seems like the interest is around line 6763:
Code:
03-12 17:24:50.042 4026 5467 D GmsGcmMcsSvc: Scheduling heartbeat in 2292 seconds...
03-12 17:24:50.043 4026 3478 D GmsGcmMcsOutput: Outgoing message: HeartbeatPing{}
03-12 17:24:50.175 4026 3477 D GmsGcmMcsInput: Incoming message: HeartbeatAck{last_stream_id_received=5}
03-12 17:24:50.176 4026 3477 D GmsGcmPrefs: learnReached: gcm_network_wifi / 44078
03-12 17:24:51.361 1947 2565 I chatty : uid=1002(bluetooth) e.StateMachines expire 29 lines
03-12 17:24:51.368 1947 2521 I chatty : uid=1002(bluetooth) bt_main_thread expire 27 lines
03-12 17:24:51.369 614 2518 I chatty : uid=1002 [email protected] expire 4 lines
03-12 17:24:51.369 1947 2576 I chatty : uid=1002(bluetooth) bt_a2dp_sink_wo expire 2 lines
03-12 17:24:51.370 1963 2170 I LocalBluetoothProfileManager: Failed to connect A2DP device
03-12 17:24:51.370 1963 2170 D CachedBluetoothDevice: onProfileStateChanged: profile A2DP, device=27:59:BE:CE:45:42, newProfileState 0
03-12 17:24:51.371 1947 2150 I chatty : uid=1002(bluetooth) BT Service Call expire 2 lines
03-12 17:24:51.371 1947 1947 I chatty : uid=1002(bluetooth) com.android.bluetooth expire 5 lines
03-12 17:24:48.193 1214 1923 I chatty : uid=1000(system) Binder:1214_3 identical 1 line
Also, I'm running without gapps, using microG if that matters.
Try to change selinux to permissive. Also mind that build is beta and there are severe issues with current AEX builds.
Golbinex said:
Try to change selinux to permissive. Also mind that build is beta and there are severe issues with current AEX builds.
Click to expand...
Click to collapse
Yeah I knew this going in and I'm willing to use a cable right now because other than this issue the ROM is rock solid and the only one with microG support for the A3
The SELinux setting is grayed out, how do I go about changing it? Found a lot of different guides online
ReekyMarko said:
Yeah I knew this going in and I'm willing to use a cable right now because other than this issue the ROM is rock solid and the only one with microG support for the A3
The SELinux setting is grayed out, how do I go about changing it? Found a lot of different guides online
Click to expand...
Click to collapse
https://f-droid.org/en/packages/com.mrbimc.selinux/
I don't know if it still works, hasn't been updated in almost 3 years so I doubt it but it's what I used to use on an older device
Golbinex said:
[*]Flash this empty image file to userdata partition with fastboot flash userdata userdata.img
Click to expand...
Click to collapse
This did not work. On contrary, the internal available space drop from 128Gb to only 10Gb.
garylawwd said:
https://f-droid.org/en/packages/com.mrbimc.selinux/
I don't know if it still works, hasn't been updated in almost 3 years so I doubt it but it's what I used to use on an older device
Click to expand...
Click to collapse
It works fine.
Technical said:
This did not work. On contrary, the internal available space drop from 128Gb to only 10Gb.
Click to expand...
Click to collapse
You can skip wiping data after flashing stock rom if you don't mind preinstalled xiaomi apps or try methods from other roms. Also you can wipe data with fastboot format:f2fs userdata (wipes internal storage as well!), if you get segmentation fault, try newer fastboot tool.
Golbinex said:
It works fine.
You can skip wiping data after flashing stock rom if you don't mind preinstalled xiaomi apps or try methods from other roms. Also you can wipe data with fastboot format:f2fs userdata (wipes internal storage as well!), if you get segmentation fault, try newer fastboot tool.
Click to expand...
Click to collapse
Thank you, but, I see two problems that I have passed before:
1) I can't boot without wiping data
2) Fastboot do not accept format commands in current MI A3 bootloader
Rom is abandoned, but feel free to try my Crdroid build
I flashed the ROM (Lineage os 17.1) into my device, which is a Xiaomi Redmi Note 7 (code name lavender), after that, I can't access my internal storage. Wiping the data will make the device stuck in a boot loop. I tried "default_password" and "password" but nothing worked. I have not set a password.
u have to "format data "
not just only "wipe data"
u will loose ur interal storage after format
matthias1976 said:
u have to "format data "
not just only "wipe data"
u will lose ur internal storage after format
Click to expand...
Click to collapse
If I format data, I will need to flash the ROM again, and the same problem occurs
When u boot rom and u start configuring it for first time, at secure startup screen(or something like that) tap NO.
zlata said:
When u boot rom and u start configuring it for first time, at secure startup screen(or something like that) tap NO.
Click to expand...
Click to collapse
There is no
zlata said:
secure startup screen
Click to expand...
Click to collapse
Format data and boot rom complete.
I have exacly the same issue. I have tried same operations. I am still looking for a solution...
Format data doesn't change anything since the encryption is done when you boot the Rom the first time.
General Mount question issue
Hello,
twrp can only mount my external card. That seems to be a Device independent issue. All other partitions are not mountable and are displayed with 0 MB. What can I do to fix this?
Google Play Store does not seem to be able to install/Update apps anymore as well.
I have installed:
* latest Twrp version 3.3.1.3
* Android 7.1.2 (Lineage 14-01-180117)
* Sony Xperia X Compact (Kugo)
* Kernal 3.10.18
I've been riding try (via twrp):
* whipe All posibilities (not successful, because not mounted)
* Repair of the partition (not successful, because not mounted)
* change the formatting (ext2 or whatever) (not successful, because not mounted)
* use an older twrp version (no difference)
* remove all start passwords (no difference)
What could be the cause of that and how can it be fixed from my side? Because of the problem, I can't do anything via twrp or install new or Update aps or install a new rom ?
This is the only post I placed, if there is a bretter location, please let me know.
fountain_k said:
...What could be the cause of that and how can it be fixed from my side? Because of the problem, I can't do anything via twrp or install new or Update aps or install a new rom
This is the only post I placed, if there is a bretter location, please let me know.
Click to expand...
Click to collapse
You (and everybody else who has this problem) should install OrangeFox recovery - https://sourceforge.net/projects/or...angeFox-R10.1_01-Stable-lavender.zip/download
fountain_k said:
Hello,
twrp can only mount my external card. That seems to be a Device independent issue. All other partitions are not mountable and are displayed with 0 MB. What can I do to fix this?
Google Play Store does not seem to be able to install/Update apps anymore as well.
I have installed:
* latest Twrp version 3.3.1.3
* Android 7.1.2 (Lineage 14-01-180117)
* Sony Xperia X Compact (Kugo)
* Kernal 3.10.18
I've been riding try (via twrp):
* whipe All posibilities (not successful, because not mounted)
* Repair of the partition (not successful, because not mounted)
* change the formatting (ext2 or whatever) (not successful, because not mounted)
* use an older twrp version (no difference)
* remove all start passwords (no difference)
What could be the cause of that and how can it be fixed from my side? Because of the problem, I can't do anything via twrp or install new or Update aps or install a new rom
This is the only post I placed, if there is a bretter location, please let me know.
Click to expand...
Click to collapse
wipe - advance wipe - select system - wipe it. then intall new custom rom. there might be some bugg. like - twrp will restart 2/3 times. after the custom rom successfully flashed. be careful - dont Ok setup lock screen every boot.
i hope you will be fine. Anyway Thats how i solved my case
EDIT: i take back EVERYTHING i just said
fountain_k said:
Hello,
twrp can only mount my external card. That seems to be a Device independent issue. All other partitions are not mountable and are displayed with 0 MB. What can I do to fix this?
Google Play Store does not seem to be able to install/Update apps anymore as well.
I have installed:
* latest Twrp version 3.3.1.3
* Android 7.1.2 (Lineage 14-01-180117)
* Sony Xperia X Compact (Kugo)
* Kernal 3.10.18
I've been riding try (via twrp):
* whipe All posibilities (not successful, because not mounted)
* Repair of the partition (not successful, because not mounted)
* change the formatting (ext2 or whatever) (not successful, because not mounted)
* use an older twrp version (no difference)
* remove all start passwords (no difference)
What could be the cause of that and how can it be fixed from my side? Because of the problem, I can't do anything via twrp or install new or Update aps or install a new rom
This is the only post I placed, if there is a bretter location, please let me know.
Click to expand...
Click to collapse
The solution for me was to erase the boot area by using "fastboot boot erase" and reflashed the boot area. I can't remember what I have finaly flashed, because I have installed everything new and have a clean installation now.
Nexus 7'13 CROSS - Custom ROM Scripted Setup (c)2020-2021 k23m
CROSS works on PC with Windows, or WinPE if you do not have Windows installed, or VirtualBox with a Windows guest.
Currently supported ROMs:
- Android 10 LineageOS 17.1
- Android 11 LineageOS 18.1
- Android 11 LineageOS 18.1-flox
Previously supported ROMs:
- Android 7 LineageOS 14.1
- Android 7 LineageOS 14.1-microG
- Android 10 LineageOS 17.1-flox
FEATURES
- automatic scan of developer's website for the latest ROM version
- automatic download of all required components
- automatic single-click installation
- optional components like root or special kernel
- all you have to do is select yes/no during the installation
- both flo and deb are supported
PREREQUISITES
- unlocked device
- installed N7 USB drivers
- original eMMC partition layout may be required
All of the above are ensured with RESTOCK - also a scripted tool, available here:
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
---------------------
lineage-install-2.bat
---------------------
This script installs and/or offers the following optional components:
- Android 10 LineageOS 17.1 UNOFFICIAL maintained by ripee https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-17-1-t4038425
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-max.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
---------------------
lineage-install-3.bat
---------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1 UNOFFICIAL maintained by followmsi https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-04-07.3569067/
- TWRP (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip by k23m (optional, no need if already repartitioned)
- root: Magisk (optional)
- GApps: pico (optional)
NOTE: automatic scan of the developer's website is not possible.
Please download the ROM from: https://drive.google.com/drive/fold...HZThGTnM?resourcekey=0-0BunAmDBWluYPghT0Fs6CA
Save it in CROSS' folder and drag-and-drop it on lineage-install-3.bat to start the installation.
--------------------------
lineage-install-3-flox.bat
--------------------------
This script installs and/or offers the following optional components:
- Android 11 LineageOS 18.1-flox OFFICIAL maintained by npjohnson https://forum.xda-developers.com/t/...s-7-2013-wi-fi-repartition-only-flox.4255325/
- TWRP-flox (optional, no need to reflash it if exists already)
- repartition: sysrepart-ultimate.zip (flox compatible) by k23m (optional, no need if already flox-repartitioned)
- root: Magisk (optional)
- GApps: pico unofficial by ipdev (optional)
------------------------
getlog.bat and relog.bat
------------------------
If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post.
----------
fstrim.bat
----------
Improve performance of your eMMC.
---------------
repartition.bat
---------------
If sysrepart repartition is impossible due to TWRP or GPT issues, run the repartition.bat script.
SUPPORT
[FIX][EMMC] Nexus 7 2013 ⊕ bricked, dead, frozen or stuck ⊕
Quick Links if fastboot mode is not available, try Unbricking Guide if fastboot mode is available, do RESTOCK In this thread I would like to consolidate information about eMMC flash memory failures and remedies. When flash memory fails it...
forum.xda-developers.com
[+]RESTOCK - stock restore, repartition, repair and reset, including USB driver fix
RESTOCK is a new Nexus 7 2013 repair and factory reset tool for Windows. The NRT app (Nexus Root Toolkit) is similar but is old, closed-source, unsupported, abandoned, does no eMMC diagnostics and most importantly - it offers no repartitioning...
forum.xda-developers.com
If you select the local file option, CROSS will scan the data folder and offer the newest found file for installation. If nothing is found, you can type/paste a specific file name to install. You can drop anything you like to the data folder - CROSS is now a basic universal ROM installer.
SAMPLE OUTPUT
Code:
Nexus 7'13 LineageOS 17.1 Install v1.3 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]:
--2020-05-15 06:17:53-- https://lineageos.wickenberg.nu/flo/
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'tmp1'
tmp1 [ <=> ] 6.32K --.-KB/s in 0.001s
2020-05-15 06:17:57 (5.33 MB/s) - 'tmp1' saved [6473]
Found for download: lineage-17.1-20200515-UNOFFICIAL-flo.zip
Use local TWRP file? (no if unsure) [y/n]:
Press any key to continue . . .
Downloading installation files.
--2020-05-15 06:19:02-- https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img
Resolving dl.twrp.me... 45.249.91.154
Connecting to dl.twrp.me|45.249.91.154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9271296 (8.8M) [application/octet-stream]
Saving to: 'twrp-3.3.1-0-flo.img'
twrp-3.3.1-0-flo.img 100%[=================================================>] 8.84M 945KB/s in 11s
2020-05-15 06:19:15 (788 KB/s) - 'twrp-3.3.1-0-flo.img' saved [9271296/9271296]
--2020-05-15 06:19:15-- https://lineageos.wickenberg.nu/flo/lineage-17.1-20200515-UNOFFICIAL-flo.zip
Resolving lineageos.wickenberg.nu... 88.129.42.110
Connecting to lineageos.wickenberg.nu|88.129.42.110|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 413523888 (394M) [application/zip]
Saving to: 'lineage-17.1-20200515-UNOFFICIAL-flo.zip'
lineage-17.1-20200515-UNOFFIC 100%[=================================================>] 394.37M 2.71MB/s in 3m 17s
2020-05-15 06:22:34 (2.01 MB/s) - 'lineage-17.1-20200515-UNOFFICIAL-flo.zip' saved [413523888/413523888]
--2020-05-15 06:22:34-- https://jaist.dl.sourceforge.net/project/opengapps/arm/20200515/open_gapps-arm-10.0-pico-202005
15.zip
Resolving jaist.dl.sourceforge.net... 150.65.7.130
Connecting to jaist.dl.sourceforge.net|150.65.7.130|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 101519489 (97M) [application/octet-stream]
Saving to: 'open_gapps-arm-10.0-pico-20200515.zip'
open_gapps-arm-10.0-pico-2020 100%[=================================================>] 96.82M 3.25MB/s in 36s
2020-05-15 06:23:11 (2.73 MB/s) - 'open_gapps-arm-10.0-pico-20200515.zip' saved [101519489/101519489]
--2020-05-15 06:23:11-- https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Resolving github.com... 52.64.108.95
Connecting to github.com|52.64.108.95|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f19-3a5b8341b6e2?
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-
Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a13162209f0fff91
&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filename%3DMagisk-v20
.4.zip&response-content-type=application%2Foctet-stream [following]
--2020-05-15 06:23:11-- https://github-production-release-asset-2e65be.s3.amazonaws.com/67702184/81204200-6ca5-11ea-8f1
9-3a5b8341b6e2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200515%2Fus-east-1%2Fs3%2Faws4
_request&X-Amz-Date=20200515T072529Z&X-Amz-Expires=300&X-Amz-Signature=681f649c20ad2b0eabf80411650867d6db9144197a42a639a
13162209f0fff91&X-Amz-SignedHeaders=host&actor_id=0&repo_id=67702184&response-content-disposition=attachment%3B%20filena
me%3DMagisk-v20.4.zip&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com... 52.216.134.219
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|52.216.134.219|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5942417 (5.7M) [application/octet-stream]
Saving to: 'Magisk-v20.4.zip'
Magisk-v20.4.zip 100%[=================================================>] 5.67M 2.30MB/s in 2.5s
2020-05-15 06:23:15 (2.30 MB/s) - 'Magisk-v20.4.zip' saved [5942417/5942417]
--2020-05-15 06:23:15-- https://forum.xda-developers.com/attachment.php?attachmentid=4480528
Resolving forum.xda-developers.com... 104.18.19.88, 104.18.18.88
Connecting to forum.xda-developers.com|104.18.19.88|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594 [following]
--2020-05-15 06:23:16-- https://dl.xda-cdn.com/4/4/8/0/5/2/8/sysrepart.zip?key=Wwfo1oqhImScVpTSzXTlzA&ts=1589527594
Resolving dl.xda-cdn.com... 104.27.191.76, 104.27.190.76
Connecting to dl.xda-cdn.com|104.27.191.76|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 782958 (765K) [application/zip]
Saving to: 'sysrepart.zip'
sysrepart.zip 100%[=================================================>] 764.61K 591KB/s in 1.3s
2020-05-15 06:23:20 (591 KB/s) - 'sysrepart.zip' saved [782958/782958]
Press any key to continue . . .
1. boot the Nexus in fastboot mode: when OFF press POWER + VOLUME DOWN
2. when in the bootloader menu, connect it to your PC
3. wait a few seconds, then...
Press any key to continue . . .
Verify...
Lock status...
Flash TWRP? [y/n]: y
sending 'recovery' (9054 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.516s]
finished. total time: 0.812s
1. on N7 select "Recovery mode" with volume button
2. on N7 press power button to boot Recovery
3. when you see TWRP main menu press any key to continue
Wait...
*
Installing...
*****
Repartition? (no if already repartitioned) [y/n]: y
Transferring: 782958/782958 (100%)
2575 KB/s (782958 bytes in 0.296s)
***
Wait...
Installing zip file '/sdcard/sysrepart.zip'
Checking for Digest file...
###############################
# k23m Nexus 7'13 Repartition #
###############################
Creating log and gpt backup
Removing partitions
Creating new partitions
Formatting new partitions
###############################
Operation completed. Copy backup gpt and log files from internal storage to PC before rebooting.
###############################
Done processing script file
***
...REBOOTING
When you see TWRP main menu press any key to continue...
*****
Proceed only if you really see TWRP main menu
Press any key to continue . . .
Do dirty flash? (no if unsure) [y/n]: n
Wiping data without wiping /data/media ...
Done.
Formatting Cache using make_ext4fs...
Done processing script file
Formatting System using make_ext4fs...
Done processing script file
Wiping Cache & Dalvik...
-- Dalvik Cache Directories Wipe Complete!
Done processing script file
Formatting cache using make_ext4fs...
Done processing script file
***
Transferring: 413523888/413523888 (100%)
3649 KB/s (413523888 bytes in 110.640s)
***
Wait...
Installing zip file '/sdcard/lineage-17.1-20200515-UNOFFICIAL-flo.zip'
Checking for Digest file...
Warning: No file_contextsTarget: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keysPatching system image unconditio
nally...script succeeded: result was [1.000000]Done processing script file
Install root? [y/n]: y
Transferring: 5942417/5942417 (100%)
3868 KB/s (5942417 bytes in 1.500s)
***
Wait...
Installing zip file '/sdcard/Magisk-v20.4.zip'
Checking for Digest file...
***********************
Magisk 20.4 Installer
***********************
- Mounting /system
- Device is system-as-root
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.tzdata
- System-as-root, keep dm/avb-verity
- Target image: /dev/block/mmcblk0p14
- Device platform: arm
- Constructing environment
- Adding addon.d survival script
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Done processing script file
Install GApps? [y/n]: y
Transferring: 101519489/101519489 (100%)
3623 KB/s (101519489 bytes in 27.359s)
***
Wait...
Installing zip file '/sdcard/open_gapps-arm-10.0-pico-20200515.zip'
Checking for Digest file...
##############################
_____ _____ ___ ____
/ _ \ | __ \ / _ \ | _ \
| / \ || |__) | |_| || | \ \
| | | || ___/| __/ | | | |
| \ / || | \ |__ | | | |
\_/ \_/ |_| \___| |_| |_|
___ _ ___ ___ ___
/ __| /_\ | _ \ _ \/ __|
| (_ |/ _ \| _/ _/\__ \
\___/_/ \_\_| |_| |___/
##############################
Open GApps pico 10.0 - 20200515
- Mounting partitions
- Gathering device & ROM information
- Performing system space calculations
- Removing existing/obsolete Apps
- Installing core GApps
- Installing swypelibs
- Installing calsync
- Installing googletts
- Installing packageinstallergoogle
- Miscellaneous tasks
- Copying Log to /sdcard
- Installation complete!
- Unmounting partitions
Done processing script file
***
Done.
Press any key to continue . . .
SUPPORT - http://bit.ly/2C35sLZ
Press any key to exit...
_____________________________________________________
REPARTITION
sysrepart.zip - 1.1GB system, data is not wiped
sysrepart-max.zip - 1.3GB system, data is not wiped, automatically downloaded by LOS 17.1 script
sysrepart-flox.zip - 1.5GB system, data is wiped, 'vendor' partition is added, automatically downloaded by LOS 17.1-flox script
sysrepart-ultimate.zip - 4GB system, data is wiped, 'vendor' partition is added, 'recovery' is enlarged to 64MB in-place and your current TWRP continues to function, flox compatible, automatically downloaded by LOS 18.1-flox script. For N7-16GB try sysrepart-ultimate-2.zip
sysrepart-stock.zip - data is wiped, original partitions are restored
reboot immediately after repartition!
sysrepart-ultimate/stock work on any previous repartitions
sysrepart/max/flox work reliably only on original partitions
to install GApps larger than pico/nano you need sysrepart-ultimate
sysrepart-ultimate supports custom, oversized TWRP builds
To recover from other repartition attempts, simply install sysrepart-ultimate if you intend to use LOS17+ or sysrepart-stock if you have other plans. If direct sysrepart installation is impossible due to TWRP or GPT issues, run the repartition.bat script. On rare occasions you may have to run RESTOCK and "Restore original partitions" with it.
_____________________________________________________
UPDATE version 2.5 changes:
- update components' URLs
- update relog.bat
- remove installation scripts of no longer available ROMs
- add update.bat cleanup script (run it once)
- add repartition.bat script for repartition-only
- add lineage-install-3.bat script
Download CROSS2.zip and unzip it then download cross-update-XXX.zip and unzip it to the CROSS folder, overwrite existing files.
Also check the very latest interim updates in this post https://forum.xda-developers.com/t/iiiii-cross-custom-rom-scripted-setup.4092215/post-87622749
____________________________________________________
NOTE - most of the attached files are meant for direct script download. Except for CROSS and its updates do not download them manually unless you know what you are doing.
Hi, thank you very much for this useful tool.
I wonder whether your script could be updated to support dirty flash also. Now it seems to always make a clean flash. But it is not very convenient to set up the device after each security update.
I am not very experienced in making batch files but I was thinking about adjusting your script like follows. From:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="Red"]echo.
echo Installing...
call:wait 5
adb shell twrp wipe /data[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
To:
Code:
:adbd
ping -n 3 127.0.0.1 >nul
set /p =*<nul
adb devices >tmp0 2>&1
find /i "recovery" tmp0 >nul
if not %errorlevel% == 0 goto adbd
[COLOR="red"]echo.
set /p FLASHTYPE=Do you want to make clean flash or dirty flash? Clean flash will erase all data (except the files in the internal storage) [clean/dirty]: || set FLASHTYPE=null
echo Installing...
call:wait 5
if /i %FLASHTYPE%==dirty (
echo Skipping wiping data...
echo Performing dirty flash...
goto dirty)
if /i %FLASHTYPE%==clean (
adb shell twrp wipe /data
)
:dirty[/COLOR]
adb shell twrp wipe /system
adb shell twrp wipe dalvik
adb shell twrp wipe cache
call:wait 3
adb push -p %LNZN% /sdcard/
call:wait 3
echo Wait...
adb shell twrp install /sdcard/%LNZN%
Any comment on this? Would this worked correctly?
prorokrak said:
....Any comment on this? Would this worked correctly?
Click to expand...
Click to collapse
Thanks for the suggestion. This code can be abbreviated, same as the other optional items:
Code:
set /p ANS=Do dirty flash? (no if unsure) [y/n]: || set ANS=n
if /i !ANS!==n (
adb shell twrp wipe /data
)
I added it to the v1.2 update.
I just gave this script a try. This is quite slick and saves a bunch of time! Thanks for this. :good:
CROSS 2 release
CROSS version 2.0
- new log script
- new fstrim script
- updated components' URLs
- removed LOS microG as it is no longer available
Both LineageOS 14.1 and LineageOS 17.1 install flawlessly. There may be temporary download issues. If so, retry later. LOS17 server errors...
Code:
Resolving lineageos.wickenberg.nu... 83.209.185.118
Connecting to lineageos.wickenberg.nu|83.209.185.118|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2020-10-11 10:13:40 ERROR 500: Internal Server Error.
:highfive:
Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?
jelles01 said:
Hello I came here from my topic where you suggested me using this. When I fire up lineage-installer2.bat, it can't connect to the server. It asks if I want to use a local file, which I answered yes to. When i gave the name of the file ( "lineage-17.1-20201007-UNOFFICIAL-flo.zip" which I placed inside the CROSS folder, it gave me an error and exited.. What's the deal there?
Click to expand...
Click to collapse
Hi again, first copy eg "lineage-17.1-20201009-UNOFFICIAL-flo.zip" to "CROSS\data" folder, then answer [y] to the question...
Code:
Nexus 7'13 LineageOS 17.1 Install v2.0 @2020 k23m
SUPPORT - http://bit.ly/2C35sLZ
This script assumes that USB drivers are already installed.
If not, then run RESTOCK first or install them manually.
Enter device name (flo=WiFi; deb=LTE) - [flo/deb]: flo
Use local ROM file? (no if unsure) [y/n]: y
Found local file: lineage-17.1-20201009-UNOFFICIAL-flo.zip
As you can see it is found automatically without entering a file name. If nothing is found, you could type any file name but the file must be located in the data folder.
It has worked! The install and setup was buttery smooth, thank you so much for this tool. Amazing!
A little help.
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1?
Thanks in advance!:highfive:
GeekyTanuj said:
I am about to receive my refurbished unit in a couple of days. chances are that it will likely be on the last stock software. I have a general knowledge about rooting and installing custom ROMs on a variety of devices but nexus 7 seems different to work it. Will this script automatically root and install the TWRP apart from the designated flavor of lineageOS?
Also, will I need to go through the prerequisites (i.e. RESTOCK) procedures even if I am on stock ROM and partition by default? Will I need to repartition every time when switching ROMs after this? Can the CROSS be used again if i had to switch from say LOS 17.1 to 14.1? Thanks in advance!:highfive:
Click to expand...
Click to collapse
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:
You are a lifesaver!
k23m said:
Refurbished N7s usually come with old KitKat stock and it is advisable to run RESTOCK first to update the bootloader before flashing LineageOS. Also RESTOCK will unlock it and install N7 USB drivers on your Windows.
Yes, CROSS can be used multiple times, and will root and install TWRP. Repartition is required only once.
Pro tip: for LineageOS updates answer [y] to the "Do dirty flash?" question to retain your OS settings and apps. But being "dirty", it may not work properly after major OS changes.
Should there be LOS17 server download issues, get lineage-17.1-20201017-UNOFFICIAL-flo.zip from an alternative server and drop it into CROSS' data folder as described in this post.
Cheers
:highfive:
Click to expand...
Click to collapse
Thank you so much for developing this, RESTOCK as well as stock MM debloat script. it literally saved hours and hours of hassle that one has to face while getting to different versions of android! Running 10 with latest updates. feels so good!
kernel Configuration.
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:
GeekyTanuj said:
While Android 10 seems tempting and it actually is, it isn't just offering the kind of experience I am looking for and hinders my daily experience in one or the other way.
Looks like you might be using LOS 14.1 with the ElementalX kernel. Can you recommend the best settings for video playbacks and light gaming? Please share your configuration as well.
Thanks and cheers!:highfive:
Click to expand...
Click to collapse
For video and games LOS17 seems optimal, check these benchmarks.
Personally I use LOS14 without Gapps and with EX kernel including a modification to the battery life extender. I lowered max battery charge to 4.00V which is equivalent to 75% (under)charge resulting in 8x increase of battery life. Furthermore, the mod allows for constant external power connection and no battery overcharging nor overheating/swelling. I edited "buildconfig.sh" in EX zip:
Code:
replace
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4200" >> $CONFIGFILE
with
echo "write /sys/devices/i2c-0/0-006a/float_voltage 4000" >> $CONFIGFILE
:good:
You gave my Nexus 7 (2013) a new lease on life! Woo-hoo!
I was running a years-old version of the vanilla stock FW and it was soooo slow. Somebody in some comment section somewhere mentioned RESTOCK & CROSS, so I tried out RESTOCK2 and it worked flawlessly.
Then I tried installing 17.1 via CROSS2 without repartitioning (as I believed RESTOCK did that). I got an error that I did not save, hoping it wasn't a big deal. I got stuck on the Google loading screen, so I ran CROSS again. I was going to try 14.1, but wasn't given the option again (bonus? 17.1 looks beautiful and it didn't make me redownload anything, which was smart coding on your part).
I think I should have run the logging programs when I first saw errors, because I'm afraid they were cleared by the reinstallation. I did send what I could after running the loggers post-successful installation, just in case.
Now, 17.1 is working so smoothly with a quick Netflix sideload (no GApps here, used APKMirror + the APKMirror Installer) - which certainly is only working thanks to Magisk. How long did it take me to figure out how to put app icons on the homescreen (swipe up, of course!) I don't think I want to reveal
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!
iforget said:
I think the only thing I'm missing is DoubleTap2Wake which I installed with RESTOCK but see now it wasn't an option with 17.1 via CROSS. Apparently somebody has it goin' on LOS17.1 or 18 but this was so easy, not sure I want to try messing with a custom kernel just yet until I get a little bored.
Thank you so much--it's unbelievable there aren't 8 million comments on this thread, it's SO well done. If you made this for a modern/uber-popular tablet surely there would be though. Thank you thank you thank you!
Click to expand...
Click to collapse
If the Lineage build is using followmsi's sources, then you do not need to change kernels.
You just need to activate DT2W.
See this post on how to activate using a kernel manager.
The thread with the ever changing name. xda thread - Link
If you want something simple, I use a magisk module that enables it on boot.
DT2W GitHub - Link
Cheers.
PS.
Sorry for a bit of OT.
PPS.
The Lineage 17.1 build is using followmsi's sources.
hi
I have issue with otg on my N7, i used cross2 without problems : i installed twrp, lineageos 14, root the nexus and installed elementalx and googleapp
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ?
it's a kernel issue?
any app works
thx
gibnexus said:
my usb otg cable with a usb key is never detected , i can mount the usbstick with twrp (sometime i can see it sometime not in twrp) but after few minutes it diseppear
someone can help me ? it's a kernel issue?
Click to expand...
Click to collapse
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.
k23m said:
LOS14+EX kernel OTG is OK. Use the built-in file manager.
There could be a hardware issue - pin #4 may have a dry joint and work intermittently.
Click to expand...
Click to collapse
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx
gibnexus said:
Hi man
thanks for your answer but it’s not a pin 4 issues , I have just changed the daughter board, and this evening I used restock2 , I restocked, install twrp, used the fix 30 and root but don’t install elementalx
I used the app usb otg helper and everything is ok
I can see my usb stick..
Help me please .. I like s2w and 2tw to turn on my screen
I would have the both otg and gesture to awake and used a better android system like lineageos
Thx
Click to expand...
Click to collapse
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all
gibnexus said:
Hi
I begin to believe it’s my otg cable who has some trouble
I will buy a new one and see ...
Just a last question elementalx and los 14 support otg without nothing else ? ( no app or addons ? )
So thx to you for your work my old nexus was sleeping in a corner and now it’s relive
Thx for all
Click to expand...
Click to collapse
I can assure you that straight LOS14+EX OTG works fine.
You must have enabled the "USB OTG + charge mode" option which is meant for car use or externally powered OTG devices. It is NOT NEEDED for normal, N7-powered OTG storage.
This thread is for sharing your experiences with Project Treble GSI images on the Lenovo Smart Tabs M10 (TB-X605F/L) & P10 (TB-X705F/L). I'll update this post as more things are discovered.
You can load Android 10 and 11 GSI ROMs on top of Lenovo's stock Pie ROMs.
You can also load Android 10 and 11 GSI ROMs on top of Lenovo's stock Oreo ROMs. There are some graphics glitches when you use the stock Oreo ROMs.
WARNING 1: this procedure will wipe your whole device (including data). So do a backup first.
WARNING 2: this is experimental. If you don't know what you're doing, then you could brick your device. The risk is all yours.
Loading over stock Pie
unlock the bootloader (if not already unlocked)
download Disable_Dm-Verity_ForceEncrypt.zip (created by @Zackptg5). If you want your data partition encrypted, then rename the zip file to Disable_Dm-Verity_enfec.zip. We'll use this to disable dm-verity on boot.
download modify_phh_gsi.sh to your SDcard or OTG device. I wrote this script to by-pass phhusson's read-write mount of /system during boot, which freezes our tablets. The script also runs resize2fs to make the /system filesystem take up the whole /system partition. Don't forget to make this script executable with chmod.
copy those files to your SDCard or OTG device:
Code:
adb push modify_phh_gsi.sh /external_sd/
adb shell chmod a+x /external_sd/modify_phh_gsi.sh
adb push Disable_Dm-Verity_ForceEncrypt.zip /external_sd/
[B]only if you want an encrypted data partition[/B]: adb shell mv /external_sd/Disable_Dm-Verity_ForceEncrypt.zip /external_sd/Disable_Dm-Verity_enfec.zip
load the stock Pie ROM using LMSA rescue mode or QComDLoader
boot the device into fastboot (Power+VolDown)
flash the GSI image: fastboot flash system your_gsi.img (you can install the GSI image in twrp, if you prefer)
flash TWRP (for Pie): fastboot flash recovery pie_twrp.img
boot into twrp (pwr+VolUp+VolDown)
format Data partition
install Disable_Dm-Verity_enfec.zip or Disable_Dm-Verity_ForceEncrypt.zip
run modify_phh_gsi.sh and boot the GSI:
Code:
adb shell /external_sd/modify_phh_gsi.sh
adb reboot
(optional) if your GSI doesn't include Google Apps, then download and install a gapps zip (ARM64) in TWRP. I use "pico", but choose the one that suits you. Do this after running modify_phh_gsi.sh - to avoid running out of space.
reboot to system
Loading over stock Oreo
unlock the bootloader (if not already unlocked)
download and unzip the stock Oreo ROM
load the stock Oreo ROM using QComDLoader, and your device in EDL mode. When it's finished, do not boot into the system. QComDLoader configuration settings:
Code:
Download Mode: Upgrade
Chipset: 8953
eMMC Programmer: prog_emmc_firehose_8953_ddr.mbn
Raw program: rawprogram_unsparse_upgrade.xml
patch0: patch0.xml
boot the device into fastboot (Power+VolDown)
flash the GSI image: fastboot flash system your_gsi.img (you can install the GSI image in twrp, if you prefer)
flash TWRP (for Oreo): fastboot flash recovery oreo_twrp.img
boot into twrp (pwr+VolUp+VolDown)
(optional) if your GSI doesn't include Google Apps, then download and install a gapps zip (ARM64) in TWRP. I use "pico", but choose the one that suits you. OpenGApps isn't officially available for Android 11 yet.
(optional) to get the right pixel density, add "ro.sf.lcd_density=240" to vendor/build.prop. I wrote gsi4tablet.sh to do this for you. Run it in twrp adb shell. Make sure the script is executable (using chmod).
reboot to system
Here are some links to Lenovo's stock Oreo ROMs:
TB-X605F: TB-X605F_USER_S000022_20181026_Q00020_ROW_Bundle
TB-X605L: TB-X605L_USER_S000020_20180921_Q00020_ROW
TB-X705F: TB-X705F_USER_S000017_20180831_Q00020_ROW
TB-X705L: TB-X705L_USER_S000023_20180921_Q00020_ROW
Choosing a GSI image
@phhusson keeps a full list of Project Treble GSI images.
Our devices are all ARM64 A-only. This means that you should only get ARM64 and A-only GSI images. Anything else will not work.
If there is an ARM64 A-only "vndklite" GSI, you can use that.
But do not use AB (or AB vndklite) GSIs, because this tablet is non-System-As-Root (nonSAR).
Note for A11: there is no A-only GSI with vndklite. So just use the A-only GSI.
"This device is not Certified by Google"
If you get this message when you boot the GSI, use ADB and follow instructions under "How to bypass certified device after first boot?".
If you can't find sqlite3 in adb, then install the Device ID app from this XDA article to get the GSF number on your tablet.
"Insufficient storage space available in System partition"
If you get this error message when trying to install GApps, read this post.
What about Android 12 ?
There are no non-SAR A12 GSIs for these tablets, because of the vndk-lite implementation.
If you want to try Android 12, visit this thread about converting the tablet to system-as-root (SAR). It is also experimental.
How do I repartition my tablet?
You might want to do this to increase the size of the system partition. Google it, if you like. But there are no instructions on this thread. No one wants to support noobs who trash their partition tables.
Where do I find... ?
QComDLoader is downloaded during an LMSA rescue. You'll find it in C:\ProgramData\LMSA\Download\ToolFiles\QcomDLoader_1.3.2\QcomDLoader_1.3.2. Alternatively, @Chaser42 has a link and some instructions at the bottom of the first post in this thread.
EDL mode: the easiest ways to enter EDL mode are: adb reboot edl or in TWRP: Reboot->EDL Mode. Alternatively, from a powered-off device: insert USB cable while holding VolUp
TWRP for Oreo for TB-X605F/L.
TWRP for Oreo for TB-X705F/L.
Magisk (for phhusson-based GSI ROMs) lives here.
GApps lives here.
Disable_Dm-Verity lives here.
Last modified: 2 September 2022 (add note about A11 and vndklite)
Since you mentioned me, I've taken a brief look - can you boot ARM64 AB on Pie? On many devices, updating to Pie changes the arch to AB. Note that "A/AB" in GSI is not the same thing as physical partition layout.
AndyYan said:
Since you mentioned me, I've taken a brief look - can you boot ARM64 AB on Pie? On many devices, updating to Pie changes the arch to AB. Note that "A/AB" in GSI is not the same thing as physical partition layout.
Click to expand...
Click to collapse
On stock Pie, Hackintosh5's app reports it's an A-only device supported by VNDK 28 Lite. System properties confirm that.
I just tried to load an AB GSI ROM over Pie. The device boots to qcom diagnostic 900E mode.
So looks like it's definitely A-only on stock Pie. There's just something unusual about the treble implementation on stock Pie.
Loading an A-only GSI over stock Pie just hangs on reboot. It never gets to the boot animation. I've unsuccessfully tried different combinations of permissiver, disable_dm-verity and magisk. No luck.
(There is no vbmeta partition, by the way.)
But thanks for the suggestion about trying AB. It was worth a try.
Yahoo Mike said:
I have successfully loaded @phhusson 's AOSP 10.0 ("Quack") and @AndyYan 's LineageOS 17.x on my TB-X605F.
Click to expand...
Click to collapse
Hi Yahoo Mike,
is the LOS 17 fully functionnal on TB-X605F?
Thanks
Success and Failure
I went through the process above and this worked great. I do have one small problem......
Twrp loads with a black screen and is unusable from the tablet screen in recovery mode. Fortunately this isn't a big deal if you use adb from your pc to control twrp.
2. FLASHING GAPPS
Put the tablet into recovery from adb or through hardbuttons.
open cmd:
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
kmh5147 said:
I went through the process above and this worked great. I do have one big problem and another not so big.
The not so big problem; twrp loads with a black screen and is unusable from the tablet screen in recovery mode. Fortunately this isn't a big deal if you use adb from your pc to control twrp.
The big problem; after loading linos 17 and also ASOP 10, I am unable to run the gapp suite. After installing the gapp suite using twrp on linos 17, linos almost becomes unusable. After installing ASOP with the integrated Gapps, it's also almost not usable upon startup. The problem is with certification of the device, I get millions of messages upon startup after installing the gapp suite or installing a rom with the gapp suite. The message effectively is "This device is not Certified by google"
Click to expand...
Click to collapse
TWRP for Oreo (8.1)
Here's a version of TWRP for Oreo (8.1) for TB-X605F/L. It doesn't mount the data partition, but everything else works. I'll try to fix the data partition next week.
Does anyone have a TWRP for Oreo for TB-X705F/L ?
This device is not Certified by Google
This seems to be a common problem with GSI images.
Use ADB and follow instructions under "How to bypass certified device after first boot?".
Note that the GSF can change whenever you do a factory reset. If it changes, you need to register the new GSF.
Monpseud0 said:
Hi Yahoo Mike,
is the LOS 17 fully functionnal on TB-X605F?
Thanks
Click to expand...
Click to collapse
I don't know if LOS is "fully" functional. I loaded it, but didn't thoroughly test it. Wifi worked.
I've been using Quack and it's stable. Wifi, camera, bluetooth, audio all work. NovaLauncher works fine. Some graphics flicker until they load. I haven't found the right settings under "Phh Treble Settings" to stop that.
kmh5147 said:
I went through the process above and this worked great. I do have one small problem......
Twrp loads with a black screen and is unusable from the tablet screen in recovery mode. Fortunately this isn't a big deal if you use adb from your pc to control twrp.
2. FLASHING GAPPS
Put the tablet into recovery from adb or through hardbuttons.
open cmd:
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
Click to expand...
Click to collapse
I would recommend going with lineage os based on my testing so far. Some apps are a little buggy with flickering, and random minor issues hear and there. I'm thinking we need an updated bootloader, is a newer bootloader available???
Lineage OS 17
I just wanted to give an update with lineage 17, I was able to get passed the issues with the gapps by registering the google services id through their webpage.
Everything thing seems to work very well...... wifi, audio, and both front and rear camera work perfectly. The only problem I am still dealing with is flickering in overlay situations, and nothing I've tried from a developer settings perspective fixes the issue. If the flickering can be fixed, I think we'll have a really good option here.
One other thing I wish I could get working in this lineage OS is the google assistant ambient mode. I can't get the option to show up in the assistant settings. Have ambient mode on this tablet would be perfect with the original alex cradle.
kmh5147 said:
I'm thinking we need an updated bootloader, is a newer bootloader available???
Click to expand...
Click to collapse
I think we're stuck with this bootloader until we can work out how to load GSI over stock Pie.
kmh5147 said:
The only problem I am still dealing with is flickering in overlay situations, and nothing I've tried from a developer settings perspective fixes the issue. If the flickering can be fixed, I think we'll have a really good option here.
Click to expand...
Click to collapse
I'll have a look at the overlays on the weekend. Maybe that will fix our problems.
Which device do you have? They might all need slightly different overlays.
I tried HavocOS (2020-07-09) with GApps. It booted and was pretty smooth, but I couldn't enable root or adb. Might need to wait for the next release.
It also insisted on face unlock, which was annoying.
Here's a guide on how to fix the "Insufficient storage space available in System partition" when you try to install GApps.
solution
In TWRP:
press "Mount"
untick "Mount system partition read-only", then tick "System".
go back to main menu and select "Wipe". Don't panic. We're not going to delete any files from the system.
select "Advanced Wipe"
tick "System" and select "Repair or Change File System"
select "Resize File System". If that button is not there, then you mounted the system partition as read-only. Go back and untick that.
confirm that TWRP is asking "Resize System?" and then swipe to resize
now you can go back to main menu and install GApps
why does this happen?
The system partition is roughly 3GB in these devices. However, after flashing a GSI image, the filesystem size can be considerably less.
For example:
Code:
X605F:/ # df -H
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 26M 1.3G 2% /
tmpfs 1.4G 188k 1.4G 1% /dev
tmpfs 1.4G 25k 1.4G 1% /tmp
/dev/block/mmcblk0p26 260M 172k 260M 1% /cache
/dev/block/mmcblk0p52 25G 46M 25G 1% /data
/dev/block/mmcblk1p1 128G 24G 104G 19% /external_sd
/dev/block/mmcblk0p24 1.9G 1.8G 60M 97% /system
X605F:/ # blockdev --getsize64 /dev/block/mmcblk0p24
3221225472
In this example, the partition size of /system is about 3.2GB (3221225472), but the filesystem size is 1.9GB with only 60M free. Because there's only 60M free, GApps fails with the message "Insufficient storage space available in System partition".
The solution is to resize the filesystem to include the unused 1.3GB on the partition. That's what TWRP does in the solution above.
Here's our example filesystem after following the steps above:
Code:
X605F:/ # df -H
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 26M 1.3G 2% /
tmpfs 1.4G 188k 1.4G 1% /dev
tmpfs 1.4G 45k 1.4G 1% /tmp
/dev/block/mmcblk0p52 25G 46M 25G 1% /data
/dev/block/mmcblk1p1 128G 24G 104G 19% /external_sd
/dev/block/mmcblk0p24 3.2G 1.8G 1.3G 59% /system
There's now 1.3GB free on the filesystem because it's been resized to fill up the whole partition. TWRP saves the day (again) ... and GApps is happy!
Yahoo Mike said:
I think we're stuck with this bootloader until we can work out how to load GSI over stock Pie.
I'll have a look at the overlays on the weekend. Maybe that will fix our problems.
Which device do you have? They might all need slightly different overlays.
Click to expand...
Click to collapse
Hi Mike, I have the TB-X605F and its hardware version is 60.
Thank you for all of the effort in making this thing work!
I was also able to install AOSP 10.0 Quack on my TB-X705F using your guide. Thanks so much! Didn't install TWRP yet as I don't know if it supports Oreo. With regard to that, i'm assuming it refers to the vendor rather than the rom we're running, correct?
I did encounter a little bit of flickering for some graphics. It's very intermittent. Seems like it affects dark grays more than anything. Most everything works fine. Will try some others and report back.
Yahoo Mike said:
I tried HavocOS (2020-07-09) with GApps. It booted and was pretty smooth, but I couldn't enable root or adb. Might need to wait for the next release.
It also insisted on face unlock, which was annoying.
Click to expand...
Click to collapse
What 'smallest width' are you putting in the developer option. The standard DPI settings are for a phone i'm assuming because everything is huge lol. So far I feel like 600 & 790 are good settings depending on how large you want things.
---------- Post added at 07:29 PM ---------- Previous post was at 06:59 PM ----------
Running the July Build of Descendant X and so far its pretty awesome. I've noticed that the flickering seems to be limited to Google Applications. For instance if you scroll through the Play Store.
Mr. Jedge said:
...Didn't install TWRP yet as I don't know if it supports Oreo. With regard to that, i'm assuming it refers to the vendor rather than the rom we're running, correct?
Click to expand...
Click to collapse
That's correct. TWRP needs to be compiled with a kernel from a stock Oreo boot.img.
The TWRP for Pie seems to be incompatible with the stock Oreo vendor/firmware/bootloader we have to load before flashing a GSI. TWRP is functional, but the screen is blank. That's fixed by compiling TWRP for 8.1 with the stock Oreo kernel.
But you might want to try the X705 TWRP (for Pie). You might get lucky and it works.
Yahoo Mike said:
I think we're stuck with this bootloader until we can work out how to load GSI over stock Pie.
I'll have a look at the overlays on the weekend. Maybe that will fix our problems.
Which device do you have? They might all need slightly different overlays.
Click to expand...
Click to collapse
Do you think the flickering is an overlay issue, or an issue with the vendor? I was going to try flashing a different Oreo build to check, but it looks like there are no full images other than the original; only OTAs.
Mr. Jedge said:
Do you think the flickering is an overlay issue, or an issue with the vendor?
Click to expand...
Click to collapse
I built and installed a vendor overlay, but it didn't fix the flickering. I'm not really sure it did anything.
I started playing with the "smallest width" parameter you found. On stock Oreo it's set to 800dp. When I used 800dp on the GSI, most (but not all) of the flickering stopped. At 600dp, the flickering started again.
The "smallest width" also seems to affect calculations for the keyboard display. For some dp settings, the input dialog box is not drawn. It's there, but it's just not rendered. You can test it with the "smallest width" option. When you change the dp, just tap the option again. With some dp settings (like 700dp), the input text box is "invisible". You can use the keyboard to change the dp, but your input is not displayed while you are typing. Set it back to 800dp, tap on the option again and the input box is there.
While 800dp stops most of the flickering in PlayStore, the drawer (swipe from the left) writes over the whole screen.
843dp fixes the drawer problem, but does weird things to the soft buttons (back/home/recent).
840dp fixes soft buttons but the drawer problem returns.
And to make it even more complicated, portrait mode seems to prefer different dps. 721dp worked ok in portrait, but not in landscape.
It's going to be a matter of finding the sweet spot. Or perhaps there's a second setting that also needs to be changed at the same time ???
Anyway, give it a try.
New discovery. I downloaded a DPI changer to use instead if the smallest width option. Changing the DPI didn't yeild any difference in reference to flickering, but changing the resolution did. Default resolution is 1200 x 1920 which matches Lenovos specs. However I lowered it to 1180 x 1900 and the flickering has gone away completely....at least in the play store. Haven't noticed it anywhere else. The drawer blanks out the rest of the store however which is weird but acceptable. I'll keep playing around, but it's time to go-to bed.
Mr. Jedge said:
New discovery. I downloaded a DPI changer to use instead if the smallest width option. Changing the DPI didn't yeild any difference in reference to flickering, but changing the resolution did. Default resolution is 1200 x 1920 which matches Lenovos specs. However I lowered it to 1180 x 1900 and the flickering has gone away completely....at least in the play store. Haven't noticed it anywhere else. The drawer blanks out the rest of the store however which is weird but acceptable. I'll keep playing around, but it's time to go-to bed.
Click to expand...
Click to collapse
Interesting.
Only thing I can add is that if you add the following to /vendor/build.prop you don't get that big font during configuration when you install a GSI.
Code:
ro.sf.lcd_density=240
In stock that is set in /system/build.prop.
Most of the GSI images assume lcd_density of 480 (xxhdpi) for mobiles, but our tablets are 240 (hdpi).