Database Develop

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!

nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.

After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.

Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472

Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?

Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.

Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.

Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.

zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?

please fix dead links

dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.

please fix dead links

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1

After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now

lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.

[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient

[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location

lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone

server stilll unreachable.

Help a Noob: Rooting and installing ROMs

I recently started playing pokemon go and I am getting really frustrated while playing because it lags soo much and my phone is generally quite slow now. I have been told rooting and installing a good ROM can help with this and I have never attempted this, could someone please explain what rooting and ROMs are and their benefits and a how to guide for this phone and also the best ROM?
I know there are loads of threads on this but if someone could link me best threads I would be eternally gratefull!!

First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).

Hyoretsu said:
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Click to expand...
Click to collapse
Thank you soo much for your reply and sorry about my late reply. My variant is LG-D405n and software version is V20c-234-30. I think I understand what Root and ROM is thx.
So could you link me to the best method to root and install ROM on my phone?
And what is the best ROM for my device to free up the RAM and CPU used on my device to increase my phone speed?

First of all, install these required apps:
http://king.myapp.com/myapp/kdown/img/NewKingrootV4.9.6_C151_B309_en_release_2016_08_18_105203.apk (For rooting)
https://play.google.com/store/apps/details?id=com.cgollner.flashify (For flashing the Custom Recovery)
https://play.google.com/store/apps/details?id=jackpal.androidterm (For terminal emulation)
Custom Recovery:
TWRP: http://forum.xda-developers.com/devdb/project/dl/?id=18679&task=get
Personally recommended Custom ROM, CyanogenMod (Ports Android updates to older phones plus some tweaks) and Gapps (Google Apps, it's needed to have things like calculator, play store, etc):
CM13: https://download.cyanogenmod.org/get/jenkins/175208/cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J8-w7.zip
Gapps: http://opengapps.org/ (Go to this link, select ARM in platform, 6.0 in android and Nano in variant, then just click the download image button)
Put the TWRP img, the CM13 rom img and gapps on microSD or internal storage. Open Kingroot and click on the green button after the 3 introduction images. After a few minutes, your device will be rooted. Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Then, go to flashify and flash your custom recovery image (TWRP or CWM) in the flash recovery img option. After this, reboot into recovery by pressing Volume Down + Power and when you see the LG Logo, let go of the Power button and press it again. Then select yes two times with the volume keys for selection and power button to actually select the options (Don't worry, your device won't be factory resetted if you successfully installed custom recovery). Then, if you want, make a backup of your entire phone (recommended, just in case something goes wrong or if you just want your apps back when the process is done) in the Backup section and then do a factory reset through the Wipe option (Don't select anything, just swipe the bar). Select the Install option and select your ROM zip. After this, do the same process as the ROM installation but this time with Gapps zip. There you go, now you have CM13 installed. If you want root again, you don't have to install Kingroot again this time, as CM13 has built-in root, just enable Developer options and activate root and you're ready to go. Also, if you want the apps you had before the installation, just restore your backup (ONLY THE DATA PARTITION, otherwise CM13 will be uninstalled and replaced with stock ROM). If something goes wrong and you accidentally brick your device, just reply and I'll help you fix it. (If helped, click the Thanks! button)

Hyoretsu said:
Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?

Firebird3334 said:
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Click to expand...
Click to collapse
You have to change "(aboot.bin storage directory) with the directory in which aboot.bin is stored. And no, you don't need SuperSU, when you use the su command, a KingRoot window will open, just say yes.

EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?

Firebird3334 said:
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Click to expand...
Click to collapse
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146

Hyoretsu said:
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Click to expand...
Click to collapse
You have helped me out so much already! Thank you so much!
But just one more thing though, could you explain how to install magisk and xposed in layman's term so I can use Android Pay?

I don't know what magisk is nor layman's term, but to install Xposed just go to this thread: http://forum.xda-developers.com/showthread.php?t=3034811, download both Xposed installer apk and xposed zip. Install xposed apk and flash xposed zip

Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...

amonlb said:
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
Click to expand...
Click to collapse
First of all, you don't need to use that TWRP build, you can use the latest one. To fix the only errors that should appear (Updater error 7 and 6), delete the first lines of updater-script until you reach the ui_print part (the first line of your file should be "ui_print("Target: 1471683591");"). Also, delete any double spaces that exist (there should be two, one before "abort" at line 27 and the other before "abort" at line 30). If it still gives the same error, try wiping Cache, data, system and dalvik-cache partitions, try to install the ROM, it'll give the error. Now, reboot your phone and try to install without wiping anything. (To properly see the line indications, open the file using Notepad++)

[Dualboot Patcher]Full Guide For How To DualBoot Your Note 4 (EXY/SD)

Dualboot patcher 101
Device : Galaxy Note 4
Difficulty level : Easy
This is a full guide to understand and use Dualboot Patcher App​
Download latest app snapshot from : Noobdev
Files » DualBootPatcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
Latest as of Jan 8 2017
Install it like a normal apk
Dualbooting begins here ---
Main things to do are
Setup Dualboot boot enviroment
Setup Dualboot files
Flashing
Switch between roms
App sharing
Part 1
Setting up for first time use
-Open dualboot patcher app and do the following
-Go to Roms tab then click the 3 dot menu on "Primary"
-Press Set Kernel {if it didnt ask you at the beginning}
-Then press "Update RamDisk"
Part 2
Patching Files for dualboot
-Download the rom you want to dualboot / any mods for it / xposed or whatever flashableZIP you want to install on your secondary rom
-Go to "Patch Zip File" Press the + and click "Add Flashable Zip"
-Select your ROM Zip
-Select your Device (Trelte For exynos or Trlte For Snapdragon)
-Select "Data slot" in Partition Configuration
-The ID is your parition name , basicly SAME ID for zips = Same flash location, Type rom1 for example [No caps]
-Do the same for any other zips (making sure the ID is the excat same)
Part 3
Flashing
Once you are done patching files , you will end up with a duplicate collection of your original files, but they end with _data-slot-[ID].zip suffix
-Grab those files and go flash them in your recovery
-in the recovery screen you will see [Multiboot] prefix behind most scripts, that means you are flashing a patched zip
-Once you are done flashing just hit reboot from the recovery
Part 4
Switching
You will be greated with your new rom , do the first setup and you are now running your secondary rom
Now, to switch roms do the following
-Install your dualboot patcher app on your secondary rom
-Open it and go to "Roms" Section
-Suprise, you will see Primary and below it [ID] (Data Slot)
-Press the primary and reboot , thats it
Part 5
App Sharing
Lets say you want your app data to be available on all your roms , Whatsapp data , telegram data , game data etc
-Open the app on your primary rom , go to "App Sharing" Section and enable " Share Individual applications"
-Press "manage shared applications"
-Click on an app "whatsapp for example"
-Tick "Use shared data"
-Hit ok then Then go back after selecting all your apps
-It must show a toast saying "The changes will take effect next reboot"
-Reboot your device to the secondary rom and do the same thing for the same apps
App data is now shared across both roms,
F.A.Q please read before attempting this
1- Faild to set kernel due to unrecognized device
-Common issue with custom roms, you can fix it by editing your Buid.prop , changing device name , code etc and ro.patcher
2- Flashing files via recovery , will it affect my primary rom ?
- No , all the files are directed to your new rom enviroment , the only things that can affect dualboot is kernel changes
3- How to change primary / secondary kernel ?
-To change primary , just flash the new kernel , then follow " Part 1 " of the guide again
-To Change Secondary , Follow " Part 2 " of the guide to patch the Kernel zip then flash in recovery
4- Where are the files located ?
-your secondary system can be found under /data/multiboot/data-slot[ID]/System (only seen when you are using primary rom or Recovery file manager)
-Your shared app data can be found under /data/multiboot/_Appsharing
5- Enabling app sharing, my data for the app is gone.
-When you enable app sharing it changes the data location, so whatever data you had need to be moved with it, best thing to do is to backup the app you want to share with titaniumbackup (before enabling shared data for it) then restore it when you enable data sharing and rebooting
6- How many roms can i "dualboot"
-As much as you like aslong as you have storage in your data partition i had 4 roms dualbooted at one point
7- How much storage does it consume ?
-CM roms are usually around 1GB for system + few GBs for data (total of 3GB-4GB For normal user with some apps)
-TW roms are heavier around 2-3GB for system (most bloated AF roms) and same for data
8- My secondary rom broke due to a mod or something, how can i switch roms in recovery ?
-Download dualboot utilites
-Files » Utilities : DualBootUtilities-9.1.0.r80.gd5920b2.zip
-Flash in recovery and it will give you an aroma installer enviroment to select your roms
9- Switch roms without aroma
-In TWRP select flash IMG option instead of zip
-Navigate to /internalmem/Multiboot/[ID]/boot.img
-select flash boot
-swipe to flash then reboot
10- Can i install a rom with aroma installer ?
-Yes , just make sure that the aroma does NOT reboot your device after completion as the dualboot script needs to run after the rom script is done to set the new kernel etc
—---------------------------
Hope this helps whoever wants to use this app , its very simple ,it might look complicated but its easy, GL and have fun
This guide can be used for other devices , Dont forget to hit thanks and reply if it helped.
All thanks for the original devoloper and poster @Anik_khan

First here
Will give it a try ASAP and post my feedback soon

I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?

the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list

webmaster750 said:
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
Click to expand...
Click to collapse
Very nice configuration, thank you

the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case

I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?

happy2472 said:
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
Click to expand...
Click to collapse
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.

BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
ro.patcher.device=trlte ?

BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
This is what i get

happy2472 said:
This is what i get
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
That is what I used.
ro.patcher.device=trlte
Search for that thread for your model but I think it's the same.

BluePhnx said:
Tthttps://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
Click to expand...
Click to collapse
Nope still no good ... let me reboot and see

New

happy2472 said:
New
Click to expand...
Click to collapse
Are you on the latest version?

Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?

happy2472 said:
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
Click to expand...
Click to collapse
look for ro.product.device= instead of ro.patcher.device=
This worked for me -> ro.product.device=trlte

happy2472 said:
This is what i get
Click to expand...
Click to collapse
Sorry for late response. Your issue is due to your custom Rom changing treltexx names in prop to graceltexx. Usually renaming the changed text to treltexx must work. Use a file editor and search for any grace mention and make sure it says treltexx. Specially the device codename
And update the app It seems old
Sent from my SM-G935F using Tapatalk

Unable to access Roms after a Nandroid Restoration
After doing a nandroid back up in twrp... I restored with my 4 roms with the dualboot patcher....
Only one Rom boots and works the others dont work... whats causing this.... is there anyway to fix this because I have many good data on those roms....plus I would like to feel safe I can do a backup of my roms.

ananjaser1211 said:
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
Click to expand...
Click to collapse
You mentioned making a back up... I have not been sucessfull in making a back up of this app roms... I used twrp and None of the Roms work after restoring the back up.

I got error while flashing zip file from recovery on my device... Seems like it does not support for "trltechn".
Help Please
Thanks a lot

[Rom] [Ufirm_Flat_QE2_Hybrid_Nougat_Rom_FlashFire_Install][Status Official For All]

Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source

In the OP I had the ADB_Root_G930U_QE2Files.zip linked to the ADB_Root_G935U_QE2Files.zip zip so please make sure you have the ADB_Root_G930U_QE2Files.zip when downloading. Its fixed in the OP now so just double check
I recommend everyone put the Flashfire AP zip and Rom Zip on your internal storage as the AP file is so large that it may not be read properly do too limitations of some SD Cards. When you select AP file in Firmware there should be 4 partitions that are selected. If not then you have a bad download or need to have AP file on internal storage

Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks

ledezma2003 said:
Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks
Click to expand...
Click to collapse
You may have to flash the TMO version of this rom

jrkruse said:
You may have to flash the TMO version of this rom
Click to expand...
Click to collapse
Ok will try that when I get a chance. Thanks again.

Thx for an awesome rom.
Sorry if this question is asked before but couldn't find a solution (checked Verizon thread as well).
I am running Playstore version ROM and everything is working fine except Video Recording.
Photo is fine but when I record a video with included Camera NX, it only plays sound and the screen is either still or black.

I have been taking a needed break. I will update all my s7 roms including this one in the next few days

Nice

That rom can flash for g930p? tks your work!!

@jrkruse
Thanks for all your contributions to this device. I just bought this device and I've been diving through the forums trying to gather as much info on this locked down device.
Could you provide me with just the boot images that don't check the system image and from what model/rom are they from?
Oh and could you provide the partitions locations? The latest roms have an updated Knox that blocks SU from doing it's thing and I have to perform everything via adb (eng boot).

Blank screen
Hello,
I am on your custom rom and the phone was working fine for a day. After I restarted the phone I am not able to see the lockscreen. Its just blank. I do hear the sound of taking a screenshot when I press the buttons and I also can see the " shut down, restart, emg mode" buttons when I hold the power button but no lockscreen. I tried running the recovery boot img but nothing changed.
There is some kind of issue at the locksceen after a restart.

I'm Stuck
jrkruse said:
Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
Click to expand...
Click to collapse
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?

Reegs said:
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?
Click to expand...
Click to collapse
In my case I created a folder named Download in Internal Storage and copied Zip and AP files there. I didn't have trouble coping files there.
From my experience & guess, you may still have old files & settings even though you flashed U-firm files Step 1-2.
Try to access recovery mode and do factory reset and see if this helps. Make sure you backup all important files to External SD because it will factory reset.

So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!

wolfpls254 said:
So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!
Click to expand...
Click to collapse
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.

kyungone said:
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.
Click to expand...
Click to collapse
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?

wolfpls254 said:
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?
Click to expand...
Click to collapse
The QF6 ROM you mentioned is T-mobile firmware so it will have Tmobile apps. Most of them can be removed from ROM install or disabled after.
Other than that there's no performance difference.
If you want Tmobile like environment with Tmobile update schedule, go with T-mobile one. If you want less carrier apps, go with U-Firmware one.

I will no longer be updating my s7 threads until the time Oreo is released with root method. For now I have worked with @stang5litre to bring my non-root method to his amazing rom. He currently has a nougat release found here http://stang5litre-roms.proboards.com/

I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?

amdeng said:
I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?
Click to expand...
Click to collapse
If you at any point tried to root it or flashed the modified boot image then you are no longer passing the safteynet checks, my suggestion is to do a clean install and see if it works then try it again making sure you don't root after you are done installing this rom.

[Root][SM-T590] Samsung Galaxy Tab A 10.5 (2018) root tutorial

Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.

Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn

J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology

J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?

stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions

User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)

any solutions, followed steps but no root

I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)

I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.

Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.

IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time

mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too

IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510

mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup

There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all

For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.

kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?

vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked

kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.

kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?