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.
Features::
Build based on latest CM13.0 and TWRP source.
Workaround on touchscreen. Touch screen fully works! No matter what your device's version is.
All function in a normal TWRP
Changelog:
15/7/11
First release
15/10/24
Sync latest TWRP source
Update prebuilt kernel from beta357
Fix a typo: nz510j, now it can be used to flash an official release
15/11/21
Sync latest TWRP source
Build kernel from new source
Add support for F2FS
16/03/12
Sync latest TWRP source (TWRP 3.0)
Use new kernel align with CM13
16/08/05
Sync latest TWRP source
Use new kernel align with CM13
Restructure device tree
Download link::
https://s.basketbuild.com/filedl/devs?dev=dianlujitao&dl=dianlujitao/nx510j/twrp_nx510j_v5_f2fs_dianlujitao.img
Install guide::
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Run "fastboot -i 0x19d2 flash recovery twrp_nx510j_v5_f2fs_dianlujitao.img"
4. Reboot
Source code::
https://github.com/MoKee/android_bootable_recovery-twrp/tree/mkm
https://github.com/dianlujitao/android_device_zte_nx510j/tree/twrp
XDA:DevDB Information
TWRP, Tool/Utility for all devices (see above for details)
Contributors
dianlujitao
Version Information
Status: Stable
Current Stable Version: 5
Stable Release Date: 2016-08-05
Created 2015-07-11
Last Updated 2016-08-04
how to install this .img?
Hi. Can you make a build for nx511j (z9 mini)?
djbosanac said:
how to install this .img?
Click to expand...
Click to collapse
I've added a simple install guide
How do we boot into recovery? I flashed the recovery but when I try to boot into recovery from fastboot it always boots to the main OS
Can't boot in this recovery after installing it.
Sent from my NX510J using XDA Free mobile app
Hi, it will works with newest ZTE firmware 3.06 ? or maybe someone has a newest version ? THX
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
5[Strogino] said:
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
Click to expand...
Click to collapse
Will be fixed as long as I have time, now I'm too busy
How long will this command take? All I get is < waiting for device >
Had to do this first:
- Connect phone while normally booted
- Run the installer that is automatically mounted on windows
- click 7 times the buildnumber in "about phone" to enable developer options
- enable usb debugging in developer options
Edit:
Installed your cyanogenmod build, but still have a problem. Cant reboot to recovery. What I have to do is get into fastboot, flash TWRP, reboot to recovery.
Edit2:
I can boot to recovery, only if usb is connected.
5[Strogino] said:
Can not install official updates/ROMs. There is a misspelling in default.prop:
ro.product.name=nz510j
Must be:
ro.product.name=nx510j
Click to expand...
Click to collapse
EDIT: The following isnt needed anymore as of the latest update!
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
- Install the drivers ( http://pdanet.co/a/ )
- Unzip the ZIP
- Start the file "Install_TOOL.exe"
- Coose 2: "Install TWRP 2.8.6.0"
- Wait for restart to the new TWRP (in nubia style!)
Click to expand...
Click to collapse
jogai said:
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
Click to expand...
Click to collapse
A friend of mine received this smartphone this week and he's unable to get twrp installed, tried many different methods, but apparently the touchscreen doesn't work when he needs to press an option. He did it through Win XP, maybe that's the reason why... I'm nervous as well as I ordered the phone as well through the same seller...
I really don't know why it's not working...
jogai said:
To bypass this problem I use another TWRP now from here: http://www.androidiani.com/forum/mo...3-z9-max-lollipop-5-0-2-cuoco92-firmware.html
Download: https://mega.nz/#!OgYljCAa!eH54Uc7Tdld1N3Oz3L4TIr1uiBx6EZSILf67MFgpgJk"
Translated:
Click to expand...
Click to collapse
already fixed
K3nshiro said:
A friend of mine received this smartphone this week and he's unable to get twrp installed, tried many different methods, but apparently the touchscreen doesn't work when he needs to press an option. He did it through Win XP, maybe that's the reason why... I'm nervous as well as I ordered the phone as well through the same seller...
I really don't know why it's not working...
Click to expand...
Click to collapse
Try my latest release,
and plz tell me which of the following path exists on your friend's phone:
/sys/bus/i2c/devices/2-004a
/sys/bus/i2c/devices/2-005d
/sys/bus/i2c/devices/2-0024
dianlujitao said:
Try my latest release,
and plz tell me which of the following path exists on your friend's phone:
/sys/bus/i2c/devices/2-004a
/sys/bus/i2c/devices/2-005d
/sys/bus/i2c/devices/2-0024
Click to expand...
Click to collapse
Thank you dianlujitao,
I hadn't seen that you had already fixed the typo, sorry for that.
I've told my friend about the new TWRP and asked him about the path - if he asks me where to find this on the phone, where should he look for, or can this be found through Windows as well ?
I'll keep you informed about my findings.
Thanks again,
Ken
K3nshiro said:
Thank you dianlujitao,
I hadn't seen that you had already fixed the typo, sorry for that.
I've told my friend about the new TWRP and asked him about the path - if he asks me where to find this on the phone, where should he look for, or can this be found through Windows as well ?
I'll keep you informed about my findings.
Thanks again,
Ken
Click to expand...
Click to collapse
Can be found even through CM file manager.
Run adb shell on computer, then use ls to find it
Hey!
I got it working on my Z9 max
Didn't work though through root path on internal storage, had to run it through another path on my pc.
Fiddling around a bit these days before I try out your Cyanogen Rom.
Btw, do you have a proper link (nubia official) for the download of the new Nubia UI?
I tried to locate it on nubia.cn, but I'm unable to find it...
I'd really appreciate if you could reveal the link
Cheers
Sent from my NX510J using Tapatalk
K3nshiro said:
Hey!
I got it working on my Z9 max
Didn't work though through root path on internal storage, had to run it through another path on my pc.
Fiddling around a bit these days before I try out your Cyanogen Rom.
Btw, do you have a proper link (nubia official) for the download of the new Nubia UI?
I tried to locate it on nubia.cn, but I'm unable to find it...
I'd really appreciate if you could reveal the link
Cheers
Sent from my NX510J using Tapatalk
Click to expand...
Click to collapse
http://bbs.nubia.cn/thread-554721-1-1.html
Latest nubia ui v3.62
dianlujitao said:
http://bbs.nubia.cn/thread-554721-1-1.html
Latest nubia ui v3.62
Click to expand...
Click to collapse
Thanks a ton dianlujitao,
Sorry for late reply, I'm currently on vacation, I'll do it when I return.
I got a couple of questions regarding this. If you can and if you want, I'd appreciate if you could give them a look, no hurry. I'm very well aware that this is your time, and I have no right to request anything.
I just don't want to brick the phone
1. Can I use your Twrp to make a Nandroid backup?
2. Can I use your Twrp to flash it (The Brush file) or should I do it with default recovery?
3. As per instructions, it says that I should unroot it and reset to factory values.... Is this necessary?
4. Where does your Twrp save the backup, to internal memory or SD card?
Last but not least, I have to say that so far the phone has impressed me, specially the camera, awesome pics.
I let the device store them on the SD card, and sometimes I have seen (4 times to be precise) that the pic is corrupt. Would you know if this is fault of the phone or of the SD card?
Cheers,
Ken
P. D. Do you have a PayPal account for donations setup for instance?
Sent from my NX510J using Tapatalk
K3nshiro said:
Thanks a ton dianlujitao,
Sorry for late reply, I'm currently on vacation, I'll do it when I return.
I got a couple of questions regarding this. If you can and if you want, I'd appreciate if you could give them a look, no hurry. I'm very well aware that this is your time, and I have no right to request anything.
I just don't want to brick the phone
1. Can I use your Twrp to make a Nandroid backup?
2. Can I use your Twrp to flash it (The Brush file) or should I do it with default recovery?
3. As per instructions, it says that I should unroot it and reset to factory values.... Is this necessary?
4. Where does your Twrp save the backup, to internal memory or SD card?
Last but not least, I have to say that so far the phone has impressed me, specially the camera, awesome pics.
I let the device store them on the SD card, and sometimes I have seen (4 times to be precise) that the pic is corrupt. Would you know if this is fault of the phone or of the SD card?
Cheers,
Ken
P. D. Do you have a PayPal account for donations setup for instance?
Sent from my NX510J using Tapatalk
Click to expand...
Click to collapse
1. yes, but system,boot and data is enough
2. yes
3. no
4. it's up to u
5. no idea
6. I forgot my paypal passward and passward reset answer, so...
Related
Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse
No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:
munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it
Sounds definitely awesome!
Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!
munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL
XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!
munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.
New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback
Solved! Will give you soon cm11 in multiboot!
munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:
Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!
Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47
Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
Introduction
This is a UNOFFICIAL build of LineageOS for the Samsung Galaxy Core Plus.
It's not ready yet and has some bugs in it which could cause problems to some users.
The ROM will only work on the SM-G350 Version of the Phone (without any Numbers/Letters behind).
This ROM could be used for daily use now (though you should look at the list of what doesn't work first).
Known Bugs
Camera sometimes switches to green-purple. The resulting picture doesn't have the weird color, but it may be flipped and/or distorted at the edges.
Video Recording
Codecs (some work, some don't. I tested MP4 and AVI, both work. I should really make a list...)
Installation Instructions
Special thanks to @Giovix92 for making this tutorial!
Requirements:
1: A computer with Windows.
2: An Internet connection.
3: A backup of your phone data (contacts, photo, music, videos, and other).
4: About 300 MB free space on your SD card.
5: Phone charged at least 80%.
Download links are below
I do NOT take any responsibility for bricked devices!
Let's start!
1: Download the Samsung USB Drivers.
2: Download the ODIN3. (Only for Windows)
3: Download the TWRP Odin package to your desktop and download the LineageOS 13 zip to your SD card.
4: Make a backup of your files, because the storage will be wiped. (External SD card will not be wiped)
5: Reboot your phone in to the Download mode (Volume Down- , Home- and Power button). Press the Volume Up button when asked. Then open the ODIN3 and connect your phone to your PC.
6: Press AP and choose the TWRP Odin package (recovery.tar) and make sure re-partition is NOT ticked. "Auto-Reboot" should not be ticked either, otherwise you will need to be quick to boot into the recovery immediately after flashing.
7: Press start! Wait a few seconds. Then your phone will be rebooted. Now you can disconnect the cable and power off your phone.
8: Boot your phone in to the TWRP Recovery (Volume Up-, Home- and Power button).
9: Go to Wipe, and Swipe to Factory Reset.
10. After wiping go to the home screen by pressing the home button.
11: Go to Install. Choose the "external_sd" from the top bar. (It says "Storage: Internal Storage (xxxxMB)" by default)
12: Choose the LineageOS 13 ZIP and Swipe to Confirm Flash. Make sure you don't power off while flashing!
13: After the zip has been flashed choose "Reboot System".
14: Wait 5-15 minutes to boot the phone. If the phone keeps booting take out the battery and do a Factory Reset again.
15: When the phone boots the first time, go through the Setup Wizard and you are ready to use your phone!
If there was something you didn't understand, please don't hesitate to ask
Changelog
23-01-2021:
Security patches until April of 2019
Updated Chromium from 67.0.3396.87 to 87.0.4280.101
Disabled latinimegoogle (which is compiled against an incompatible instruction set and results in crashes)
Fix offline charging
Old Changelogs:
02-05-2019:
Include all security patches up to January 2019 (and most of February and March, except for the PNG vulnerability)
NFC
Fix up some of the codecs (h264 and ac3, which should enable you to watch most videos)
Remove Gello (the old, bloated Browser) in favour of Jelly
Using way less hacks than previously (again)
05-04-2018:
Include all security patches up to March 2018
SELinux is now enforcing
OTA Updates the third (now using the internal Updater)
Using way less hacks than previously
24-05-2017:
Now compile with newest toolchain (Commit)
Fix SD Card (Device commit, Kernel commit)
Removed PMEM from the kernel (as this saves some RAM) (Commit)
OTA Updates (Commit)
18-04-2017:
Switch to LineageOS
4 Months of Security Patches
10-04-2017:
Fixed GApps (through a modified WebView)
07-04-2017:
Fixed Network (Commit)
Enabled permissive SELinux (Patch, Commit)
10-10-2016:
Bringup
Downloads
Samsung USB Drivers
Odin v3.09
Odin v3.11.1
TWRP 3
TWRP 2.8.1.0
lineage-13.0-20210123-UNOFFICIAL-cs02.zip
Sources
Device tree
Kernel tree
Proprietary files
WebView
Thanks To/Credits
Thanks to ...
... androidlover5842, ishantvivek, SandPox, ZIM555 and everyone else working on Samsung's hawaii-Boards
... berkantkz and santeri3700 for teaching me the basics of ROM developing
First Version of CM 13 is up
First! Good rom man!
Inviato dal mio ASUS_Z00A utilizzando Tapatalk
Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.
gaetano76le said:
Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.
Click to expand...
Click to collapse
Still working on that.
I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card
This is the same on stock when listening YT idk why it happens.
For the sdcard fix check if there are correct mounts for vold.fstab or framework
BTW. Videoplayback isnt working good on YT on Internet browser and is glitched too on chrome.
TimSchumi said:
I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card
Click to expand...
Click to collapse
bump
@TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too
So, any changes about the network?
QGM said:
bump
@TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too
Click to expand...
Click to collapse
Thanks for searching :good:
I'll write to developer and ask for the fix!
john_sdr said:
So, any changes about the network?
Click to expand...
Click to collapse
Not now, still working on it. I don't even know where to search.
something about the vpn? or maybe something isnt compatible with cm13?
I searched on google and disable the firewall could be a solution.
john_sdr said:
something about the vpn? or maybe something isnt compatible with cm13?
Click to expand...
Click to collapse
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
SpYneX_ said:
I searched on google and disable the firewall could be a solution.
Click to expand...
Click to collapse
Could you test it?
TimSchumi said:
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
Could you test it?
Click to expand...
Click to collapse
How could you even disable a device's firewall?
Well, i just red here "https://forums.oneplus.net/threads/official-cm13-nightly-builds-rolling-out-for-opo.411202/page-103" that its may be fault of the recovery. I dont think that we all got the same twrp though, is something you can test? i used santori's twrp, i had it flashed quite a time. maybe an update or a modification will solve that issue
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
I also could try to make CM Recovery first, and if it won't work, I'll give TWRP a try.
Abiti7 said:
Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!
Click to expand...
Click to collapse
I still need to search what causes the Internet and SD Card to fail. Bluetooth does work, only Bluetooth Calls, Car connection and other devices are untested.
You can subscribe to this thread or subscribe to the DevDB project, to get a notification if it's updated. To get updates on your Smartphone, you could install XDA Legacy (Tapatalk) or XDA Labs (just called XDA) from Play Store.
john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
CM Recovery didn't fix the problem. And I somehow can't get TWRP to boot.
Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?
tanush said:
so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?
Click to expand...
Click to collapse
I don't think, I'm sure it's not supported because I put the codenames on github and P2c72 is not in the list. No problem if you want to multiboot I'll add it in no time. You can flash all the roms available here for p2a42 on your P2c72 just fine by removing the first lines "assert get prop" in the updater-script. You can flash these roms the usual way via twrp. But if you use the DualBoot Patcher as for now it won't recognize the P2c72.
911-Future_Maker said:
I don't think I'm sure it's not supported because I put the codenames on github and P2c72 is not on the list. No problem if you want to multiboot I'll add it in no time.
Click to expand...
Click to collapse
Cheers! My phone is on the way from china. Might be another week or so Right now just browsing everything that we have here.
Thanks for this. After so many ROMS ported recently, this would really help me out with having one stable daily driver and others to try to. Not an android developer but I'd like to try my hands as well finally to make a ROM and maybe look into the two bugs that are persistent across all ROMS. Let's see. I've just developed apps for now.
Anyways, thanks, this is indeed good stuff.
Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?
911-Future_Maker said:
Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?
Click to expand...
Click to collapse
yes, thats the only reason I had to get it from china. Apparently, only 32 gb version is available outside china.
Thank You Bro
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?
tanush said:
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?
Click to expand...
Click to collapse
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.
911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
911-Future_Maker said:
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.
Click to expand...
Click to collapse
Sorry brother didn't go through as I can't actually do it. Still waiting on my bootloader :/
So anyone had any success with p2c72?
I tried, but it fails. Doesn't throw any error but gets stuck in the boot and eventually reboots in twrp.
My only doubt is how does it know that the phone is p2c72? The build.prop says p2a42 so does the app thinks that its p2142 and wrongly patch it?
Is this just for experimenting or is there any advantage using 2 os same time? Isn't this can be cause a heat problem because of the more cpu/ram usage?
Can't find supported version of app! Can anyone here help me out wuth version?
---------- Post added at 04:29 AM ---------- Previous post was at 04:20 AM ----------
911-Future_Maker said:
Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
Not able to find the version as mentioned. Tried newer version but not supported.
Multuboot log uploaded.
What to do for setting up kernel in 2nd step?
Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it
muniphs said:
Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it
Click to expand...
Click to collapse
Try different version.
kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse
muniphs said:
kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse
I had tried r201.
Click to expand...
Click to collapse
During the last few months I have been testing several Nougat rom/kernel/modem/su combinations for the hlte N9005 international.
I created this thread to share my setup, hoping it will help others to save the many hours of research, trial, error and frustration I had before reaching the jackpot.
I have 3 hlte phones at my disposal, two myself and one my wife. All three are running trouble free.
By using my setup you will get:
Absolutely no freezes, reboots or FCs
Stable root and Safetynet checks ok
GPS fast and stable fix - average 5 seconds worst 20 seconds
Low battery drain (of course actual drain depends heavily on your apps and usage)
Everything works (AFAIK - you tell me what does not)
Keep in mind my main goal is to provide a stable setup. I will do my best to update this thread regularly, but it is very unlikely I will be using the very latest builds available, mainly because before I adopt a new build it must be thoroughly tested.
If you're interested head to the guide in Post #2
Why Resurrection Remix?
RR has, IMHO, the best combination of features and stability. The RR team has been around for a long time without the ups and downs of other roms. For the Note 3 we are in a very fortunate time, with an official build and many unofficial builds to choose from.
Since RR is based on LineageOS, it is available for most devices. It is very likely when we finally retire our Note 3 and move to another flagship, RR will be there for it.
Why Not Oreo?
Well, thread title says it all.
Credits and Thanks:
@vidwhal for the current RR build
@gj86 for Synergy kernel
@Jairus980 for Xenial kernel
@Hereiwas and @jcadduono for modems and bootloaders
@topjohnwu for Magisk
@stangri and @kantjer for Magisk unofficial daily beta builds
@Deic for the Safetynet fix Magisk module and @NovelliJack for finding the module
@MastahF and all other contributors that made the Open GApps project possible
Special thanks to @tarkzim for the RRN build used in initial setups.
and everyone else I forgot to mention.
>>>>>>> I know - screenshots below are from a previous setup. I will update then sometime in the future.
Rock Stable Setup
Using Resurrection Remix
Revision 11 - 11-Mar-2018
Phase 1 - Prepare for install
Here I am assuming you have a Windows PC. If not you will need to use google search to adapt my instructions to your available OS/hardware. The PC is only required for this phase.
1 - Samsung USB Driver:
Make sure you have the Samsung USB driver installed in your Windows PC.
If not download and install the latest driver:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.65.0.exe
2 - Odin:
If you do not have Odin, get it here, unpack to any folder and create a shortcut pointing to Odin3 v3.09.exe.
There are newer versions of Odin, but they may have issues with our Note 3. Odin v3.09 is the one to use.
3 - TWRP
New to TWRP? Read this guide: TWRP: the complete guide to using Recovery on Android.
If you do not already have it, install TWRP 3.2.1-0. Download it from https://dl.twrp.me/hlte. More info here.
If you no not have TWRP installed download the .tar file and flash with Odin.
If you have an older version download the .img file and use your current TWRP to flash the image into recovery partition.
4 - Update Bootloader and Modem:
You have to install latest Nordic Countries Bootloader and Modem. I have prepared a "tar.md5" with both.
And yes, modem is not country or region dependent. Rest assured Nordic will work no matter where you are.
Get it from here: N9005_Nordic_XXUGPQB1-Modem_XXSGBQD1-Bootloader.tar.md5
Updating bootloader and modem is a must!
If you don't you may get the "SIM Card not detected" error and GPS fix will be slow or not work at all.
There are many sure ways to flash modem and bootloader so that they "stick". What always works for me is:
- Restart into Recovery (TWRP)
- Select Reboot->Power off
- Turn on directly into download mode by holding Down Arrow+Home+Power at the same time
- Connect phone to PC
- Flash with Odin using the AP slot
Now you should check if update was successful. The best way is to install the app Phone INFO, run it and select the Firmware tab. The correct Bootloader and Baseband (modem) above should be displayed. There is a screenshot in first post.
If the update did not work repeat the steps carefully until it does. You may, as a last resort, after powering off remove the battery, wait for about 30 seconds, reinsert the battery and then turn on directly into download mode.
Thanks to @Hereiwas for the files I have used in previous setups. Check out in his thread Bootloader and Baseband for SM-N9005.
If you need more info on flashing modems and bootloaders also take a look at @jcadduono thread [Direct Download] Latest Bootloaders & Modems.
PHASE 2 - Download the necessary installation files
1 - Resurrection Remix Nougat rom - thanks @vidwhal:
Download from here: RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip.
Please note that I am not the rom builder or developer. All credits go to @vidwhal and the RR Team.
This is the rom thread: [ROM][HLTE][UNOFFICIAL][OMS]Resurrection Remix N.
Please note this build may not be the latest available. The goal here is to have a stable rom that you will be able to use as a daily driver with no issues for a long time. Only after a lot of testing a new build makes into my setup.
I modified the zip to remove Magisk. This will make it easier to use newer or beta Magisk builds if necessary in the future. Remember Safetynet is a cat and mouse game and changes happen fast.
Special thanks to @tarkzim, who produced the RR builds used in earlier setups. He did a fantastic job of producing a very stable build without a Note 3 device for tests. His builds led me to create this thread.
2 - Magisk v16.0 Official - thanks @topjohnwu):
Magisk Installer: Magisk-v16.0.zip
Magisk Manager: MagiskManager-v5.6.1.apk (optional - you might need it in the future)
Magisk Uninstaller: Magisk-uninstaller-20180222.zip (optional - you might need it in the future)
if you decide to use newer builds do it at your own risk. I strongly recommend to keep these.
3 - Gapps:
Open Gapps Pico: open_gapps-arm-7.1-pico-20180311.zip
Not much to say here. Open GApps FTW.
Again the above build is the one I tested. Use this for a failproof installation, but feel free to use a newer build. Usually it will not be a problem.
I prefer Pico Gapps so I have the bare minimum as system apps. And I live by the KISS Principle. All other gapps I need are installed as user apps so I am allowed to use Titanium Backup to backup/restore them with data.
If you would rather use another Gapps package just pick the one you want. All packages should work but the Aroma. Aroma does not work in TWRP 3.
4 - Xenial Kernel - thanks @Jairus980:
Xenial Kernel: [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
Kernel thread: [Kernel][Xenial][Hlte].
With Xenial you have some fixes like the correct charging current in lock screen and working Gravity, Linear acceleration and Orientation sensors. Of course there is a lot more under the hood. If you plan to do some kernel tweaking Xenial offers more options.
If you do flash Xenial kernel do not report any bugs in RR thread. To report a bug you must first go back to stock kernel by dirty flashing RR and Magisk. If you are still able to reproduce the bug then you may post it in RR thread.
Even if there is a newer kernel release, you should keep using the build I posted here to have my tested stable setup.
Special thanks to @gj86 for his Synergy Kernel, used in my previous setup. It is also a great option.
5 - GPS Fix:
In this setup there is no need for a GPS fix. GPS is fast and rock stable as it should always have been.
But you really must update your modem to my recommend Nordic QB1 or GPS will be slow or not work at all.
Do not worry about your current location. The modem will work not matter where you are.
Latest RR builds somehow made GPS fix slower. I checked the gps.conf file and it is exactly the same as in previous builds.
I have my own optimized gps.conf, prepared originally for Marshmallow CM13, with a few more adjustments for Nougat.
After installing my gps.conf in latest RR build, gps fix is back to normal, taking only a few seconds.
I prepared a flashable zip to install my gps.conf. It saves existing gps.conf and put mine in its place.
Download it from here: Fix-GPS-for-hlte-la14.1-based-roms-v1.zip.
PHASE 3 - Backup!!
Now it is time to make backups of your current setup.
Use TWRP to make a nandroid backup. You will need it if something goes wrong. If you are paranoid like me make two and save them on your PC hard drive.
If you use Titanium make also a Titanium full backup. Remember that you should never restore system apps or settings. Use Titanium only to restore user apps and xml backups of wifi passwords, call log and sms messages.
The steps to install the new ROM will not erase your internal storage, but why not make a backup of everything to your PC or an OTG USB Drive.
PHASE 4: Install
- Make sure you have updated TWRP and your bootloader and modem as instructed in phase 1
- Make sure you have all files downloaded from phase 2 in your phone - preferably in external sdcard
- Make sure you have backups!!
- Reboot into Recovery (TWRP)
- Use advanced wipe to wipe System, Data and Cache
- Flash RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip
- DO NOT WIPE ANYTHING
- Reboot System (be patient - it will take a while, around 3-4 minutes)
- Pick your preferred launcher
- Check Settings->Date & Time and make sure it is ok
- Reboot into Recovery (TWRP)
- Flash [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
- Flash Magisk-v16.0.zip
- Flash open_gapps-arm-7.1-pico-20180311.zip (or the one you prefer)
- DO NOT WIPE ANYTHING
- Reboot System (this time it will be faster)
- Go to Settings->Accounts and add your google account
- Customize your other settings
- Run Magisk Manager and check if SafetyNet passes
- If not disable/reenable "Magisk Hide" option in Magisk Manager Settings and try again
- Restore/install apps/data
- PROFIT!
[Reserved]
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
tarkzim said:
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
Click to expand...
Click to collapse
Sorry, you are absolutely right.
Thanks for being cool with it.
The main point in changing the rom zip is removing the magisk manager system app. It is a little tricky for noobs to remove the system app to be able to install the v5 beta Magisk Manager.
And thanks again for making your fantastic RR build available.
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
sperug said:
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
Click to expand...
Click to collapse
This does not happen in my phones.
In my work phone I have 600+ apps installed. It takes a while to open but no crashes.
If you post a logcat I may be able to help.
I reinstalled everything, and before made a full wipe, also of the internal storage. And the problem was no more present! Wow! And thank you again...
I checked AFH and have 30+ downloads of installation files.
Any more success or failure cases? Please let me know.
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
BobbyKa said:
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
Click to expand...
Click to collapse
AFAIK it should work for you no matter where you are.
I live in Rio de Janeiro, Brasil and use it.
If it does not work for you just flash another one.
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
BobbyKa said:
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
Click to expand...
Click to collapse
To use Sammy Spen apps/features you need a Touchwiz based stock rom.
There are some apps with similar features for AOSP roms.
Many users say the best is SPenCommand developed by @emandt. It is paid but users say that the app is well worth the price.
Check the SPenCommand Google+ Comunity.
Great post. I don't see google assistant working, any clue?
Sent from my Pixel using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:10 PM ----------
Please ignore, I installed nano gapps and it worked
Sent from my Pixel using Tapatalk
what about battery life ?
has anyone tried this on Sprint Note 3 sm-n900p ?
svbarbosa said:
Check the SPenCommand Google+ Comunity[/URL].
Click to expand...
Click to collapse
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
BobbyKa said:
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
Click to expand...
Click to collapse
I have never used SPenCommand myself. Just read good things about it many times in other threads. Try to search and get help from people who are using it.
You may also check these apps: Note Buddy (S Pen Helper) and CM S Pen Add-on(ROOT).
And this guide on them: The Ultimate S Pen Customization Tool for Your Galaxy Note 3.
But be advised that I have no experience using these apps. Just found them using google.
opexblue said:
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
svbarbosa said:
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
Click to expand...
Click to collapse
Thank you for fast response. I will try other kernel.
Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.
Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"
Or simply join the telegram group.
Peace.
Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol
Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.
Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.
Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery
Update:
Added Magisk news;
Added stock PRA ramdisk
UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?
Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.
The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot
How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka