Related
I have been woeking on a custom kernel I will be releasing shortly but I am having a problem with it. Everything works great with it but when I change the kernel version # and attempt to boot it freezes at rhe samsung screen. I tried insmod -f and compiling with modversions enabled and it continues to freeze and I do not know how to pull a /proc/kmsg during a failed boot to find out as adb does not appear to be active. I suspect a module is barfing at the higher kernel version #. Anyone have a suggestion?
Don't change it.
Its a problem several have had, but with no clear solution yet.
Solution found
Hex edit binary modules from samsung with current required source version...not kosher but it boots and plays well with others. Use my soon to be released kernel as an example.
[ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Wileyfox Storm
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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 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.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on kipper
Official Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want)
Changelog:
Changes for kipper
Bug reports:
How to submit a bug report
LineageOS JIRA
Donate to support development:
Donate via PayPal to jrior001
Donate via PayPal to LineageOS
XDA:DevDB Information
LineageOS, ROM for the Wileyfox Storm
Contributors
jrior001, jrior001, mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Created 2018-05-20
Last Updated 2018-09-10
Reserved
Updated recovery required
http://www.theflamingskull.com/downloads/kipper/TWRP-kipper-3.2.3.img
Test Build #1
* permissive selinux for debugging purposes
Test build #2 5/30/18
camera/flashlight and UI lag resolved
the last build works well
lineage-15.1-20180902-UNOFFICIAL-kipper
i cant instal instagram app
nightly 2018-09-10
1. I installed Instagram , but it doesn't play video
2. please fix the widgets
3. when I use dark theme ( dark mod theme)
the icons of "turn on/off" in "privacy guard" don't change the color
Can't install gapps (tried pico (stuck on logo) and stock (error 70 in TWRP)).
OK, let's go w/o gapps. Can't install .apk files.
Monate said:
Can't install gapps (tried pico (stuck on logo) and stock (error 70 in TWRP)).
OK, let's go w/o gapps. Can't install .apk files.
Click to expand...
Click to collapse
From opengapps, pico and nano should fit. I'm not sure what error 70 is but if you grab the entire recovery log from a failed flash I'll be glad to look it over.
With device in recovery, after your failed flash hook up to PC, and run "adb pull /tmp/recovery.log"
Sent from my PH-1 using Tapatalk
jrior001 said:
From opengapps, pico and nano should fit. I'm not sure what error 70 is but if you grab the entire recovery log from a failed flash I'll be glad to look it over.
With device in recovery, after your failed flash hook up to PC, and run "adb pull /tmp/recovery.log"
Click to expand...
Click to collapse
Both gapps were taken from opengappsorg.
Pls, help me with 1 more thing: I want to format /data from ext4 to f2fs but I got an error. Log contains both errors.
Aaaand... I didn't find how to attach a file ;(
UPD: https://drive.google.com/open?id=1ecgkLr7jRasryLgmKvPTaxsqdNcfHGPC
Monate said:
Both gapps were taken from opengappsorg.
Pls, help me with 1 more thing: I want to format /data from ext4 to f2fs but I got an error. Log contains both errors.
Aaaand... I didn't find how to attach a file ;(
UPD: https://drive.google.com/open?id=1ecgkLr7jRasryLgmKvPTaxsqdNcfHGPC
Click to expand...
Click to collapse
The only gapps attempt in that log was opengapps "STOCK" version which has everything. That won't fit, stick with PICO or NANO, I believe both of those will fit on 15.1, anything else you want you can get from Play Store.
Also I updated the link in post #2 to a newer TWRP version. I was able to convert /cache to f2fs just fine with that one.
Whatsapp video player is not working.
iN4sser said:
Whatsapp video player is not working.
Click to expand...
Click to collapse
Whatsapp and Instagram videos are both wonky. I'm aware. The only fix I have found breaks more than it fixes so for now we're stuck like this.
Sent from my PH-1 using Tapatalk
Hey. After the appearance of this error, I decided to try again to install LOS 15.1 (installed on f2fs, so the gapps did not fit). I downloaded Apkpure.apk through a standard browser, found it through a standard file manager, clicked, but nothing happened. Rebooting the device did not help. I tried to find in the settings the item "installation from unknown sources" (somehow it is called so), but it is not there. What to do?) The same problem was before on ext4.
build lineage-15.1-20181106-nightly-kipper-signed
UPD found solution: open file from internal storage
When the official image for kipper moved from LineageOS 14 to LineageOS 15, I destroyed my telephone by not noticing that the new OS wouldn't fit in the partitions and rebooting. I then wiped the phone, restored an older LO 13 (cm-13.1.2-ZNH2KAS3NA-kipper-signed-fastboot-1eb4b5e94b.zip) via fastboot flash and was back in business.
Since TWRP won't recognize SD card and/or USB memory device, I used adb sideload to install LineageOS 15 (lineage-15.1-20181230-nightly-kipper-signed.zip). The TWRP output ends with "script succeeded: result was [1.0000]", the adb process on the (Linux) desktop counts up to 47 % and then terminates with exit code 0 and without an error message.
The installed image boots, shows the usual LineageOS boot screen (the circles moving on a line from right to left) for a few minutes, and then reboots into recovery.
How do I find out what's going wrong here? How do I fix this behavior?
Is there any way to obtain a Lineage OS 14 image to try? The official download media seem only to have the latest six snapshots, which are all LineageOS 15 images.
Greetings
Marc
everything works well
everything works well on my phone
instagram doesn't have problem anymore ( since last month)
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
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.
So I made a TWRP device tree for it using twrpdtgen by SebaUbuntu and I’m doing the repo sync of the twrp minimal manifest but I haven’t really built TWRP for a device before. The device tree is android_device_mbox_dolphinp1 but I will also try to make it obvious that that device is also the Easytone… etc so it is easy to find and I will make XDA post when it is fully complete. The main thing I need to do now is double check all the stuff in the build tree and any settings I want TWRP to have in boardconfig.mk and compile and test it. I own this device so if all goes well it could be at least booting by the end of the week. Is there anyone with TWRP building experience that would be willing to help if I make any stupid mistakes? The end goal is to make an official TWRP build on the TWRP website. This year I may also consider looking into ROM development just because I really love tinkering with this device and I would love to see it running a custom ROM with the Android TV controls and features in mind. I also want to help anyone who bought this device and was disappointed by the stock experience, which can be slow and clunky to say the least.
I am trying to do lunch but I get this error please help
~/dolphinp1-twrp/device/mbox/dolphin-p1$ lunch twrp-dolphin-p1
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
device/mbox/dolphin-p1/AndroidProducts.mk:11: error: device/mbox/dolphin-p1: twrp_dolphin-p1-user: Invalid variant: p1.
16:28:41 dumpvars failed with: exit status 1
Device twrp not found. Attempting to retrieve device repository from TeamWin Github (http://github.com/TeamWin).
Found repository: android_device_emulator_twrp
Checking branch info
Calculated revision: android-12.1
Branch android-12.1 not found
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
device/mbox/dolphin-p1/AndroidProducts.mk:11: error: device/mbox/dolphin-p1: twrp_dolphin-p1-user: Invalid variant: p1.
16:28:47 dumpvars failed with: exit status 1
build/make/core/version_defaults.mk:56: warning: Invalid TARGET_PLATFORM_VERSION 'p1', must be one of
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:68:
build/make/core/version_defaults.mk:57: error: SP2A.
16:28:48 dumpvars failed with: exit status 1
** Don't have a product spec for: 'twrp'
** Do you have the right repo manifest?