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.

[RECOVERY][ROOT] Samsung Galaxy S4 Mini Dual SIM (GT-I9192)

WARNING! ONLY USE THIS ON THE GT-I9192 MODEL!
Hello all S4 Mini owners!
I'm happy to finally release ClockworkMod recovery and an insecure kernel for the GT-I9192. With these two installed on your device, obtaining root is easy.
Attached to this post is the necessary files needed for this task. Download the following files:
Odin_v3.09.zip (if you don't have it already)
recovery-clockwork-6.0.5.1-serranodsdd.tar.zip
S4Mini_RootKit_v2.zip (contains SuperSU v1.89 and BusyBox v1.21.1)
Extract recovery-clockwork-6.0.5.1-serranodsdd.tar.zip file to your computer.
The procedure is as:
Copy the "S4Mini_RootKit_v2.zip" to your device SD card.
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up.
Start Odin, uncheck "F. Reset Time", and then click AP button.
Select "recovery-clockwork-6.0.5.1-serranodsdd.tar.md5" file that you previously extracted, and press Start button. The phone will reboot when finished.
After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode.
Select the option to install the ZIP file you have previously copied to your device and begin flashing it.
After flashing using CWM, reboot into system and enjoy your rooted device.
To get rid of the the warnings about applications doing not permitted actions, delete the following files from system/app, or let SuperSU fix it for you.
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk

Link to a test build of CM 10.2 coming in a bit. Support for multi SIM support was merged into CM earlier, so I thought I'd put out a test build to let you guys test if it's working or not.

CM 10.2 test build: http://goo.im/devs/arco/serranodsub/cm-10.2-20131022-UNOFFICIAL-serranodsub.zip
You need to flash it with the recovery I posted in first post.

arco68 said:
CM 10.2 test build: http://goo.im/devs/arco/serranodsub/cm-10.2-20131022-UNOFFICIAL-serranodsub.zip
You need to flash it with the recovery I posted in first post.
Click to expand...
Click to collapse
Unfortunately, System UI has stopped.
Sim card also not found.

Difference with other rooting methods....???
arco68 said:
WARNING! ONLY USE THIS ON THE GT-I9192 MODEL!
Hello all S4 Mini owners!
I'm happy to finally release ClockworkMod recovery and an insecure kernel for the GT-I9192. With these two installed on your device, obtaining root is easy.
Attached to this post is the necessary files needed for this task. Download the following files:
Odin_v3.09.zip (if you don't have it already)
recovery-clockwork-6.0.4.4-serranodsub.tar.zip
S4Mini_RootKit_v1.zip (contains SuperSU v1.65 and BusyBox v1.21.1)
Extract recovery-clockwork-6.0.4.4-serranodsub.tar.zip file to your computer.
The procedure is as:
Copy the "S4Mini_RootKit_v1.zip" to your device SD card.
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up.
Start Odin, uncheck "F. Reset Time", and then click AP button.
Select "recovery-clockwork-6.0.4.4-serranodsub.tar.md5" file that you previously extracted, and press Start button. The phone will reboot when finished.
After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode.
Select the option to install the ZIP file you have previously copied to your device and begin flashing it.
After flashing using CWM, reboot into system and enjoy your rooted device.
To get rid of the the warnings about applications doing not permitted actions, delete the following files from system/app
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk
Click to expand...
Click to collapse
Hi...
Appreciate your effort....!!
Could you please tell what is its difference from other rooting methods currently available in xda..??
Does it have BLN support...??
Awaiting your reply....
Thanx in advance.....
---------- Post added at 07:40 PM ---------- Previous post was at 07:10 PM ----------
Eagerly waiting for the working CM 10.2 Rom....!!
Please fix the errors and upload it s early as possible....!!

arco68 said:
CM 10.2 test build: http://goo.im/devs/arco/serranodsub/cm-10.2-20131022-UNOFFICIAL-serranodsub.zip
You need to flash it with the recovery I posted in first post.
Click to expand...
Click to collapse
Thank you, indeed, for all your efforts for i9192! Waiting for this fixed build, I'll test it as soon as you post it here.

I'll try this next week at home
Is this kernel for all regions?
Sent from my GT-I9192 using Tapatalk

Can you try adding the following to build.prop?
ro.telephony.ril.v3=qcomdsds

arco68 said:
Can you try adding the following to build.prop?
ro.telephony.ril.v3=qcomdsds
Click to expand...
Click to collapse
is it change samething?

Alexannino said:
is it change samething?
Click to expand...
Click to collapse
To see if it fixes the sim card not found issue. If not then I don't know what's wrong, as I don't have this phone myself so I can test. Could be that the multi sim stuff in 4.3 isn't compatible with the current drivers available for this phone, and in that case it won't be possible to have a working CM for it.

arco68 said:
Can you try adding the following to build.prop?
ro.telephony.ril.v3=qcomdsds
Click to expand...
Click to collapse
Could you rebuild ROM or create separate flashable zip for correct build.prop, please? Your recovery is incompatible with AROMA filemanager, cannot apply corrections after flashing ROM
Sent from my GT-I9195 using XDA Premium 4 mobile app
---------- Post added at 09:58 PM ---------- Previous post was at 09:53 PM ----------
Arco, the reason we cannot change props file from ROM itself is that device is stuck on welcome screen with SystemUI crash messages.
Sent from my Galaxy S4 Mini GT-I9192
Upd: Editing build.prop did not fix neither no sim/network message, nor systemui force close
Maybe there is something deeper than just drivers? Framework for them, for example? When running I9192 with I9195 ROM, systemui does not perform fc.

Weird. Try removing the following from build.prop. It should work in single sim card mode then.
Code:
# System prop to enable DSDS
persist.dsds.enabled=true
persist.multisim.config=dsds
# System prop for DSDS model *no binding subscription for QMI_WDS* message
persist.radio.dont_use_dsd=true
Is sim card and network working with the 9195 rom?

arco68 said:
Weird. Try removing the following from build.prop. It should work in single sim card mode then.
Code:
# System prop to enable DSDS
persist.dsds.enabled=true
persist.multisim.config=dsds
# System prop for DSDS model *no binding subscription for QMI_WDS* message
persist.radio.dont_use_dsd=true
Is sim card and network working with the 9195 rom?
Click to expand...
Click to collapse
I have to use my I9192 as primiary device on this weekend, so I will test it out after 27th.
Nope, no network (but no empty sim slot message) on official cm roms from I9190 and I9195.
Sent from my Galaxy S4 Mini GT-I9192

arco68 said:
WARNING! ONLY USE THIS ON THE GT-I9192 MODEL!
Hello all S4 Mini owners!
I'm happy to finally release ClockworkMod recovery and an insecure kernel for the GT-I9192. With these two installed on your device, obtaining root is easy.
Attached to this post is the necessary files needed for this task. Download the following files:
Odin_v3.09.zip (if you don't have it already)
recovery-clockwork-6.0.4.4-serranodsub.tar.zip
S4Mini_RootKit_v1.zip (contains SuperSU v1.65 and BusyBox v1.21.1)
Extract recovery-clockwork-6.0.4.4-serranodsub.tar.zip file to your computer.
The procedure is as:
Copy the "S4Mini_RootKit_v1.zip" to your device SD card.
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up.
Start Odin, uncheck "F. Reset Time", and then click AP button.
Select "recovery-clockwork-6.0.4.4-serranodsub.tar.md5" file that you previously extracted, and press Start button. The phone will reboot when finished.
After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode.
Select the option to install the ZIP file you have previously copied to your device and begin flashing it.
After flashing using CWM, reboot into system and enjoy your rooted device.
To get rid of the the warnings about applications doing not permitted actions, delete the following files from system/app
KNOXAgent.apk
KNOXStore.apk
ContainerAgent.apk
Click to expand...
Click to collapse
I am running I9192UBUAMH2.
I was able to flash the recovery you posted, however I can't enter on it with VOL UP+HOME+PWR. Simply got a blank screen and after some seconds the phone reboots normally...
Ops, my bad. I got it working...
Thanks!

Arco, i've tried to delete persist.dsds.enabled etc. strings, systemui works now, but no network. What exactly did you modify in this CM build? Any information helps
Sent from my Galaxy S4 Mini GT-I9192

Corias said:
Arco, i've tried to delete persist.dsds.enabled etc. strings, systemui works now, but no network. What exactly did you modify in this CM build? Any information helps
Sent from my Galaxy S4 Mini GT-I9192
Click to expand...
Click to collapse
Take a look here:
https://github.com/arco/android_device_samsung_serranodsub
https://github.com/arco/android_vendor_samsung_serranodsub
That should be all you need to build for the I9192. I'm not sure why network isn't working on this device, but it might be because the multi-sim for 4.3 that CM integrated doesn't work properly with the 4.2 libs from stock rom.

touch version
Hi,
is possible to realize the touch version of this recovery?
thanks

My co-worker...just got the samsung s 4 mini dous about a week ago (model number GT-I9192). I want to help her root...but her baseband and build number both end with "XXXUAMH2" and doesnt match the number shown on the first post of this thread. She has checked to see if there was a system update, but the phone says its up to date. Can her phone still be rooted using the file on this thread or do she need a new set of files? I have searched the form for rooting information for her phone...but all I see is info for the other models Ex. I9190 and I9195 etc....
Perhaps someone can point us in the right direction. any help would be appreciated. Thanks!

Yes you can root with this method but I suggest to flash stock kernel again after root
Sent from my GT-I9192 using Tapatalk

fburgos said:
Yes you can root with this method but I suggest to flash stock kernel again after root
Sent from my GT-I9192 using Tapatalk
Click to expand...
Click to collapse
Ok great...two things...
First: Where is the stock kernel link?
Second: Why would I need to flash it after?

[ROM][LB&UB][4.3] Rooted, Deodexed & Zipaligned Stock 10.4.1.B.0.101 V3 [19/02]

[ROM][LB&UB][4.3] Rooted, Deodexed & Zipaligned Stock 10.4.1.B.0.101 V3 [19/02]
Rooted, Deodexed and Zipaligned Sony stock 10.4.1.B.0.101 4.3 Flashable Rom V3 (19/02)!​
For Locked and Unlocked Bootloaders​
Hi Everyone,
Here is a rooted, deodexed and zipaligned stock 10.4.1.B.0.101 (Based on Generic UA) rom. A deodexed rom makes it easier to modify apks and jars without having to worry about those pesky odex files.
Hope you like it
Xposed
Xposed Framework has been integrated into the ROM. Xposed allows ROM modification without having to go through the daunting process of modifying APKs. After you've flashed the ROM, see the second post for instructions on how to activate Xposed.
Rom features:
> Based on the official 4.3 Generic UA firmware
> Rooted with the latest SuperSU
> Deodexed for easier modding
> Zipaligned for optimised RAM usage
> Init.d script support (scripts can tweak system settings for better performance)
> Xposed Framework included for the ultimate tweaking experience
> Stable, smooth and fast
> XZDualRecovery included
Changelog
Stock 10.4.1.B.0.101 Rooted, Deodexed & Zipaligned V3 (19/02)
-Based on the official 4.3 10.4.1.B.0.101 Generic UA firmware
-Changed Settings layout
-Removed GravityBox
-Cleaned up some stuff
Click to expand...
Click to collapse
Stock 10.4.B.0.569 Rooted, Deodexed & Zipaligned V2 (07/01)
-Based on the official 4.3 Generic UK firmware
-Bug fixes, including the infamous Language & Input FC!
-Added Xposed Framework and GravityBox in Settings
-Latest SuperSU v1.86 and root fixed
Click to expand...
Click to collapse
Installation instructions:
Root:
Before you can start flashing ROMs you need root. First you need to download a stock 10.3.1.A.2.67 FTF, this one for example - http://forum.xda-developers.com/showthread.php?t=2512422
After you've flashed it, use this guide to root it - http://forum.xda-developers.com/showthread.php?t=2386405
Fresh installation, if you're coming from any 10.3.1.A.2.67/.244 stock based ROMs:
*Install the latest version of Dual Recovery before flashing.*
Copy Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip to your microSD
Download this file C6603_10.4.1.B.0.101_Stripped.ftf and drop it into your Flashtool/firmwares folder on your PC
Backup any important data to your microSD
Boot into recovery and do a nandroid backup first
Do a Factroy Reset
Flash the ROM but DON'T REBOOT AFTER IT'S FINISHED, instead turn off the phone, in CWM it's in Advanced>Power Off, in TWRP it's in Reboot>Power OFF *if after pressing "Power Off" it says "Disable Recovery Flash?" just select 'No'*
Connect your phone in Flashmode (hold volume key down while plugging in USB)
Open Flashtool and flash everything in the 'C6603_10.4.1.B.0.101_Stripped.ftf' file
Turn on the phone and enjoy!
See the second post for instructions on how to activate Xposed
Fresh installation, if you're coming from any CM or AOSP based ROMs:
Copy Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip to your microSD
Download this file C6603_10.4.1.B.0.101_Stripped.ftf and drop it into your Flashtool/firmwares folder on your PC
Backup any important data to your microSD
Boot into recovery and do a nandroid backup first
Do a full wipe
Flash the ROM but DON'T REBOOT AFTER IT'S FINISHED, instead turn off the phone, in CWM it's in Advanced>Power Off, in TWRP it's in Reboot>Power OFF *if after pressing "Power Off" it says "Disable Recovery Flash?" just select 'No'*
Connect your phone in Flashmode (hold volume key down while plugging in USB)
Open Flashtool and flash everything in the 'C6603_10.4.1.B.0.101_Stripped.ftf' file
Turn on the phone and enjoy!
See the second post for instructions on how to activate Xposed
If you're coming from my previous version (V2) or any other 10.4.B.0.569 based ROM:
Copy Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip to your microSD
Download this file C6603_10.4.1.B.0.101_Stripped.ftf and drop it into your Flashtool/firmwares folder on your PC
Backup any important data to your microSD
Boot into recovery, wipe cache and dalvik cache
Flash the ROM but DON'T REBOOT AFTER IT'S FINISHED, instead turn off the phone, in CWM it's in Advanced>Power Off, in TWRP it's in Reboot>Power OFF *if after pressing "Power Off" it says "Disable Recovery Flash?" just select 'No'*
Connect your phone in Flashmode (hold volume key down while plugging in USB)
Open Flashtool and flash everything in the 'C6603_10.4.1.B.0.101_Stripped.ftf' file
Reboot and enjoy!
See the second post for instructions on how to activate Xposed
Downloads:
Stock_10.4.1.B.0.101_deodexed_V3_SuperHanss.zip (773 MB)
Mirror - Thanks @mlm1102003
Credits:
@[NUT] for Dual Recovery
@rovo89 for the Xposed Framework
@Chainfire for SuperSU
Please hit the thanks button if you like this rom! ​

Add-ons & Mods
Add-ons/Mods:
AOSP style nav bar buttons - Download
5 button nav bar. Thanks to @Rajeev for his tutorial - Download
Stock 3 button nav bar - Download
Xposed:
Xposed Framework v2.5 update - Download
How to activate Xposed Framework:
Go to Settings>Xposed
Select 'Framework' then 'Install/Update' and Grant it root permission
Then select 'Reboot' from the same screen
That's it!
How to activate Xposed Modules:
*Before activating Xposed modules (GravityBox etc.) you need to activate Xposed Framework, follow the steps above*
Go to Settings>Xposed Installer
Select 'Downloads' and download the desired modules
Select 'Modules'
Tick the box next to the module
Then go to back to the Xposed Installer menu
Select 'Framework' then select 'Reboot'
That's it!
Xposed Updates:
At this current time only Xposed Installer v2.4.1 is working with 4.3 for the XZ. Only use the current version and ignore future Xposed Installer updates. If there is a new version that works with 4.3 I will provide an OTA update.
You can still update the Modules, just not the Xposed Installer

CWM Failed with error7

in TWRP - install failed
in CWM - aborted (status 7)

Doh, not working mate... Will try next version
Sent from my C6603 using XDA Premium 4 mobile app

Damn it sorry about that guys, I'll fix it today and reupload.
Sent from my Nexus 5 using XDA Premium 4 mobile app

nkhater said:
CWM Failed with error7
Click to expand...
Click to collapse
JediRAMA said:
in TWRP - install failed
in CWM - aborted (status 7)
Click to expand...
Click to collapse
Does it give a specific error, like a message of some sort?

Drummerjed said:
Does it give a specific error, like a message of some sort?
Click to expand...
Click to collapse
If you get error 7 you probably need to update your recovery to the latest version.
Sent from my LG-V500 using Tapatalk 4

Can't wait!

i believe status 7 error is a device id check. so if your using a 6602 and this is for 6603 you will get an error. i think the dev needs to take the device id check out of the updater script

skinsfanbdh said:
i believe status 7 error is a device id check. so if your using a 6602 and this is for 6603 you will get an error. i think the dev needs to take the device id check out of the updater script
Click to expand...
Click to collapse
The script didn't have that from the start, Android Kitchen doesn't add device check to the the script. The problem is that there are multiple reasons for a Status 7 error, which is why I asked if there was an error message that states the problem.
I'm uploading it again, it sucks not being able to test it myself

about kernel : does this rom work with Doomkernel v18 ?

Worked here.

Screenshots please
Enviado do meu C6603 através de Tapatalk

rsimas said:
Screenshots please
Enviado do meu C6603 através de Tapatalk
Click to expand...
Click to collapse
Still uploading the fixed ROM! In the meantime see here - http://www.flickr.com/photos/[email protected]/sets/72157638591600843/

Drummerjed said:
Still uploading the fixed ROM! In the meantime see here - http://www.flickr.com/photos/[email protected]/sets/72157638591600843/
Click to expand...
Click to collapse
wait for your fixed rom with patient, before that can I use this as my ROM's base?

@Drummerjed
The kitchens binary will not work with the Z (if it that is the one you used), you will need a good Z binary to replace it with (like from any other ROM in this section)
The script also needs to detail the right partitions, again, lots of Z updater scripts to use to make sure it's doing the right thing for this device
Look forward to your new version.

OP updated with download links

Hope it works better How to root latest 259 stock?
Sent from my C6603 using Tapatalk

bariz143 said:
Hope it works better How to root latest 259 stock?
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Follow the instructions in the OP, this ROM includes root but requires a root fix that you need to flash after flashing the ROM
dat response time

[Tips Tricks Tools] Huawei P9 Lite

Hi,
Today I will introduce the changes you can make to your Huawei P9 lite device.
These methods have been tested on my VNS-L31C432 and it's work on B130 update and earlier.
Sorry in advance for my incorrect syntax in inglish, i'am french user
1. Update to latest version
If your device is NOT ROOTED install the OTA update.
Otherwise place a folder named "dload" into you external or internal SD card and put update file (unzipped) on this folder.
Update for VNS-L31C432BXXX to VNS-L31C432B130 dual-sim, european version here >> https://www.hidrive.strato.com/lnk/H2ljl9lt
Turn off your device.
Hold volume up/down and power button for a long time.... Update starts automatically after this.
If your device is bricked, do not format the partition (except dalvik and cache) and go update (this update is a full version, your system will be restored).
2. Unlock Bootloader/install TWRP/Root your device
Follow this steps >> http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
if you have problems to get the unlocking code, log on Huawei site with your Facebook login, CHOOSE your device model and click request the code, enter the requested information, done!
TWRP 3.0.2.0 work but nandroid backup doesn't work!
For solve this, install the "TWRP Manager" app and go backup page, done!!!
(If you need set SElinux in permissive mode please read below).
3. Set SElinux to permissive mode for ever!
Download "Terminal IDE" app.
Open it and run this:
(please, type a command at a time)
Code:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
restart your device, done!
4. Install Xposed Frameworks
Follow this step >> http://forum.xda-developers.com/huawei-p9lite/how-to/guide-xposed-p9-lite-t3425315 and chose this version >> http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip (xposed-v86-sdk23-arm64 work fine, no battery drained).
5. Best Xposed module worked fine
Here are some useful and functional modules (not exhaustive list..)
-Amplify (for battery saving)
-Greenify (for battery saving)
-BootManager (for chose your apps in start on boot)
-Play Store Changelog (to display your apps and update at the opening of the Play Store)
-WiFiKeyView (view your wifi key in new tab at wifi setting. Little bug your key is not visible but copy your key and past on a note worked)
-XInternalSD (chage the path to dowload file from Chrome >> external SD) (work on other app )
-VolumeSteps+ (If you find that your volume increases too quickly, This module add steps in the volume bar! Customisable)
-ActivityForceNewTask (Force app open in correct app)
-Force Immersive Mode (Force immersive mode in your app, customisable)
-VirtualSensor (Material emulation of gyroscop, not worked with pogo dev running for this isue)
-AdBlocker and Lucky Patcher Module (I'm not sure that really works..)
6. Use your External SD on Internal (Full supported!!)
This trick enable the official feature "adoptable storage" on your Marshmallow with EMUI. better than Link2SD.
-Connect your device in your PC.
-Run ADB and run this comand:
Code:
adb shell
sm list-disks
you will see a number, that is the identifier of your SD card. For example "159,49".
Run this comand (replace YOUR_SD_IDENTIFIER ):
Code:
sm partition disk:YOUR_SD_IDENTIFIER mixed:50
Done, your external SD have 50% of memory for external and 50% for internal emulation.
Next, appointment in your storage settings and check the total capacity of the device! It may appear 0.00 o available, it's just a visual bug don't worries
Use a "DiskInfo" app or a file explorer for see correctly values.
7. BONUS play the walking dead season 1 and 2 on your P9 lite
I love this game! But device not suported..
the only solution is to take a file from the game with the unlocked level ...
Version named "Mali".
I hope you enjoyed my guide if you have questions or other tricks leave a comment.
Thanks!

nice guide, thinking myself do one like this, but can be improved... add multi user, multi window, calling recorder, substratum/layer support, build.prop mods, smart-e, smart cover etc

Therand said:
...
Hold volume up/down and power button for a long time.... Update starts automatically after this.
...
Click to expand...
Click to collapse
I was trying this some time ago...
With TWRP, I was just getting booted into TWRP. Is there something I'm doing wrong or is it just me? I would appreciate any suggestions.

Thank you Snapdesign, If you have more info to add , I would edit the post and I would quote you.
Zeruno, TWRP, stock recovery and stock updater some many diferent. if you don't remove it, you have full acces on it.
Your device is shutdown, hold volume up + volume down + power and don't release it before the updater screen appears!
normally it works...

Therand said:
Thank you Snapdesign, If you have more info to add , I would edit the post and I would quote you.
Zeruno, TWRP, stock recovery and stock updater some many diferent. if you don't remove it, you have full acces on it.
Your device is shutdown, hold volume up + volume down + power and don't release it before the updater screen appears!
normally it works...
Click to expand...
Click to collapse
Yep there's my problem -- updater screen never comes but TWRP loads instead. I wonder if there is some adb command?! That would solve a problem.

i do not think there is an command to go in the updater..
Wait for a more positive response from another user
Or try this at your risk...
Put any file for update (update.app, META-INF, ...) On a .zip archive named "update.zip" and place in your adb folder.
Connect your device on PC launch adb and run this:
Code:
Adb reboot bootloader
Wait for see bootloader screen and run:
Code:
Adb sideload update.zip
I not tested personally this method...

Otherwise place a folder named "dload" into you external or internal SD card and put update file (unzipped) on this folder.
Update for VNS-L31C432BXXX to VNS-L31C432B130 dual-sim, european version here >> https://www.hidrive.strato.com/lnk/H2ljl9lt
Turn off your device.
Hold volume up/down and power button for a long time.... Update starts automatically after this.
If your device is bricked, do not format the partition (except dalvik and cache) and go update (this update is a full version, your system will be restored).
Click to expand...
Click to collapse
Is this the procedure if your phone is rooted but you still want to install the OTA? (My current situation)

This method work on a rooted and no-rooted device.
The root "disable" the OTA function.
Don't try OTA on stock app update in your setting if your device is rooted.

The trick to use ext sd to increase space works with both stock and root or only with root?
Inviato dal mio SM-N9005 utilizzando Tapatalk

This trick no need a su promp comand.
Su command is only available for root user.
Trick work on no root acces
EDIT: im not sur if adb shell work for guest user.. try it

After lot of test, this version Xposed Framework is not a better for P9 lite.
Version unmodified v86 work fine with resource hook activated!
The direct download link >> http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip

Therand said:
1. Update to latest version
If your device is NOT ROOTED install the OTA update.
Otherwise place a folder named "dload" into you external or internal SD card and put update file (unzipped) on this folder.
Update for VNS-L31C432BXXX to VNS-L31C432B130 dual-sim, european version here >> https://www.hidrive.strato.com/lnk/H2ljl9lt
Turn off your device.
Hold volume up/down and power button for a long time.... Update starts automatically after this.
Click to expand...
Click to collapse
Hello,
will this trick work even with TWRP recovery or only with stock recovery? is there any other way to install OTA updates if I have TWRP and root?

SwH.85 said:
Hello,
will this trick work even with TWRP recovery or only with stock recovery? is there any other way to install OTA updates if I have TWRP and root?
Click to expand...
Click to collapse
This trick work on a rooted or stock device.
Work only with stock updater.
Is not possible to update with OTA if your device is rooted, no isue.
If you proced a manual install, your device lost the root and your bootloader re-lock automatically.
Possible to re-unlock and re-root after this update.

Therand said:
After lot of test, this version Xposed Framework is not a better for P9 lite.
Version unmodified v86 work fine with resource hook activated!
The direct download link >> http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip
Click to expand...
Click to collapse
I'm with xposed-v86.0-sdk23-arm64 by-wanam, but in fact i see in xposed the oficial xposed-v86-sdk23-arm64.zip showing as compatible with huawei devices.
So, how can i change it, in a safe way?

Nomatrix said:
I'm with xposed-v86.0-sdk23-arm64 by-wanam, but in fact i see in xposed the oficial xposed-v86-sdk23-arm64.zip showing as compatible with huawei devices.
So, how can i change it, in a safe way?
Click to expand...
Click to collapse
Version 86 by wanam possible drain battery faster...
For use version 86 unmodifier follow steps:
1. Unistall your framework with this zip file >> http://dl-xda.xposed.info/framework/uninstaller/xposed-uninstaller-20160829-arm64.zip flash zip with TWRP recovery and reboot.
2.Install the v86 framework with TWRP recovery, reboot
3. Done

About the 6th step, is it reversible? Once I've done it, can I change it again to what it used to be?
Thank you

inrope said:
About the 6th step, is it reversible? Once I've done it, can I change it again to what it used to be?
Thank you
Click to expand...
Click to collapse
use root essentials... much easier... you can revert but be aware that you might lose some data

Hi guys, I have two questions. First, how can I move apps data from internal memory to SD card? And second, does our phone have a front camera flash? Thanks

so it is possible to use my sd card as internal storage? how will this be displayed in my os?
does it just think of it as 1 bigger internal sd or something else? just want to make sure before buying the phone .
also, is the huawei p9 lite a good phone to be rooted and used with custom firmware (e.g. supportive community etc.)
thank you very much in advance for answers!
have a nice day everybody

Kyrok said:
so it is possible to use my sd card as internal storage? how will this be displayed in my os?
does it just think of it as 1 bigger internal sd or something else? just want to make sure before buying the phone .
also, is the huawei p9 lite a good phone to be rooted and used with custom firmware (e.g. supportive community etc.)
thank you very much in advance for answers!
have a nice day everybody
Click to expand...
Click to collapse
Adoptable storage for SD card is not available in stock firmware due to EMUI security policy. But you can do it in custom firmware based on AOSP.
P9 Lite has fully functional CyanogenMod, SlimRom, Resurrection Remix, MedRom (based on stock EMUI 4.1.1 Android 6) and Revolution OS ( Bases on stock EMUI 5.0 Android 7).

Alternative method magisk root [stock android 9][NO TWRP][Samsung A70 FN/DS]

purpose of this post is to share an alternative method for those who fail to root using @topjohnwu recommended method or the method posted by @Grarak here on A70 forum that involves patching recovery.img in magisk and then flashing that in twrp>install to boot.
failing to root means either bootloops or unstable magisk root or magisk root disappearing randomly or after a module installation.
this is not my original guide , i was told this method by @raeumler via PM and i am sharing it on A70 forums incase other methods dont work.Some of the steps may not be neccesary , but i did them ritually anyway
my phone model is SM-A705FN /DS and firmware version is A705FNXXU5ASL4( with 1st jan 2020 updates) . country is PAK
do this at your own risk! i will not be responsible for any negative consequences
appropiate links and files will be posted as attachments
rooting procedure( read each step twice)
1- UNLOCKING BOOTLOODER= this will factory reset device . backup your data
read step 02 of this linked guide https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
DOWNLOAD FIRMWARE AND ATTACHMENTS= now i am assuming you have stock samsung android 9. if not, download your firmware via SamFirm windows program and flash in odin to go to stock[ program available in attachements]. Download other attachements too
2-Find vbmeta.tar in downloaded attachments and unpack it. you will get vbmeta.img file.
3. unzip stock Samfirm downloaded firmware. you will get 5 files in it (BL,AP,CP,CSC and CSC_HOME).open the AP File from the factory rom with 7zip
4. remove userdata.img, vendor.img and system.img from the AP file
5. replace vbmeta.img with the one you have downloaded in step 2.
6. repack AP as AP.tar [ use 7zip or peazip. i used peazip windows program, ensure file type is TAR]. transfer this AP.tar to your phone
7. install magisk manager 7.5.1 on your phone and open it. connect your phone to internet.
8. hit the upper install button and choose "patch a file"
9. choose the repacked AP file and patch it[ this requires active internet as magisk needs to download its zip file]
10. copy the AP file which magisk creates in internal storage/download/magisk_patched.tar back to your pc (better keep it named as such for differentiation, its irrelevant how the file is named as long its a tar file)
11. download,unzip and open Odin 3.1.3.1[available in attachements]. i used Odin3+v3.13.1_3B_PatcheD.exe , there is a simple version too inside the zip
12. go into download mode on your phone (shut down completely then hold vol+ vol- togather and plug in cable connected to PC ). Odins should show Com port X as blue
13. in odin: put the BL, CP and HOME_CSC in its place (the files from the factory firmware you downloaded in step 1 from SamFirm windows program) and place the magisk patched AP on AP
16. check if you want autoreboot or not, its your own taste (some feel safer with autoreboot unchecked, both works)[ i kept autoreboot checked]
15. hit start and let it finish (when it stucks on something try another cable and install latest samsung adb driver.)
16. let the system reboot
17. if you get stuck in bootloop or freeze >10 min on samsung logo, try to force reboot.press volume down + power till screen turns blank then press volume + and power till bootloader unlock screen appears and then let go of all keys.
if still it doesnt boot, then press volume down and power togather to force shutdown and then press volume up and power till stock recovery boots up. Mine at this stage said firmware is corrupt ,factory reset needed so thats what i did in stock recovery. power off system in stock recovery and then press volume+ and power till bootloader warning screen , let go of all buttons, it should now boot up fine with magisk manager app in app drawer. DONT OPEN IT YET
download this app from play store https://play.google.com/store/apps/details?id=fr.petrus.tools.reboot&hl=en_US. open app and press reboot. No need to press any keys
on reboot complete ,connect to internet,open magisk, let it check for updates, it should say installed in both portions. magisk will do additional enviromental steps and then reboot. on booted up, use the linked reboot app to reboot again.
now magisk should be installed all fine
for viper4android>open magisk>swipe left and tap downloads> installed 2.7.1.6> reboot with linked app
on reboot check if app is installed, if not > install and login on xda labs and download viper4android 2.7.1.6> open app> give it root accesss> let it reboot device on installtion> on bootied up reboot again with linked app and then check drivers on viper4android[ make sure master switch is on and then play some music ,tap the chip icon to see driver status and processing status
from here onward, always use the linked reboot app to reboot device. if an app or module reboot device automatically( like viper4android does ) then on boot complete,reboot again with the linked app
Credits to @Grarak for his original work and files
 @raeumler for his guide.

Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.

kac222 said:
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
Click to expand...
Click to collapse
This is for stock android 9 as the title says.
Follow @MarvinMod guide to root android 10

Yes i know but i tried for yourself. I know how rooted on Android 10. Regards.
Wysłane z mojego SM-A705FN przy użyciu Tapatalka

Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?

DelphisDoofer said:
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
Click to expand...
Click to collapse
Download phone info app and note pda, csc and phone codes.
Use these codes to Google your exact firmware and download that ( you may have to visit various websites that offer better speed)
The samfirm, frija only allows latest firmware to be download, not the currently installed one.
One you have the stick firmware file, then you can proceed with rooting.
If you are on android 9 use this guide
If you are on Android 10 use MarvinMod guide.
This reboot app is what I currently use. Haven't experimented with other apps.
The root is permanent as long as your reboot with the mentioned key combination or the reboot app.
The reboot app simple allows you to reboot without the key combination. If you don't want to use this app then you must reboot with the mentioned key combination to retain root. Otherswise you wouldn't have root unless you reboot again with correct combination.
To make this easy I suggested that reboot app
Yes I feel you bro, I had Samsung note 2 then note 4 phone and they were easier to root.
But with Google changing things the best way to root is to use magisk and this complicated methods

i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....

raeumler said:
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
Click to expand...
Click to collapse
I didn't messed with boot or recuvery files like the way you DM me.
But I have been noticing strange behavior with petrus app.
Reboot option in petrus app is kinda of like fast reboot or reboot UI. Because all apps opened and present in task manager remain so after reboot with petrus app.
Also once you power off with petrus app,
1= booting up with root key combination results in phone getting freeze Or bootlooping
2=. Force shutting phone again bootloop phone.
3= Going to stock recovery and rebooting system bootloop.
4= going to stock recuvery and shutting off phone from there and then simply pressing power button without key combination, successfully bootup phone with root intact.
This is such a bizzare behaviour
Oh and i am still on Android 9 pie.