[ROM][8.0][OpenKirin's AOSP - Treble - Oreo for Honor View 10] - Honor View 10 ROMs, Kernels, Recoveries, & Other D

{
"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"
}
* AOSP Oreo Project Treble For Honor View 10 by OpenKirin Team *
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About
There is a slightly AOSP customization adapted for our device Honor View 10
* stock Honor V10 EMUI Camera with the last "AR lens" feature
* FPS gestures
* Oreo Google Pixel Bootanimation
* Chrome Browser
* OmniClockOSS
* This ROM already included Nano Gapps
* Security Patch 1 February 2018
Downloads
* system_hv10_02.zip md5 : 896f9c0f5e7e2d056a7b08bfbdd944a0
* system_hv10_01.zip md5 : 28d0e7c049f2699803d7c41b622040b7
Installations
* first of all, make sure that you have already frp & bootloader unlocked
* second : you may want to backup system partition ( just check the second post )
* go to recovery and perform : "Wipe data/factory reset" & "Wipe cache partition"
* with USB cable connected, keep pressing volume down and check at the same time "Reboot system now"
* fastboot flash system system.img
* fastboot reboot
* Note : just extract system.img from previous system_hv10_02.zip !
Issues
* 3G & 2G always full signal
* you can play media files stored on external storage, only from Files manager
* SafetyNet still not pass
( we'll try to fix these issues on the next updates )
Warning
* Stock EMUI Camera is not 100% working - there are some features that still do not work !
* this cannot be a ROM issue, as any other third-party camera application it's working like expected
Credit
phhusson for his awesome work on Project Treble !
OldDroid
XePeleato
Special Thanks :
svetius
Screenshots
​
XDA:DevDB Information
AOSP, ROM for the Honor View 10
Contributors
surdu_petru, OldDroid, XePeleato, phhusson
Source Code: https://github.com/OpenKirin-Treble
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-02-18
Created 2018-02-18
Last Updated 2018-02-22

Backup system partition !
You may want to backup first system partition, if you want later to go back to stock EMUI.
Here are the steps :
- install Magisk to root your device
- connect usb cable and type into a command :
adb shell
su
dd if=/dev/block/bootdevice/by-name/system of=/storage/emulated/0/system.img
Click to expand...
Click to collapse
Copy system.img to your desktop :
adb pull storage/emulated/0/system.img
Click to expand...
Click to collapse
Whenever you want to go back to stock Emui , put your device in bootloader mode and type :
fastboot flash system system.img
Click to expand...
Click to collapse
It may require also a factory reset into recovery !
Sparse system image from BKL-L09 B130 (C432) : BKL-C432B130_system .img

*** reserved ***

Wow first AOSP ROM for this device
Many thanks Openkirin Team
Enviado desde mi BKL-L09 mediante Tapatalk

Awesome work mate. I've been refreshing this forum since the day I bought this device for any custom ROMs
---------- Post added at 07:23 PM ---------- Previous post was at 06:57 PM ----------
Could you please post a What's not working list please? Or is it the issues list you've mentioned?

shihabsoft said:
Awesome work mate. I've been refreshing this forum since the day I bought this device for any custom ROMs
---------- Post added at 07:23 PM ---------- Previous post was at 06:57 PM ----------
Could you please post a What's not working list please? Or is it the issues list you've mentioned?
Click to expand...
Click to collapse
Yes, the bugs was listed on the Issue section in OP ... if you find more bugs, please just let us to know

surdu_petru said:
Yes, the bugs was listed on the Issue section in OP ... if you find more bugs, please just let us to know
Click to expand...
Click to collapse
I'll surely try tomorrow.
Before that,
Is the face unlock working?
Is the fingerprint scanner based navigation working?

Fixed some microSD issues !
I just pushed a quick update in order to fix some external sdcard issue !
Patch fix .
Most likely it's a workaround and not a final fix, because we should update properly sdcardfs part into kernel - for a proper fix . This will be done in the next updates .
Huawei/Honor implemented their sdcardfs stuff into kernel and it's not 100% compatible AOSP .
Please use system.img from system_hv10_02.zip, and external sdcard issues will be fixed for moment !

Finally released ????.
Thanks to the devs..

surdu_petru said:
You may want to backup first system partition, if you want later to go back to stock EMUI.
Here are the steps :
- install Magisk to root your device
- connect usb cable and type into a command :
Copy system.img to your desktop :
Whenever you want to go back to stock Emui , put your device in bootloader mode and type :
It may require also a factory reset into recovery !
Click to expand...
Click to collapse
How much time it will take to copy system.img to root?
Its taking lot of time for me to copy img file to root. I granted root privileges to shell as well.

Apart from the known issues, everything is working flawlessly.
1)Face unlock working.
2)Fingerprint working.
3)Fingerprint scanner based navigation working (limited tho)
4)WiFi & Bluetooth working.
Issues
1)ADB not working, "Allow USB Debugging" alert not popping up, as the device stays unauthorized.
Tried killing the adb server, restarting the device. But it's not showing up.
Temporary Fix for unauthorized ADB
1)Go to C:\users\user_name\.android and copy the file adb_key.pub to your phone via MTP.
2)Enable developer options, and check Local Terminal in the list.
3)Open the terminal app from the app drawer.
4)Execute "stop adbd"
4) Copy adb_key.pub from your internal storage to /data/misc/adb/adb_keys.
Example - cp /sdcard/adb_key.pub /data/misc/adb/adb_keys
5)Execute "start adbd"
6)Now just do "adb kill-server" in the windows cmd and try listing the devices "adb devices".
That's it now will show up as authorized.
I've one request tho, please add options to enable/disable navigation bar and add utouch capabilities. I hate the on screen navigation bar
Will be updating this post as I encounter any issues.
Once again, thanks for the ROM

shihabsoft said:
Apart from the known issues, everything is working flawlessly.
1)Face unlock working.
2)Fingerprint working.
3)Fingerprint scanner based navigation working (limited tho)
4)WiFi & Bluetooth working.
Issues
1)ADB not working, "Allow USB Debugging" alert not popping up, as the device stays unauthorized.
Tried killing the adb server, restarting the device. But it's not showing up.
I've one request tho, please add options to enable/disable navigation bar and add utouch capabilities. I hate the on screen navigation bar
Will be updating this post as I encounter any issues.
Once again, thanks for the ROM
Click to expand...
Click to collapse
Yes, I already see it ... as soon as you install Magisk adb stop working.

surdu_petru said:
Yes, I already see it ... as soon as you install Magisk adb stop working.
Click to expand...
Click to collapse
I've followed your steps to take backup of system.img. But now I tried to flash it back it says "Invalid sparse file format at header magic" even though it eventually completes the flashing process. But the phone is now in bootloop, could you please help me out?
---------- Post added at 09:12 AM ---------- Previous post was at 08:44 AM ----------
surdu_petru said:
Yes, I already see it ... as soon as you install Magisk adb stop working.
Click to expand...
Click to collapse
Please upload the stock system.img if you have one, am kinda stuck now.
---------- Post added at 10:04 AM ---------- Previous post was at 09:12 AM ----------
Temporary Fix for unauthorized ADB
1)Go to C:\users\user_name\.android and copy the file adb_key.pub to your phone via MTP.
2)Enable developer options, and check Local Terminal in the list.
3)Open the terminal app from the app drawer.
4)Execute "stop adbd"
4) Copy adb_key.pub from your internal storage to /data/misc/adb/adb_keys.
Example - cp /sdcard/adb_key.pub /data/misc/adb/adb_keys
5)Execute "start adbd"
6)Now just do "adb kill-server" in the windows cmd and try listing the devices "adb devices" - it will show up as authorized.

shihabsoft said:
I've followed your steps to take backup of system.img. But now I tried to flash it back it says "Invalid sparse file format at header magic" even though it eventually completes the flashing process. But the phone is now in bootloop, could you please help me out?
---------- Post added at 09:12 AM ---------- Previous post was at 08:44 AM ----------
Please upload the stock system.img if you have one, am kinda stuck now.
---------- Post added at 10:04 AM ---------- Previous post was at 09:12 AM ----------
Temporary Fix for unauthorized ADB
1)Go to C:\users\user_name\.android and copy the file adb_key.pub to your phone via MTP.
2)Enable developer options, and check Local Terminal in the list.
3)Open the terminal app from the app drawer.
4)Execute "stop adbd"
4) Copy adb_key.pub from your internal storage to /data/misc/adb/adb_keys.
Example - cp /sdcard/adb_key.pub /data/misc/adb/adb_keys
5)Execute "start adbd"
6)Now just do "adb kill-server" in the windows cmd and try listing the devices "adb devices" - it will show up as authorized.
Click to expand...
Click to collapse
Please can you provide a screenshot from your desktop when you flash system.img via fastboot ?
Yes, I can provide you stock Emui B130 system.img for BKL-L09, today later.

hi guys i am new to honor and i got my device a week back can any one help me in detail how to flash this and i have indian version v10 and is the camera qualtiy same or bad?

surdu_petru said:
Please can you provide a screenshot from your desktop when you flash system.img via fastboot ?
Yes, I can provide you stock Emui B130 system.img for BKL-L09, today later.
Click to expand...
Click to collapse
Please check the attached screenshot.
That's what am getting, when I tried to flash the backup system.img of my device. Even though the flashing process finishes, but the device is stuck in a boot loop. The backup system.img file is around 5.50 gb.
Please do provide the stock system.img for BK-L09 (C675) BUILD.

shihabsoft said:
Please check the attached screenshot.
That's what am getting, when I tried to flash the backup system.img of my device. Even though the flashing process finishes, but the device is stuck in a boot loop. The backup system.img file is around 5.50 gb.
Please do provide the stock system.img for BK-L09 (C675) BUILD.
Click to expand...
Click to collapse
OK, thanks ... Does you already tried a data/factory reset in recovery ? Its already stated on the second post.

surdu_petru said:
Please can you provide a screenshot from your desktop when you flash system.img via fastboot ?
Yes, I can provide you stock Emui B130 system.img for BKL-L09, today later.
Click to expand...
Click to collapse
Thanks for providing stock system.img. Could you please add the download link to first post?

alohahe3000 said:
Thanks for providing stock system.img. Could you please add the download link to first post?
Click to expand...
Click to collapse
Yes sure, but a bit later ... BTW it should work also with your backup of system.img and after flash it via fastboot just force device to go to recovery and perform a data/factory reset and cache as well .

surdu_petru said:
OK, thanks ... Does you already tried a data/factory reset in recovery ? Its already stated on the second post.
Click to expand...
Click to collapse
I've done a factory reset. Then, rebooted to boot loader and flashed the backup system.img, and rebooted the device. Since then, the device is in a boot loop. If possible, please upload the stock system.img ASAP

Related

[Toolkit] Mac OS X Toolkit for unlocking, flashing, rooting

Hello everyone!
Since there was such a demand for a OS X Toolkit, I've made one. It's quite simple and is made in Bash. It should work on all OS X versions.
It has been downloaded over 700 times on MediaFire alone and has been tested by several members, including myself.
Requirements:
* OS X
* A OnePlus One
* Cable to connect to your Mac (needs to be able to transfer data, if one cable doesn't work try another!).
That's it.
What it can do:
* Instructions to enable USB Debugging.
* Unlock or lock the bootloader of your OnePlus One
* Flash a custom recovery or the stock recovery (TWRP, CWM, PhilZ, Stock)
* Can root the OnePlus One (SuperSU)
* Reflash the entire device back to stock
* Install ADB and Fastboot to your Mac for manual use
* Do some basic ADB/Fastboot commands like rebooting, checking bootloader status and sideloading.
* Remove the tamper bit.
It's all one application that you need to run. It's quite simple and I've tried to make it as user friendly as possible. Hopefully it'll work for you. If it doesn't, please post in the thread and I'll probably take a look, same goes for bugs or such things.
Please remember that it must not be renamed, otherwise it won't work.
Thanks to the creators of the recoveries and Chainfire for SuperSU. Those are the real devs.
The source is available inside the application in Contents/Resources/Scripts, it doesn't have any comments or anything, but should be so straight forward that reading it shouldn't be a problem.
Enjoy!
Downloads:
Mega
MediaFire
Changelog:
Ver. 1.2.8
- Updated stock image to XNPH38R.
- Updated the stock recovery to XNPH38R's recovery.
- Added an experimental way to restore the old blue lockscreen.
Ver. 1.2.6
- Updated the TWRP image 2.8.0.1
- Updated SuperSU binary to 2.02.
- Removed unnecessary(?) reboot command at the end of the bootloader unlock menu.
- Updated the "reflash back to stock" image to XNPH33R.
Ver 1.2.4
- Updated the TWRP image to 2.7.1.1.
Ver. 1.2.3
- Made it clear that booting custom recoveries without unlocking the bootloader is impossible in OTA 30O or later.
- Made the DMG automatically open after mounting.
- Changed the wget binary to another one. The previous wget was likely built with my personal OpenSSL setup from Homebrew and was thus not compatible with everyone.
- Small fixes
Ver. 1.2.1
- Big bug fix to rooting without installing a bootloader (rebooted you previously into recovery when it was supposed to reboot you into fastboot). Thanks to Nandmp for finding that one.
- Removed the "You need an unlocked bootloader to root" information in the rooting menu.
- Removed a few sudos that weren't necessary.
- Minor fixes here and there.
Ver. 1.2
- Added a way to lock the bootloader.
- Added a special way to unlock a relocked bootloader without wiping the phone. It can also remove the tamper bit! See the devs' thread for more information.:
- Made it possible to root the phone without installing a custom recovery.
- Made it easier to reflash back to stock. It now downloads and the factory image automatically in a designated folder.
- Added locking in the basic adb/fastboot commands.
- Added reflashing the stock image by using a manually downloaded factory image in the basic commands.
- Loads of fixes here and there.
Ver. 1.15
- Fixed critical bug in reflashing back to stock for 64GB devices (thanks to @X10D3 for finding this one)
- Added experimental "boot to any custom recovery without installing it" to the basic fastboot commands.
Ver. 1.1
- It can now be run from anywhere!
- Added new custom logo and DMG style
- Problem where some people couldn't open the application due to multiple terminals should be fixed now.
- Fixed compression issue. It's now around 45MB again.
Ver. 1.05:
- Added a way to check the current lock status of the bootloader in the basic commands center.
- Small changes to the instructions when unlocking the bootloader.
- Reshuffled Installing ADB/Fastboot and some basic commands.
- Made some small changes to the basic commands menu to make it a little neater and easier to use with some extra instructions for certain commands.
Ver. 1.02:
- Removed warranty disclaimer since OnePlus does actually not invalidate your warranty by unlocking.
- Included further important steps to flash a custom recovery.
- Added the ability to install ADB and Fastboot into the system for manual use in the terminal.
- Added some basic commands you can do without installing ADB/Fastboot to the system like rebooting.
- Added version to About.
- Updated screenshot below.
Ver. 1.00:
-Initial release.
OnePlus thread
Here's a screenshot:
{
"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"
}
Thank you!!
Warranty will NOT be void Anyway thanks, hoping someone will try it
blak24 said:
Warranty will NOT be void Anyway thanks, hoping someone will try it
Click to expand...
Click to collapse
Really? That's very interesting. Got a source on that? If so I'll remove the disclaimer from it in the next version if someone finds bugs or similar problems.
Well OnePlus always stated that rooting the phone will not void phone's warranty
Consistant said:
Really? That's very interesting. Got a source on that? If so I'll remove the disclaimer from it in the next version if someone finds bugs or similar problems.
Click to expand...
Click to collapse
Yeah, I just Googled it and it seems indeed like the warranty isn't voided by unlocking the bootloader. That's a first, props to OnePlus for doing that.
And thanks to you for pointing out! I'll make sure to get that fixed once someone has properly tested it in case it needs additional changes.
When I run the toolkit, this happens?
---------- Post added at 11:35 AM ---------- Previous post was at 11:18 AM ----------
joeg6217 said:
When I run the toolkit, this happens?
Click to expand...
Click to collapse
Seems to have sorted itself out. It's now working
When flashing a recovery:
ERROR: could not get pipe properties
rebooting...
Just posting for FYI.
I've used a few different toolkits for a variety of phones.
This was the best and easiest I've used yet.
Everything worked perfectly.
Brilliant
:good:
in my Mac won't start (mavericks )....
---------- Post added at 09:14 PM ---------- Previous post was at 09:08 PM ----------
only a corrupted downloaded file. noow work on my maverick's imac, sorry
Thank you!
Sent from my One using XDA Premium 4 mobile app
Consistant said:
Hello everyone!
Since there was such a demand for a OS X Toolkit, I've made one. It's quite simple and is made in Bash. It should work on all OS X versions.
It is under testing by several members, but I cannot test it personally due to not having One. I've gone through it many times now, checked that ADB and Fastboot works on two OS X computers and it should work perfectly fine, but at least keep it in mind.
Requirements:
* OS X
* A OnePlus One
* Cable to connect to your Mac (needs to be able to transfer data, if one cable doesn't work try another!).
That's it.
What it can do:
* Instructions to enable USB Debugging.
* Unlock the bootloader of your OnePlus One
* Flash a custom recovery or the stock recovery (TWRP, CWM, PhilZ, Stock)
* Can root the OnePlus One (SuperSU)
* Reflash the entire device back to stock
* Install ADB and Fastboot to your Mac for manual use
* Do some basic ADB/Fastboot commands like rebooting, checking bootloader status and sideloading.
It's all one application that you need to run. It's quite simple and I've tried to make it as user friendly as possible. Hopefully it'll work for you. If it doesn't, please post in the thread and I'll probably take a look, same goes for bugs or such things.
Please remember that it must not be renamed, otherwise it won't work.
Thanks to the creators of the recoveries and Chainfire for SuperSU. Those are the real devs.
The source is available inside the application in Contents/Resources/Scripts, it doesn't have any comments or anything, but should be so straight forward that reading it shouldn't be a problem.
Enjoy!
Downloads:
Mega
MediaFire
Changelog:
Ver 1.1
- It can now be run from anywhere!
- Added new custom logo and DMG style
- Problem where some people couldn't open the application due to multiple terminals should be fixed now.
- Fixed compression issue. It's now around 45MB again.
Ver 1.05:
- Added a way to check the current lock status of the bootloader in the basic commands center.
- Small changes to the instructions when unlocking the bootloader.
- Reshuffled Installing ADB/Fastboot and some basic commands.
- Made some small changes to the basic commands menu to make it a little neater and easier to use with some extra instructions for certain commands.
Ver 1.02:
- Removed warranty disclaimer since OnePlus does actually not invalidate your warranty by unlocking.
- Included further important steps to flash a custom recovery.
- Added the ability to install ADB and Fastboot into the system for manual use in the terminal.
- Added some basic commands you can do without installing ADB/Fastboot to the system like rebooting.
- Added version to About.
- Updated screenshot below.
Ver 1.00:
-Initial release.
OnePlus thread
Here's a screenshot:
Click to expand...
Click to collapse
I'm trying to unlock my boot loader, but thing is popping up.
Make sure your phone is inside Android, is connected to your Mac and has
USB Debugging enabled.
After continuing you need to authorize your computer by looking at your phone and tell it to 'Always allow' your computer.
Press any key to continue...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
sharp2G said:
I'm trying to unlock my boot loader, but thing is popping up.
Make sure your phone is inside Android, is connected to your Mac and has
USB Debugging enabled.
After continuing you need to authorize your computer by looking at your phone and tell it to 'Always allow' your computer.
Press any key to continue...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
Yes, that's ADB starting up it's server as usual. Keep waiting (it looks for your device) for a minute or two. If nothing happens try using the "See all devices connected" in the "basic adb and fastboot commands" menu. If you need to keep waiting forever or it says "No devices" then you need to try with another USB cable as that one might not have data transfer capabilities.
Remember as the instructions tell you, you need to enable USB Debugging and you need to be inside Android (like on the homescreen or something).
Consistant said:
Yes, that's ADB starting up it's server as usual. Keep waiting (it looks for your device) for a minute or two. If nothing happens try using the "See all devices connected" in the "basic adb and fastboot commands" menu. If you need to keep waiting forever or it says "No devices" then you need to try with another USB cable as that one might not have data transfer capabilities.
Remember as the instructions tell you, you need to enable USB Debugging and you need to be inside Android (like on the homescreen or something).
Click to expand...
Click to collapse
I've managed to get root access thanks to your application for Mac! THANK-YOU!
Huge bug when flashing to stock. It's flashing userdata instead of userdata_64G. userdata_64G has to be used when you're flashing the 64gb variant. A work around is to delete the userdata file and rename userdata_64G to userdata. then run the install script. You may modify your app so that it asks if you have the 16 or 64 then load the install script associated with the size.
Worked great! Thank you!
X10D3 said:
Huge bug when flashing to stock. It's flashing userdata instead of userdata_64G. userdata_64G has to be used when you're flashing the 64gb variant. A work around is to delete the userdata file and rename userdata_64G to userdata. then run the install script. You may modify your app so that it asks if you have the 16 or 64 then load the install script associated with the size.
Click to expand...
Click to collapse
Thank you so much for pointing this out, that's an extremely ugly bug that can cause problems. I'll make sure to get that fixed as fast as I can by adding a simple prompt asking for the version.
Consistant said:
Thank you so much for pointing this out, that's an extremely ugly bug that can cause problems. I'll make sure to get that fixed as fast as I can by adding a simple prompt asking for the version.
Click to expand...
Click to collapse
Awesome. Thanks for the update.
this should be added to the tool/utilities section great work man, saw this on the oneplus forum too :good::good::good::good::good::good::good:
I have a question. We need to download anything else like sdk, drivers or just the tool kit? I have see that adb drivers and fastboot can be installed from the tool kit. Thats all?
Thanks.

[RECOVERY] [ISOREC] [TWRP 3.0.2-1] [OFFICIAL] [26/04/2016]

{
"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"
}
Disclaimer​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Features​
Code:
. Completely new theme
. True Terminal Emulator
. Language translation
. Flashing of sparse images
. Adopted storage support for select devices
. Reworked graphics to bring us more up to date with AOSP
. SuperSU prompt will no longer display if a Marshmallow ROM is installed
. Update exfat, exfat fuse, dosfstools
. Update AOSP base to 6.0
. A huge laundry list of other minor fixes and tweaks
Installation instructions
Code:
[U]Flash via Recovery[/U]
. Download the TWRP zip file from the Downloads section
. Flash using CM/TWRP recovery
. Kernel must be IsoRec compatible
. What is IsoRec? Please visit [URL="http://forum.xda-developers.com/galaxy-s2/orig-development/isorec-isolated-recovery-galaxy-s2-t3291176"][U]here[/U][/URL]
Code:
[U]Flash via HeimdallSuite (Windows only)[/U]
. Download [URL="http://forum.xda-developers.com/attachment.php?attachmentid=3713767&d=1460278689"][U]HeimdallSuite[/U][/URL] & [URL="http://forum.xda-developers.com/attachment.php?attachmentid=3713769&d=1460278744"][U]Samsung USB Drivers[/U][/URL]
. Install Samsung USB Drivers
. Connect the phone in Download mode (Vol. Down + Home + Power)
. Go to Heimdall Suite/Drivers & open 'zadig' (Run in admin mode)
. Select 'List All Devices' under 'Options'
. Select 'Gadget Serial' & 'libusb0 (v1.2.5.0)' from the drop menu & scroll menu respectively
. Click on Install/Replace Driver
. Close 'zadig'
. Reboot again into Download mode
. Open 'heimdall-frontend'
. Select 'Utilities' tab & click on 'Detect' under 'Detect Device' option
. Make sure the 'Output' window says 'Device Detected'
. Scroll down to 'Download PIT' section & click on 'Save As...' under 'Destination File'
. Type any name under 'Name:' and select 'Save'. Do not give any filename extensions
. Click on 'Download'
. Reboot again into Download mode
. Select 'Flash' tab
. Load the downloaded pit under 'PIT'. Do not select 'Repartition' checkbox
. Click the 'Add' button under 'Partitions (Files)'
. Select 'RECOVERY' from the drop down menu in 'Partition Name' under 'Partition Details'. Make sure 'Partition ID' reads 7
. Download the latest TWRP image from the official website
. Load the img image under 'File'
. Now click on 'Start'
. The image will get flashed in '/dev/block/mmcblk0p6' partition under mountpoint '/recovery'
. Device will automatically restart when flashing is complete
Code:
[U]Update via Recovery[/U]
. Download latest TWRP image from the official website
. Boot into TWRP and from 'Install' select 'Install Image'
. Select the downloaded img image file
. Select 'Recovery' under the Partition selection menu
. Swipe to start the Flash
. Reboot again into recovery to use the new updated TWRP
Changelog​
Code:
[U]26/04/2016[/U]
. Updated TWRP sources
. Fixed labeling of storage
. Fixed fsck.f2fs generation
. Added USB OTG support
. Removed many depreciated flags(TWRP tree cleanup)
Bugs​
Code:
None
Downloads
#include <recovery.dl>​
Video Review
Join the TWRP Community for the latest updates
​
XDA:DevDB Information
TWRP, Tool/Utility for the i9100
Contributors
arnab, Dees_Troy, Lanchon
Source Code: https://github.com/TeamWin/android_device_samsung_i9100
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-04-26
Created 2016-03-07
Last Updated 2016-04-27
Themes
TWRP Themes Folder
TWRP Themes by @G.M.L​
A huge thanks to @Lanchon who let me use his script.
:So the wait is over now...Thanks a lot for new TWRP
thanks @arnab
Skyline said:
:So the wait is over now...Thanks a lot for new TWRP
Click to expand...
Click to collapse
Plz use the disable isorec to clear the existing twrp recovery if coming frm a previous isorec recovery. After then install.
Sent from my MI 3W using XDA Free mobile app
arnab said:
Plz use the disable isorec to clear the existing twrp recovery if coming frm a previous isorec recovery. After then install.
Sent from my MI 3W using XDA Free mobile app
Click to expand...
Click to collapse
Why is this needed? I have just installed it over previous isorec recovery and all is fine.
arnab said:
Plz use the disable isorec to clear the existing twrp recovery if coming frm a previous isorec recovery. After then install.
Sent from my MI 3W using XDA Free mobile app
Click to expand...
Click to collapse
It also work for me without disabling isorec I am on Doorimanx B031 + cm12.1 by markox8. Is there any serious Problem with it?
Hi, @arnab! I got error 255 when i try format cache in f2fs. If i format manualy and try wipe cache, i got error too.
SaZoN said:
Hi, @arnab! I got error 255 when i try format cache in f2fs. If i format manualy and try wipe cache, i got error too.
Click to expand...
Click to collapse
I have this same issue...its not twrp fault.. Only the cache throws the the error... I think its bcoz if the external/f2fs-tools repo... Here the mkfs.f2fs gets compiled...i tried to use the cm repo but it wont even compile... I had to use the omni repo.
Soln:- Install cm... Go to cm recovery... Type adb shell on pc... Then format it frm there... Mkfs.f2fs /dev/block/mmcblk0p7....when u come back to twrp.. Frm settings just use rm-rf for the cache partition... I already forwarded this problem to twrp lead developers.
Sent from my MI 3W using XDA Free mobile app
So....
Does this new version have OTG support?
I get tired of having to break out the terminal in TWRP everytime i want to flash a ROM from my USB key with ROMs on
And if it doesnt, why, because CWM has had OTG out of the box forever
p.s. I may have a pathological hatred of TWRP
Don't know why , but it doesn't work for me , if I flash it then reboot I get stuck on samsung logo
Sent from my GT-I9100
Iam requesting this to every one...Plz plz plz if u find any problem...report it to the Bugs section.
Just to echo it here (as I used the bug-report for that) and as it might prevent some people from running into problems later:
@arnab
not a bug, but maybe you should also name the zip to reflect it is an IsoRec recovery (e.g. recovery-IsoRec-TWRP_i9100_3.0.0-0) ? Just to make sure there is no confusion about that.
beautiful
Thank you
works good and thanks for this update
@Troubadour666 Can you come up with some themes for our device resolution ???
Themes
Deleted
Deleted
Any one with theme experience, plz contact me in private. I don't know any RT here.

[Q][GSI][A/AB][arm64] Android Q Developer Preview

EXPERIMENTAL AND MOST LIKELY BROKEN
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Android "Q" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 2019, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
[more stable] Pixel: Ported from Pixel 2 firmware (walleye)
Generic: Ported from Google GSI with gapps
GET UPDATES FROM: https://t.me/androidqgsi​
Requirements :
Treblized device with 8.1 or P vendor
Global Bugs :
VoLTE
Device specific Bugs :
...
Instructions :
for A-Only :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Flash FixZygote.zip
Reboot
for AB :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Reboot
Downloads :
Q Developer Preview
Notes :
Fix gapps: install google play services with "adb install"
if images didn't worked properly post your logs(logcat and console-ramoops) on telegram group i'll come for help : @androidqgsi
Logcat without PC: take /data/local/tmp/logs/log
Enable adb before boot using this command in TWRP:
Linux/mac :
Code:
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Win :
Code:
adb push C:\Users\<userName>\.android\adbkey.pub /data/misc/adb/adb_keys
Donate:
My paypal: https://www.paypal.me/erfanoabdi
Tested on:
give me logs if didn't worked, or donate me a device
Tested by myself:
Moto Z (A-only)
Moto X4 (AB)
Thanks
ENJOY!​
[DEV-ONLY] Bug Fixing
NVM
Ah actually this is ridiculous to have bug fixing post here, and i hate my port, real P GSI shouldn't done like this. but anyway this is ported from closed source P and i can point in most popular fixable bugs here...​
by looking into logs(adb logcat -b all) if we see :
1) library "libxxxxxxxxx.so" not found
fix of this error is very simple as you guys all know we just need to put needed lib from system image of base rom in https://github.com/erfanoabdi/P_sem...GSI_Patches/Vendor/P Blobs/POST-sGSI_1/vendor
and zip up "POST sGSI 1" with new libs
Feel free to make pull request new libs in github
2) cannot locate symbol :
for example LG RIL error was like this:
Code:
CANNOT LINK EXECUTABLE "/vendor/bin/hw/rild": cannot locate symbol "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE" referenced by "/vendor/lib64/[email protected]"...
a) here we need to find where is unknown symbol located in 8.1 system image
so in terminal goto system/ and :
Code:
grep -r "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE"
output in this case is :
Code:
Binary file lib/[email protected] matches
Binary file lib64/[email protected] matches
(here you may get long list of blobs, only find and grab needed ones)
b) now just copy libs to vendor and rename them
in this case i renamed [email protected] to [email protected]
***important rule keep string name same as original file only replace one letter (a->W)***
c) and sed renamed lib (in my case) :
Code:
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib/[email protected]"
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib64/[email protected]"
we're almost done here
d) now open POST-sGSI_2 and sed "referenced by" lib from error line in log
like this : https://github.com/erfanoabdi/P_sem...ETA-INF/com/google/android/update-binary#L154
e) and zip up "POST sGSI 1/2" with new libs
Feel free to make pull request new libs/hax in github
3) more...
NVM
WIKI : https://github.com/erfanoabdi/P_semiGSI/wiki
i hope we get a full GSI eventually one P is released, been waiting a while for this. at least now its semi done, it should be easier to create a full GSI for kirin (aka my H9) and MTK devices.
Hi, will it support Honor9?
I'm waiting for kirin chipset supported gsi
Dumpling- Needs mokee vendor
waiting support kirin960 and more?
Sent from my Honor V9 using XDA Labs
Jamie_oppo said:
Do you need to be a on a treble rom before flashing this?
Ive got a 5t (dumpling) and flashed the open beta which gave treble. Then flashed a normal custom rom. I tried all the zip at this point and no luck decrypted.
Click to expand...
Click to collapse
Same phone here, I flashed the rom, but it reboots every time to the bootloader...
ChristiaanP said:
Same phone here, I flashed the rom, but it reboots every time to the bootloader...
Click to expand...
Click to collapse
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots.
Jamie_oppo said:
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots
Click to expand...
Click to collapse
I was on OB 11
Awesome... btw Currently booting phones
Mi 5 (gemini)
Redmi 4 Prime (markw)
Redmi 4x (santoni)
Redmi 3s/3x/Prime (land)
Zuk Z2 Plus (z2_plus)
Redmi Note 4 sd (mido) (Tested on PE and Lineage-ex vendors)
Lenovo P2 (kunato)
Redmi Note 5 Pro (whyred) (With mokee vendor)
Mi 6 (sagit) LG V30 (h930)
Redmi 5 Plus (vince) (Tested with cardinal-aosp vendor)
Exynos S9+ (Unstable as **** as its not QCOM)
Redmi 4A (rolex) (crDroid Treble)
OnePlus 5/T (Only one user has reported it to work with proof though)(Mokee trees)
Bugs for land or all devices!
- half volte is working (only outgoing call and volume for jio left to fix)
- app opening time is extra
None volte users r really lucky
Also jio4gvoice app is not working
Update for DP5
THE MEGAPOST OF NOTES FOR THE P GSI HERE
Wiki page: https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5T and https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5 (Thanks to timocapa)
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
Some things to take into consideration before I followed these steps: I was using OB11 as my daily driver since it's release and I have always been encrypted.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install the latest BETA version of Mqgisk
Click to expand...
Click to collapse
Alternative instructions if you are getting kicked back into the recovery with the display log saying "RescueParty", do all of the above but replace step 11 with the steps below (Thanks to @jelousdogs for his method):
11) Flash POST Zip 1,2 (Dont flash zip 3 Yet)
12) Reboot to system (You will see the rom booting and reboot to recovery suddenly)
13) Flash POST zip 3 in recovery and reboot to system
If this STILL does not work, try this: After completing all of these steps, mount vendor partition in TWRP, then use the TWRP File Manager. Copy the build.prop file from the vendor partition to your internal storage (/sdcard) and move it to your PC via MTP in recovery. Add "persist.sys.disable_rescue=true" (without quotes) to the bottom of the build.prop file you have just copied to your PC. Save and transfer it back to your internal storage. Copy the build.prop from your internal storage to /vendor, replacing the original file. Press on the build.prop file in your /vendor partition and press "chmod". Remove all of the "0000" numbers in the text box and type "0600", then confirm the chmod. Reboot to the OS.
Click to expand...
Click to collapse
DIRTY FLASHING DP5 FROM DP4 (Thanks to timocapa):
1) reboot into TWRP and flash the DP5 GSI.
2) reboot into the OS.
Simple as that.
Click to expand...
Click to collapse
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON (Your stock launcher must be working, i.e. not Force Closing, in order for this to work because the new overview app switcher is part of the stock Pixel Launcher).
- Weird software issues like apps not opening, random FCs, settings going blank? Try a factory reset in TWRP and reboot to see if it has fixed any problems!
Click to expand...
Click to collapse
Known bugs confirmed by a number of 5/t users:
- Potato quality camera, you can use GCam to remedy the problem but expect blue dots in HDRmode (OnePlus problem)
- Front facing camera can only be used in OOS camera (wait for official sources)
Click to expand...
Click to collapse
To get rid of the three persistent notifications:
1) install GMS update (https://www.apkmirror.com/apk/googl...2-8-72-100400-202717283-android-apk-download/)
2) Tap on the blue finishing setup notification and connect to wifi, then force close the pixel setup so it re-appears again
3) Go to settings > accounts > sign into google
4) Tap on the blue notification again and you should be able to go further than "pixel is finishing setup" page.
5) Force stop play store to remove the play store persistent notification
Click to expand...
Click to collapse
Hope this helps other OP5/5T users out there who are having trouble booting this.
Can someone tell me if boot this rom on mi mix2s It is able for treble rom i tryied to flash but doesnt boot.
Reserved for review
Boots
Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?
unrealmac said:
Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?
Click to expand...
Click to collapse
No
ZeroInfinity said:
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly July 15th is what I used)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) install in-call audio fix
13) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install magisk. I recommend this version as it was the only one working for me: https://drive.google.com/open?id=10LV_j43YUmmHNe0PjE_GNo9kkb-1gAnD
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- If you get kicked into recovery and TWRP's display log shows something about RescueParty, flash the POST 3 zip again and rebooting. You might want to try this 2-3 times if it did not work the first time.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON
Bugs that I have encountered personally but may not affect you, need confirmation:
- MTP isn't working, even with the workaround.
- ADB is detected but when doing "adb devices", it will stay on the "connected" status so you can't issue any adb commands via PC.
- Fingerprint not even detected, no option to enrol in security settings.
To get rid of the three persistent notifications:
1) force stop pixel setup in app settings
2) install GMS update (https://apkdot.com/apk/google-llc/g...s-12-8-66-100400-200774163-beta-041/download)
3) when the blue notification appears again, open it and connect to wifi
4) force stop pixel setup again
5) the next time the notification appears, it should allow you to finally finish the setup
Hope this helps other OP5/5T users out there who are having trouble booting this.
Click to expand...
Click to collapse
Thanks! It worked!

[Xiaomi Mi Pad 4] Android Generic System Image installation Guide

I started a little Android Generic System Image installation Guide on my Github :
https://github.com/GBouerat/xiaomi_mi_pad_4
(work in progress)
https://github.com/GBouerat/xiaomi_mi_pad_4/tree/master/TWRP
Code:
fastboot oem device-infov
Is it really device-infov or is it typo.
P.Kosunen said:
https://github.com/GBouerat/xiaomi_mi_pad_4/tree/master/TWRP
Code:
fastboot oem device-infov
Is it really device-infov or is it typo.
Click to expand...
Click to collapse
It's a typo, thanks
Code:
fastboot oem device-info
Thank you very much, mate! Can we expect to see an official TWRP release as well as LineageOS 15.1?
PS: Does Android P GIS work well? Are there any known issues so far?
Please do include the build.prop tweaks mentioned here - those are quite necessary for the device to function as a tablet.
cRaZy-bisCuiT said:
PS: Does Android P GIS work well? Are there any known issues so far?
Click to expand...
Click to collapse
None of those P GSIs boot.
Anyone able to root using Magisk on v9.6.23 boot.img (http://en.miui.com/thread-3538488-1-1.html)? Magisk patched boot.img doesn't seems to boot for me and I have to revert to stock boot.img.
Edit: hah, never mind. I forgot to disable forceencrypt when i flashed the new stock kernel and it encrypted data. Had to wipe data and unencrypt to root again.
Magisk on GSI is incompatible with adb usb debug mode, no ?
GBouerat said:
Magisk on GSI is incompatible with adb usb debug mode, no ?
Click to expand...
Click to collapse
works fine for me
Hi
Could You please write with recovery version is this? There are 2 recovery versions as of 2018.7.13 and 2018.7.11 with description like bellow:
2018.7.13 update
1. Fix the problem of not recognizing the external memory card.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
2018.7.11 update:
1. Update the attempt to repair the decrypted data, and expect whether the follow-up can reach the expected.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
---------- Post added at 11:42 AM ---------- Previous post was at 11:12 AM ----------
I booted my pad with Your recovery and I can't see external SD card, so I expect that is the 2018.7.11 version. Am I right?
Hi again.
I found on another forum recovery that supports external sd-card. It's: recovery-TWRP-3.2.2-0713-MIPAD4-RuEn-Kirhe.img and it's working fine on my mi pad 4
{
"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"
}
bartekm01 said:
Hi again.
I found on another forum recovery that supports external sd-card. It's: recovery-TWRP-3.2.2-0713-MIPAD4-RuEn-Kirhe.img and it's working fine on my mi pad 4
Click to expand...
Click to collapse
Hallo
Where did you find this TWRP?
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
bartekm01 said:
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
Click to expand...
Click to collapse
Tanks!!
Encryption
bartekm01 said:
Hi
Could You please write with recovery version is this? There are 2 recovery versions as of 2018.7.13 and 2018.7.11 with description like bellow:
2018.7.13 update
1. Fix the problem of not recognizing the external memory card.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
2018.7.11 update:
1. Update the attempt to repair the decrypted data, and expect whether the follow-up can reach the expected.
2. After brushing in twrp, the first time you enter twrp, it may restart once. This is normal. If you restart repeatedly, or you cannot decrypt the data, please give me feedback in time.
---------- Post added at 11:42 AM ---------- Previous post was at 11:12 AM ----------
I booted my pad with Your recovery and I can't see external SD card, so I expect that is the 2018.7.11 version. Am I right?
Click to expand...
Click to collapse
Hi,
Were you able to encrypt your Mi Pad after flashing the GSI?
jonklinger said:
Hi,
Were you able to encrypt your Mi Pad after flashing the GSI?
Click to expand...
Click to collapse
I didn't install gsi
Hi !
What's the difference between ab version and aonly version ?
EDIT: I flash today Android Pie GSI version.
After flashing GSI, you can found Open GAPPS unofficial here: https://builds.nezorfla.me/?dir=opengapps/pie/arm64
For no error 70, before flashing Open GAPPS, you must do that: Wipe -> Advanced Wipe -> Select System -> Repair or Change File System -> Resize File System -> Swipe to Resize
After, you can flash Open GAPPS, Magisk (for root) and Dm-Verity, and finally reboot
bartekm01 said:
I found it on 4pda. Link to download
https://drive.google.com/file/d/1CaX9pkdBcOZFMlxwQdOC2TPeknQGJHNZ/view?usp=drivesdk
Click to expand...
Click to collapse
Have you also flashed the misc file together with the TWRP? Or in this version there is no need?
snke said:
Have you also flashed the misc file together with the TWRP? Or in this version there is no need?
Click to expand...
Click to collapse
No only TWRP. I didn't flash misc - I think that misc changing region but I did not found any information about it.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
arkansis said:
Hi !
What's the difference between ab version and aonly version ?
EDIT: I flash today Android Pie GSI version.
After flashing GSI, you can found Open GAPPS unofficial here: https://builds.nezorfla.me/?dir=opengapps/pie/arm64
For no error 70, before flashing Open GAPPS, you must do that: Wipe -> Advanced Wipe -> Select System -> Repair or Change File System -> Resize File System -> Swipe to Resize
After, you can flash Open GAPPS, Magisk (for root) and Dm-Verity, and finally reboot
Click to expand...
Click to collapse
MiPad4 is only a partition. There is no b partition for seamless updates.
So far I didn't install any GSI but I've have installed China stable, developer and xiaomi.eu roms and I didn't have to resize system partitions. An ROMs are bigger maybe that's why You need to extend partitions but installation should end with error because of lack "b" partition
AICP 8.1 GSI works fine.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-t3839168
dzidexx said:
AICP 8.1 GSI works fine.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/8-1-0-t3839168
Click to expand...
Click to collapse
I'm agree, in my opinion It's the best GSI rom for MP4.

[RECOVERY][UNOFFICAL] TWRP 3.3.1-0 [8.1][SM-T595]

Closed Per OP Request
{
"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"
}
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
*/
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Downloads:
TWRP 3.3.x
Please Install Via Odin!
Disabling Force Encryption(Highly recommended)
This process involves wiping your data
- flash twrp on your current rom
- Click Wipe and then click format data(Wipes your /sdcard as well)
- Go to download mode and flash stock
- Make sure to to not let it boot and reboot to download mode again(Power + Vol Up + Vol Down + USB cable)
- Flash TWRP again and boot to recovery(Power + Vol Up + USB Cable)
- Flash RootFix (Optional, for magisk) - https://drive.google.com/file/d/19C9byrqlw_TGo-Nfm4Z-WcT6yB6sM2oP
- Flash DM-Verity and Force Encryption Disabler - https://zackptg5.com/android.php#disverfe
- Boot to stock
Flash Magisk if you want
PS: Only tested on T595XXU3ASC1
Bugs:
Encryption
MTP
Must Click "Disable MTP" to make ADB work
Brightness cannot be changed
you tell me
Device Sources:
Device Tree
Kernel Tree
XDA:DevDB Information
TWRP SM-T595, Tool/Utility for the Samsung Galaxy Tab A series
Contributors
rupanshji
Source Code: https://github.com/minimal-manifest-twrp
Version Information
Status: Alpha
Created 2019-08-06
Last Updated 2019-08-08
Reserved
Changelog
07-Aug-19
Code:
Fix Mouse Cursor Bug
Fix Flashing of files
Remove useless stuff
06-Aug-19
Code:
Initial Build
I will be working on building lineage very soon as well. However I don't have enough data to download 4-5 builds everyday.
All those willing to test or just discussing the development in general can join my telegram group - https://t.me/smt595
INTERESTING!!
At the moment Odin freezes while I try to load the recovery image. (Odin 3.13, ROM T595XXU3BSF3)
Supercoach1970 said:
INTERESTING!!
At the moment Odin freezes while I try to load the recovery image. (Odin 3.13, ROM T595XXU3BSF3)
Click to expand...
Click to collapse
oof my bad i uploaded the whole folder instead of a file
EDIT: Link fixed!
Great work Rupanshji!! It works on my SM-T595. THANKS!!!
Not so quick, it does not work on mine. When I flash twrp in odin it tells me that it is unverified package on tablet and odin says failed. Anyway, could anyone share a patched bootloader? I have the latest rom ...... June.
vq8acsxht said:
Not so quick, it does not work on mine. When I flash twrp in odin it tells me that it is unverified package on tablet and odin says failed. Anyway, could anyone share a patched bootloader? I have the latest rom ...... June.
Click to expand...
Click to collapse
Unlock your bootloader m8
rupanshji said:
Unlock your bootloader m8
Click to expand...
Click to collapse
No the bootloader was unlocked. I finally was able to flash twrp. You missed a step though:
0) Reflash all the OEM First before flashing TWRP
Just a heads up to anyone else....
If you get this message in red text:
"Only official released binaries are allowed to be flashed"
or this message in a blue screen of death:
"Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost."
Congradulations! You just tripped SAMSUNG'S SECURITY APE! You just won..... more flashing.... :silly:
Just reflash "ALL OF THE STOCK FIRMWARE." The BL + AP + CP + CSC to fix it and put the ape back into the cage.
Here is the command to push a file to the SD card with ADB:
adb push Disable_DM-Verity.zip /sdcard/Disable_DM-Verity.zip
Thanks rupanshji !!!! Hope you get encryption working soon and LOS.
If you could also make it compatible with the SM-T597, that would be nice
Hi rupanshji. Any news on lineage? I'm really impressed with the specs of the tablet and confused why there is almost zero efforts to get any custom roms ready for that device.
Just to let everyone know. LOS is still being worked on. His laptop is in repair so he has to get it back. If you have the 595 tablet PLEASE JOIN THE TELEGRAM GROUP so you know what is going on.
rupanshji
All those willing to test or just discussing the development in general can join my telegram group - https://t.me/smt595
Click to expand...
Click to collapse
dezzo77 said:
If you could also make it compatible with the SM-T597, that would be nice
Click to expand...
Click to collapse
I can confirm that it is working on SM-T597P with firmware T597PVPS2ASG3. I also went ahead and pulled the stock recovery and boot, as well as modified the RootFix for any device. You can find those files here Link. Thanks Dev for bringing this to light . I also didn't follow the install directions exactly so ill list the steps i took.
1. Flash TWRP with modded odin and reboot to download.
2. Flash Stock recovery and as soon as it reboots enter stock recovery.
3. Wipe Data/Factory Reset.
4. Reboot to Bootloader from Stock Recovery.
5. Flash TWRP again and after reboot enter TWRP.
6. Flash RootFix.
7. Flash DM-Verity and Force Encryption Disabler.
8. Reboot to system.
If anyone would like me to pull the stock recovery of their firmware for them i'm more than happy to.
Compatability with the sm-t590 would be greatly appreciated
Build number
T590XXU3BSG3
Added T590XXU3BSG3 stock boot and stock recovery Here
koobie777 said:
I can confirm that it is working on SM-T597P with firmware T597PVPS2ASG3. I also went ahead and pulled the stock recovery and boot, as well as modified the RootFix for any device. You can find those files here . Thanks Dev for bringing this to light . I also didn't follow the install directions exactly so ill list the steps i took.
If anyone would like me to pull the stock recovery of their firmware for them i'm more than happy to.
Click to expand...
Click to collapse
SM-T597P firmware t597pvpu2bsh7 Android 9 will work your loader?
alexpuz said:
SM-T597P firmware t597pvpu2bsh7 Android 9 will work your loader?
Click to expand...
Click to collapse
yeah for sure
Sent from my SM-G955U using Tapatalk
Sm-t595nzkadbt
Model: SM-T595NZKADBT
Basisbandversion: T595XXU4BSG3
Still no luck :/
With modded Odin from kobi and TWRP from the 1. Site.
Error: Only official...
dm.homelinux.com said:
Model: SM-T595NZKADBT
Basisbandversion: T595XXU4BSG3
Still no luck :/
With modded Odin from kobi and TWRP from the 1. Site.
Error: Only official...
Click to expand...
Click to collapse
try this workaround what i found for our tablet in KG State Prenormal
https://forum.xda-developers.com/showpost.php?p=80856871&postcount=772
koobie777 said:
I can confirm that it is working on SM-T597P with firmware T597PVPS2ASG3. I also went ahead and pulled the stock recovery and boot, as well as modified the RootFix for any device. You can find those files here Link. Thanks Dev for bringing this to light . I also didn't follow the install directions exactly so ill list the steps i took.
1. Flash TWRP with modded odin and reboot to download.
2. Flash Stock recovery and as soon as it reboots enter stock recovery.
3. Wipe Data/Factory Reset.
4. Reboot to Bootloader from Stock Recovery.
5. Flash TWRP again and after reboot enter TWRP.
6. Flash RootFix.
7. Flash DM-Verity and Force Encryption Disabler.
8. Reboot to system.
If anyone would like me to pull the stock recovery of their firmware for them i'm more than happy to.
Click to expand...
Click to collapse
can you make please the fix root for T595XXU4BSG3 please .. cause this one gives bootloop.
thanks in advance

Categories

Resources