Hello!
Long story short, me and a few nice guys from Russian 4pda community have cobbled together a fix for Elephone's encryption.
As a free bonus, we also added in pretty decent early initd script support (Selinux is temporarily switched to Permissive until all scripts are done executing, so it's considerably more powerful than some "vanilla" initd solutions out there)
It also includes Root and basic busybox binary
Procedure is as follows
First, you need to flash a custom recovery (TWRP will do)
Then you need to apply "data partition size fix" to ensure encryption can engage
The fix is here.
http://ge.tt/5rTpLXN2
Apply it via install zip function of custom recovery.
Next you need to flash custom boot image and crutch files.
The zip is here
.
http://ge.tt/9ET9wXN2/v/0?c
Flash it the same way (install zip from custom recovery)
Now you can:
1) enable encryption (Settings->Security) as it should be on all standard Android
2) run shell scripts at early startup (place them in /system/etc/initd/ ), just make sure that they are a) shell scripts with .sh extension b) readable writabel and executable for root user
Some notes on encryption
* Make sure to back up important data before initial encryption - failures are unlikely but still possible
* Charger MUST be connected during initial encryption
* Encryption of a "freshly reset" phone takes no more than 30 mins, may take longer for in-place encryption of large amounts of data
* if the phone hangs during initial encryption, usually pulling out battery doesn't hurt and you can just re-try encrypting (second time is the charm usually)
* sometimes, initial encryption fails (phone reboots, remains unencrypted). This is not a dangerous problem, just try again!
* if the phone hangs on password entry screen, just press and hold power, phone will reboot
Special thanks to rublix, m4sk, and other great people of 4pda.ru !
P.S.:
If Ge.tt links die, you can find the links to zip files in my 4pda post
http://4pda.ru/forum/index.php?s=&showtopic=669808&view=findpost&p=42783990
Oddly enough, initd works only when encrypted, when unencrypted Selinux seems to interfere early on. Wonder why. Will keep working on it
Hi there,
I had kinda trouble today skipping the "Verify your account" after a recovery Factory Reset.
Long story short, a collegue's daughter locked her phone, and he had to perform a factory reset from recovery.
Since she changed her phone number and lost her password, no google's account recovery were possible.
After a week of trial and error, he decided to let me take an eye.
As you know :
- If you perform a factory reset with recovery, a google's anti-theft feature, called Factory Reset Protection, occurs and force you to login once with a google account that was previously set on this phone.
- If you perfrom a factory reset with android built-in (Settings -> Backup and restore -> Factory reset), you won't encounter this issue.
- If for a reason or an other, you don't know the required credentials, don't have unlocked your bootloader and never checked "Allow oem unlock", you're kinda screwed.
Here is how I figured a way to bypass this feature (BTW, I won't post any link this I didn't wrote any of theses tools. I juste figured a way to use them) :
Disclaimer :
I have not made any of the tools or adb command.
I can't be held responsible for any damage done to your phone.
Don't use any of theses instructions if you don't know the consequences.
Use theses instructions/tools at your own risk.
I achieved this bypass by search and trial.
English is not my native language. Name has been translated and may not be accurate. However, I'm sure you'll find what I meant.
1) Install minimal ADB and fastboot (Google that)
2) Install Motorola's USB drivers (Motorola's website)
3) Power on your phone, set-up a wifi connection.
4) Return to the Wifi wizard, choose a connection you do not want to connect to. Check 'Show password" and enter a random password.
5) Double press the text, choose "Share".
6) Long press "Gmail", you'll be redirected to Gmail's settings.
7) Press "Notification" then "Application settings"
8) Press Option (3 dot menu) then "Manage account"
9) From there, you'll sucessfully enter phone settings. Unlocking the "Developper option" won't work anyway.
10) Press "Users" and create a new one. Don't set it up ; instead, log in the newly created user.
From there, it was Trial and Error and I, somehow, managed to allow Developper option.
11) Try various things such as : Enabling developper option from new user ; Switch to owner and try again ; Open an app and return to settings with the little square (suspended app) with owner and new user.
Search anywhere, be patient, try various things, it'll work somehow ...
From a certain point, you'll be able to unlock the Developper option.
12) In Developper Option, check "Enable USB debugging"
13) Open a cmd in Windows, navigate to the adb folder. Type in the following command :
Code:
adb devices
You should be able to see the phone. If not, ensure you have the correct drivers (From device manager).
If your phone is detected, type in the following command :
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Thanks to : Matthew Read (android stackexchange)
14) Perform a factory reset from settings.
15) Optionnal : After phone reboot, enable Developper Option, check "Allow OEM unlock" to allow future bootloader unlock and flashing.
That should do it.
Step 11 is very vague but I spent few hours unlocking this phone and I did LOT of things. I spent 1 hour or so on this step and forgot what I precisely did to unlock this option.
If you manage to succeed, please post your instructions.
I WON'T relock the phone in order to discover exactly what worked.
This won't work for long, since this is a security fault and will be patched (as every previous bypass) sooner or later.
Be patient and be curious ! Have fun
Don't waste time here.....
Already Video available on YouTube...
My friend got Moto X Play and after update to Marshmallow he formatted his SD card as internal storage. However, without any apparent reason, phone stopped to recognize the card as internal-formatted: after inserting it, in Storage and USB settings section "Checking..." is displayed and followed with "Not inserted". After clicking the card entry it gives option of forgetting encryption key, which I don't want to do - my goal is to recover data from the card which was encrypted by the phone.
I wanted to follow guide below to recover encryption key and decrypt card on the computer, but there is significant problem about it - phone is not rooted and bootloader is locked. I can't unlock the bootloader, cause encryption key would be wiped with the whole data partition.
http://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html
Cause I know C and basics of POSIX programming, I've tried to use Dirty Cow exploit (https://github.com/timwr/CVE-2016-5195) to replace run-as binary with my own, that included low-level POSIX C instructions of copying content of /data/misc/vold to temporary partition from which I could do adb pull to the computer. And indeed, exploit succeeded in replacing binary and after running it from adb shell, run-as process outputs UID 0, which means it's run by root user. However, SELinux is set to enforcing, which apparently doesn't allow me to access /data/misc/vold even by a process with elevated privileges - any attempts of opening the directory in C end with file I/O functions returning error codes.
My question is - is there any method available to our X Play with Marshmallow that allows for at least temporary root so that I can copy encryption keys to the computer? I tried to find another exploit root based on Dirty Cow, but all I found is just proof of concept stuff. I've tried rooting apps like KingRoot or Kingoroot, but they don't manage to get root.
Phone system specifications:
Android version: 6.0.1
Android security patch level: March 2016 - thanks to it it's vulnerable to Dirty Cow, which was fixed in December 2016
System version: 24.61.52.lux_reteu.reteu.en.EU reteu
Build number: MPD24.107-52
Hello,
I remember when i set up A1 in firstboot, it asked if i want to be prompted with a password before booting android, to which i said no.
So this in effect, must have encrypted with the default password on first boot. This lets the system boot, and core services started, if the device gets rebooted
without my knowledge(so that i recieve calls and sms) VS, if it asks password before booting(uses my pin as password instead of default password), the core services arent available untill i put my pin in.
This issue was supposed to get solved through Nougat's FBE.
So my question is that, does Mi A1 uses FBE, so that even if i had opted for my pin as password before booting, i would not be blocked of using core services like phone and sms, with OS waiting at pin prompt?
Thanks.
as i have researched more, A1 does not support FBE.
read this excellent writup
In the above article, it shows how to convert to file based encryption. This option in the developer settings is missing from A1.
this is the first major disappointment with A1. Was shocked on system setup to see this. Didn't expect this from a phone expected to receive updates upto P.
ashjas said:
as i have researched more, A1 does not support FBE.
read this excellent writup
In the above article, it shows how to convert to file based encryption. This option in the developer settings is missing from A1.
Click to expand...
Click to collapse
Why do you think ? What encryption does it use ?
It uses FDE. This can be seen when you reboot the device - the black background and basic keyboard. This is FDE.
FBE would boot the device in an intermediary state with wallpaper, full keyboard.
Now if you ask me FDE seems a bit more secure - you can be sure that everything on the device's data partition is encrypted and the only available function is emergency call.
FBE encrypts certain folders but more code is running at startup so you can in theory receive notifications and stuff for certain apps. I certainly don't need stuff running before i authenticate.
gradinaruvasile said:
It uses FDE. This can be seen when you reboot the device - the black background and basic keyboard. This is FDE.
FBE would boot the device in an intermediary state with wallpaper, full keyboard.
Now if you ask me FDE seems a bit more secure - you can be sure that everything on the device's data partition is encrypted and the only available function is emergency call.
FBE encrypts certain folders but more code is running at startup so you can in theory receive notifications and stuff for certain apps. I certainly don't need stuff running before i authenticate.
Click to expand...
Click to collapse
So when the phone was set up in a way, where there was no password asked during (in the middle of) the boot process, how easy would it be for thiefes to access data stored on a A1 ? And how much would it help them if bootlocker was unlocked ?
When you reboot the phone, and you do not have a FDE password set up, the phone still asks for a PIN aftrer booting, with the text "Unlock for all features and data". This sounds like FBE to me.
- PIN is probably from the SIM card. My A1 never asked anything until i set up a password. But mine came with Android 7.1.1 so it is a possibility that some to come with later versions (that have FBE?)?
- FDE is usually enabled anyway on Android 7.1+ but it has a default password set ("default_password" AFAIR). So if you run TWRP for example, even without installing it,it will acces your data because it knows this default password. If you specify a custom password the disk will not be unlocked without it.
- A locked bootloader brings additional security. The idea behind it is to have a verified boot chain - if someone gets hold of your phone to not be able to flash custom system apps on it.
The partitions are checksummed and verified via dm-verity. So at boot time any unauthorized alterations (done, say, with booted TWRP, installed Magist and root then re-locked bootloader afterwards) will trigger a "System Destroyed" message.
The above will be all disabled if you unlock the bootloader and install TWRP. As for now TWRP (or any other loader) cannot ensure system consistency. It is possible to flash stuff on your device by restarting it and launching TWRP. If you have a strong encryption password set up your data partition will still be inaccesible to them but if you get your phone back and start it up the malware will start and do nasty stuff like siphoning all your data, passwords etc (because you can flash system apps that can see everything on the device).
After restart, it asked me for a PIN and then for SIM PIN, (even when draw pattern was my configured way for unlock). It never again asked me for PIN, only right after reboot. Why else would I be asked for a PIN only after reboot, if not because of FBE?
A Noobs guide to Galaxy Note 4 Verizon Motherboard Hardware repair and replacement
and Other Samsung Galaxy Note 4 repair ( Att, Tmobile etc ) starting in thread 2 ( user input welcome )
My Overheat Heat and flash problem issues leading to
OEM Motherboard replacement and acquiring ROOT again
OP Note : read the whole guide or for that matter any OP
Thanks to many XDA-Developers forums, if you are not quoted or mentioned here I will add you !!
Device : Samsung Galaxy Note 4 Verizon SM-910V this OP ONLY !!!
Code:
[COLOR=Red][B]Your warranty is now void.[/B][/COLOR]
*most likely you don't have a warranty because you broke it, ROM'd it, its old and past warranty anyway !**
So, There is no warranty anyway, not even if you did anything in this thread to it
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or your getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this guide
before flashing it! (thanks @hsbadr)
YOU are choosing to make these modifications, and if
you point the finger at anyone for messing up your device, we will laugh at you
Symptoms : ROMs not flashing/installing , crashing, High heat, low battery life on new battery hardware note working specifically fingerprint.
Problems : digging through many forums 2 years later to root and unlock the bootloader, it took DAYS
Solution: keep track of my progress and make a useful step by step NOOB guide for Everything !
Section 1: Repairs
Then the rest of the sections are for Rooting, Installing TWRP custom recovery, fixing bootloader , and installing ROMS
Section 2: Flashing via ODIN and the correct rootable OEM rom 5.1.1 on a windows PC
section 2a: Flashing via Heimdall on a Linux device --need comments
Section 3: Achieve temporary root to install bootloader fix
Section 4: Use of ADB to (windows and linux ) to copy over bootloader fix
Section 5: install TWRP custom recovery and your first rom
Section 1: Repairs
If you have to replace the motherboard, and you have any other futzy component, might as well order it at this point, your going through pretty much the same process. I am only doing the motherboard, but the cameras and USB board are right there as well on this repair
I have been running a rooted Verizon Galaxy note 4 since Cynogenmod crashed and switched to Lineageos 14 and then 15.
Here is the forum
https://forum.xda-developers.com/no...eo-8-1-0-unofficial-lineage-15-1-rom-t3760969
After several suggestions and searches, many users hinted I may be getting a Bad internal memory,
which refuses to write anymore.
So I had to go to Walmart and buy a LG Straight talk phone to use as my daily driver,
Then I ordered a new motherboard from China, 29.00 on Aliexpress.
See OP thread #2 below!! It was not fun searching for it, but I saved $20 to $40 from buying on ebay
What I bought may not be available from this seller, but here is the link. Use a desktop browser, it will show "suggested" other devices...
Code:
[URL]https://www.aliexpress.com/item/with-Android-System-Original-unlocked-for-Samsung-Galaxy-Note-4-N910V-Motherboard-Good-Working-Free-Shipping/32802513232.html?spm=a2g0s.9042311.0.0.66e04c4dpohrQm[/URL]
When I received it , it was time to look for a repair procedure on YouTube.
Hardware needed: thin shim and 00 size phillips, AND a blank cheap SD card you don't mind losing. It may be unusable after we are done
Cell Phone repair tool kit really helps save your fingernails !
Complete note 4 teardown video:
Code:
[media=youtube]ZND9Q73wjr8[/media]
Just the Motherboard video
Code:
[media=youtube]5KpT755hNpM[/media]
In the second video, you can see the phone booting up as a test to see if you have all the connections correct.
Because it came from china, its a good idea to setup your user and
download the app CPUz before you put all the screws back in,
and check to see if you have a real or fake chipset.
Yaayyyy mine was real . Thanks Aliexpress.
Button it up and do a factory reset (it booted up set up as a no user) so I wanted a fresh install oem with my user.
Section 2: Installing the Correct rootable OEM rom so we can install Anything else.
FIRST check to see if you have the emmc brickbug or you will BRICK it !!
1. Google play store install eMMC Brickbug
If your long number starts with 15xxxxxxxxxxxxxxxxx, YOU are Golden ! if not STOP, get another board ! or you are going to waste time , and get another board !
The Galaxy Note 4 Verizon had a special custom locked bootloader installed after the 4.4.4 release to 5.0.1 and made it very difficult to get
root access to your device.
I saw the notice
DON'T UPDATE YOUR BOOTLOADER TO ANYTHING AFTER THE LATEST BUILD AS OF 4/19/16
warning about a week to late. So I finished out my 2 year contract and watched the forums.
Seriously noobs, don't update your new motherboard ...
The rom pre-installed on my replacement motherboard was already setup booted to a running 5.0.1 oem rom, I could not root it.. with any method I remember downgrading my 6.x.x to 5.1.1 in one of the many forums listed here at XDA
This one was the one I used back then, and It turned out that is where I started..
Only a Verizon Samsung Galaxy note 4 Developer Edition has the ability to install custom roms, and most likely the motherboard you bought or have is NOT a developer edition
IF you have a eMMC that starts with 15 we can reprogram it a developer edition
Thanks to @hsbadr
Here are most of the downloads we need:
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
2. Download Odin, Download TWRP, and Samsung_unlock_n4-fix
3. On your windows PC, create a folder c:/Odin and extract the Odin zip file there, and copy the TWRP image there
4. Download the following OEM root able ROM to your c:/Odin folder
Code:
[URL]https://forum.xda-developers.com/devdb/project/dl/?id=18880[/URL]
5. Plug your phone into a USB port on your Windows PC
6. Install the necessary drivers if they don't automatically install from Samsung
Code:
[URL]https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows[/URL]
7. Set up your phone for flashing ROM and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Power Off phone
Enter Download Mode - press and hold in this order <down arrow> <home> <power> until screen comes on. release buttons.
press up arrow to enter download mode
8. Open windows explorer and go to your c:/Odin folder. You should have an odin exe file, and the twrp file, and the large rom file.
a. right click odin exe and open as administrator
b. check to see if your connected to your phone. you should see a blue box in upper left with a com under it.
If you unplug your phone, you should hear the disconnect notice and the com and blue bar will go off, and when you connect, the com and blue bar and reconnect noise should appear.
9. click the AP button box, select the ROM file that you downloaded above.
NOTE : this ROM will disable WIFI so you wont be able to use the play store unless you have cellular connection.
you will have to transfer other files via usb cable !
Click start, do not unplug! until it stops.
10. Device will reboot. Remove cable, and battery before boot completes
11. Enter recovery mode . Press in order ,<volume up><home><power>
wait for the little android dude to do his thing, then there will be a menu. select factory reset, and reset and let it reboot
Set up minimal user or as a new phone with no user and check the settings in step 7
Set up your phone for flashing roms and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Yayy, you now have a rootable device
Section 3 Achieve temporary root to install bootloader fix
In my try to obtain temporary root, I tried every method in all the forums ( go ahead and look and try )
The only 2 programs that reported to work is Kingroot, and Kingoroot. These are APK's that are NOT in the play store
you will have to download them and install them as unknown sources. I was only able to install kingroot . Kingoroot apk would not install
in both my 5.0.1 original on my motherboard, as well as what we just installed 5.1.1 I was unsucessful at obtaining root with these programs
Then I remembered Kingoroot has a windows version that installs on the PC <dangerous dont install yet>
On your PC you will need AVG antivirus to catch the malware ( other antivirus may work but this is what I had ) my PC is windows 7 ultimate
Advanced Users only :Recommend running a virtual machine with windows so as to keep your PC completely malware free. just delete the VM after this process !
This section you will need on your Note 4 from the Play Store : root checker
You will need a throw away SD card
You will need read through section 4 and 5 and get all files and programs there ready to install use and or transfer
0.5 update your AVG
1. With AVG installed on my PC, and my phone connected as a mtp with usb I downloaded and installed Kingoroot for windows.
https://www.kingoapp.com/
NOTE after not being able to install forum recommended kingoroot apk's i dint want wast time install the newest kingoroot apk from the website. Maybe it will work for you. If you do get kingoroot apk to work on your Note 4 let me know.
2. In the install process for kingoroot windows version AVG will quarantine a file.
there will be a couple popups .. close them
when its installed it will open and start talking to your phone.
3. press the root button.
It will take 30 sec to a minute to install some files on your phone and achieve root, there will be a new floating toolbar on the phone. root will disappear after a reboot, but not the resident programs this root is pretty stable, but i was not able to install SuperSUME (paid version ) as recommended in a XDA guide to obtain permanent root for this 5.1.1 rom. If your successful with super SUme with this let me know.
4. Open root checker to verify ! yayy.
5. Cleanup instructions when finished with this guide below
Section 4: Use of ADB to (windows and Linux ) to copy over bootloader fix
1. Your Note4 phone should be running with root, make sure phone is connected
Explanation : ADB is a Google provided tool for the android platform. It communicates with your phones operating system , transfers files , and actuates programs remotely in the background. totally necessary for development of ROM's, TWRP, and programs for every android device
You may or may not know that your android device is running a Linux kernel, with some Linux programs, with custom folders and custom files and settings, and the touch screen is the GUI graphical user interface touch input.
ADB is a command line user interface, when you turned this on in Developer settings, the kernel is listening constantly on the USB com port and some times on the WiFi com port for commands. if you don't need it turn it off, it could be a security hole, but we need it on.
It works great on windows, mac, or Linux varieties
2. Install on your computer
Code:
[URL]https://developer.android.com/studio/releases/platform-tools[/URL]
If you have linux, your distribution may have a package you can install from your distribution. Then it will be in your path as a command
3. Windows users , extract or install into c:/ADB and add that to your PATH variable if you want to use it all the time as a command
4. Open a command prompt window (search command or cmd , right click open as administrator)
5. If you have ADB folder in your path or are running Linux change directories to the folder where you downloaded the Samsung n4 fix file
6. You should still have root
type
Code:
adb devices
The ADB daemon ( little server program ) will start and return some information.
your phone will have a popup screen and should ask for permission, click allow
again type
Code:
adb devices
7. You should see something like this
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device.
If you see something listed like the above adb is working. Now on to the next command to move the Samsung_unlock_n4-fix to the phone.
type dir ( or ls -al for Linux users ) to verify Samsung_unlock_n4-fix is in your directory
8. Send Unlocker to Phone with adb
Type or copy and paste the following command:
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/
You should see successful output .
If you don't, check your PATH, check if your in the right folder, or make sure samsung_unlock_n4-fix is in your adb folder
9. Activate the unlocker. This requires root and a reboot. After the reboot you have to go and reactivate root in Section 3.3 above
type the following
Code:
adb shell
Congratulations you are now looking at the linux command line interface on your phone . the $ prompt means you are in the shell
10. activate superuser mode ( kind of like administrator in windows but more powerful )
type
Code:
su
then press enter key
YOU SHOUD NOW SEE a # prompt
This means you succeed in root. If you dont see a # you missed a step above somewhere , or your root was unstable and took too long to get to this point,that is why I said read thru this section and get ready..
Ok at this point we have the file we needed transfered, we have root, now we need to upgrade the permissions on the file so #root level of the operating system can use it !
The next command does all that then executes the command to upgrade your phone to developer edition !
Copy and paste the following command series and press enter.the && joins each command
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
The device will reboot and flash the developer code.
You should see some sort of progress in the window.
When done ,unplug the cable and pull the battery to shut down phone.
11. Make sure you have a cheap throwaway SD card installed !
One More Time to unlock the boot loader !! section 3 and 4 short version
Put the battery and cable back in and turn the phone back on and make sure its plugged in your PC.
Now repeat the kingoroot PC to gain temp root
open a command prompt or shell
type or copy paste the following to verify its connected
Code:
adb devices
transfer the fix
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/ && a
open the shell on your phone
Code:
adb shell
gain super user rights
Code:
su
unlock the boot loader
same command series
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
You will see your phone do a series of outputs then reboot. when it reboots, disconnect the cable.
If this step is sucessful your phone will keep rebooting. This is NORMAL . after the first or second reboot, pull the battery and pull the sd card, and set the sdcard aside. It will need to be thrown out or repartititioned to be usable. or you can keep it as a memento on your charm bracelet.
Your bootloader is NOW UNLOCKED . keep phone off until you read the next section
Section 5a: install TWRP custom recovery
Currently right now you have 5.1.1 installed with some Chinese malware on your phone and PC,
A custom developer edition and an unlocked boot loader. Lets fix them all.
Turn on phone download mode . <down volume><home><power> then volume up to enter download mode
Open Odin again ( see above )
Connect phone ( look for com and blue bar )
Select AP button, and browse to TWRP file
Press start. when finished phone will restart.
Don't let it boot all the way back up! , pull battery, and install good SD card, and if you read this section you downloaded what you needed for a new ROM onto your sdcard
Turn off the automatic rebooting in the custom tab, DO NOT select the PIT tab
Press start
Once it finishes it will say Success or FAILED
IF it says FAILED start the whole process over! you didn't unlock the bootloader !
If success, Power off the phone with the pull battery method and disconnect your cable
Press and hold these buttons immediately to enter TWRP ,
<volume up> <home> <power>.
Swipe to allow changes in TWRP.
Select backup , change to SD card, You can also plug in a memory device into the USB port. If it sees it you will be able to use that for backup space
BACKUP everything . You now have a custom recovery installed, a unlocked bootloader, and a rootable ROM Backed UP !
If you feel you want to do this all over again if you flash the OEM Samsung ROM via Odin by accident like I did, ha ha skip the next steps
Select the backup button, select all the partitions, select the source, where you want to store it.
Name the backup rooted-backup-everything-5.1.1
Select start and go make some coffee or a sandwich. its about 4 gigabytes compression, so it may take about 5 to 10 minutes
Clean up -
uninstall windows kingoroot PC and do a virus check
check for hidden folders and registry entries
Section 5b. Install your first ROM
Cleanup : After your backup WIPE your phone twice
THIS IS TO guarantee, no Kingoroot or kingroot stuff is in the phone !!!
WIPE IT TWICE !!!
Some guides (listed below ) say to adb sideload over a root file , then install an older rom. I haven tried this. Let me know if you did and are successful.
Whatever ROM you use, please post a success story in the reply's. I am interested in how you all do.
I have tried every note 4 ROM and this is the most succesful for me and most stable
I have been using this ROM for a while, and the lineageos 14 version too
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
In most all ROMS, you can update the bootloader (TWRP) by TWRP app if rooted
you can update the modem ( a partition that contains original Samsung code to run the cell and wireless ) via ODIN
Roms and patches and other goodies can be installed via TWRP by downloading to your device or transfering them to your sd card
Oem ROMS must be installed via ODIN, and will WIPE all you just accomplished. so unless your selling your device, or giving it to grandma DONT.
If you copied the rom ( usually a zip file ) and the necessary files, and have upgraded your bootloader and modem to the newest,
Now install your ROM, and after your initial setup, come back to TWRP and do a full backup !
every time you try a new rom, and get it set up, do a backup. that way you can switch and test to your hearts desire till you run out of SD memory.
The cool thing is you can backup to an external memory device ! more room !
Follow the directions in the OP of your ROM to install. Enjoy
All the above info was gleaned from the following pages
Thanks to @beaups for discovering exploit !!!
Thanks to @hsbadr [HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910VVRU2CQL1]
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144[/URL]
and his files
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
Thanks to @ryanbg [Official] Note 4 Verizon Bootloader Unlock
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913[/URL]
and @urgodfather
Code:
[URL]https://forum.xda-developers.com/showpost.php?p=66381707&postcount=342[/URL]
Thanks to @chriskader [HOWTO] Converting your Retail Note 4 to a Developer Edition Note 4
and @Mickey387 for discovering how to compile the note 4 32bit hardware drivers into Oreo !!
and @_mone @ripee
for maintaining and working hard on
[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][trlteduos]
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
some of this was also posted on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked
Update:
Looking for a motherboard for a 910 that's not a v?
Thanks to user @maralexbar I need to update some info
Method 1 use eBay. Find your correct motherboard easily.
Method 2. Save some money use Ali Express ( China )
If you use Ali, and don't find your motherboard on a direct search, keep digging.
I forgot to mention this.
Looking for my Verizon motherboard, I found lots of parts like the USB internal connector etc. But no mobo. I had to go thru the store listing of the seller of the USB connector to find a vendor that had a mobo. Then I tried comparing different vendors. So do some digging. There is a billion people on Ali express selling stuff. Don't give up.
Plus Ali wants happy international buyers. So if you get a bogus item, you get your money back.
reserved #2
reserved #2
reserved #3
Reserved #3
reserved #4
Reserved #4
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
b1ggjoe said:
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
Click to expand...
Click to collapse
Your more than welcome
Announcement:
Thanks to @ripee
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.