{
"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"
}
UPDATE 12/3/2017 - New version of TWRP has been released v3.1.0-0. See below:
https://twrp.me/site/update/2017/03/10/twrp-3.1.0-0-released.html
I have updated versions T710/715/T810/T815 with new builds. TWRP is now v3.1.0-1
Features:
System image backup/restore
Factory image flashing.
F2FS support.
Supersu root option removed which would cause a bootloop on 5.1.1 and 6.0 devices.
MTP fix - MTP now finally working in recovery.
SEANDROID warning fix
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
I have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP 3.1.0-1 for Galaxy Tab S2 T710/T715/T810/T815 models - Lollipop 5.0.2/5.1.1 Marshmallow 6.0.1/Nougat 7.0
twrp_3.1.0-1_sm-t710_13317
twrp_3.1.0-1_sm-t715_13317
twrp_3.1.0-1_sm-t810_13317
twrp_3.1.0-1_sm-t815_13317
twrp_3.1.0-1_sm-t817r4_201117
TWRP 3.0.2-1 for Galaxy Tab S2 T710/810 models - Lollipop 5.0.2/5.1.1 Marshmallow 6.0.1
TWRP_3.0.2-1_sm-t710
TWRP_3.0.2-1_sm-t810
TWRP 3.0.0-1 for Galaxy Tab S2 T710/715/810/815 models - Lollipop 5.0.2/ 5.1.1/6.0.1
TWRP_3.0.0-1_sm-t710
TWRP_3.0.0-1_sm-t715
TWRP-3.0.0-1-sm-t810
TWRP_3.0.0-1_sm-t815
TWRP 2.8.7.1 for Galaxy Tab S2 T710/715/810/815 models - Lollipop 5.0.2 and 5.1.1
LOLLIPOP 5.0.2 ONLY:
twrp_2.8.7.1_LL_5.0.2_t710
twrp_2.8.7.1_LL_5.0.2_t715
twrp_2.8.6.3_LL_5.0.2_t810
twrp_2.8.6.3_LL_5.0.2_t815
LOLLIPOP 5.1.1:
twrp_2.8.7.1_LL_5.1.1_t710
twrp_2.8.7.1_LL_5.1.1_t810
Device tree on Github
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
Note: T717T/P, T817T/P users can flash T*10 or T*15 variant respectively.
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
TO ROOT:
Flash SuperSU below with TWRP.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Credits to Teamwin for their work. Suzook and my other testers.
You are the best
---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------
small issue : twrp_2.8.7.1_LL_5.1.1_t810.tar
access denied
whynottoday said:
You are the best
---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------
small issue : twrp_2.8.7.1_LL_5.1.1_t810.tar
access denied
Click to expand...
Click to collapse
Same here.
@ashyx incredible work.. does this mean root is achievable through SuperSU flash in TWRP? Or you need a custom kernel for that like on Galaxy S6?
it works thanks
itskapil said:
@ashyx incredible work.. does this mean root is achievable through SuperSU flash in TWRP? Or you need a custom kernel for that like on Galaxy S6?
Click to expand...
Click to collapse
You need my custom kernel.
I just want to confirm that t710_twrp_2.8.7.1_LL_5.0.2 also works on T715.
Vielen Dank!
Flashed the TWRP LL5.0.2 version for T810. Everthing´s ok. Thanks.
Deacon-Frost said:
Flashed the TWRP LL5.0.2 version for T810. Everthing´s ok. Thanks.
Click to expand...
Click to collapse
I flashed the 5.0.2 version on the 710 ok (even though Im on 5.1.1, the 5.1.1 tar would not work)
thedanks said:
I flashed the 5.0.2 version on the 710 ok (even though Im on 5.1.1, the 5.1.1 tar would not work)
Click to expand...
Click to collapse
Please give more details of what didn't work. I can't debug with such generic comments.
thedanks said:
I flashed the 5.0.2 version on the 710 ok (even though Im on 5.1.1, the 5.1.1 tar would not work)
Click to expand...
Click to collapse
Please give more details of what didn't work. I can't debug with such generic comments.
Hi ashyx ......I see,you took the 815 also to the list. Anyone test it? Thx a lot man. Will Try to get root with twrp. Anyone tested a supersu.zip ? Should work also too get root. ...
Gesendet von meinem SM-T815 mit Tapatalk
---------- Post added at 03:57 PM ---------- Previous post was at 03:46 PM ----------
So, maybe the first custom Roms will come soon. ....... ????
Gesendet von meinem SM-T815 mit Tapatalk
---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------
@ashyx ,what is the easiest way to deodex a firmware?
Gesendet von meinem SM-T815 mit Tapatalk
ashyx said:
Please give more details of what didn't work. I can't debug with such generic comments.
Click to expand...
Click to collapse
Sorry I grabbed a copy of the permissive kernel tar that was broke... once I got the new version all was fine.
Just root my SM-T815 ......great work, thx man.....
Gesendet von meinem SM-T815 mit Tapatalk
It work fine for my T710 with 5.0.2
Just noticed a minor issue with the T710 5.0.2 version. In the Reboot options pressing "Power Off" reboots back into recovery instead of turning off.
jabbado said:
Just noticed a minor issue with the T710 5.0.2 version. In the Reboot options pressing "Power Off" reboots back into recovery instead of turning off.
Click to expand...
Click to collapse
Remove your usb cable.
ashyx said:
TWRP 2.8.7.1 for Galaxy Tab S2 T710/715/810/815 models - Lollipop 5.0.2 and 5.1.1[/SIZE
Click to expand...
Click to collapse
Would you mind sharing your device tree?
edit: only reason I ask is it's been a loooong time since I've compiled a recovery for an unsupported device and I'd like to get back in the loop... only my attempts at doing so are failing lol. Thanks.
BigBot96 said:
Would you mind sharing your device tree?
edit: only reason I ask is it's been a loooong time since I've compiled a recovery for an unsupported device and I'd like to get back in the loop... only my attempts at doing so are failing lol. Thanks.
Click to expand...
Click to collapse
I don't have a fully working device tree yet.
The device tree I initially created to compile twrp always failed to boot even though the compile process always completed successfully.
I finally managed to build a bootable version by porting some of the binaries and libs from another device and using some of the files from the compile.
It seems when compiling from the latest 5.1 omni sources there is an issue, well for me anyway.
I contacted big biff on IRC about this and he seems to think it should compile OK and doesn't know what the issue is.
However I can't even get a bootable version from existing working trees.
I can't be bothered reverting everything to earlier sources so just used some of the working files from the build I compiled from source and the rest ported over.
I still haven't managed to nail the issue.
If you want I can get something up on github and maybe we can work on it to get it booting?
You will have to bear with me though as I deleted a load of stuff as I needed the space, so it may have gone.
What is the issue you are having?
ashyx said:
I don't have a fully working device tree yet.
The device tree I initially created to compile twrp always failed to boot even though the compile process always completed successfully.
I finally managed to build a bootable version by porting some of the binaries and libs from another device and using some of the files from the compile.
It seems when compiling from the latest 5.1 omni sources there is an issue, well for me anyway.
I contacted big biff on IRC about this and he seems to think it should compile OK and doesn't know what the issue is.
However I can't even get a bootable version from existing working trees.
I can't be bothered reverting everything to earlier sources so just used some of the working files from the build I compiled from source and the rest ported over.
I still haven't managed to nail the issue.
If you want I can get something up on github and maybe we can work on it to get it booting?
You will have to bear with me though as I deleted a load of stuff as I needed the space, so it may have gone.
What is the issue you are having?
Click to expand...
Click to collapse
I'm getting the same issue where it won't boot. Sits at the BL with the Recovery is SE Android warning. Can't get past that dagum screen. Here's my current tree: https://github.com/BigBot96/android_device_samsung_gts2wifi
Compiles without errors but no go. The last recovery I ported was for the Verizon Galaxy Tab 2 7.0 LTE and it was very simple to get up and running. Both CWM and TWRP.
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Working 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"
}
Changelogs:
Ask Dees-Troy
Me: Fixed all the bugs
Can be used as daily driver
Tested on Motorola Moto E XT1022
DOWNLOADS
As per moderators request, I am providing an alternative download location which is non-commercial afaik.
DOWNLOAD LINK:
TWRP 2.8.5.0 WORKING: http://d-h.st/sd0A
TWRP 2.8.5.0: https://mega.co.nz/#!AMByHZ7C!-MNDkV82n0Ph7EAjMLYyMXjKkosjJP7mRjwQV_m5ZSo
TWRP 2.8.5.0 OLD LINK: https://www.dropbox.com/s/d6h1bzxjqwd9tx1/twrp2.8.5.0-recovery.img?dl=0
TWRP 2.8.2.0: https://www.dropbox.com/s/zztjaaoybudtub9/recovery.img?dl=0
Message to Moderator:
"I cannot delete the file from d-h.st because I need to keep track of number of downloads made by my friends. So I will just give this link below with the Strike" - #buzz
OLD LINK:
HERE: http://d-h.st/LSN
P.S. DevDB upload didn't work for me!
XDA:DevDB Information
TWRP 2.8.5.0, Tool/Utility for the Moto E
Contributors
#buzz
Source Code: https://github.com/omnirom/android_bootable_recovery/tree/android-5.0
Version Information
Status: Stable
Current Stable Version: 2.8.5.0
Stable Release Date: 2015-02-17
Created 2014-12-13
Last Updated 2015-02-17
Working fine
Used this recovery to install rom and wipe , install working fine and will test all functions soon and report back
usb mtp through recovery is not working in this @#buzz and also by @ashwin007
AshuGite said:
usb mtp through recovery is not working in this @#buzz and also by @ashwin007
Click to expand...
Click to collapse
what is this "usb mtp through recovery" ..... can anyone please explain
edit:- i figured it out....
---------- Post added at 08:10 PM ---------- Previous post was at 07:39 PM ----------
MTP not working
dchatterjee172 said:
what is this "usb mtp through recovery" ..... can anyone please explain
ps:- i figured it out....
---------- Post added at 08:10 PM ---------- Previous post was at 07:39 PM ----------
MTP not working
Click to expand...
Click to collapse
MTP = Media transfer protocol
thread cleaned
please use the report button for issues with members and their posts
Op any news about slimLP????
Sent from my XT1022 using xda premium
twrp 2.8.3.0 is live. mtp fixed in it. but you can
complied it @#buzz
I couldn't find 2.8.3.0, but with 2.8.2.0 the backup issue with non-matching md5 checksums (seen with 2.7.1.0 and 2.7.2.0) seems to be fixed now. (XT1021, retail 4.4.4). Tested multiple times, with and without compression.
Thanks a lot! (No need for CWM experiments anymore.)
What I'm missing in TWRP: a means to set not only the time zone, but date and time as well - my XT1021 reports a date in the past and an almost random time each time I boot into recovery.
#buzz
Can you plz say something about slim lp!!!!!!
@SidDev said:
twrp 2.8.3.0 is live. mtp fixed in it. but you can
complied it @#buzz
Click to expand...
Click to collapse
Actually I am currently not interested in updating this recovery because I am concentrating on making lollipop ROM for our device. I have cherry picked a lot of changes and I am still working on it.
steve8x8 said:
I couldn't find 2.8.3.0, but with 2.8.2.0 the backup issue with non-matching md5 checksums (seen with 2.7.1.0 and 2.7.2.0) seems to be fixed now. (XT1021, retail 4.4.4). Tested multiple times, with and without compression.
Thanks a lot! (No need for CWM experiments anymore.)
What I'm missing in TWRP: a means to set not only the time zone, but date and time as well - my XT1021 reports a date in the past and an almost random time each time I boot into recovery.
Click to expand...
Click to collapse
My intentions are to make lollipop boot up. For that very reason, I made this recovery update. I am happy that you like this. I will surely update it to the latest version but I need some time also.
nisu4717 said:
#buzz
Can you plz say something about slim lp!!!!!!
Click to expand...
Click to collapse
Slim lp ROM is made long ago. But the kernel gives some errors with msm_vidc and init things. Also I am working on the kernel to bring it to the latest caf lollipop flags. Now I can say that, the ROM is made (it installs perfectly) but kernel is what I am stuck with. Anyway, I will try my best.
Sent from my XT1022 using XDA Free mobile app
EDIT: I have still worked on some major things and made one more build.
Package Complete: /home2/ramsudharsan/slimlpcaf/out/target/product/condor/Slim-condor-5.0.2.alpha.0.91-UNOFFICIAL-20150102-1341.zip
Need to recompile once and then I will test it. I have made some changes in the kernel also. I will try.
#buzz said:
Actually I am currently not interested in updating this recovery because I am concentrating on making lollipop ROM for our device. I have cherry picked a lot of changes and I am still working on it.
My intentions are to make lollipop boot up. For that very reason, I made this recovery update. I am happy that you like this. I will surely update it to the latest version but I need some time also.
Slim lp ROM is made long ago. But the kernel gives some errors with msm_vidc and init things. Also I am working on the kernel to bring it to the latest caf lollipop flags. Now I can say that, the ROM is made (it installs perfectly) but kernel is what I am stuck with. Anyway, I will try my best.
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Hope you fix all the errors and get the ROM booting
#buzz said:
Actually I am currently not interested in updating this recovery because I am concentrating on making lollipop ROM for our device. I have cherry picked a lot of changes and I am still working on it.
My intentions are to make lollipop boot up. For that very reason, I made this recovery update. I am happy that you like this. I will surely update it to the latest version but I need some time also.
Slim lp ROM is made long ago. But the kernel gives some errors with msm_vidc and init things. Also I am working on the kernel to bring it to the latest caf lollipop flags. Now I can say that, the ROM is made (it installs perfectly) but kernel is what I am stuck with. Anyway, I will try my best.
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
A little suggestion
Upload sources to github
May scova or pearcyg_2 can help.
Scova is too good at kernel
i need some help please
I have been trying to flash twrp 2.8 ,but it getz stuck at the sending 'recovery' <8867>kb like this in minimal adb cmd prompt ..
Sorry i dont have ss to provide as no extra phone or cam to take ss ...
I tried 4-5timesxit stays there only ..i wana flash lollipop soak test.
Please update the recovery to the latest version 2.8.5.0:thumbup:
Sent from my XT1022
I have cw recovery in my phone can I know how can I remove that and install this twr without using PC?
vkeyzzzz said:
I have cw recovery in my phone can I know how can I remove that and install this twr without using PC?
Click to expand...
Click to collapse
Use flashify. Tried this many times, works like charm.
Recovery Updated to 2.8.5.0!
gtsfreak said:
Please update the recovery to the latest version 2.8.5.0:thumbup:
Sent from my XT1022
Click to expand...
Click to collapse
maslascher said:
Use flashify. Tried this many times, works like charm.
Click to expand...
Click to collapse
Check OP for the Updated TWRP 2.8.5.0 recovery!
#buzz said:
Check OP for the Updated TWRP 2.8.5.0 recovery!
Click to expand...
Click to collapse
Finally a update thanks
Tested and working great. MTP is also working fine. Great work @#buzz :good:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
{
"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"
}
DOWNLOAD:
TWRP 3.1.0: https://www.androidfilehost.com/?fid=817550096634755236
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version
2) Reboot to TWRP
3) Hit Install
4) Browse to the location of the TWRP-3.0.2-lt02ltespr.zip file on your device and select it
5) swipe to flash
THEMES:
Download Link: TWRP 3.0x Themes
Instructions:
1.goto /sdcard/twrp/ folder and create a new folder called theme
2.copy the twrp theme to /twrp/theme/ folder
3.rename the twrp theme zip file to ui.zip
--ex: rename uiResurrectionRemix.zip to ui.zip
4.reboot to recovery
Credits:
@Dees_Troy
@DarkFrenzy
@dumpy83 (for twrp themes)
DarkFrenzy said:
TWRP 3.0.0
NOTE: YOU HAVE TO LEARN HOW TO TOUCH TO USE THIS RECOVERY
FEATURES:
1. F2FS SUPPORTED
2. MTP WORKS FINE
3. LOLLIPOP SUPPORT
4. NEW LOOK/DESIGN
5. TAP TO WAKE UP
6. I DON'T KNOW
Download Links:
TWRP3.0 ODIN FLASHABLE
TWRP3.0 FLASHABLE
TWRP 2.8.7.0
NOTE: THIS IS RECOMMENDED FOR EVERYONE
FEATURES:
1. F2FS SUPPORTED
2. NO MTP (USE "adb push" COMMAND TO TRANSFER FILES)
3. LOLLIPOP SUPPORT
4. NEW THEME
5. TAP TO WAKE UP
6. I DON'T KNOW
Download Links:
TWRP2.8.7.0 ODIN
TWRP2.8.7.0 FLASHABLE
Click to expand...
Click to collapse
Hy doesn't the official work?
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
majorkid said:
Hy doesn't the official work?
Click to expand...
Click to collapse
I already flashed it.
---------- Post added at 06:13 PM ---------- Previous post was at 05:51 PM ----------
DarkFrenzy said:
TWRP 3.0.0
NOTE: YOU HAVE TO LEARN HOW TO TOUCH TO USE THIS RECOVERY
FEATURES:
1. F2FS SUPPORTED
2. MTP WORKS FINE
3. LOLLIPOP SUPPORT
4. NEW LOOK/DESIGN
5. TAP TO WAKE UP
6. I DON'T KNOW
Download Links:
TWRP3.0 ODIN FLASHABLE
TWRP3.0 FLASHABLE
TWRP 2.8.7.0
NOTE: THIS IS RECOMMENDED FOR EVERYONE
FEATURES:
1. F2FS SUPPORTED
2. NO MTP (USE "adb push" COMMAND TO TRANSFER FILES)
3. LOLLIPOP SUPPORT
4. NEW THEME
5. TAP TO WAKE UP
6. I DON'T KNOW
Download Links:
TWRP2.8.7.0 ODIN
TWRP2.8.7.0 FLASHABLE
Click to expand...
Click to collapse
Says you have to learn how to touch to use this recovery? Well I flashed and can't figure out how to make it work. I use the same recovery on my 6p and it works great. What is the trick to make 3.0 work on the tab? Really appreciate your work in this tab as I haven't even picked it up in over a year until I saw the good work you've accomplished.
I flashed the second one and it worked
majorkid said:
I flashed the second one and it worked
Click to expand...
Click to collapse
Yeah me too. I just couldn't 3.0 to work.
The dev is doing his best. And thank you for the great work youre doing..
btvolta said:
Says you have to learn how to touch to use this recovery? Well I flashed and can't figure out how to make it work. I use the same recovery on my 6p and it works great. What is the trick to make 3.0 work on the tab? Really appreciate your work in this tab as I haven't even picked it up in over a year until I saw the good work you've accomplished.
Click to expand...
Click to collapse
Touch is not working correctly.if u touch wipe the reboot option is pressed and so on. I have mastered where to touch.
But twrp 3.0 is not really important at the moment. I just posted it so that tab 3 217s will have everything updated.now cm13 roms are getting ready to upload.
Sent from my ASUS_T00J using XDA Free mobile app
DarkFrenzy said:
Touch is not working correctly.if u touch wipe the reboot option is pressed and so on. I have mastered where to touch.
But twrp 3.0 is not really important at the moment. I just posted it so that tab 3 217s will have everything updated.now cm13 roms are getting ready to upload.
Sent from my ASUS_T00J using XDA Free mobile app
Click to expand...
Click to collapse
Really looking forward to CM13, thank you so much for all of your work man.
TWRP-3.0
..............Touch screen issue fixed for TWRP-3.0
https://www.androidfilehost.com/?fid=24415232478677872
Credit: @Dees_Troy
lilferraro said:
..............Touch screen issue fixed for TWRP-3.0
https://www.androidfilehost.com/?fid=24415232478677872
Click to expand...
Click to collapse
Really ? I m on the bed. Will see that
Thanks.your really genius.
EDIT: IT WORKS AS ITS OFFICIAL BUT HAS NO F2FS SUPPORT. I WILL POST TWRP 3.0 WITH F2FS SUPPORT SOON...
Sent from my ASUS_T00J using XDA Free mobile app
@Dark Frenzy and lilferraro . Thank you guys for the awesome collection of ROMs, kernels built from source to choose from , and for leaving nothing out. And even going as far as the updated 3.0 twrp recovery with f2fs support. And thanks to you gentlemen I'm no longer on kit kat 4.4.2 and now I'm rockin cm 13 -6.0 marshmallow. Flashed the test kernel zip which by the way is working really well. One thing I did notice was how good the WiFi signal is compared to what it was on 4.4.2 and I'm very happy about that because that was a huge issue that this tab had while on stock firmware. Baseband is not listed in settings . battery drain is not bad (using kernel auditor apk ) although in the thread Performance Control is recommended but I always keep an extra charger with me . This thing is running smooth . just flashed alpha 4.0 xposed framework ver.80 zip. And now running xposed. Just wanted to hit the thank you button a couple of times in the threads and to say thank you for all of this .. You guys make one bad @$$ team.
A request for the SM-T211.....would be beneficial
@DarkFrenzy
Using TWRP 3 with F2FS and any time I try to flash an Aroma-based installer for Open GApps, TWRP totally locks up and I cannot start the install.
GlitterKill said:
Using TWRP 3 with F2FS and any time I try to flash an Aroma-based installer for Open GApps, TWRP totally locks up and I cannot start the install.
Click to expand...
Click to collapse
Is that only with f2fs twrp? I think that's same with all other twrp for SM-T217S/T.
You need to touch at the corner to press next button and so on, u need to figure out where it touches but that's difficult but I have mastered it lol
Sent from my LG-F320 using XDA Free mobile app
DarkFrenzy said:
Is that only with f2fs twrp? I think that's same with all other twrp for SM-T217S/T.
You need to touch at the corner to press next button and so on, u need to figure out where it touches but that's difficult but I have mastered it lol
Sent from my LG-F320 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I haven't tried the non-F2FS one, yet.
Is TWRP 3.0 required to flash the MM roms? Or will another one work? I am wondering if the trouble I am having installing ROMs right now may be coming from using the new recovery.
Twrp updated and its now stable
Changes or whats new:
MTP
USB Storage
Aroma Installer Touch
F2FS
DarkFrenzy said:
Twrp updated and its now stable
Changes or whats new:
MTP
USB Storage
Aroma Installer Touch
F2FS
Click to expand...
Click to collapse
Thanks for the update
majorkid said:
Thanks for the update
Click to expand...
Click to collapse
new updated :
added Tmobile Support
https://androidfilehost.com/?fid=24591000424945297
I want to install this on my tablet, but don't have a previous twrp version installed, how would I go about doing this?
Taji34 said:
I want to install this on my tablet, but don't have a previous twrp version installed, how would I go about doing this?
Click to expand...
Click to collapse
Use Flashify from playstore ..
You can root using KingUser apk .. if not successful use odin to flash TWRP from twrp.me but in tar file .. You can flash custom roms from there ..
Team Win Recovery Project 3.0.2-4
This is for the International SM-G935F/FD/X, Korean SM-G935K/L/S, and Canadian SM-G935W8 Exynos models only! Do not flash on flat S7 or Qualcomm models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edge.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
You can follow this video by Max Lee if you'd like: How to Root Galaxy S7 & S7 Edge! [Exynos ONLY]
Otherwise, follow these instructions:
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2lte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
If you only want a bootable system partition:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Note: This does not disable the forced encryption on Bxxx firmware, only Axxx firmware due to a change in vold by Samsung.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-4 - Fix restoring of non-ext4 partitions, update f2fs drivers, update to BPID source & Linux 3.18.43
v3.0.2-3 - Fix booting on BPH6/APGH bootloaders, rebase on Note 7 sources, enable NTFS-3G formatting
v3.0.2-2 - Fix MTP issue in kernel
v3.0.2-1 - Separation of Korean variants, retrieve actual model from bootloader, drop modem from fstab, remove legacy flags, add bootdevice symlink, last_kmsg support
v3.0.2-0 - See here for the changes.
v3.0.1-0 - Fixed USB OTG storage
v3.0.0-0 (twrp.me) - Disabled backup/restore of modem partition (must be signed and flashed in Odin)
v3.0.0-0 - Initialize new device tree based on Samsung OSRC G935FXXU1APAW kernel.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_hero2lte (android-6.0)
Device tree (Korea): https://github.com/TeamWin/android_device_samsung_hero2ltekor (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal8890 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_herolte
Version Information
Status: Stable
Current Stable Version: 3.0.2-4
Stable Release Date: 2016-10-15
Created 2016-03-11
Last Updated 2016-11-08
Reserved
If you have a G935P, G935V, G935R, or G935A (aka the US Snapdragon models) your bootloader is locked. I will not be making TWRP for your device - it simply cannot happen. Sorry.
Update: G935T users can expect TWRP for their devices as soon as T-Mobile convinces Samsung to unlock the bootloader - I already have a fully complete working build ready.
You know who you can blame?
THE DONALD!~~~~~~~~~~~~
or Obama, I dunno, blaming Obama is getting kind of old guys, sorry.
Woohoo
Sent from my SM-G935F using Tapatalk
I will need someone to verify if features are working as this was just a copy paste of the herolte (non-Edge) device tree.
Mainly expecting brightness slider to not work, so please if things don't work, join #twrp on freenode and talk to me.
Is this for the Snapdragon or the Exynos devices or should it work on both? And does this also apply for the kernel?
reayard said:
Is this for the Snapdragon or the Exynos devices or should it work on both? And does this also apply for the kernel?
Click to expand...
Click to collapse
you're in the Exynos forum
reayard said:
Is this for the Snapdragon or the Exynos devices or should it work on both? And does this also apply for the kernel?
Click to expand...
Click to collapse
It specifically states in the title G935F, so it's for Exynos.
Can I ask if someone on a Vodafone UK handset tries this, let me know if it works and confirms an unlocked bootloader. I'd do it myself but I'm still undecided whether to keep this thing and that could decide it for me. I'd almost certainly have problems with a return if knox is tripped. Cheers!
Wooohooo. Thanks!!
I wonder if this TWRP works for all G935 variants. I do recall that TWRP worked mainly for most note 5 and S6 variants regardless of model.
---------- Post added at 04:52 PM ---------- Previous post was at 04:46 PM ----------
jcadduono said:
you're in the Exynos forum
Click to expand...
Click to collapse
Thunder Bay! Nice city, I visit often. Glad to see someone from Canada working on exynos version!
Brava27 said:
I wonder if this TWRP works for all G935 variants. I do recall that TWRP worked mainly for most note 5 and S6 variants regardless of model.
---------- Post added at 04:52 PM ---------- Previous post was at 04:46 PM ----------
Thunder Bay! Nice city, I visit often. Glad to see someone from Canada working on exynos version!
Click to expand...
Click to collapse
This will only work for G935F (and possibly G935FD?) which are the only known Exynos variants of S7 Edge.
I will be working on the Snapdragon variants as well once their sources are released.
jcadduono said:
This will only work for G935F (and possibly G935FD?) which are the only known Exynos variants of S7 Edge.
I will be working on the Snapdragon variants as well once their sources are released.
Click to expand...
Click to collapse
Can't wait till you get a snapdragon version out my 935t is missing root so much lol
Beefheart said:
It specifically states in the title G935F, so it's for Exynos.
Can I ask if someone on a Vodafone UK handset tries this, let me know if it works and confirms an unlocked bootloader. I'd do it myself but I'm still undecided whether to keep this thing and that could decide it for me. I'd almost certainly have problems with a return if knox is tripped. Cheers!
Click to expand...
Click to collapse
Completely same boat as you lol.
Sent from my SM-G900F using XDA Free mobile app
Forgive my ignorance. What differentiates the Exynos from the Snapdragon version as far as name? And how can I identify the Snapdragon version? I NEVER know where y'all find all these names for these devices. LOL
---------- Post added at 11:52 AM ---------- Previous post was at 11:50 AM ----------
mrbigdrawsz said:
Forgive my ignorance. What differentiates the Exynos from the Snapdragon version as far as name? And how can I identify the Snapdragon version? I NEVER know where y'all find all these names for these devices. LOL
Click to expand...
Click to collapse
Actually, I think I found it. Snapdragon is the SM-G935T. Sorry for asking.
mrbigdrawsz said:
Forgive my ignorance. What differentiates the Exynos from the Snapdragon version as far as name? And how can I identify the Snapdragon version? I NEVER know where y'all find all these names for these devices. LOL
Click to expand...
Click to collapse
AFAIK they ate the processors. Both are totally different architectures, so this being built for one literally means it won't work on the other.
Generally I believe Exynos is international whilst snapdragon is everywhere else. I'm not sure what constitutes as international however.
Sent from my SM-G900F using XDA Free mobile app
riso123 said:
AFAIK they ate the processors. Both are totally different architectures, so this being built for one literally means it won't work on the other.
Generally I believe Exynos is international whilst snapdragon is everywhere else. I'm not sure what constitutes as international however.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I appreciate the info. I'm aware of the different architectures, etc...Just wasn't sure how the names differentiated the two variants. But I've tracked it down and will hopefully be able to find it in the future. LOL
Do I need to root my Phone before I flash twrp? Or does twrp this? Or is there the option to root in twrp?
Sorry for dumb question just want to be sure. And I want root xD
xPr0metheus said:
Do I need to root my Phone before I flash twrp? Or does twrp this? Or is there the option to root in twrp?
Sorry for dumb question just want to be sure. And I want root xD
Click to expand...
Click to collapse
Other way round. Flash this through odin to be able to flash a kernel in recovery which gives root access.
Sent from my SM-G900F using XDA Free mobile app
Beefheart said:
It specifically states in the title G935F, so it's for Exynos.
Can I ask if someone on a Vodafone UK handset tries this, let me know if it works and confirms an unlocked bootloader. I'd do it myself but I'm still undecided whether to keep this thing and that could decide it for me. I'd almost certainly have problems with a return if knox is tripped. Cheers!
Click to expand...
Click to collapse
+1 one the Vodafone bootloader. I neeeeeed root on this thing. I'll be able to get to a pc soon so will just try it out hopefully
KNOX 0X0 or 0x1 ?
Flashing anything custom will trip Knox. So 0x1.
Sent from my SM-G935F using Tapatalk
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
downesey said:
+1 one the Vodafone bootloader. I neeeeeed root on this thing. I'll be able to get to a pc soon so will just try it out hopefully
Click to expand...
Click to collapse
Would really be appreciated if you could confirm. Is it a UK Vodafone handset you have?
Sent from my SM-G935F using Tapatalk
{
"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'm 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/KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
* BOOM! goes the dynamite
*/
[COLOR="181818"]About Project New World[/COLOR]
Hi XDA community, we are proud to present our vision of Android based on AOSP with features that we think are useful.
The main goal of Project New World is to provide a clean and fast ROM with nice and useful features.Thanks for your
attention and we hope you will enjoy our builds as much as we do.
[COLOR="181818"]Warning[/COLOR]
This build is based on B32 blobs so it requires an updated bootloader + modem. (They can be found in the download section)
Also is this a BETA build that means you may face high battery drain, force closing apps etc. Please be aware of this.
[COLOR="181818"]Features[/COLOR]
Coming soon
[COLOR="181818"]Bugs[/COLOR]
VoLTE
(Speaker bug) [While calling toggle loudspeaker to avoid]
(Dual Sim) [If you get no in call audio try to switch data sims etc.]
[COLOR="181818"]Installation instructions[/COLOR]
Attention! The bootloader needs to be unlocked
1. Update your version of TWRP (3.2.1-0 or > recommended) [Download]
2. Perform a backup of your current ROM (optionally)
3. Wipe system,data and cache (optionally) [Needed if coming from another rom!; always good to avoid bugs]
4. Install the Universal B32 bootloader and your model specific modem.
5. Install Project New World
6. Install GApps (optionally) [Recommended -> Unofficial Open GApps (arm64) (8.1)]
7. Reboot
[COLOR="181818"]Source[/COLOR]
Kernel
Device tree
Vendor to be continued..
[COLOR="181818"]Download[/COLOR]
Bootstack - B32 and modems
Project New World Beta Builds
[COLOR="181818"]Credits[/COLOR]
LineageOS
Unjustified Dev
DrakenFX
(If you think you should be on the list hit me up)
XDA:DevDB Information
Project New World - O_MR1, ROM for the ZTE Axon 7
Contributors
OrdenKrieger
Source Code: https://github.com/ProjectNewWorld
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Created 2017-12-31
Last Updated 2018-01-31
Frequently Asked Questions
Do I need to update my bootstack before flashing?
Yes, if you don't come from B32 stock it's necessary to update your boostack and modem. That files
can be found under the download section.
Does this rom support modifications?
No, because I don't know how every modification out there exact works which can cause
problems with debuging and overall stability.
Does this rom support custom kernels?
No, because this falls under the same section as modifications, but every kernel that is based
on the source of the stock kernel of this rom, should work fine.
Will you add feature or app XYZ?
No, our team decides democratically and we only want unique or necessary features
without overloading the rom. Also should the rom work the same no matter which device
it's used on.
Why isn't everything working flawlessly?
Remember, this is a Beta build for testing purposes. Also are this build based on old
N proprietary blobs and since ZTE didn't release any new for now it's impossible to fix
certain issues.
When will a new build drop?
When I think it's alright. I don't want to release untested work.
Downloading. Thank you very much for your work.
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Gases said:
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Click to expand...
Click to collapse
Flash universal bootloader
I installed it as soon as it hit AFH. Flashed bootloader and modem. No problems with install other than a corrupt sd notice. Working on that. Data/Wifi/Bluetooth operational. The camera doesn't fc but is very dark and takes dark images. Known issue, so let's move on. Substratum works. Mono looks sweet on 8.1. The big cluster doesn't seem to be downclocking on Interactive. Switching to Conservative solves that. Too early to tell much else. Gratz on a solid first release!
Edit: I backed up my SD card, formatted it and copied everything back. It's working fine. I've had this problem with a few other Oreo builds. Not sure why Oreo sees it as corrupted initially.
Gases said:
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Click to expand...
Click to collapse
you installed the B32 bootloader.
https://androidfilehost.com/?fid=962157660013068930
t started off well for me.
WesTD said:
Flash universal bootloader
Click to expand...
Click to collapse
I tried flashing the universal bootloader provided in the OP. It still shows the same error.
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
kenet said:
you installed the B32 bootloader.
https://androidfilehost.com/?fid=962157660013068930
t started off well for me.
Click to expand...
Click to collapse
Just tried that one as well, no difference.
I'm flashing that first, then the A2017U B32 modem provided in the OP, and then flashing the ROM. It shows error 7, and it says that my device name isn't correct.
Gases said:
I tried flashing the universal bootloader provided in the OP. It still shows the same error.
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
Just tried that one as well, no difference.
I'm flashing that first, then the A2017U B32 modem provided in the OP, and then flashing the ROM. It shows error 7, and it says that my device name isn't correct.
Click to expand...
Click to collapse
Surely you downloaded corrupted the zip.
Gases said:
I tried flashing the universal bootloader provided in the OP. It still shows the same error.
---------- Post added at 08:21 PM ---------- Previous post was at 08:18 PM ----------
Just tried that one as well, no difference.
I'm flashing that first, then the A2017U B32 modem provided in the OP, and then flashing the ROM. It shows error 7, and it says that my device name isn't correct.
Click to expand...
Click to collapse
No mine sis the same to. Left my device name as blank lol. Had to manually remove the trust zone. Try redownloading it or go in and change it to blank like i did
kenet said:
Surely you downloaded corrupted the zip.
Click to expand...
Click to collapse
I honestly don't think so. I just re-downloaded everything, flashed everything and got the exact same error. What can I do?
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
reV17 said:
No mine sis the same to. Left my device name as blank lol. Had to manually remove the trust zone. Try redownloading it or go in and change it to blank like i did
Click to expand...
Click to collapse
How can I do that? I've tried doing it, but I get an error saying the ZIP file is in an incorrect format.
I'm sorry for asking so much, I'm a complete noob and I can't find information on this
Gases said:
I honestly don't think so. I just re-downloaded everything, flashed everything and got the exact same error. What can I do?
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
How can I do that? I've tried doing it, but I get an error saying the ZIP file is in an incorrect format.
I'm sorry for asking so much, I'm a complete noob and I can't find information on this
Click to expand...
Click to collapse
can you confirm, what version of TWRP are you using? Try using the latest. That fixed my problem. Still had the N1 version installed
reV17 said:
can you confirm, what version of TWRP are you using? Try using the latest. That fixed my problem. Still had the N1 version installed
Click to expand...
Click to collapse
I'm using version 3.1.1-0. I just tried removing the assert and got error 6 while trying to flash.
Gases said:
I'm using version 3.1.1-0. I just tried removing the assert and got error 6 while trying to flash.
Click to expand...
Click to collapse
Flash the latest TWRP 3.2.1-0 using TWRP and then flash the unmodified zips
Gases said:
I'm using version 3.1.1-0. I just tried removing the assert and got error 6 while trying to flash.
Click to expand...
Click to collapse
3.1.1-0 is janky. I had problems with Oreo and that version. 3.2.1-0 seems solid.
Would you look at that... Updating TWRP solved it! Thanks, guys! @Cablespider @reV17
Can I root this ROM? Or is Magisk incompatible with Oreo?
Magisk 15.1 is running fine.
Gases said:
The flash fails. It says that my device isn't an Axon 7, it shows the device name as "."
Click to expand...
Click to collapse
Update your TWRP. Forgot to mention that.
is footej camera working good ?
deleted
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/pioneer
Downloads :
https://download.lineageos.org/pioneer
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
0
Seppppx said:
@LuK1337
By WFD you mean Wi-Fi direct or Wi-Fi display?
Click to expand...
Click to collapse
Latter one.
Amazing!
Thank you very much and outstanding work OP! I got this device last week installed LOS17.1 right away, and there is v 18 already in the works! So cool.
drkshdwprophet said:
Thank you very much and outstanding work OP! I got this device last week installed LOS17.1 right away, and there is v 18 already in the works! So cool.
Click to expand...
Click to collapse
Did u install it ?
Can I say what's working and what not?
Arbaazhussain said:
Did u install it ?
Can I say what's working and what not?
Click to expand...
Click to collapse
Do it yourself.
LuK1337 said:
Do it yourself.
Click to expand...
Click to collapse
Ok and it was quick reply
---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------
Should I use nikgapps android 11?
Will it work?
Arbaazhussain said:
Ok and it was quick reply
---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------
Should I use nikgapps android 11?
Will it work?
Click to expand...
Click to collapse
God only knows.
LuK1337 said:
God only knows.
Click to expand...
Click to collapse
Ok I will try
Root which magisk version should be used?
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
Sir can u say me what are changes brought with everyday build?
Arbaazhussain said:
Ok I will try
Root which magisk version should be used?
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
Sir can u say me what are changes brought with everyday build?
Click to expand...
Click to collapse
Do I look like someone who'd use Magisk? Also no, I'm not going to put my time into writing changelogs.
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
emc02 said:
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
Click to expand...
Click to collapse
Yeah, it is quite possible that @Arbaazhussain and other people asking about official builds / future plans will annoy me so much that I'll just drop support entirely.
emc02 said:
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
Click to expand...
Click to collapse
The builds is always unofficial unless the lineage 18 is released as stable and then maintainers can make it official
So it is unofficial now
later official if luk sir does of course
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
LuK1337 said:
Yeah, it is quite possible that @Arbaazhussain and other people asking about official builds / future plans will annoy me so much that I'll just drop support entirely.
Click to expand...
Click to collapse
Sorry if I have annoyed you
I ask for forgiveness from the depth of my heart
Goddamn, didn't expect this one. Gonna try this one soon
i have installed this ROM. very good. no problems. also have installed nikgapps BASIC. everything is OK. thanks to the dev luK1337
Enviado do meu H4113 através de Tapatalk
Is there a way to activate VOLTE? I thought VOLTE and wifi calling were options on LOS 17. I had bricked this phone trying to update to the last LOS 17 and has been unused for a month or so, so I might be thinking of a rom I had on my XZP. Either way works good so far except I haven't been able to activate it on my new carrier, but that's another story.
Error installing
Hello,
I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.
The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Any help would be greatly appreciated,
Thanks.
DarkInvaderr said:
Hello,
I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.
The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Any help would be greatly appreciated,
Thanks.
Click to expand...
Click to collapse
Try to fastboot boot latest twrp instead.
LuK1337 said:
Try to fastboot boot latest twrp instead.
Click to expand...
Click to collapse
Tried doing that but i either get FAILED (Write to device failed in SendBuffer() (Too many links)) or FAILED (Write to device failed (no link)).
Flashed my firmware again just in case so i guess its not hard bricked?
Ill try to fastboot boot from a different PC to see if the issue is there.
Thanks for replying.