Related
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.3:
-Fix to libraries to avoid issues when formatting partitions
CHANGELOG for 2.3.2.1:
-Updates to fix permissions
-Fix USB OTG on GNex
CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
Direct Download
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Awesome job guys
Sent from my EVO 3D using tapatalk
Very well done!
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
vWvSTATICvWv said:
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
Click to expand...
Click to collapse
Hmmm, I will look in to this .....
vWvSTATICvWv said:
I have a nice recovery theme on my E3D. Maybe someone can make some nice TP ones, so we're not stuck with grey
Click to expand...
Click to collapse
Which theme? Maybe someone would want to convert it.
Sent from my Touchpad using xda premium
Awesome work teamwin. This is awesome. Need this on my samsung epic.
Leoisright said:
Hmmm, I will look in to this .....
Click to expand...
Click to collapse
Yea I probably will make a theme when I get the tp in a few days
Sent from my Nexus S 4G using xda premium
I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.
To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.
So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod
This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod
I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.
For the moment I changed the names back so it uses Clockwork for the default and behaves normally.
bobtidey said:
I have switched to using TWRP for recovery on both Touchpad and Nook as it is very nice to use without having to fiddle with the buttons.
To make it even easier on Touchpad I thought I'd make the boot to recovery from CM7 go into TWRP rather than have to catch the moboot menu.
So in /boot I did mv uImage.ClockworkMod uImage.ClockworkMod1 and mv uImage.TWRP uImage.ClockworkMod
This superficially worked in that the boot to recovery from CM7 went into TWRP very nicely. But unfortunately when I then select Reboot to System from TWRP it then reboots straight back into ClockworkMod and restarts TWRP rather than go through moboot and into CYanogenMod
I guess there must be something going on in the real ClockworkMod to flip the default boot back which TWRP isn't doing.
For the moment I changed the names back so it uses Clockwork for the default and behaves normally.
Click to expand...
Click to collapse
The bootloader project is here: http://code.google.com/p/moboot/
If you're feeling inclined you can ask how you set the default boot for recovery and whatnot. That would probably be a good start. Maybe someone on my team knows, but it can't hurt to learn anyway.
Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d
I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.
When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.
I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.
anyone flash roms with this yet. In the eco people are stating wipin isn't working and hey flash and get stuck in a boot loop
Sent from my PC36100 using xda premium
I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.
bobtidey said:
Thanks for that pointer. There does seem to be some anomaly around the use of moboot.next and moboot.action.d
I think when rebooting from CM7 into recovery then either moboot.next or moboot.action.d is being set up to action ClockworkMod so it goes straight in without the moboot menu. Real ClockworkMod then deletes the action files so that when it does a reboot moboot goes through its menu, times out and re-enters the default CM7.
When TWRP is renamed then the sequence starts the same but there is then a moboot.next file that points to ClockworkMod and when it tries to do a system boot then moboot kicks in and repeats the action back into recovery.
I'll comment back on the moboot project as I suspect the cleanest actions here are for moboot to do the housekeeping of action and next files so it doesn't get stuck in this loop.
Click to expand...
Click to collapse
All versions of moboot have a README in the moboot_X.X.X.zip file.
From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should
You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
bluedogtouchpad said:
I installed the newest XRON rom along with moboot and TWRP on my Touchpad and TWRP did not seem to install. Is there a way to just install TWRP without having to do the whole thing over again? Maybe threw terminal mode or something. Since I tried to install TWRP I did not install CWM.
Click to expand...
Click to collapse
I had the same problem. I installed CWM first, then install TWRP through CWM.
Installed successfully after running the clean boot zip.
I went to the backup section to try and perform a backup but it gives me options that i can select/unselect and am not sure what should and shouldn't be selected.
Thanks
jcsullins said:
All versions of moboot have a README in the moboot_X.X.X.zip file.
...
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
Click to expand...
Click to collapse
Thanks. I should have checked the readme.
I discovered the home key trick the first time I tried this and was beginning to wonder how to get out of the loop.
Good to hear TWRP will remove it as well as I'm keen to use this as the standard and be able to reboot into recovery from CM7.
Extra refinement would be if CM7 reboot menu listed all the boot options it could find so that it wouldn't be necessary to rename the image to match the Clockwork that will be used when recovery is chosen.
LastQuark said:
I had the same problem. I installed CWM first, then install TWRP through CWM.
Click to expand...
Click to collapse
Did you install CWM by itself? If so how did you do that?
Thanks,
Wow awesome I never thought this would be possible. A revolution in recovery it seems. Wonder why other devices haven't got this already.
jcsullins said:
All versions of moboot have a README in the moboot_X.X.X.zip file.
From the README (this part was the same in all versions, I think):
##
## to select *next* boot image
##
echo "NAME1" >/boot/moboot.next # will boot uImage.NAME1 without menu
# NOTE: moboot does not delete the file, so the OS booted should
You are correct, it would be cleanest if moboot removed/managed this.
However, there is no code in moboot (or specifically, the ext2 fs code
it uses) to write to the filesystem. After I am done adding lvm support
to moboot, I plan on adding support to moboot to save some state information
to a raw partition (raw lvm volume). Once that is done, I should be able
to lift the requirement that the OS (or recovery, etc.) remove the
moboot.next file.
Also, for v0.3.5+ of moboot, you can hold the Home key to force it to
show the menu (thus overriding the moboot.next file).
Regardless, I am told the next release of TWRP for the Touchpad will
remove the moboot.next file.
Click to expand...
Click to collapse
Thanks, I tested this extensively in an attempt to get my Touchpad into TWRP by default and ran into the same issue with moboot.next, I tried to make it read only after putting Cyanogemnod into it among other things but couldn't get it to work 100%. For now, seems like other folks are running into the same issues and sounds like you guys will take care of it in the next release of moboot. Thanks for all the work.
[Size=+2]A500 Public Recovery v0.2 based on Koush's CWM v5.5.0.4[/Size]
Here is a new Clock Work Mod for the ICS unlocked bootloaders only.
Features:
* cleanup tab option: shortcut to try to fix forcequits after updates, return to recovery and select on the main screen (Wipes Cache, dalvik, and fixes permissions)
* Standard options to backup and restore to either the SD card or internal storage
* Mount points match those of most running roms
* adb shell works as root (with or without system mounted)
* set boot mode menu to select the boot partition (hidden on know non-multiboot bootloaders)
* setbootmode and itsmagic command line tools for advanced users
* /data/linux directory is not deleted on erase userdata, nor backed up on nandroid backup (just like /data/media) to allow a space for linux files for dual boot and chroot linux installes.
While there may not be much fantastic yet about the recovery it appears funcitonal at this point. (Features such as touch ui may appear in the future)
Why is it called Public: its public in the sense that all the scripts and code required for anyone to build it have been made avalible. (note some linux knowledge may be needed to build it yourself)
[Size=+2]Installation[/Size]
There are to main ways to install
1) using fastboot or nvflash you can install the image
A500PubRecovery_v0.2.img MD5: 0e40a494cd066b1c8e1a8d01493f1452
2) using a any exiting recovery (as long as you have one of the unlocked bootloaders) you can install with an update.zip
A500PubRecovery_v0.2_update_S.zip MD5: 349d0d6284fc6d1e071827a37a8a55e5
** (FYI the fastboot command to run on your computer is 'fastboot flash recovery A500PubRecovery_v0.2.img')
[Size=+2]Developers Additional Information:[/Size]
Build instructions (including how to fetch the source code) is here:
https://github.com/ezterry/AcerRecovery/blob/recovery_manifest/README.mkdn
(Thanks yous/Credits are also included)
Kernel:
as of version 0.2 the kernel is built from source (see above for information on fetching the build tree including the linux kernel)
the kernel in v0.1 was a patched for system r/w acer ICS Stock kernel
additional information can be seen on the commit:
https://github.com/ezterry/AcerRecovery/commit/402da6f73e752e80312318e177035ee02e4fbf89
The biggest thanks is as manythings in the Android World to Koush, and the CyanogenMod team. (They did the hard part, I've just tweaked it for the A500 configuration)
[Size=+2]Version List[/Size]
v0.2:
A500PubRecovery_v0.2.img 0e40a494cd066b1c8e1a8d01493f1452
A500PubRecovery_v0.2_update_S.zip 349d0d6284fc6d1e071827a37a8a55e5
v0.1:
A500PubRecovery_v0.1.img 4414bdbdd3aa7b7d7d1166595e6ccb2a
A500PubRecovery_v0.1_update_S.zip f45e7e3b640b42a68ec9bb08bd4b88ce
for details on the source commits used in the builds please see:
https://github.com/ezterry/AcerRecovery/blob/recovery_manifest/VERSIONS.mkdn
I will put it in the guide ,so when you flash the unlocked boot loader you can chose to install this with it , the more options for the user the better.
Thanks for the hard work.
Awesome !!! im curious to look at source so thanks for this
Sent from my SCH-R760 using XDA
btw,
The a501 is a very similar device.. is some more advanced user wishes to test things out and let me know if and changes is needed or if its good as is (fastboot boot may be useful if you wish to boot it without actually saving it to the tab)
Other Acer devices probably need slight modifications, if you help I can look into adding it to the codebase/builds..but I can only test the a500 as it's the only tab I own.
Just try to make sure you have a link to the source code of any kernel..and failing that that it Lisa stock kernel from an official OTA image.
I have a A500 with the Build.Number "1.033.00_EMEA_DE".
I have Problems to get the CWM with that Tutorial:
http://www.brutzelstube.de/2012/acer-iconia-a500-mit-android-4-0-ics-rooten/
Its all running fine but when i want to boot into the CWM it seems to work but then the Android Guy with open Stomach and the Red ExclamationPoint is showing.
I wonder if i can use this Public Recovery v0.1??
Maybe someone can help me that.
Basian Mile said:
Its all running fine but when i want to boot into the CWM it seems to work but then the Android Guy with open Stomach and the Red ExclamationPoint is showing.
Click to expand...
Click to collapse
If you are running a stock ICS rom you need to make sure you don't have the recovery patch still installed, otherwise the stock recovery will be installed on reboot if any other recovery is installed.
If you have the script and patch.. this recovery as any other custom recovery will be overwritten.
Sent from my Galaxy Nexus using Tapatalk 2
The CWM (v5 from Thor2002ro) is running now. I was using the wrong CPUID. That was my falut. But now its ok.
So i can flash this new Recovery just in this right?
If you have one of the the unlocked ics bootloader you can flash this recovery.. either directly or with the update.zip from a working custom recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Great Job!
If you want to build an A510 version, just change the data partition to point to /dev/block/mmcblk0p10. Everything else stays the same. If it doesn't boot, i may need to have the A510 recovery kernel.
BTW.. the recovery kernel doesn't really need to be patched for r/w, because /system never gets mounted as readonly, so it never does a remount to r/w. I've repacked recoveries with stock ICS kernels and they work fine. == Although, it doesn't hurt to patch them. ==
Euclid's Brother said:
BTW.. the recovery kernel doesn't really need to be patched for r/w, because /system never gets mounted as readonly, so it never does a remount to r/w. I've repacked recoveries with stock ICS kernels and they work fine. == Although, it doesn't hurt to patch them. ==
Click to expand...
Click to collapse
Part of it is I intend the kernel for my own ics rom. (Safer anyway in my opinion to not find any surprises as a user but not the biggest issue)
Tested it and installed fine , it's barebones recovery but I think A lot will love it , clean and simple. I used fastboot to install it .
Thanks Ez.
BTW I'm working on the next release
1) Some minor bug fixes (partitioning sdcard and full wipe are a bit strange at present.. in most cases we don't re-partition sdcards.. and wipe if you are installing a rom after will fix its self)
2) Now that acer has released their source, I've dropped the pre-built tweaked stock kernel, and added a source build, mostly still stock but I've changed to lZMA to allow some more space for the recovery ramdisk. (also system remount is allowed by default in this kernel so no postbuild acrobatics .. ie KPatch script)
3) add setbootmode/itsmagic binaries to the system. A500 (this is in github as is the kernel so building from synced source will give you a recovery with these pre-installed)
4) hopefully add an interface to call said binaries
Also I have an A510 test version I need someone (with the tab) to try.. PM me
Edit (Feature Idea):
whould anyone be interested in recovery when wiping not only skiping /data/media (internal /sdcard) but also skiping /data/linux ?
The idea is dual boot people bootling linux could use a ramdisk to run some bindmount/piviot root hackery to make /data/linux the root directory
also anyone using chroot to run a linux distro along side android could use the /data/linux directory as the chroot jail
let me know and I'll look into making APR here support such a feature
Is it posible to add app cwm for install.zip,backup,restore since rom ?
For exemple,the same app into sgs2 with siyha kernel or another kernel ??? Big thanks
Envoyé depuis mon A500 avec Tapatalk
ezterry said:
3) add setbootmode/itsmagic binaries to the system. A500 (this is in github as is the kernel so building from synced source will give you a recovery with these pre-installed)
Click to expand...
Click to collapse
Ehm, definitely don't put itsmagic next to setbootmode, it corrupts the kernel image in AKB.
ezterry said:
Edit (Feature Idea):
whould anyone be interested in recovery when wiping not only skiping /data/media (internal /sdcard) but also skiping /data/linux ?
The idea is dual boot people bootling linux could use a ramdisk to run some bindmount/piviot root hackery to make /data/linux the root directory
also anyone using chroot to run a linux distro along side android could use the /data/linux directory as the chroot jail
let me know and I'll look into making APR here support such a feature
Click to expand...
Click to collapse
Yeah I'm actually thinking to install linux to /data/linux and chroot there, too, exactly the same way.
micky387 said:
Is it posible to add app cwm for install.zip,backup,restore since rom ?
For exemple,the same app into sgs2 with siyha kernel or another kernel ??? Big thanks
Click to expand...
Click to collapse
I'm not exactly sure what you are talking about,
If you want to use this recovery with RomManager (as an unofficial 3.x+ recovery) you may. (In rom manager select flash recovery, select a500, select that you have manually installed a CWM recovery, select 3.x) To make it "official" koush needs to update his repo.. and I'm not going to poke that until I fix some minor outstanding bugs.
Actions will by default happen on the /data/media partition (as that is usually /sdcard) and no roms are yet in the system.. but I may work on fixing that after I make the next release. Currently running a backup myself.
If you want some other app to do this.. it needs to be compatible with the clockwork mod API.
Skrilax_CZ said:
Ehm, definitely don't put itsmagic next to setbootmode, it corrupts the kernel image in AKB.
Click to expand...
Click to collapse
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
ezterry said:
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
Very clever... i was worried myself at first when i saw you mention itsmagic... i'm so happy we have an open bootloader now with no tricks... oh, except the original hacking
Thanks so much for your work on this!
ezterry said:
I'm not exactly sure what you are talking about,
If you want to use this recovery with RomManager (as an unofficial 3.x+ recovery) you may. (In rom manager select flash recovery, select a500, select that you have manually installed a CWM recovery, select 3.x) To make it "official" koush needs to update his repo.. and I'm not going to poke that until I fix some minor outstanding bugs.
Actions will by default happen on the /data/media partition (as that is usually /sdcard) and no roms are yet in the system.. but I may work on fixing that after I make the next release. Currently running a backup myself.
If you want some other app to do this.. it needs to be compatible with the clockwork mod API.
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
OK.
I want to know if it's possible to add the same app (a part of recovery)
Thanks
ezterry said:
next to as in both the "itsmagic" and "setbootmode" binaries are in /sbin? .. I hope you can live with that.
I don't intend to automatically run it *ever* in this recovery, just want it to exist for anyone cleaning the system to return to a HC bootloader.. probably won't even add it to the GUI as its not something you want to do by mistake (and really I don't want to promote anyone to do.. its just there for some advanced users doing advanced operations). Boot mode however will be in the gui.
Click to expand...
Click to collapse
Yeah that's ok, I meant next to as in GUI, that would bring only problems.
v0.2 is out (see op)
Bugfixes:
~ wipe full data fix
~ fix on formating the external sdcard
~ cleaned up some warnings
Features:
~ added multiboot support (select boot partition)
~ added itsmagic binary (command line only)
~ switch to kernel source build rather than pre-built kernels
~ added /data/linux support (skip on wipe data, and nandroid backup)
kernel was built from:
https://github.com/ezterry/AcerTabKernel/commit/a6312764aa19ea7fe581b9931723c206a12b11ef
config file: apr_a500_defconfig
besides the configuration the kernel source is thus far unchanged from the acer a500 ICS drop
The kernel is built along with the recovery, see developer notes in OP for a link to the build instructions.
v0.2 doesn't boot for me.
Using Skrilax v6 bootloader I can't boot v0.2 while v0.1 works fine, both flashed from fastboot.
I also tried flashing v0.2 from v0.1 recovery, same results.
I've just got a new Samsung Galaxy TAB A 7.0 LTE SM-T285, For some reason I can't seem to find any resources for this hardware yet in this forum, anyone know where I could find one? I'll try to find out if the current methods (custom recovery and root) for other tab versions work on this.
CUSTOM ROMS
============
Android 5.1.1 Lollipop (Stock)
Tinker V5 Edition based on the Samsung Stock Rom SM-T280/T285
Android 6.0 Marshmallow
Cyanogenmod 13 for the SM-T285 Only
OMNIRom for the SM-T285 Only
Android 7.1 Nougat
Cyanogenmod 14.1 for the SM-T285 Only (Experimental, things are broken, depcrated in favor of LOS 14.1)
LineageOS 14.1 for the SM-T285 Only
Other Operating systems
Porting for Sailfish OS is currently in progress for the SM-T285, stay tuned
TWRP RECOVERY AND ROOT
=======================
TWRP is available for both the T280 and T285. You should find the relevant threads in this Galaxy Tab A forum.
If you want to root stock, easiest way is to install TWRP and go for SuperSU. Please see the TWRP threads for SM-T280/T285 on how to root after TWRP is installed.
KERNEL
======
Custom kernel with working sources for the SM-T285 can be found Here
DEVELOPMENT
============
If you want to build LineageOS 14.1 on your SM-T285 LTE device, you can use this manifest, not that this is still a work in progress:
https://github.com/jedld/android.git
UPDATE 10/06/2016
================
After a couple of weeks of trial and error and tinkering, I've been able to compile a kernel for the SM-T285 from source and so far it seems to work flawlessly!
Screenshot here: http://imgur.com/a/HRgsq
link to my kernel sources here: https://github.com/jedld/kernel_samsung_gtexslte.git
You can also thank samsung for giving us a "broken by default" kernel source. I had to mix and match defconfigs from their other kernel releases just to make this thing work. Download modified boot.img here:
http://forum.xda-developers.com/galaxy-tab-a/development/kernel-galaxy-tab-7-0-2016-lte-sm-t285-t3474967
UPDATE 09/20/2016
================
This device is now ROOTED!
http://forum.xda-developers.com/galaxy-tab-a/help/resources-samsung-galaxy-tab-7-0-2016-t3431022/post68777842#post68777842
Download Pre-rooted Tinker Edition V5 in this thread: Tinker Edition Thread
Post Root Post Mortem Analysis for the SM-T285 (09/21/2016)
=========================
Q: How were you able to find root? What did you do?
A: Surprisingly the SM-T285 bootloader isn't actually locked like we thought it was (Once you OEM unlock of course and disable FRP). The bottomline is that
we simply needed patches to mkbootimg to properly package a boot image for this device as there were additional fields and sections not found on a normal boot image. There were even minor breaking difference between the tab 4 and the boot image for this device.
Q: I thought the bootloader was locked?? Why did it take so long?
A: I blame it on the really vague errors the bootloader shows when loading an improperly packaged boot image. What helped was my faith to open up a hex editor when I needed to, and really look at the stock images and the images we were making. What really pushed me to investigate further was the fact that I was able to make a really small modification to the ramdisk and use the abootimg -u update function instead of the create options.
Q: So the bootloader doesn't really check the image?
A: Yup, The bootloader doesn't do any check. I haven't checked if that is the case for the recovery partition though. Even without the SELINUXENFORCE headers at the end it still continues like other samsung devices do.
Q: So the mkbootimg patches are all that we need?
A: Yup, if you have CM, AOSP build env ready you can simply add the modified mkbootimg to system/core:
https://github.com/jedld/degas-mkbootimg/commit/b63ae38e2ab7040cc7ddaef777652a56b2e48322
Sample usage below:
Code:
degas-mkbootimg -o boot.img --base 0 --pagesize 2048 \
--kernel boot.img-zImage --cmdline "console=ttyS1,115200n8" --ramdisk boot_kitchen/boot.img-ramdisk-new.gz --dt boot.img-dt
Next challenge will be getting Cyanogenmod on this device as well as TWRP.
You won't because it has a locked bootloader, therefore not currently rootable and certainly no custom recovery.
jaritico said:
any idea to unlock bootloader?
Click to expand...
Click to collapse
Not unless Samsung provides one.
jaritico said:
any idea to unlock bootloader?
Click to expand...
Click to collapse
Probably no hope for root. the PIT, boot and recovery are basically untouchable, selinux enforcing enabled also does not help. You can still debloat and customize the system partition though:
http://forum.xda-developers.com/android/development/guide-samsung-galaxy-tab-7-0-sm-t285-t3438296
I'm working on getting CM 12.1 to run on this device.
jedld said:
Probably no hope for root. the PIT, boot and recovery are basically untouchable, selinux enforcing enabled also does not help. You can still debloat and customize the system partition though:
http://forum.xda-developers.com/android/development/guide-samsung-galaxy-tab-7-0-sm-t285-t3438296
I'm working on getting CM 12.1 to run on this device.
Click to expand...
Click to collapse
Yes at least the saving grace is that Samsung left Dm-verity off for this device.
If only they'd have left out the root restriction in the kernel too we'd have a rootable device.
I have an idea for this that I haven't tried yet.
Basically Samsung sends out security Policy updates via OTA, they recently released an SEPOLICY update to most devices breaking root. Chainfire patched this.
As this policy is stored in DATA and over rides the one in the boot.img it may be possible to use a patched SEPOLICY by creating a flashable DATA image with the patched SEPOLICY thereby removing the SElinux root restriction.
I ran it by Chainfire and he said in theory it should work except for that fact that the SEPOLICY in DATA is signed.
I have yet to try this out.
I think it would be difficult to get CM running as the kernel may need some patches and as we know that can't be touched.
ashyx said:
Yes at least the saving grace is that Samsung left Dm-verity off for this device.
If only they'd have left out the root restriction in the kernel too we'd have a rootable device.
I have an idea for this that I haven't tried yet.
Basically Samsung sends out security Policy updates via OTA, they recently released an SEPOLICY update to most devices breaking root. Chainfire patched this.
As this policy is stored in DATA and over rides the one in the boot.img it may be possible to use a patched SEPOLICY by creating a flashable DATA image with the patched SEPOLICY thereby removing the SElinux root restriction.
I ran it by Chainfire and he said in theory it should work except for that fact that the SEPOLICY in DATA is signed.
I have yet to try this out.
I think it would be difficult to get CM running as the kernel may need some patches and as we know that can't be touched.
Click to expand...
Click to collapse
I ran it by Chainfire and he said in theory it should work except for that fact that the SEPOLICY in DATA is signed.
I have yet to try this out.
Click to expand...
Click to collapse
Would probably need to brush up on se policies in linux. If there are already files available that I just need to flash over to /data I can try it out and also a means to test it if it works.
I've created a petition here:
https://www.change.org/p/samsung-unlock-the-bootloader-for-the-samsung-galaxy-tab-a-7-0-2016?recruiter=286570213&utm_source=petitions_show_components_action_panel_wrapper&utm_medium=copylink&recuruit_context=copylink_long
Not sure if samsung is the type that listens to this sort of thing though.
ashyx said:
As this policy is stored in DATA and over rides the one in the boot.img it may be possible to use a patched SEPOLICY by creating a flashable DATA image with the patched SEPOLICY thereby removing the SElinux root restriction.
I ran it by Chainfire and he said in theory it should work except for that fact that the SEPOLICY in DATA is signed.
I have yet to try this out.
Click to expand...
Click to collapse
I made an attempt to patch sepolicy using data however all I got in the logs was
Code:
E/SELinux ( 733): Function: fileToArray, File Open Unsuccessful:
E/SELinux ( 733): Function: getVersionhash, signature is NULL
I/SELinux ( 733): Function: selinux_init_verify_sepolicy, getVersionhash return false
E/SELinux ( 733): Function: VerifyPolicy , selinux_init_verify_sepolicy is failed
So far I have no indication that my patch worked
Code:
sepolicy-inject -s shell -t system -c file -p read -P sepolicy -o sepolicy
The error above only comes up if I place sepolicy in /data/security and sepolicy_version in /data/security/spota
sha256 hashes were also updated in the version file so I'm not sure what I'm missing.
If I could have a copy of a samsung ota that actually updates the policies I can probably have better direction
jedld said:
I made an attempt to patch sepolicy using data however all I got in the logs was
Code:
E/SELinux ( 733): Function: fileToArray, File Open Unsuccessful:
E/SELinux ( 733): Function: getVersionhash, signature is NULL
I/SELinux ( 733): Function: selinux_init_verify_sepolicy, getVersionhash return false
E/SELinux ( 733): Function: VerifyPolicy , selinux_init_verify_sepolicy is failed
So far I have no indication that my patch worked
Code:
sepolicy-inject -s shell -t system -c file -p read -P sepolicy -o sepolicy
The error above only comes up if I place sepolicy in /data/security and sepolicy_version in /data/security/spota
sha256 hashes were also updated in the version file so I'm not sure what I'm missing.
If I could have a copy of a samsung ota that actually updates the policies I can probably have better direction
Click to expand...
Click to collapse
Finally found a way to patch the kernel on this device. Stay tuned...
jedld said:
Finally found a way to patch the kernel on this device. Stay tuned...
Click to expand...
Click to collapse
Turns out I was just able to modify files in the boot.img, though when I try to update the sepolicy itself, it won't boot.
jedld said:
Turns out I was just able to modify files in the boot.img, though when I try to update the sepolicy itself, it won't boot.
Click to expand...
Click to collapse
Can you at least explain a bit further?
What modifications allow you to create a boot able image?
How have you overcome image signing?
Only way I can think of is hex editing the signature, however I was under the impression this was crc based.
ashyx said:
Can you at least explain a bit further?
What modifications allow you to create a boot able image?
How have you overcome image signing?
Only way I can think of is hex editing the signature, however I was under the impression this was crc based.
Click to expand...
Click to collapse
Yeah I was able to flash a modified boot.img using heimdall, turns out that you just need to use abootimg -u boot.img -r yourmodifiedramdisk so that you don't overwrite the SELINUXENFORCE headers appended at the end of the boot.img file, it appears the bootloader only checks for the presence of those headers but does not actually compute the sig.
Modifying ramdisk works, haven't tried modifying the kernel itself.
I tried to modify the sepolicy files after using sepolicy-inject but it throws a KERNEL not SEnforced error. I am not certain if this is just a blanket error if the kernel doesn't boot due to modifying the policy files incorrectly or if there is legit checking going on. Nevertheless I am able to modify the init.rc files now.
jedld said:
I tried to modify the sepolicy files after using sepolicy-inject but it throws a KERNEL not SEnforced error. I am not certain if this is just a blanket error if the kernel doesn't boot due to modifying the policy files incorrectly or if there is legit checking going on. Nevertheless I am able to modify the init.rc files now.
Click to expand...
Click to collapse
Continued checking it out. So even though I can modify the ramdisk, I am unable to add more than 1000 - 2000 bytes before setting off the SEAndroid enforce error on bootup. Might be some headers on the boot.img that I fail to update when the ramdisk size gets bigger. Trying to modify the sepolicy in any way even if there is minimal change in size prevents it from booting. I have no idea what is checking it, I'll try to hexedit and see what happens.
jedld said:
Continued checking it out. So even though I can modify the ramdisk, I am unable to add more than 1000 - 2000 bytes before setting off the SEAndroid enforce error on bootup. Might be some headers on the boot.img that I fail to update when the ramdisk size gets bigger. Trying to modify the sepolicy in any way even if there is minimal change in size prevents it from booting. I have no idea what is checking it, I'll try to hexedit and see what happens.
Click to expand...
Click to collapse
So I used a hexedit on the sepolicy file and was able to modify one byte of it effectively changing its sha256sum... and it worked. So the sepolicy file CAN be changed, however current sepolicy-inject and supolicy tools does something to it that trips it, looks like samsung has again added a proprietary modification sepolicy format.
I've never known a kernel not boot due to the kernel not SEANDROID enforcing warning.
It's a meaningless warning and easily bypassed.
However this is on bootloader unlocked devices.
So just let me get this straight, you have been able to repack the boot.img with modifications to the ramdisk then force flash it via Heimdall and it still boots?
ashyx said:
I've never known a kernel not boot due to the kernel not SEANDROID enforcing warning.
It's a meaningless warning and easily bypassed.
However this is on bootloader unlocked devices.
So just let me get this straight, you have been able to repack the boot.img with modifications to the ramdisk then force flash it via Heimdall and it still boots?
Click to expand...
Click to collapse
yup. that's correct. I'll post my modified boot.img in a while
jedld said:
yup. that's correct. I'll post my modified boot.img in a while
Click to expand...
Click to collapse
note that using the update only method of abootimg "abootimg -u boot.img -r xxxxxx " is the only one that works for repacking the ramdisk. Trying to build the boot.img from scratch using any other method has so far failed for me.
Here is a flashable boot.img for the SM-T285.
It contains the following modifications to the ramdisk:
a file at /this_device_is_owned
and a modified init.rc that creates a /tmp folder
jedld said:
Here is a flashable boot.img for the SM-T285.
It contains the following modifications to the ramdisk:
a file at /this_device_is_owned
and a modified init.rc that creates a /tmp folder
Click to expand...
Click to collapse
now managed to patch sepolicy using chainfire's supolicy tool. needed to use a customized mkbootimg due to changes in the Tab A image format for this. now attempting to root the device... wish me luck
Welcome to a simple tutorial that will help OnePlus 2 (OP2) owners and possibly other device owners install custom ROMs in such a way that eliminates most, if not all possibility of system errors, resulting in the longest lasting and most stable custom ROM installations!
DISCLAIMER: Your Warranty was voided long before you were ever even ready to complete this tutorial.
Therefore, I am not responsible for a broken or bricked device, especially if your rage towards a bricked device caused you to throw your device into a wall. This tutorial is actually designed to reduce the amount of "Rage Quitting" on modifying your device.
This Tutorial assumes you have already completed OEM Unlock, Root, installed TWRP or other Custom Recovery, and are basically ready to install a custom ROM on your OP2.
Before beginning, backup any files you may need, I upload mine to my Google Drive then download after completing the ROM install. You can also use Nandroid to backup your current system (optional as there are methods to restore even the most bricked OP2 that doesnt even have a working recovery or OS, trust me I have done it at least 5 times because I constantly try new ROMs and mods). There are three necessary prerequisite steps required to complete before using this method to install your custom ROM. These prerequisites are listed below:
Prerequisite One: Ensure your OnePlus 2 has been FULLY updated on the stock Oxygen OS ROM before you install your TWRP or other Custom Recovery. If not, Return to factory ROM, Un-Root, and update until you cannot update any more, then return to this tutorial afterwards.
Prerequisite Two: Ensure your OnePlus 2 has the latest update of the TWRP or other Custom Recovery. The Latest TWRP for the OP2 can be found here: https://twrp.me/oneplus/oneplustwo.html
Prerequisite Three: Ensure your device can receive files via ADB PUSH while in custom recovery. To do this, reboot your phone into recovery, connect to PC, hold down the "Shift" key and while holding, right-click in a window containing a file you wish to transfer, and select "Open Windows PowerShell Here" or "Open Command Prompt Here". Use the command "adb push Lin15.zip /sdcard" (remove the quotes, "Lin15.zip" is an example file) to push the file onto your device. Then, if your custom recovery has a file explorer as TWRP does, use it to navigate to /sdcard and see if the file is there. Also, your windows should show a successful transfer and should say "Okay" underneath your command line. If unsuccessful, install OnePlus 2 Drivers along with Universal ADB drivers and then try again. If still unsuccessful, try TWRP 3.1.1-0 (Download Link Below 2 Paragraphs in Blue Text Section). If unsuccessful at this point, there is something wrong as Win 10 with OP2 Drivers, Universal ADB Drivers, and TWRP 3.1.1-0 is my exact setup.
There are many custom ROMs available for the OP2. The method for installing custom ROMs is generally the same, but can differ in certain ways. This method SHOULD work for your custom ROM, but is not guaranteed. If this method fails, then visit your custom ROM's development page, and follow their instructions instead.
In this Example, I will be installing the latest (at the time of writing) Lineage 15 Android Oreo 8.0 Third Alpha Build OS/ROM and will be including instructions for the proper installation of the A.R.I.S.E. Magnum Opus System Sound Mod (Based on Viper4Android). I will include links to downloads, but their main XDA page can be found here: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 This installation will use the latest (at the time of writing) TWRP 3.1.1-0 Custom Recovery.
INSTALL TIME:
Begin by rebooting into recovery. Under "Wipe" options, you will first want to format data, select the option and type "yes" when prompted to confirm the operation. Repeat this step once again to ensure a squeaky clean wipe.
Next, also under "Wipe" Options, select the "Advanced Wipe" Options. You will then select EVERY BOX (Yes, this includes Internal Storage and will wipe EVERY SINGLE FILE from your device, this is INTENTIONAL and is why you MUST have a device that can accept ADB PUSH files in recovery!). This will wipe every file from existence, completely. This is what allows such a stable, squeaky clean install, as not a single piece of evidence from any other ROM/OS will be left behind, leaving basically no chance for errors or conflicts during installation of new ROM. You will want to complete this step again to ensure a squeaky clean wipe.
Navigate to the TWRP Home/Start-Up Screen and connect your device to your PC (WARNING: DO NOT USE ADB SIDELOAD MODE!!! I HAVE NEVER, EVER HAD A SUCCESSFUL ROM INSTALL FROM SIDELOAD!!!). Simply leave the device at this screen, and do not touch it. At this point, if you do not have all the necessary files to install your custom ROM and mods, you will need to download them now. I ALWAYS recommend the "Pico" Gapps package if installed in a ROM (some ROMs include Gapps). The reason for this is because the Pico package includes the bare minimum to get Google Play Services and Google Play Store up and running. This eliminates unwanted Gapps and reduces the chance of installation conflicts. The golden rule is: The less you install in TWRP, the better. If you want more Gapps, then after setting up the phone at the end of the ROM install, just search for them in the Google Play Store, its how I get mine every time. In the case of Lineage 15, the list of downloads is below:
Lineage 15 OS/ROM: https://www.androidfilehost.com/?fid=961840155545594199 (Dev Page: https://forum.xda-developers.com/oneplus-2/development/rom-lineageos-15-0-t3668056)
Android Oreo 8.0 Pico Gapps Package: https://www.androidfilehost.com/?fid=817550096634796662
Super SU 2.82 Root Installer (Select the Flashable 2.82 ZIP file): http://www.supersu.com/download
BusyBox Flashable Zip Package (Large page with many tools, scroll down to find the BusyBox tool): https://forum.xda-developers.com/showthread.php?t=2239421
A.R.I.S.E. Magnum Opus System Sound Mod (Select the "ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip" Option): https://www.androidfilehost.com/?w=files&flid=176171
Once all necessary files are downloaded, give them their own folder inside Windows and rename all of them to something simple as shown here:
View attachment 4273530
(Lin15.zip, Gap.zip, SU.zip, Busy.zip, Arise.zip)
Ensure your device is in custom recovery at the home/startup screen and is plugged firmly into your PC. DO NOT navigate ANYWHERE inside custom recovery or touch the device.
Now we will ADB PUSH these fresh install ZIP files over to your device. Inside the window containing your downloaded ROM files, hold down the "Shift" key and while holding, right-click and select "Open Windows PowerShell Here" or "Open Command Prompt Here". To ADB PUSH files, simply type "adb push FILE.zip /sdcard" where "FILE" is the target file and "/sdcard" is the target destination. Correct capitalization of letters is IMPORTANT! My window looked like this when finished:
View attachment 4273532
(adb push Lin15.zip /sdcard, adb push Gap.zip /sdcard, adb push SU.zip /sdcard, adb push Busy.zip /sdcard, adb push Arise.zip /sdcard)
Your ROM files should now appear on your device at your target destination. Disconnect your device and use the Custom Recovery File Explorer to navigate to the destination to confirm. "/sdcard" is the easiest to use destination.
Now we will install ALL of the ROM files, back-to-back with NO REBOOTS, NO WIPES, NO OPERATIONS WHATSOEVER INBETWEEN INSTALLS, THIS IS EXTREMELY IMPORTANT!!! Navigate to the Custom Recovery "Install" Section and navigate to your destination for your files. Flash the ZIP files in this order EXACTLY: Lin15, Gap, SU, Busy, Arise.
The A.R.I.S.E. Instillation is an AROMA style installer. It is a HUGE Sound Mod suite containing many options. Select the sound mods you like, but there is a module that is REQUIRED and 4 others that are highly recommended, listed below:
CORE Module is REQUIRED!!! Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions fix are all highly recommended no matter what the ROM or mods, just in case. If these problems do not exist, selecting the options will not change anything, so do not worry.
My personal A.R.I.S.E. install included the following modules and delivers absolutely AMAZING sound quality while keeping installed modules to a minimum (otherwise known as a "Lightweight" install): Core Module, Viper4Arise 2.5.0.5, Viper4Arise Profiles, Uninstall MusicFX, Remove Deep_Buffer, Set SELinux to Permissive, and SD Card Permissions Fix. Its a highly recommended package
ONLY AFTER ALL FILES HAVE BEEN INSTALLED, navigate to Custom Recovery "Wipe" section, select "Advanced Wipe" and then check the "Dalvik Cache" and "Cache" options, DO NOT SELECT ANYTHING ELSE OR YOU WILL NEED TO START COMPLETELY OVER, WIPE PHONE AND RE-ADB PUSH FILES TO ENSURE A SQUEAKY CLEAN INSTALL!!! Perform this step again to ensure a squeaky clean wipe.
YOU ARE NOW FINISHED WITH A SQUEAKY CLEAN ROM INSTALL BUT THERE ARE A FEW MORE RECOMMENDED STEPS!
Recommended: DO NOT immediately reboot into system after install. Instead, navigate to Custom Recovery "Reboot" Section and select "Power Off" Instead. Once device is off, plug into A/C Outlet charger (DO NOT USE A PC, DETECTION OF PC WILL CAUSE DEVICE TO BOOT), and allow to fully charge, then cool off. This will ensure that Battery Calibration is set to 100% upon Initial Boot
Initial Boot: Boot Device, Initial boot will take around 5-10 minutes. DO NOT TOUCH THE DEVICE DURING THIS TIME. When you see the startup screen, STILL DO NOT TOUCH THE DEVICE! Instead, allow device to sit and idle, allowing the ROM to "Settle" for a MINUMUM of 5 minutes, 10 is recommended. Then, BEFORE setting up the device, reboot and allow another 5 minutes of "settling".
Run through the Device Initial Setup. You will want to select any desired options now, and avoid having to search settings later. Once at Device Home Screen, immediately open app drawer and select SuperSU app. Inside SuperSU, navigate to settings and apply the following options:
Disable Re-Authentication, Default Access: Grant, Enable SU During Boot, Trust System User
These SuperSU options will allow mods to function with complete stability and no interference, leading to a smoother experience. After, completing this step, Reboot your phone and ENJOY YOUR NEW, ROCK-SOLID, STABLE ROM INSTALL!!!
Nice job bro thanks working here!
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.
shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Now I tried it again and this time flashed busy box as well but the same error.
Screen shot for your reference. Is there another way to install it?
shailinder said:
Nopes. It did not work out for me. I flashed ROM, Gapps, and Magisk before and landed on your thread and flashed only the ARISE zip. But it did not flashed properly and I got an error 1 or something like that. What could be the reason?
Click to expand...
Click to collapse
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
pops106 said:
Why are people recommending using adb push to get the files on the phone.
I always just drag and drop them on the phone in windows explorer, never had any problems.
Only time I ever need adb is for flashing recovery.
Click to expand...
Click to collapse
Well we all know performing this method of install is not a requirement for installing ROMs, but it is the most fool-proof method and ensures there are no file conflicts between old and new ROMs/OS's. I cannot even tell you how many times I have done quick, minimal work installs and end up with tons of errors, laggy or freezing screens at random times, force closing apps, busybox system link failures, the list goes on and on. After using the "Squeaky Clean" method, I can honestly say Lineage 15 is as stable as the Stock/Factory Oxygen OS.
wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Thanks. I got it install using a different method and it is working wonderfully.
wallacengineering said:
Error 1 is what occurs on the non-AROMA older A.R.I.S.E. package install if you have not set up any settings in the customizable .prop file that comes with the ZIP. Upon initial install, this "Error 1" will install a .prop file under /sdcard. If you open this .prop file with a text editor, you can then use examples such as "install.core=true" to install the core. However, the AROMA installer requires none of this. And as far as I experienced, NONE of the other packages work on Lineage 15. You will want to delete whatever A.R.I.S.E. zip you have now, and follow my download link for the AROMA version. Then, wipe everything and perform a "Squeaky Clean" ROM install as shown in this thread, and it should work and be rock-solid stable.
Click to expand...
Click to collapse
Fair enough
And thanks to the opp for the thread
pops106 said:
Fair enough
And thanks to the opp for the thread
Click to expand...
Click to collapse
No problem, the thread was a random idea after accidentally stumbling across the fact that TWRP can accept ADB PUSH files. I honestly had no idea, and was stuck in a bootloop after a custom ROM failed to install correctly. I had no backup and was getting ready to just give up, enter Qualcomm Diagnostics Mode and perform the Oxygen OS Firmware/Software OEM install when I decided to reboot into Recovery and attempt SideLoad of a previous ROM that had worked.
This did not work, as sideload is apparently a dumb way of doing things. I never understood why sideload tries to install a file that is in the middle of transferring. Just seems like a flawed concept to me. Anyways the install was very slow, buggy and laggy, and when finished had installed such a corrupt system, due to installing a partially transferred file while it is being transfered and then sticking all the pieces together, was so unstable that more than a minute idling at the home screen or any attempt to open ANY app caused the phone to reboot.
Sideload is a worthless feature in my opinion and I will never use it for any operation ever again so long as I live. So all of a sudden I decide to plug the phone into my PC while in recovery and observe how Windows detects the phone when you turn Sideload mode on and off, as to try and troubleshoot my sideload to get an effective install (which by the way will never happen, to this day I have never had a sideload install work correctly), and noticed when I turned it off, the device still showed up as a recognized Android device under Windows Device Manager. Then, you may not believe me on this, but I did actually randomly decide that more than likely, it was interfaced on Universal ADB, and that it I typed "adb devices" into a windows command prompt, it should show, and it did. The rest is history.
I know the feature had been around for some time as I found out later on, but I had never seen any information about it anywhere on any thread, and even when I asked for ideas for troubleshooting, while XDA users helped for sure, I guess they just didnt have that idea, and gave me alternative routes as well such as the Qualcomm Diagnostics full OEM wipe method which I was already familiar with. This does show, however; that experimenting and troubleshooting on your own can be a great way to learn new things!
Hi, thank you for the post.
I am enjoying v4a bcoz of you only.
I got a query btw, can I install dolby & atmos along with v4Arise?
Please add a note for HaruhiOS
HaruhiOS checks if a clean flash is required before flashing and will abort to tell the user that a clean flash is necessary if ever. It is my design goal to avoid the need for clean flashing as much as possible
Due to this the user should avoid unnecessary clean flashing, which actually ruins performance and battery life and reduces device health when using my ROM
if already.....
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.
magnamentis said:
hey,
if one would already go thus far to wipe internal storage as well, i'd say that it's making sense to format storage by changen from ext4 to ext2 and back to ext4. wiping is not always getting us rid of all residues while changing the file system and going back to the one we want/need does indeed reformat everything, this is a procedure that is useful once the storage card is corrupted.
Click to expand...
Click to collapse
Apparently e2fsck and fsck.f2fs is too hard
Once the storage card is corrupt no formatting will help you anyways
Just stop believing in dumb stuff. If you have to clean flash every other build a ROM developer releases they messed up big time and they should fix their code
This is a port of Lanchon REPIT.
- Nexus 7 (2013) Deb (LTE) and Flo (WiFi) -
Disclaimer:
I am not responsible for your actions or consequences, directly or indirectly, related to the files and/or advice offered.
It is your choice to proceed.
What is REPIT?
REPIT is a simple, safe, device-only, data-sparing, and easily portable repartitioning tool for Android devices.
See the GitHub README for more on What REPIT is. GitHub - Link
Limitations:
Requires TWRP (or TWRP based) recovery.
Does not support encrypted devices.
Will cause data loss if the repartitioning process is externally interrupted.
See the GitHub README for more on Limitations. GitHub - Link
---
Notes:
A few years ago (September 2018), I made a port of REPIT for deb,flo and manta that was spread out between multiple threads.
Some comments and instructions were lost in thread chatter or just in a different thread altogether.
The file name actually configures the repit script.
Noted that you may have to toggle MTP Disable, Enable, Disable.
Noted that you may have to reboot into TWRP after disabling MTP.
Remember /tmp is wiped after a reboot. Copy repit to /sdcard and after rebooting back into TWRP, copy it from /sdcard to /tmp using TWRP File manager.
Noted that you may have to unmount cache and data.
Do NOT flash repit from USB/OTG.
This is designed for a stock partition layout. If your device has been modified and a vendor partition was created, REPIT will not work.
Side note:
Lanchon added Nexus 7 (2013) to the official list. (November 2019)
Lanchon REPIT GitHub - Port Request - Commit
---
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Backup what you want to save and store it off device.
Copy it to your computer, cloud storage, USB, ...
Instructions:
This operation might take a long time and must not be interrupted.
- Depending on the device and REPIT configuration, this might take a few hours.
Make sure your battery is fully charged or mostly charged.
- You can connect to a charger while the REPIT script is running. May or may not charge depending on the recovery.
How To:
If you already have a ROM installed, repit will backup, change the partition, restore and resize.
- You can just reboot once the script finishes.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to system
If you are doing a clean install, add the +wipe option to system in the zip file name. This will speed up the partitioning since system will not be backed up and restored.
lanchon-repit-20210220-system=max+wipe-cache=16M+wipe-flo.zip
- Reboot back into TWRP after the script finishes.
- Then follow the instructions from the rom thread to install the rom you are going to use.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to recovery
Follow the instructions from the rom thread to install the rom you are going to use.
---
Changes:
Nexus 7 (2013) [Deb][Flo]
Pushed a bit pass the safe zone and claimed a bit more unallocated space.
Updated to the current REPIT scripts.
Separate zip files for deb and flo.
Nexus 7 (2013) GitHub - Commit
Download Links:
MediaFire - Link
SourceForge - Link
GoogleDrive - Link
Direct Download from MediaFire:
lanchon-repit-20210221-system=max-cache=16M+wipe-deb.zip MediaFire - Download
lanchon-repit-20210221-system=max-cache=16M+wipe-flo.zip MediaFire - Download
REPIT Links:
Lanchon REPIT GitHub - Link
- My fork GitHub - Link
Credits:
Lanchon for his excellent REPIT project.
The Android Community and everyone who has helped me learn through the years.
Cheers all.
Note about configuration.
The user configuration is done by renaming the zip file before flashing it.
Not much room to change on deb/flo.
The modifiable partitions are only system and cache (22 and 23).
The actual partitioning is done by a sector range. This is declared inside the script along with a default configuration.
Code:
# the set of partitions that can be modified by REPIT:
# <gpt-number> <gpt-name> <friendly-name> <conf-defaults> <crypto-footer>
initPartition 22 system system "same keep ext4" 0
initPartition 23 cache cache "same keep ext4" 0
initPartition 24 misc misc "same keep raw" 0
# the set of modifiable partitions that can be configured by the user (overriding <conf-defaults>):
configurablePartitions="$(seq 22 23)"
...
# the set of contiguous partitions that form this heap, in order of ascending partition start address:
heapPartitions="$(seq 22 24)"
# the disk area (as a sector range) to use for the heap partitions:
heapStart=$(parOldEnd 21) # one sector past the end of tzb.
heapEnd=$(parOldStart 25) # the start of recovery.
By default, REPIT will back up, restore, compress and/or expand a partition.
The +wipe option will wipe the partition.
The max option is an easy way to allocate the remaining space for a partition.
The misc partition is not part of the user-config but, it is in the sector range.
It will be moved to the the end of the sector range without alteration.
The default zip name lanchon-repit-20210221-system=max-cache=16M+wipe-flo.zip
Creates a 16M clean cache partition. (Wiped)
Uses the rest of the unallocated space in the range for system.
System is backed up and restored since the +wipe option was NOT added to system.
Since only system and cache can be configured, this only allows a few options for deb and flo.
Default zip name. -system=max-cache=16M+wipe-
Include wipe system. -system=max+wipe-cache=16M+wipe-
See the GitHub README for more on how to configure. GitHub - Link
Cheers all.
<RESERVE>
<RESERVE>
I think this deserves a bump, because, this is some great work right here for those wanting to stick with a stock-like partition layout!
Hi, I want to go back stock partition size. So i have to rename the zip.
What zip name?
ipdev said:
This is a port of Lanchon REPIT.
- Nexus 7 (2013) Deb (LTE) and Flo (WiFi) -
Disclaimer:
I am not responsible for your actions or consequences, directly or indirectly, related to the files and/or advice offered.
It is your choice to proceed.
What is REPIT?
REPIT is a simple, safe, device-only, data-sparing, and easily portable repartitioning tool for Android devices.
See the GitHub README for more on What REPIT is. GitHub - Link
Limitations:
Requires TWRP (or TWRP based) recovery.
Does not support encrypted devices.
Will cause data loss if the repartitioning process is externally interrupted.
See the GitHub README for more on Limitations. GitHub - Link
---
Notes:
A few years ago (September 2018), I made a port of REPIT for deb,flo and manta that was spread out between multiple threads.
Some comments and instructions were lost in thread chatter or just in a different thread altogether.
The file name actually configures the repit script.
Noted that you may have to toggle MTP Disable, Enable, Disable.
Noted that you may have to reboot into TWRP after disabling MTP.
Remember /tmp is wiped after a reboot. Copy repit to /sdcard and after rebooting back into TWRP, copy it from /sdcard to /tmp using TWRP File manager.
Noted that you may have to unmount cache and data.
Do NOT flash repit from USB/OTG.
This is designed for a stock partition layout. If your device has been modified and a vendor partition was created, REPIT will not work.
Side note:
Lanchon added Nexus 7 (2013) to the official list. (November 2019)
Lanchon REPIT GitHub - Port Request - Commit
---
Be Careful.
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start modifying partitions.
Backup what you want to save and store it off device.
Copy it to your computer, cloud storage, USB, ...
Instructions:
This operation might take a long time and must not be interrupted.
- Depending on the device and REPIT configuration, this might take a few hours.
Make sure your battery is fully charged or mostly charged.
- You can connect to a charger while the REPIT script is running. May or may not charge depending on the recovery.
How To:
If you already have a ROM installed, repit will backup, change the partition, restore and resize.
- You can just reboot once the script finishes.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to system
If you are doing a clean install, add the +wipe option to system in the zip file name. This will speed up the partitioning since system will not be backed up and restored.
lanchon-repit-20210220-system=max+wipe-cache=16M+wipe-flo.zip
- Reboot back into TWRP after the script finishes.
- Then follow the instructions from the rom thread to install the rom you are going to use.
Boot into TWRP
Swipe to Allow Modifications
Copy the repit zip to /tmp
Disconnect from computer
Disable MTP
Disable MTP TWRP -> Mount
Install repit
TWRP -> Install -> navigate to /tmp and flash the repit zip
Reboot to recovery
Follow the instructions from the rom thread to install the rom you are going to use.
---
Changes:
Nexus 7 (2013) [Deb][Flo]
Pushed a bit pass the safe zone and claimed a bit more unallocated space.
Updated to the current REPIT scripts.
Separate zip files for deb and flo.
Nexus 7 (2013) GitHub - Commit
Download Links:
MediaFire - Link
SourceForge - Link
GoogleDrive - Link
Direct Download from MediaFire:
lanchon-repit-20210221-system=max-cache=16M+wipe-deb.zip MediaFire - Download
lanchon-repit-20210221-system=max-cache=16M+wipe-flo.zip MediaFire - Download
REPIT Links:
Lanchon REPIT GitHub - Link
- My fork GitHub - Link
Credits:
Lanchon for his excellent REPIT project.
The Android Community and everyone who has helped me learn through the years.
Cheers all.
Click to expand...
Click to collapse
I have been trying to repartition Nexus flo 2013 following the steps outlined above with lanchon-repit-20210221-system=max+wipe-cache=16M+wipe-deb.zip for 19.1 version but keep getting Error 1, see photo. Any help will be much appreciated. Thank you
greenleaves said:
I have been trying to repartition Nexus flo 2013 following the steps outlined above with lanchon-repit-20210221-system=max+wipe-cache=16M+wipe-deb.zip for 19.1 version but keep getting Error 1, see photo. Any help will be much appreciated. Thank you
Click to expand...
Click to collapse
Problem fixed. Now 19.1, pico gapps and Magisk 25.0 were flashed in success. The problem was that I didn't follow through the steps carefully described on the OP to increase the partition sizes as follows:
The file name actually configures the repit script.
Noted that you may have to toggle MTP Disable, Enable, Disable.
Noted that you may have to reboot into TWRP after disabling MTP.
Remember /tmp is wiped after a reboot. Copy repit to /sdcard and after rebooting back into TWRP, copy it from /sdcard to /tmp using TWRP File manager.
Noted that you may have to unmount cache and data.
Do NOT flash repit from USB/OTG.
This is designed for a stock partition layout. If your device has been modified and a vendor partition was created, REPIT will not work.
greenleaves said:
Problem fixed. Now 19.1, pico gapps and Magisk 25.0 were flashed in success. The problem was that I didn't follow through the steps carefully described on the OP to increase the partition sizes as follows:
The file name actually configures the repit script.
Noted that you may have to toggle MTP Disable, Enable, Disable.
Noted that you may have to reboot into TWRP after disabling MTP.
Remember /tmp is wiped after a reboot. Copy repit to /sdcard and after rebooting back into TWRP, copy it from /sdcard to /tmp using TWRP File manager.
Noted that you may have to unmount cache and data.
Do NOT flash repit from USB/OTG.
This is designed for a stock partition layout. If your device has been modified and a vendor partition was created, REPIT will not work.
Click to expand...
Click to collapse
Edit: NVM, i used restock to start fresh, and it all went fine. I've had this table kicking around long enough that I'm sure something was done that sysrepartundo couldn;'t undo.
How did you actually fix it? I ran sysrepartundo, am running it from the tmp folder with mtp disabled and nothing mounted, and still getting error 1. I've double check, all my partition sizes are stock.. I've been at this a few hours now and am getting frustrated.
theistus said:
I ran sysrepartundo, am running it from the tmp folder with mtp disabled and nothing mounted, and still getting error 1. I've double check, all my partition sizes are stock.. I've been at this a few hours now and am getting frustrated.
Click to expand...
Click to collapse
sysrepartundo is ancient and useless nowadays, try sysrepart-stock instead
Thank you for the script. I was able to repartion my flo and make it compatible with android 12L. Everything went smooth after realising (and correcting this mistake) that i"ve been putting the .zip inside /sdcard/tmp instead of /tmp (I was getting error 1 in TWRP).
During instalation process i"ve connected flo to charger and it indeed charged during repartition process
Things i"ve noticed
- TWRP appeared to be very laggy during repit process and took several seconds to reconginse the charger (to show to + sign next to the battery % to be precise)
- after device rebooted to stock 6.0.1, MTP didn"t work correctly. It appeared in my computer as "Nexus 7", but was completely empty. One more reboot (this time got short loading toast of "android is updating") and internal memory was visible from computer again
THANKS! It worked great for me also. I have mentioned it in the [GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 Stock to Android 12 Tutorial.
Hi,
I had used @followmsi's sysrepart_1280_120.zip some time ago.
Now I'm interested in @followmsi's lineage 19.1 and want to use your lanchon-repit-20210221 script for increasing the system partition again.
Would you still consider the partition layout as stock, so I could use your script ? (See attachments)
And do I need a PC as the USB port is inoperative, so no way to connect to a PC?
Thank you very much in advance!
curiousde2002 said:
Hi,
I had used @followmsi's sysrepart_1280_120.zip some time ago.
Now I'm interested in @followmsi's lineage 19.1 and want to use your lanchon-repit-20210221 script for increasing the system partition again.
Would you still consider the partition layout as stock, so I could use your script ? (See attachments)
And do I need a PC as the USB port is inoperative, so no way to connect to a PC?
Thank you very much in advance!
Click to expand...
Click to collapse
You should be good to go.
Using one of the older (re)partitioning methods did not affect the partition table too much.
The note about a stock partition layout is mainly for users who used a (re)partition script that adds a separate vendor partition.
Cheers.
ipdev said:
You should be good to go.
Using one of the older (re)partitioning methods did not affect the partition table too much.
The note about a stock partition layout is mainly for users who used a (re)partition script that adds a separate vendor partition.
Cheers.
Click to expand...
Click to collapse
Would you recommend any precautions like putting files like restock on my device before running your script as I cannot connect to PC?
Thanks a lot for your help!
hi, i need some help, after using this script i can't seem to install any rom, i just can't format or mount any of my partitions, and sideload stops at some random %, anything i can do to restore? i backed up all files advised.
Hello, i'm having trouble installing Android 12L on my Nexus 7. I simply cannot get lanchon-repit to flash. It wont work, no matter how often I follow the steps and how thorougly I follow the guide. I tried everything. Already restored to "fabric-partitions" so on and so forth.
I'm constantly getting Error 1. I'm slowly losing my mind here.
Kind regards hoping for an answer
septchy
edit: also constantly says partition #30 not found.
I'm getting the following errors on flo:
Code:
FATAL: partition #31 unexpected
[ERROR 1]
Any ideas? Thanks