Team Win Recovery Project 3.0.2-1
This is for the International SM-N930F/X, Duos SM-N930FD, and Korean SM-N930K/L/S Exynos models only! Do not flash on Snapdragon models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Note 7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WARNING #3: When using custom kernels on the Note 7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxynote7exynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gracelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest Samsung Anti-Root Protection Removal zip.
Without exiting TWRP, transfer the samsung-antiroot-removal zip to your device over MTP* and flash it using [Install] in TWRP.
This zip will allow you to flash SuperSU versions earlier than 2.77 and use other rooting methods.
It uses a hex pattern (by Chainfire) replacement method in the kernel that simply disables the anti-rooting protection.
It will also disable the status bar notification about unauthorized changes.
It includes the functions of the no-verity-opt-encrypt zip.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-1 - Fix restoring of non-ext4 partitions, update f2fs drivers, update to BPID source & Linux 3.18.43, add 60% battery charging limiter
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-b3 - Fix colors and use NTFS-3G
v3.0.2-0-b2 - Initialize new device tree based on Samsung OSRC N930FXXU1APGK kernel source.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (International): https://github.com/TeamWin/android_device_samsung_gracelte (android-6.0)
Device tree (Korea): https://github.com/TeamWin/android_device_samsung_graceltekor (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal8890 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy Note 7, Tool/Utility for the Samsung Galaxy Note 7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_gracelte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-10-15
Created 2016-08-23
Last Updated 2016-11-08
jcadduono said:
Team Win Recovery Project 3.0.2-0-b2
This is for the International SM-N930F/X, Duos SM-N930FD, and Korean SM-N930K/L/S Exynos models only! Do not flash on Snapdragon models!
snip
Click to expand...
Click to collapse
For the current note 7 series, @jcadduono will be the primary maintainer. I will subscribe to this thread however, I will be getting the n930fd. Good job @jcadduono!
Thank you very much sir and i try now
Sent from my SM-N930F using Tapatalk
I am away from PC but will try later tonight or tomorrow. Meanwhile any N930F users face any issue or got bootloop after testing here is stock recovery and kernel based on N930FXXU1BPH6 to fix bootloop
http://d-h.st/cHao
Flash it with Odin for AP tab
I have faced this y'day while modifying CF auto root and experienced that it may fail initially to flash soon after Odin log showing Initializing - Fail
Repeated attempt should work.
...on your mark, get set, go! Bye bye Samsung Pay... again...
Nice to see you here, Im using your rom on my note 4, s6, next is note 7, but my note 7 is 930FD, 2sim, so I have to wait more...
dr.ketan said:
I am away from PC but will try later tonight or tomorrow. Meanwhile any N930F users face any issue or got bootloop after testing here is stock recovery and kernel based on N930FXXU1BPH6 to fix bootloop
http://d-h.st/cHao
Flash it with Odin for AP tab
I have faced this y'day while modifying CF auto root and experienced that it may fail initially to flash soon after Odin log showing Initializing - Fail
Repeated attempt should work.
Click to expand...
Click to collapse
lehongwang said:
Nice to see you here, Im using your rom on my note 4, s6, next is note 7, but my note 7 is 930FD, 2sim, so I have to wait more...
Click to expand...
Click to collapse
Yeah Samsung has so far only released APGK and not FD's BPH6. I don't know if the S7 bootloader changed that happened in BPH6 on G930 also applies to N930FD though, so this might work for N930FD just the same as N930F.
It works!
Whats the status on Canada/US models?
I have an N930W8, waiting patiently for root ^.^
Also, I remember having pretty bad wakelock / deep sleep problems with the Note 5 root, has that issue been figured out for Note devices? I remember having to use a modified SU and Dr.Ketans deep sleep fix in order to have my Note 5 sleep properly. Just wondering if this is still a thing or not ^.^
i23u8 said:
It works!
Click to expand...
Click to collapse
Awesome! If you have the time, join #twrp on irc.freenode.net and upload recovery.log for us from the build. We need to make sure everything is detected and pointed to the right locations, as well as features working.
Here's a checklist if you want to go through it for us as well:
Code:
Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Modem/Firmware/EFS (if applicable) partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Use pass or fail in each box.
Data encryption/decryption will most certainly not work.
imatts said:
Whats the status on Canada/US models?
I have an N930W8, waiting patiently for root ^.^
Also, I remember having pretty bad wakelock / deep sleep problems with the Note 5 root, has that issue been figured out for Note devices? I remember having to use a modified SU and Dr.Ketans deep sleep fix in order to have my Note 5 sleep properly. Just wondering if this is still a thing or not ^.^
Click to expand...
Click to collapse
They will never receive TWRP support and it's unlikely that they will ever see root either, unless an engineering boot image is leaked similar to what happened with the S7, but being stuck on an old kernel for the rest of your devices life just to root is kind of crappy. Do advise selling it and buying an F or FD Exynos model.
Ok I can confirm - TWRP works
Root - No
Root didn't work may be because of I have updated to latest base PH6 and believe this base have some changes and issue reported on S7 on this base as well
Before this Y'day I have modified CF auto root based on PH6 recovery and sent log to CF as well tested file from CF as well. According to @Chainfire he is aware of this and he will first fix S7 issue and probably this should fix for us as well.
So game started and have to wait till new magic from @Chainfire
Again thank to @jcadduono and @bigbiff for great work. Again Thank you very much to all involved to this project behalf of N7 community.
Here attached logs.
PS : Very busy today and just arrived from out, couldn't resist to test. Will report more details later
Regards
Dr.Ketan
dr.ketan said:
Again thank to @jcadduono and @bigbiff for great work. Again Thank you very much to all involved to
Dr.Ketan
Click to expand...
Click to collapse
+1
thanks to all for your help!
Do I have to flash both SuperSU and no-verity? Or SuperSU alone is fine?
Also tried this on both APG7 and BPH6 and they bootloop.
Here are the results of the testing so far:
Status Blocking checks
Pass [ ] - Correct screen/recovery size
Pass [ ] - Working touchscreen
Pass [ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
Pass [ ] - Reboot to system
Pass [ ] - ADB & ADB shell
Pass [ ] - Flash zips in Install page
Pass [ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
Pass, yellow [ ] - UI colors (red/blue inversions)
Pass [ ] - Screen goes off (and back on )
Pass [ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
Pass [ ] - System, Data, Internal Storage, microSD card, and Modem/Firmware/EFS (if applicable) partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
Pass [ ] - Correct date
[ ] - MTP read/write
Pass [ ] - USB Mass Storage read/write
Pass [ ] - Set brightness level
Minor checks
Pass [ ] - Reboot to bootloader
Pass [ ] - Reboot to recovery
Pass [ ] - Power Off
Pass [ ] - Battery level
Pass [ ] - Temperature
[ ] - Encrypted backups
Pass [ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
It's works but no root
Sent from my SM-N930F using Tapatalk
i23u8 said:
Do I have to flash both SuperSU and no-verity? Or SuperSU alone is fine?
Also tried this on both APG7 and BPH6 and they bootloop.
Click to expand...
Click to collapse
Flash supersu on apg7 and see if boot
If not
Flash stock files I have provided on prev page
Flash twrp
Flash dm verify disabler
Now device will boot
Fixing screen colors, yellow should not be normal lol.
Okay what I want to know is:
Does USB-OTG work?
Does mounting and writing to NTFS work?
Does mounting and writing to exFAT work?
Does mounting and writing to f2fs work?
Does MTP work (microSD card)?
Does MTP work (format internal storage to mount data unencrypted after flashing opt-encrypt zip)?
Does USB Mass Storage button work in Mount page (with external SDcard) - allows oldschool access to microSD from PC?
Output of following commands from terminal:
Code:
ls -l /dev/block/bootdevice/by-name/
cat /proc/partitions
ls /dev/block
dr.ketan said:
Flash supersu on apg7 and see if boot
If not
Flash stock files I have provided on prev page
Flash twrp
Flash dm verify disabler
Now device will boot
Click to expand...
Click to collapse
Hi Dr Ketan, I've flashed APG and SuperSU and it didn't boot, it loops.
I'm able to recover the phone.
Hi jcadduono,
Does USB-OTG work? Yes it works.
Does mounting and writing to NTFS work? Yes, my external HDD on NTFS works.
Does mounting and writing to exFAT work? Yes it works, my USB-OTG is exFat.
Does mounting and writing to f2fs work? I didn't convert any of my storage.
Does MTP work (microSD card)? Yes, it works.
Does MTP work (format internal storage to mount data unencrypted after flashing opt-encrypt zip)? Yes it works before I make my first boot to system.
Does USB Mass Storage button work in Mount page (with external SDcard) - allows oldschool access to microSD from PC? Yes this works.
Apart from those I havent tested, booting to system and then booting back to TWRP, I lose access to the data partition and it looks like I need to re-wipe and install no-verity.
i23u8 said:
Apart from those I havent tested, booting to system and then booting back to TWRP, I lose access to the data partition and it looks like I need to re-wipe and install no-verity.
Click to expand...
Click to collapse
Is it encrypting again after installing no-verity zip? This was an issue on Exynos 7870 and if it's happening on 8890 that would be terrible. (they made it impossible to disable encryption on 7870)
Also, see if the colors are fixed in https://idlekernel.com/twrp/gracelte/twrp-3.0.2-0-b3-gracelte.tar.md5
They should be blue and black and grey, no yellow!
And check NTFS again, I removed kernel driver for pure ntfs-3g to see if I could trim it down a little and make NTFS more stable.
Just two things to add to previous report
1.flashing from USB storage working
2.adb and and shell working from recovery
I kind of liked the yellow, it looked more like Parallax-y.
Confirmed that the colors are back to the normal blue, black, gray combo.
I'm not able to recheck NTFS because I stepped away from my bag to attend to work for a few minutes (then back to reflashing).
Related
I wanted to create a thread so as to report any unique findings from the internet realm regarding the Nvidia Tegra Note OEM Tablet.
Please post your own discoveries and updates!!!
Bootloader Partition Images
WARNING ONLY ADJUST PARTITIONS IF YOUR DEVICE HAS A WORKING BOOTLOADER WITH FASTBOOT
(Some early devices have a limited bootloader with no menu and no fastboot mode. If this is so, do not modify your partitions unless certain of your actions. A bootloader is a special device starting partition that later starts the extended boot partition. The bootloader should give fastboot access allowing you to re-partition or correct mistakes.)
Buttons: Power-Button + Top-Volume. Release after a few second..
= Bootloader menu should show, allowing fastboot 'on' switch
= or Blank Screen Bootloader possibly with fastboot (read above warning)
To partition your device you do need it unlocked it. The command below should do this. You need a fastboot commandline service which is usually supplied from the bootloader level. The computer used to control the changes also needs its own ADB and FASTBOOT protocol utilities.
After the below command is issued your device will reboot and user data wiped! You device should then be open for partition changes.
Code:
fastboot oem unlock
Recovery Partition Images
TWRP Recovery (Team Win Recovery Project)
Shaky Builds and Source Code
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can Root your device by installing SuperSu from the recovery mode if the zip installer allows unsigned zips.
Vendor System Recovery Images
https://developer.nvidia.com/gameworksdownload
Vendor Released Over-The-Air Based Updates
Consider:Updates can remove apps that have been moved into system partition! Example AdAway, SuperSu, Link2SD, DroidWall, etc.
Files are ripped from the below directory once downloaded and before confirming an upgrade;
Code:
/sdcard/nvidia/app/ota/download/ROM/
or direct link;
Code:
/storage/sdcard0/nvidia/app/ota/download/ROM/
(July, 2015 OTA 5.1 Lollipop. EVGA Version 3.0) 446.3MB
tegra_note_7_system_update_3.0__5.1.zip
ERROR NOTICE. The first release of lollipop consumes most of the system folder. Those trying to install further items will experience an out of storage error. A remedy is to use a root mode utility like Link2sd to remove unwanted system apps.
Example
Code:
Filesystem Size Used Free Blksize
/dev 444.8M 40.0K 444.8M 4096
/sys/fs/cgroup 444.8M 12.0K 444.8M 4096
/mnt/asec 444.8M 0.0K 444.8M 4096
/mnt/obb 444.8M 0.0K 444.8M 4096
/system 755.9M 754.3M 1.6M 4096 <<<
/cache 755.9M 12.8M 743.2M 4096
/data 12.6G 1.0G 11.6G 4096
/mnt/factory 15.7M 4.0M 11.7M 4096
/lbh 252.0M 51.0M 201.0M 4096
USB
Device USB Coding
Code:
ID 0955:7535 Rev. 0102 NVidia Corp. APX
ID 0955:CF00 Rev. 0232 NVidia Tegra Note
Linux users are well supported for USB access. They also can easily install latest ADB and Fastboot from distribution repositories.
ADB and Fastboot (Client) Executables
XDA-Developers Thread
Microsoft Windows USB Drivers from Nvidia
NvidiaUSBDrivers_Rel20131017
UART Ability?
After an inspection I can't see any points to which one could easily tap into an 'exposed console' with a USB UART setup. This could indicate there is no allocation to access a terminal from a tapped in serial port or pins off the minute and well protected chipsets. Obviously those that want to software repair these tablets have access to NvFlash/APX mode, in dire situations.
NVFLASH/APX
NvFlash_v3p08p1700_RipV2 (Executables for; Linux, Mac, Microsoft)
Buttons: Power-Button + Top-Volume + Bottom-Volume. Release Power-Button only once you see branding. Release others after few seconds.
= Screen should remain black. USB connection should see Nvidia APX Device (USB ID 0955:7535).
Linux Users should copy their executable to the below directory so that it's globally available from all bash points
Code:
/usr/local/bin
NVFLASH/APX BASED RECOVERY (POSSIBLE FIX FOR BRICKED DEVICES)
Advent Computers APX Recovery
Linux users can add the nvflash executables shared above. Put the device in APX mode and issue the below command. You can replace the images in the folder to suit a different recovery or boot, etc.
Window's users can execute 'flash_signed.bat' from the command line to start the process. If you get ID errors, then perform the Linux command below without the 'sudo' section at front.
Unplug any other device. Do not use this unless your tablet is bricked as it will tailor the tablet to a particular brand and therefore hardware may not work correctly.
Code:
sudo nvflash --blob blob.bin --bct flash_signed.bct --setbct --odmdata 0x4069E000 --odm limitedpowermode --configfile flash_signed.cfg --create --bl bootloader_signed.bin --reset normal 0
Standard Blob Image (includes unpacked items)
TegraNote_blobrip_4p4rip.zip
TegraNote_blobrip_4p3p1p1.zip
Standard Boot Image (includes unpacked items)
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
RESTORE DEVICE WITH FASTBOOT IMAGES
Rootjunkysdl's Firmware Downloads
KERNEL SOURCE
http://nv-tegra.nvidia.com/gitweb/
Guides
Tomsgt has made various video tutorials on how to root-mode your device, among other topic. See here for videos..
Tom hosts his own array of core files;
Rootjunkysdl.com
ALTERNATIVE SYSTEMS
CHALLENGE CHALLENGE CHALLENGE CHALLENGE CHALLENGE
No one has yet customised another operating system for the Tegra Note 7.
* Ubuntu Touch
* Firefox OS
* Sailfish
* Plasma Active
* Tizen
Known Vendors of the Tegra Note Tablet
Advent Tegra Note 7 (http://www.adventcomputers.co.uk/)
Colorful Tegra Note 7 (http://en.colorful.cn/)
Colorfly T709 (?)
EVGA Tegra Note 7 (http://www.evga.com/)
Gigabyte Tegra Note 7(http://www.gigabyte.com.au/)
Gradiente Tegra Note 7(http://www.gradiente.com.br/)
Granville Flyone Homecare Tegra Note 7 P1640 (http://www.huiweipad.com/)
PNY Tegra Note 7 (http://www.pny.com/)
Oysters Tegra Note 7 (?)
XOLO Play Tegra Note 7 (http://www.xolo.in/xolo-play-tegra-note/)
Zotec Tegra Note 7 (http://www.zotac.com/)
***** POWER USERS *****
Install F-Doid App Store
F-droid is a safe repository of open source code Android Apps. Many Apps unavailable from Google's Store.
Recommend
~~~~~~~~~~
* AdAway (Removes Ads from Apps by blocking content)
* Hackers Keyboard
* AFWall (IPTable Firewall)
* VLC Player (official release) VideoLan
Xposed Installer
Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. That's great because it means that modules can work for different versions and even ROMs without any changes (as long as the original code was not changed too much). It's also easy to undo. As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back. There are many other advantages, but here is just one more: Multiple modules can do changes to the same part of the system or app. With modified APKs, you to decide for one. No way to combine them, unless the author builds multiple APKs with different combinations.
.
Installing Google Play on Nvidia Tegra Note.
0. Get a powerful Recovery partition image on your Tablet.
1. Obtain a Google Apps pack, usually termed GAPPS suited to your Android version.
2. Use Recovery's install zip mode to install.
Lollipop Fresh Installation + Tweaking
(for those with basic knowledge of Android manipulation)
* Make sure your tablet is OEM unlocked. Then flash a sophisticated recover image version like TWRP. This will allow root-mode enabling via a patch.
To obtain fastboot-mode, you need another computer as the debugging/command platform via USB. Holding the POWER-BUTTON and UP-VOLUME on the boot and shortly after releasing the POWER-BUTTON and later the other, will bring up a bootloader menu that can deploy fastboot protocol/mode or get to recovery-mode. This is where you can flash, oem unlock, and erase partitions, with the data coming from your command-platform. You can't format nor erase partitions till you oem-unlock the device, noting an oem unlock clears your device's user data.
Your command-platform (controlling computer used to upgrade the Tegra Note) also needs its own version of ADB (Android Debugging Bridge) and FASTBOOT protocols so as to be able to talk and understand the conversation over the USB.
RootJunky also has versions of TWRP and other recovery image versions.
* Put the tablet into fastboot-mode and flash RootJunky's shared Lollipop restore image instead of the upgrade over the air (OTA). Good idea to erase particular partition before flashing.
* Boot to the recovery stage. Install latest SuperSu.zip using sideloader or having it already on a SD. This will enable root mode.
https://download.chainfire.eu/740/SuperSU (Get Beta if available.)
* Start system. Remove Apps from system partition unneeded, or that can be moved or installed to user directory instead. This frees up vital space. Example Lollipop only leaves a few megabytes left in the system partition after installation. Consider using Link2SD. Example get Google+, Google Play, Google Magazine, etc into the user partition and any other big App off your system partition. The system partition should only have important apps needed to be retained if a factory wipe is enacted.
* Then go through all your system settings make sure you tweak them to suit both power saving and your own desires.
* Use a start-up tool like ES Task Manager to remove apps starting that don't need to be running from system boot.
* Install all Google Apps wanted. This can help to configure the system how it's meant to be.
* You could install Google Now into the system partition and remove the Launcher3 App.
* The system should now run smooth and use little battery.
.
Nice bro....keep me posted... Pre ordered xolo tegra note
Edit : got my tegra note 7
Wow fantastic find! Seriously psyched for the recovery. One step closer to roms!
Very good
Enviado do meu Moto X usando Tapatalk
[RESERVED]
.
[RESERVED]
I can not download the files to install the Play store ... Somebody help me?
Enviado do meu Moto X usando Tapatalk
ezequielbsb said:
I can not download the files to install the Play store ... Somebody help me?
Enviado do meu Moto X usando Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2397942
Get 4.3 versions since still Jellybean.
The Cydia Impactor just successfully rooted my Slate 8 (Tegra 4 platform, v. similar to the Note)
Might be worth a go?
Discussed here:
http://forum.xda-developers.com/showthread.php?t=2386677
I am looking for the drivers for this device I am on windows and cant get the adb drivers installed. Please Help
Cydia Impactor
roustabout said:
The Cydia Impactor just successfully rooted my Slate 8 (Tegra 4 platform, v. similar to the Note)
Might be worth a go?
Discussed here:
http://forum.xda-developers.com/showthread.php?t=2386677
Click to expand...
Click to collapse
Worked within 20 seconds. Even loaded the USB drivers for me!
Tomsgt said:
I am looking for the drivers for this device I am on windows and cant get the adb drivers installed. Please Help
Click to expand...
Click to collapse
I had the same problem when I was trying to use Helium to restore some apps. Windows 7 64 bit was able to install two of the three component 'parts' of the tablet but not the final driver. After the device installer had finished in opened Control Panel on the PC and then the Device Manager. The Note should be listed in Device Manager with a yellow exclamation mark. Right click on it and select 'update driver'. In the next window choose to install the driver yourself, then opt to choose from a list of drivers manually. Next choose the entry called 'Android Phone', then select 'composite ADB device' from the list on the right. I'm saying this from memory I may have missed a step so tread carefully. I already had the desktop Helium app installed on my PC which installation ADB drivers (they'll appear under Clockwork Mod in the driver list I mentioned). I'm away from my PC for now so it'll be a while before I can refine these instructions.
These are just basic observations, but I've playing around with the Note connected to a TV and USB hub etc
http://forum.xda-developers.com/showthread.php?p=48416270#post48416270
I haven't tried wireless display yet. I hope to by a Miracast/DLNA compatible adapter for my TV soon so I can see what works. Full screen mirroring is what I'm aiming for.
becksvector said:
Worked within 20 seconds. Even loaded the USB drivers for me!
Click to expand...
Click to collapse
Did you already have the drivers downloaded and installed to your machine, or did it use its own drivers?
that'd be great if folks no longer need to get the drivers manually set up and override the crying about mismatches.
My Tegra Note Homecare Fly One does not connect on my PC ..
Does anyone have the drivers?
thank you
I made a discovery.....Battery drain issue.....battery drains really fast even when on power save settings with prism and running on 1 core..... Even when im not even using it like the memory is clean and cache is clear and everything.......After 100% charge it barely lasts me 6 hours of a day at college when im using it on and off....Like word processing and taking a couple of photos thats it.....
So after a few days since I got it the battery started getting better and better......So what was 6 hours of on and off usage of my tablet is not almost 24 hours of the same kinds of usage with still 45% ish of battery remainig!!!!! So I guess the way we charge our devices makes a difference as well....Batery doctor has a feature that charges the device in a specific way like as fast as possible to 80% then slows current down to prelong battery life. I want to see how long my battery will last and will upload screenshots while im doing so.....Right now it is 10:26 pm and battery is at 43% with 22 hours and 2 mins on battery.
Working with a Developer on CWM recovery for this device
Root video if anyone needs help
http://youtu.be/0521gm9ajz4
Been looking for a game stream apk or mod if anyone has it.
roustabout said:
Did you already have the drivers downloaded and installed to your machine, or did it use its own drivers?
that'd be great if folks no longer need to get the drivers manually set up and override the crying about mismatches.
Click to expand...
Click to collapse
I had some element of a connection as my computer could see the tablet for transferring media. But after pressing the USB button I had the lot!
Team Win Recovery Project 3.0.2
Notice: This is a test build as a start to becoming an official build, I am looking for feedback right now - do not consider this stable!
I am currently looking for users to test all the features and report back with what works.
Quote the 2nd post and put a pass or fail in each of the [ ] boxes!
Please, if you can, post your recovery.log after doing the tests that fail, as well as dmesg.log
Code:
adb shell cat /tmp/recovery.log > recovery.log
adb shell dmesg > dmesg.log
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://idlekernel.com/twrp/kipper/ (temporary! THESE ARE TEST BUILDS!)
Find instructions on how to unlock and root your device with fastboot here:
https://twrp.idlekernel.com/devices/wileyfoxstorm.html (temporary device page - do not download from here!)
CHANGES
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Brightness node not set (unknown location, join #twrp to help!)
Battery status possibly unknown
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
Device tree: https://github.com/jcadduono/android_device_wileyfox_kipper
Kernel sources: https://github.com/jcadduono/android_kernel_cyanogen_msm8916/tree/twrp-6.0
TWRP: https://github.com/omnirom/android_bootable_recovery
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Wileyfox Storm, Tool/Utility for the Wileyfox Storm
Contributors
jcadduono, The Team Win Recovery Project team
Source Code: https://github.com/jcadduono/android_device_wileyfox_kipper
Version Information
Status: Testing
Current Beta Version: 3.0.2-0
Beta Release Date: 2016-04-27
Created 2016-04-28
Last Updated 2016-04-29
TWRP functional checklist
Code:
Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
jcadduono said:
Code:
Blocking checks
[Pass ] - Correct screen/recovery size
[ Pass] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[Pass] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Click to expand...
Click to collapse
I really want to see this get done but I don't have time to test everything right now. Done some basic tests, will edit with the rest whenever I have the time to do so.
Hi, I'm on CM13 and i cannot maount microsdcard and usbotg in TWRP, any solutions?
aciupapa said:
Hi, I'm on CM13 and i cannot maount microsdcard and usbotg in TWRP, any solutions?
Click to expand...
Click to collapse
Flashed twrp-3.0.2-0-test3-kipper.img and found unable to use mirco SD card as available storage.
Previously had TWRP-2.8.7.0-kipper-recovery on device, however after updating to CM13 this was unable to find/use micro SD card as available storage too.
Marshmallow issue or recovery one.
To acces microsd and otg, you need to flash COS12.1.1, then it magically works. To use it on cm13 you need to backup cm13 install COS12 and resrore cm13 (yeah, complicated)
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
To acces microsd and otg, you need to flash COS12.1.1, then it magically works. To use it on cm13 you need to backup cm13 install COS12 and resrore cm13 (yeah, complicated)
Click to expand...
Click to collapse
So create a TWRP backup, install cos12 then simple restore the back and should work?
Yes. I use it like this now
Sent from my Wileyfox Storm using XDA Labs
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
But after flashing cos12 reboot into recovery ans check if partitons mount
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
Yes. I use it like this now
Sent from my Wileyfox Storm using XDA Labs
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
But after flashing cos12 reboot into recovery ans check if partitons mount
Click to expand...
Click to collapse
I Google for a TWRP cos 12.1.1.zip however no joy.
Fail to install via a custom recovery users advised.
The issue only occurred after I installed CM13, that's when TWRP couldn't find microsd storage.
Go to cyngn.com/support and look for zip withouth fastboot in name
Sent from my Wileyfox Storm using XDA Labs
aciupapa said:
Go to cyngn.com/support and look for zip withouth fastboot in name
Click to expand...
Click to collapse
Installed the none fastboot cos 12.1.1 zip via recovery, then let it run the install build, however when I rebooted into recovery I was unable to get the external sdcard to be accessible still.
Thanks for suggested fix. :good:
Idk, why, but it always helps me. have you rebooted phone after COS12 flashing?
aciupapa said:
Idk, why, but it always helps me. have you rebooted phone after COS12 flashing?
Click to expand...
Click to collapse
I made TWRP backup of my current CM13 ROM, then wiped all partitions except internal and external SD card storage. Installed cos12.1.1 zip within TWRP, then rebooted to let stock lollipop ROM initialised. Then rebooted to TWRP to find external SD still not found.
Maybe try reflashing twrp
aciupapa said:
Maybe try reflashing twrp
Click to expand...
Click to collapse
I tried reflashing TWRP-2.8.7.0 recovery, then twrp-3.0.2-0-test3-kipper, cm-13.0-20160305-recovery and final cm-12.1-none-sign-recovery.
None of them could find the external SD card only internal storage. Would love to say it worked however sadly not. When on stock lollipop 5.0.1 all the recovery storage paths worked, so you would think installing cos 12.1.1 zip would restore things.
Have noticed that the original boot loader has returned, but not the battery charging while powered down image that you see getting fuller if you hit the power button. The original one was much larger under stock.
What's the function of the image file compared to the zip one please?
cm-12.1-YOG7DAS2FI-kipper-boot-debuggable-a7322d8c3a.img
Did a final version get abandoned after the test 3 release?
Probably to less tests?
I loved TWRP on my good old S2 (which seems to have NAND rw corruption since last week). Now I have the Storm I would love TWRP on my device too, but it needs proper testing.
I'm wondering: what are the risks of testing this? I might be able to help.
Well I have the test 3 one running on my storm, no issue's found.
Ok thanks. I'll try flashing it.
Blinkin89 said:
Ok thanks. I'll try flashing it.
Click to expand...
Click to collapse
Link updated in next post
None test version here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for K6 power. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the Moto X Play
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch.
MultiROM (multirom.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Adding Roms
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code:
MultiROM - https://github.com/multirom-dev
Downloads :
[*] 2017-11-20: Flashable ZIP
MultiROM TWRP Image
FAQ and other notes
Device encryption:
Encryption isn't supported right now. So decrypt your device before using this.
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
Reserved.
At last my multi-rom is available for redmi 4x now can test many roms .
What is the difference between dual boot patcher and this . Dual boot patcher is much easier to use .This is so complicated
Wasef x said:
What is the difference between dual boot patcher and this . Dual boot patcher is much easier to use .This is so complicated
Click to expand...
Click to collapse
Sorry but this isn't true...
I tried DBP and it is definitely more complicated than MultiROM.
Driv said:
Sorry but this isn't true...
I tried DBP and it is definitely more complicated than MultiROM.
Click to expand...
Click to collapse
What ... It work or no ... ?
Sent from my Redmi 4X using Tapatalk
Tested it . Booted Dot os as secondary . Working Flawlessly . And yes.. If I think of an amateur user , It is easier than Dual boot patcher as @TingyiChenchen provided the twrp and the flashable zip . One just have to flash them . And boom ...Add roms as you wish .
N.B. Never ever update magisk or any flashable zip from the added roms . Always boot into recovery ..go to the rom and chhose the option add zips .
And make sure you have backed up system and system image before messing up with This .
Hit Thanks if I helped or If you need a video tutorial .
How to encrypt? I had to format my whole phone + internal memory.
How to make rom in external storage is visible?
When I set fingerprint in primary rom, secondary rom delete this. Please, fix this issues!
Thank You for making this happen on santoni.. But i think it still need a little fix.. I'm facing two problems..
1. If i make password or FP for lockscreen on second rom.. On first rom we couldn't use password or pattern that we've entered.. It change by it self..
2. After sometimes.. We couldn't boot to second rom anymore.. It's stuck on boot logo
I hope it could be fixed on next update.. Take your time.. Thanks for the effort.. Thanks for this MultiRom
How to delete 2 roms ? And all multitom?
Wasef x said:
Tested it . Booted Dot os as secondary . Working Flawlessly . And yes.. If I think of an amateur user , It is easier than Dual boot patcher as @TingyiChenchen provided the twrp and the flashable zip . One just have to flash them . And boom ...Add roms as you wish .
N.B. Never ever update magisk or any flashable zip from the added roms . Always boot into recovery ..go to the rom and chhose the option add zips .
And make sure you have backed up system and system image before messing up with This .
Hit Thanks if I helped or If you need a video tutorial .
Click to expand...
Click to collapse
Thank you for sharing information. I have 2 questions:
1. Any conflict with primary rom like rr which integrated magisk? What would happen if I add/remove modules in magisk manager?
2. If I enabled the File Based Encryption (FBE) feature in the primary rom, which means the whole /sdcard/ is encrypted until I input password or draw gesture before boot up. Can I use MultiROM still (show OS menu and load secondary rom after I input password or draw gesture )
Thanks!
@TingyiChen can you share multirom device tree?
Edit: no need I have done it with help from Madd_Maxx
My secondary Rom won't boot!!
Give me link Patch kernel hardboot kexec for Redmi 4x ,thanks
Impossible to get a working MultiRom Manager by TWRP flashing V33 santoni zip
Though many posts for Xiaomi Redmi 4x (Santoni) do declare that MultiRom Manager works, I experience a serious problem with installation.
MultiRom.apk always says incompatible device (Santoni).
So I tried the 2 provided files. TWRP Multirom Recovery successfully flashed but no luck with "multirom-20171120-v33-UNOFFICIAL-santoni.zip".
Flashing the MultiRom Mgr application (customised for Santoni?) never get installed. This is my main problem.
Please advice!
NB1: Concerning the Encryption issues with MIUI devices I did manage to solve it and get a full TWRP device backup (including my data!) by flashing image "twrp_santoni_oreo.img" available around.
Its TWRP version is 3.1.1-8.0.
nice project
Kernel
Wasef x said:
Tested it . Booted Dot os as secondary . Working Flawlessly . And yes.. If I think of an amateur user , It is easier than Dual boot patcher as @TingyiChenchen provided the twrp and the flashable zip . One just have to flash them . And boom ...Add roms as you wish .
N.B. Never ever update magisk or any flashable zip from the added roms . Always boot into recovery ..go to the rom and chhose the option add zips .
And make sure you have backed up system and system image before messing up with This .
Hit Thanks if I helped or If you need a video tutorial .
Click to expand...
Click to collapse
Please give me the link of your kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the instructions and notes before flashing anything. Don't ask me if you don't read the instructions.
Code:
###Disclaimer###
I am not responsible if your device will be damaged, broken, boot looping. YOU are choosing to make these modification.
WARNING:
IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS.
DONATE ME HERE
Requirements
- Unlock bootloader
- For now Ticwatch S (Mooneye)
- Working adb/fastboot and driver
- Any FTP client to copy/read files to/from your watch (Optional)
HOW TO FLASH THE ROM
- Attach your devices to your PC and enable USB Debugging from settings menu
- Download the platform-tools (use either Linux or window..platform-tools-linux-Ticwatc-S.zip or platform-tools-windows-Ticwatch-S.zip) from the given links
- Unzip the folder- it includes boot.img, recovery.img and system.img
- For Linux run ./flash-all.sh
- For Windows double click on flash-all.bat
- Wait until your device reboot
- Done.. enjoy
HOW TO Flash Kernel/boot.img
- Attach your devices to your PC and enable USB Debugging from settings menu and follow the commands
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash boot boot.img
HOW TO ROOT
- Move SuperSU to your device. Use any FTP client to copy/read files to/from your device.
- Attach your device to your PC and enable USB debugging
- Reboot your device into TWRP recovery by following
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery.img
- Now flash the SuperSu and reboot
- Open BusyBox and tap to install (Only if you flashed SuperSU FOR OLDER VERSION NOUGAT) and reboot
- Done. Don't forget to donate if you like my work, Thanks.
ROMs
ROM AND KERNEL FEATURES [6-MAY-2018]
- ROM is based on release WEAR OS S(Mooneye)-[NWD1.171211.002]
- All *apk system/data, system/app, Framework & priv-app zipalign & optimized for better RAM utilization
- Kernel is based on latest kernel source 3.18.24.Released (VERSION = 4,PATCHLEVEL = 18,SUBLEVEL = 24)
- Compiled WITH UBERTC 4.9.4 (gcc version 4.9.4(optimized) (UBERTC-4.9.4))
- forced-encryption disabled
- dm-verity removed/disabled
- Scheduler optimize/support for heterogenous multi-core
- Scheduler support for heterogenous multi-processor systems
- Enables the core control
- Multi-Cluster Power Management support
- Optimized the energy consumption for advanced multi-core SoCs including big.LITTLE.
- Multi-core scheduler enable/optimized
- APM driver updated reduce battery usage during sleeping
- A lot subsystems converted to use power efficient workqueues
- Serveral other patces to reduce battery usage
- Tweaked/optimized the scheduler to balance the load across all CPUs without any regards to the power costs
- Tweaked the scheduler to reduce/save power by scaling down the frequency of the CPUs or idling them,
- Tweaked to predict the best time to save power on the CPU without affecting performance
- Tweaked for Best Performance
- And many more can't remember
- clean and smooth
NOTE: FIRST BOOT GONNA TAKE SOME TIME. BE PATIENT
[Odexed ROM]-[For Linux User]-[6/MAY/2018]
[Odexed ROM]-[For windows User]-[6/MAY/2018]
------------------------------------------------------------
KERNEL/BOOT IMAGEs
-[6/MAY/2018]
Changelog
- See above
[Kernel/boot.img]6-MAY-2018
SUPERSU AND MAGISK FOR WEAR OS
Magisk Wear OS
BusyBox+SuperSU
Source/GitHub
-Source
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
DONATE ME HERE
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Chainfire for great work in android
@Maxr1998 Big thanks for giving me knowledge and your great work for Asus Zenwatch_3 and your great github guide.
@topjohnwu for his great effort (Magisk)Thank you so much
@superR for the great kitchen
@Xmaster24 for system-less root-
Please always support devs and others (soon).
XDA:DevDB Information
[ROM+Kernel][Ticwatch S(Mooneye)], ROM for the Smart Watches
Contributors
janjan, JANJAN
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Stable Release Date: 2018-05-06
Created 2018-05-06
Last Updated 2018-05-07
Thanks,
Will test on my semi-bricked watch to try it out.
ETA when upload be done?
I'm surprised this wasn't locked. Normally mods lock a dev topic if uploads haven't been posted.
GuyInDogSuit said:
I'm surprised this wasn't locked. Normally mods lock a dev topic if uploads haven't been posted.
Click to expand...
Click to collapse
I am uploading the kernel source and update the instructions.Be patient
janjan said:
I am uploading the kernel source and update the instructions.Be patient
Click to expand...
Click to collapse
I'm being patient. Just pointing out this fact.
Mega - invalid key
Yup, decryption key is invalid.
Flashed on Mac.
Fastboot flash boot "boot.img"
Fastboot flash system "system.img"
Fastboot flash recovery "recovery.img"
Booted in about 2-3 mins.
Loads bloat removed.
Crashed when trying to run Google assistant.
Updating apps now to test further.
So far my bricked watch is working.
Very happy, great job!!
I've got a TicWatch E.. Any chance I'll be able to do the same? I'd love to donate for mentored stuff on my ticwatch e.
basicreece said:
Flashed on Mac.
Fastboot flash boot "boot.img"
Fastboot flash system "system.img"
Fastboot flash recovery "recovery.img"
Booted in about 2-3 mins.
Loads bloat removed.
Crashed when trying to run Google assistant.
Updating apps now to test further.
So far my bricked watch is working.
Very happy, great job!!
Click to expand...
Click to collapse
Enjoy
janjan said:
Enjoy
Click to expand...
Click to collapse
Unable to donate?!
I get this message:
"We cannot process this transaction because there is a problem with the PayPal email address supplied by the seller. Please contact the seller to resolve the problem. If this payment is for an eBay listing, you can contact the seller via the "Ask Seller a Question" link on the listing page. When you have the correct email address, payment can be made at www.paypal.com."
Would like to send you few £$£$£$ as a thanks
basicreece said:
Unable to donate?!
I get this message:
"We cannot process this transaction because there is a problem with the PayPal email address supplied by the seller. Please contact the seller to resolve the problem. If this payment is for an eBay listing, you can contact the seller via the "Ask Seller a Question" link on the listing page. When you have the correct email address, payment can be made at www.paypal.com."
Would like to send you few £$£$£$ as a thanks
Click to expand...
Click to collapse
Really appreciate. It link from first op is working fine.
https://www.paypal.com/donate/?toke...0ftYFV0vcrGeAA0cdWiW&country.x=DK&locale.x=DK
janjan said:
Really appreciate. It link from first op is working fine.
https://www.paypal.com/donate/?toke...0ftYFV0vcrGeAA0cdWiW&country.x=DK&locale.x=DK
Click to expand...
Click to collapse
Sent over a little something, thanks again!!
basicreece said:
Sent over a little something, thanks again!!
Click to expand...
Click to collapse
Appreciate that. I have some whiskey now it will keep me work more and more and give me effort to bring something different in future for our ticwatch s and e.
I will collect some money to buy ticwatch E to work with and bring some thing for future.
Ì followed the steps on my Ticwatch E and it all worked out nicely.
Expected to run into something not working but after 2 days of heavy use i can only say i did not encounter any malfunctions or bugs on my Ticwatch E.
Noticably better then what was on it stock.
Keep up the good work
Only thing i did not think of was that when i reset and unpair watch from settings i would need to go through the steps mentioned for flashing all over again.
I'll have to use ADB next time and see to make phone and watch pair without restart watch and unpair..
(If you could come up with some amazing solutions for this, that'd be great! )
What if we want to take a backup of the existing system image on the watch first? Mobvoi support wont release a factory image download (or the support person I was dealing with had no idea).
Do we also lose reference to which watch we had after this? IE mine is Ticwatch S 0261?
I get the below when trying.
"fastboot oem" unlock done, I then needed to do "adb reboot-bootloader" before the flash script would run otherwise it just sits there waiting for a device.
Code:
< waiting for device >
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
error: cannot load 'boot.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
error: cannot load 'recovery.img'
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
< waiting for device >
error: cannot load 'system.img'
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
< waiting for device >
Creating filesystem with parameters:
Size: 2603089920
Block size: 4096
Blocks per group: 32768
Inodes per group: 7952
Inode size: 256
Journal blocks: 9930
Label:
Blocks: 635520
Block groups: 20
Reserved block group size: 159
Created filesystem with 11/159040 inodes and 20879/635520 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
OKAY [ 0.741s]
sending 'userdata' (42564 KB)...
OKAY [ 1.282s]
writing 'userdata'...
OKAY [ 5.851s]
finished. total time: 7.875s
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
OKAY [ 0.047s]
sending 'cache' (5176 KB)...
OKAY [ 0.219s]
writing 'cache'...
OKAY [ 0.770s]
finished. total time: 1.051s
Press any key to exit...
Fcukfame said:
Ì followed the steps on my Ticwatch E and it all worked out nicely.
Expected to run into something not working but after 2 days of heavy use i can only say i did not encounter any malfunctions or bugs on my Ticwatch E.
Noticably better then what was on it stock.
Keep up the good work
Only thing i did not think of was that when i reset and unpair watch from settings i would need to go through the steps mentioned for flashing all over again.
I'll have to use ADB next time and see to make phone and watch pair without restart watch and unpair..
(If you could come up with some amazing solutions for this, that'd be great! )
Click to expand...
Click to collapse
So what happened? Did you happen to reset the watch, and end up having to flash this again? Why? But it DOES work on the Ticwatch E?
Yes it does work. Really nice actually.
I did have to flash the rom again but that was my bad..
https://forum.xda-developers.com/an.../app-reset-wear-client-switch-phones-t3058962
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.