Database Info

[Q&A][Root]Rooting with Locked Bootloader - NO OTA Method

After much tampering I managed to identify a procedure to root our phone(s) leaving the Stock ROM intact (addition of rooting apart, sure). This will remove the requirement to do an OTA update, which in the future could remove the rooting if any update will be available (Lollipop maybe?).
The process is very straightforward and has been tested in both OS X and Windows. Here it follows:
THIS SHOULD WORK FOR ALL XPERIA PHONES WITH KITKAT INSTALLED WHICH HAD A PREVIOUS ROM VULNERABLE TO TOWELROOT.
If your phone started with KitKat 4.4.4 or later and you want to keep the locked bootloader you may be doomed.​
GENERAL GUIDELINES:
Be sure to have the full FTF for the stock ROM you are currently running
Flash only the kernel of a ROM for your phone vulnerable to the Towelroot exploit unchecking the wipe checkboxes
Reboot the phone:
The phone will bootloop, but it doesn't matter. The Linux kernel and adb are alive and thus the "Towelroot" vulnerability is exploitable by rootkitXperia
Run rootkitXperia. After the rooting it should get stuck when trying to reboot the phone(*). Interrupt it with CTRL-C
Flash back the kernel for the ROM in your phone
Reboot the phone
Manually run the command to have the RIC permanently disabled:
Code:
adb shell "su -c /data/local/tmp/install_tool.sh"
(*) In some phones (Xperia Z?) rootkitXperia may not get stuck. If the phone reboots the rooting should be complete. Just flash back your original kernel and it should be done (untested).
The following section will explain in great detail every single step needed. It also includes all the links to the SW and procedures needed:
COMPREHENSIVE TUTORIAL:
PREPARATION:
Have your phone updated to the last ROM
Download Flashtool: link
Download rootkitXperia: link
Have adb installed: Suggested links: OSX/Linux - Windows
- Windows only: Install the phone drivers (probably using Sony PC Companion. I dunno, I don't use that Windows junk )
Enable the USB debugging: HowTo
In Settings/Security enable "Unknown sources"
Make it sure Flashtool/adb can connect to the phone: just try "adb shell" from the terminal.
Download a Jelly Bean stock ROM for YOUR phone: link for D2303
Otherwise for D2303 (but it is confirmed working with the M2 Aqua D2403 as well) you can use the attached FTF (kernel only)
From Flashtool download the FTF of your latest ROM (Menu "Devices/Check Updates" at least in OS X). Be sure to use the same ID
You may want to make a full backup using the Sony system app "Backup and restore" (or equivalent in other languages)
ROOTING:
Launch Flashtool in your Mac/PC
Power off the phone
While holding the Volume Down key connect the phone to the Mac/PC via USB
The phone top led should blink red and then green
Flashtool should report that the phone is connected in flash mode
Select the JB FTF of your choice (full RoM/kernel only).
In OSX Flashtool is glitched. You may need to select an FTF and then move upward with the arrow keys
Exclude all but the kernel. Uncheck the wipe checkboxes
Proceed with the kernel flashing . The blu icon with a thunder
After the flashing has terminated disconnect the phone from the USB
Start the phone:
This is the tricky part. Android now will bootloop. But we don't care, because the underlying Linux is well alive!! adb works and so it does the Linux kernel/OS.
And that is all we need, because rootkitXperia exploits the Towelroot vulnerability but without the need of launching the graphical interface. Just hurry a bit because it may or may not last forever.
Connect the phone via USB
From the terminal cd into the rootkitXperia directory
Launch the script: install.sh in OSX/Linux - install.bat in Windows
When the script gets stuck at the phone reboot terminate it (CTRL-C)
At this point, with the phone still in bootloop, you may check if the rooting has been successful. Just type the command:
Code:
adb shell "su -c id"
which should report
Code:
uid=0(root) gid=0(root) context=u:r:init:s0
If it doesn't something went wrong (it shouldn't).
DISABLE THE RIC (enable /system read/write):
Disconnect the phone
Power it off
Hold the Volume Down key and connect it to the computer
In Flashtool flash the kernel of your latest ROM.
Like before exclude all but the kernel, no wipe needed
Also there is an issue with 18.3.1.C.1.15 installed via PC Companion/Sony Bridge for Mac. One should flash (thus not excluding it) the "BOOTBUNDLE" as well as shown in this post
Disconnect the phone from the USB and reboot it
Connect the phone
Manually run the command:
Code:
adb shell "su -c /data/local/tmp/install_tool.sh"
Reboot and enjoy your rooted phone!
What to do next:
Press "Thanks!"
Backup your TA partition: link for OS X
Put a copy in your most favorite Cloud service (Dropbox/iCloud/Google Drive/Whatever). It's better be safe than sorry.
Update SuperSU binary and apk
Install adaway to get a rid of those annoying commercial
Anything else you rooted your phone for!
Unrooting/Recovery
You may need to use the OFF button near the SIM card slot if anything went wrong (like if you forgot to uncheck the wipe flags). That shuts down the phone. You would need a needle (or something very small) to push it. (**)
Flash with Flashtool the kernel and system from the ROM you previously downloaded to keep your data - or -
Rebuild the ROM with Sony Bridge For Mac/PC Companion
(**) Thanks to Vino Kulafu for the tip.
JB Kernel from the Xperia M2 D2303 FTF attached:
It's confirmed working with the following devices:
Xperia M2 D2303
Xperia M2 Aqua D2403

It's working
Miche1asso said:
After much tampering I managed to identify a procedure to root our phone(s) leaving the Stock ROM intact (addition of rooting apart, sure). This will remove the requirement to do an OTA update, which in the future could remove the rooting if any update will be available (Lollipop maybe?).
Click to expand...
Click to collapse
Yap, I have just test it and everthing is working fine. I was using Windows. And i could also update su binary without any problem. Thank you for sharing us this method which reduce a lot of wasted time.

Andrej732 said:
Yap, I have just test it and everthing is working fine. I was using Windows. And i could also update su binary without any problem. Thank you for sharing us this method which reduce a lot of wasted time.
Click to expand...
Click to collapse
Thanks for confirming!
BTW did you use the attached kernel?

Miche1asso said:
Thanks for confirming!
BTW did you use the attached kernel?
Click to expand...
Click to collapse
Yes, everything is fine.

Many thanks for this!
Successfully rooted Generic Philippine D2303 4.4.4 KK firmware, with full R/W access using the above instructions.
However, I suggest that the above steps be updated for clarity. Happy rooting guys; this is a much more convenient way to root, albeit complicated.
This should be moved to General section or Android Development section so people can see this thread easily.
:good:

Vino Kulafu said:
However, I suggest that the above steps be updated for clarity. Happy rooting guys; this is a much more convenient way to root, albeit complicated.
Click to expand...
Click to collapse
Do you mean to make a short version? I mean, as it is now it's a full guide, from A to Z. I was thinking about making a section with the 4-5 steps for the skilled users. Too bad I didn't think about reserving the second post. Is there any way to have it added? Otherwise I'll put it in the bottom with a reference on the top.
EDIT: Added a generic procedure on the top.
This should be moved to General section or Android Development section so people can see this thread easily.
:good:
Click to expand...
Click to collapse
yeah, I was thinking about making a thread there pointing to this one as well. The process is quite generic, although I think in the Xperia Z rootkitXperia does reboot the phone disabling the RIC.

No need to make a short version, my friend; it's good enough. Here are some suggestions though:
1. I think the portion about holding the up volume key is wrong since it boots the phone into fastboot mode while we need to go to flash mode.
2. Kindly stress the importance of unchecking the wipe checkboxes in flashmode. If not unchecked, you could end up with a bootlooping phone wherein the root kit will not function since the adb debug setting has been reset, which leads to #3.
3. Make use of the OFF button near the sim card slot when faced with the situation described in #2. Just flash back the original kernel and repeat.
My experience was this:
I didn't wait for reboot; I cancelled the procedure when it hung in the reboot part. Then I shut the phone off using the OFF button near the sim card slot, then flashed back stock KK kernel only. Afterwards, I proceeded to the disabling RIC then reboot again. Presto, all is well.
:laugh:

Vino Kulafu said:
No need to make a short version, my friend; it's good enough. Here are some suggestions though:
1. I think the portion about holding the up volume key is wrong since it boots the phone into fastboot mode while we need to go to flash mode.
2. Kindly stress the importance of unchecking the wipe checkboxes in flashmode. If not unchecked, you could end up with a bootlooping phone wherein the root kit will not function since the adb debug setting has been reset, which leads to #3.
3. Make use of the OFF button near the sim card slot when faced with the situation described in #2. Just flash back the original kernel and repeat.
My experience was this:
I didn't wait for reboot; I cancelled the procedure when it hung in the reboot part. Then I shut the phone off using the OFF button near the sim card slot, then flashed back stock KK kernel only. Afterwards, I proceeded to the disabling RIC then reboot again. Presto, all is well.
:laugh:
Click to expand...
Click to collapse
Ok, let me see:
1. Crap. I always get confused. It is Volume down, then, I just checked. I'll fix it.
2. Oh, I didn't think it could get so bad. I just unchecked the boxes to avoid to lose my data.. Well, yes, thinking about that it makes sense now.
3. I'll add it. Thanks.

As i know, with Locked bootloader even if you hold volume up (+ button) it will reject the connection with phone. Otherwise great guide and you should contact someone of moderators to move this in General section.
Thanks
Xperia M2 D2303 on K.K. 4.4.4

how the Xperia M2 Aqua (D2403) ?
Is there a solution root for D2403 with locked bootloader ?
sorry bad my language

Dzepar said:
As i know, with Locked bootloader even if you hold volume up (+ button) it will reject the connection with phone. Otherwise great guide and you should contact someone of moderators to move this in General section.
Thanks
Xperia M2 D2303 on K.K. 4.4.4
Click to expand...
Click to collapse
No, no. One just needs to hold Volume Down. WIth the locked bootloader we can flash all FTF we like as long as they are from Sony.
I also made a new thread in the general section just with the "General Guidelines" also pointing to this one. But thanks.
Actually it made the portal!
i_1 said:
Is there a solution root for D2403 with locked bootloader ?
sorry bad my language
Click to expand...
Click to collapse
If it had a Jelly Bean ROM just download the FTF (don't ask me from where) and follow this guide.

sorry .. no I do not understand
after successful with rootkitxperia , so need to flash back stock kernel before?

Yes, you need flash back stock KK kernel. After doing that, the phone should boot properly. Then you can proceed to disabling the RIC module steps.

Why is this?
anyone can help ?

sorry
i_1 said:
anyone can help ?
Click to expand...
Click to collapse
sorry I'm not as thorough with his files ...
now xperia M2 Aqua (D2403) has been rooting with locked bootloader on KitKat 4.4.4
Thank you Miche1asso with this awesome work ...:good::good::good:
Thank you also for Kulafu Vino has helped me with explanation...:good::good::good:

i_1 said:
sorry I'm not as thorough with his files ...
now xperia M2 Aqua (D2403) has been rooting with locked bootloader on KitKat 4.4.4
Thank you Miche1asso with this awesome work ...:good::good::good:
Thank you also for Kulafu Vino has helped me with explanation...:good::good::good:
Click to expand...
Click to collapse
Help me please i have same phone like you i dont have kernel but have the firmware for 2403

i_1 said:
sorry I'm not as thorough with his files ...
now xperia M2 Aqua (D2403) has been rooting with locked bootloader on KitKat 4.4.4
Thank you Miche1asso with this awesome work ...:good::good::good:
Thank you also for Kulafu Vino has helped me with explanation...:good::good::good:
Click to expand...
Click to collapse
You're welcome!
So, let me understand: did you flash my attached JB kernel for the M2 D2303 in the M2 Aqua D2403? I'd like this to be confirmed so in the case I will add it to the guide.

Miche1asso said:
You're welcome!
So, let me understand: did you flash my attached JB kernel for the M2 D2303 in the M2 Aqua D2403? I'd like this to be confirmed so in the case I will add it to the guide.
Click to expand...
Click to collapse
Yes ... I'm using your D2303 JB kernel
---------- Post added at 01:20 AM ---------- Previous post was at 01:09 AM ----------
Postiga 41 said:
Help me please i have same phone like you i dont have kernel but have the firmware for 2403
Click to expand...
Click to collapse
Just wait for the later addition of tutorials from Miche1asso

Postiga 41 said:
Help me please i have same phone like you i dont have kernel but have the firmware for 2403
Click to expand...
Click to collapse
The kernel I attached in the main post works for the D2403 as well. I updated the guide confirming it. Download it and follow the instruction step by step.

After flashing latest kernel , phone just shows sony then blank screen...but adb can detect the device...
any fix??

How I gained root and CWM recovery on my MT7-L09 with out bootloader unlock.

Let me start off by saying I'm new to the Huawei Ascend Mate 7 but I'm no newcomer to Android. I've been a member of XDA for some years now. Since before IceCream sandwich. I've done my far share to help out this community as it has helped me. I'm originally a themer, but lately been working on a few ROMs. Mostly tweaked based on stock, deodexed, zip aligned, debloated, and build prop mods.
My worth I bring to the table is I'm just BALLSY and experienced enough to try anything and flash just about anything. (With in reason of course). I seem to have acquired a unique talent to be able to unbrick every device that's been laid before me over the passed year or so as well as a few of my own. And have aided in the unbricking of several peoples device that have reached out to me on here.
So with this uncanny ability to be able to unbrick devices I took it upon myself to take a few stabs at gaining root and flashing CWM to my MT7-L09 without unlocking the boot loader. Due to reading post after post of people not getting replies from their emails to Huawei asking for an unlock code.
So now to the point......
I can in NO way take credit for this development nor do I take any responsibility for your actions or decisions to follow this guide unsuccessfully.
1. First I downloaded the 141 update with Supersu built in thats posted here in this forum and the Mate7.zip posted here as well.
Moved the 141 update with SU titled Update.zip to my sdcard/dload.
2. Went to settings/updater clocked MENU at the bottom, then selected LOCAL UPDATE.
3. After it completed (which took about 5 mins) I rebooted installed SuoerSu from the play store and SuperSu Pro. And opened to update binary.
4. Then used a Root Browser to locate the Mate7.zip that I downloaded earlier in the same forum. I then extracted its contents.
5. Download FLASHIFY from the play store. Grant SuperSU permission. And use FLASHIFY to flash the CWMRECOVERY.zip that was also in the Mate7.zip file that you extracted earlier.
6. And this is the most important thing. I don't know how many times I've seen people start modding and flashing then brick and ask for help only to realize "no I didn't make a backup". ALWAYS MAKE A BACKUP IMMEDIATELY AFTER INSTALLING A CUSTOM RECOVERY. If you don't then you have no one to blame but yourself when you can restore.
So as stated above I had no hand in developing any of this. Its just a method I used to gain root, update, and gain CWM recovery WITHOUT boot loader unlock.
And here's the copied text from URYLDOR's forum where I found all the essential pieces I used to gain all this. I did not unlock my boot loader though. This method nor any other would work for me so I took a shot in the dark at my method just to get root, CWM, and update as well.
ALL THANKS SHOULD BE GIVEN TO HIM FOR HIS DEVELOPMENT and if my method works for you then youre welcome to thank me for it and it alone but thank @Uryldor too.
...............................................................
Here is the translated guide to unlock bootloader on European model from the link I posted earlier.
I’m not responsible of any damage made to your device.
Download, unzip and run the Huawei product ID generator then select Huawei Y300-0000 in the product model field. Paste your IMEI in the product IMEI field and it should give you a product ID. We will use it later.
Go to http://en.club.vmall.com/emotiondownload.php?mod=unlock&action=apply tick the box at the end of the Unlocking Agreement and click next.
Here is what to choose/write in the form:
Product type: Smartphone
Product model: Huawei Y300-0000
Product SN: The SN of your Mate 7
Product IMEI/MEID: The IMEI of your Mate 7
Product ID: The number Product ID Generator gave you.
Enter the captcha and click submit.
Now it should give you your unlock code.
Download mate7.zip from https://mega.co.nz/#!aB8mRATA!nY7VJPUEESxBv5iRZ95vORbcjUQwLoyEyHagPi6RMGI and unzip it.
Install the driver if needed by running Driver\all\DriverSetup.exe
Copy SuperSU-PRO-V2.09.zip to your sd card.
Reboot your Mate in fastboot by holding Volume Down+Power for 10 seconds and plug it.
Unzip Recovery_b119.zip, go to tools, hold Shift and right click then choose “Open command windows here.
Type:
Now your bootloader is unlocked. Don’t close the command windows, now we will install the ClockWorkMod recovery.
In the window type:
You can flash recovery_stock.img with the same command if you want to revert back to the stock recovery.
Now go into recovery by holding Volume Up+Power for 10 seconds.
Then go to:
Install zip>choose zip from /storage/sdcard1> SuperSU-PRO-V2.09.zip and select yes.
Reboot.
Your Mate 7 is now unlocked and rooted!

Thanks you save my life and my mate 7... work fine here

Did you not have to flash using the force update method? I installed 141 via the local update method (came from 137) and SuperSU fails to update the binary.

ritdaw said:
Did you not have to flash using the force update method? I installed 141 via the local update method (came from 137) and SuperSU fails to update the binary.
Click to expand...
Click to collapse
Yeah but I downloaded the 141 update that has root built in. I then used "FLASHIFY" From the play store to flash the cwm.IMG. I then booted to CWM then flashed the SuperSU.zip that's mentioned in the above thread. Then made a back up in CWM. Rebooted and didn't have to update binary after all that.
Warning. Do not flash CM-11 if you used my method to root and install CWM. I did and now I'm soft bricked. I think it has something to do with the boot loader not being unlocked. I'm stuck at the "Rescue Mode" screen with the error
Error!
Func NO : 12 ( Func_load_iom3)
Error NO : 1
It took cm-11 OK. Just didn't ever boot fully so when I went to reflash the 141 update to restore it or my backup it acted like it took that fine but upon first boot back to stock I ended up stuck in "Rescue Mode" and getting the above code. ADB not recognizing it since its in "Rescue Mode" which is basically fast boot. Some fast boot commands work like Fastboot update ....... And fastboot reboot. But not " fastboot flash " does not. And that's where I think the boot loader being locked is preventing me from fast booting anything to it.
Any suggestions are appreciated.

Mmmmm... bad news men... I hope you can bring to life your Huawei mate again... I use you method and works fine... but I don't think flash any Rom... maybe you can try unlock your boot loader or use Huawei hi suite?

i was able to flash the 141 with supersu - but i wasn't able to update it, nor to flash anything with flashify because there are no root-rights - at least the phone still works
i successfully applied steps 1 and 2
3 downwards not usable (update supersu not working, even after reboot)
UPDATE: with the force update it worked

There is no cwmrecovery in the mate7 folder. Are you referring to the other recovery that isn't the stock one?

charlieb620 said:
There is no cwmrecovery in the mate7 folder. Are you referring to the other recovery that isn't the stock one?
Click to expand...
Click to collapse
Yeah it says its a modified version of stock. Its cwm. Even has the logo

Question??? I installed this Rom and everything works fine... but if I delete a system app (Google maps for example)... the app is gone but when the phone reboot the apps appears again??? I use a root browser to delete the app... which should be the problem??? I am the only whit this trouble??

Will this method also work when you;ve updated to lollipop? I cannot get the unlock code from huawei for my mate 7, and do want to root!

djzero86 said:
Question??? I installed this Rom and everything works fine... but if I delete a system app (Google maps for example)... the app is gone but when the phone reboot the apps appears again??? I use a root browser to delete the app... which should be the problem??? I am the only whit this trouble??
Click to expand...
Click to collapse
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.

mattwheat said:
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.
Click to expand...
Click to collapse
I will try....

On my ham 7 don't work... I tried doing that you say and can't delete the apps

mattwheat said:
Its because you have to also go into data/app and delete it there, and data/data and delete it there too. Then wipe dalvik and cache. Reboot. Done.
Click to expand...
Click to collapse
Well matt somes guys never learn like me.LOL I went and bought another Lg g flex. I still have My Mate 7 and mate 2 galaxy mega, note 3 , note 2 Did you see where Huawei may get the next Nexus line..

dekraan said:
Will this method also work when you;ve updated to lollipop? I cannot get the unlock code from huawei for my mate 7, and do want to root!
Click to expand...
Click to collapse
Yes, worked for me on 5.1
EDIT: !!DONT FLASH!! on 5.1, phone boots, i can get into recovery, but can't install anything
does anyone have stock recovery for B308 5.1??

Will unlock bootloader on this devices break up some features, as on Xperia devices (like DRM keys and so)?
Thank you!

your warranty, but as far as i can tell it doesn't break any features

KennyLG123 said:
Well matt somes guys never learn like me.LOL I went and bought another Lg g flex. I still have My Mate 7 and mate 2 galaxy mega, note 3 , note 2 Did you see where Huawei may get the next Nexus line..
Click to expand...
Click to collapse
Sorry just seeing this message. Yeah it was just released for pre sale yesterday. Huawei does in fact make the Nexus 6p and LG makes the 5x. I'm seriously considering getting the 6p....

Are you sure it works?
It works without unlock bootloader?
The 141, that the Russian guys, only the SuperSU app, but without the superuser binary, which will start during the boot process, it is not worth anything.
So much power could be any other rom.
The stock bootloader available in the boot process, and does not allow only the stock recovery.
Are you sure it works?

[HOW TO] [GUIDE] - How to completely disable Reactivation Lock on SM-G900V

This is a guide how to completely disable Reactivation Lock on SM-G900V in simple steps.
Schematically, we will install Android 4.4.2, bypass Samsung Account login, register a new one and then turn Reactivation Lock OFF.
The phone will be clear after this and ready for any suitable firmware.
1. Download this file: kltevzw_NCG_eLLiKat1_0.zip. It's simply a stock-based 4.4.2 ROM for SafeStrap Recovery.
2. Open kltevzw_NCG_eLLiKat1_0.zip with Windows File Explorer (just click it) and remove this file from it: system\app\SamsungSetupWizard.apk (just navigate to this file, highlite it and hit Del button).
Close Windows File Explorer, the file's size should decrease by about 2 MB.
3. Charge the battery to 50% or above.
4. Download Combination ROM COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar
5. Download zip-file with apks, attached to this post.
6. Run Odin (suppose, you have it and are familiar with flashing), point it to COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in AP slot, boot the phone to Download mode, connect it with a cable, press Start and wait till the flashing process ends. Press Exit, wait till the phone completes boot.
7. Disconnect the cable from the phone and connect again.
8. Extract apks.zip to the Desktop.
9. Copy everything from apks folder on your Desktop to the phone's memory root.
10. Copy your new modyfied kltevzw_NCG_eLLiKat1_0.zip file to the phone's memory root.
11. Disconnect the cable.
12. Press Menu (dotted button) - My Files - All - RootS5.
13. Apex_Launcher.apk - Settings - Unknown Sourches - Ok - Back - Apex_Launcher.apk - Next - Install - Done.
14. BusyBox.apk - Install - Done.
15. Safestrap_KK.apk - Install - Done.
16. tr_v2.apk - Install - Open - make it rain (you should see "You should have root, no reboot required" message) - Back.
17. Superuser.apk - Install - Open - Continue - Normal - Reboot.
18. After reboot in a pop-up window - Apex Launcher - Always - Ok.
19. Menu (dotted button) - BusyBox Free - Grant - close balloon - Install - close balloon - Back.
20. Safestrap - Grant - Agree - Install Recovery - Reboot to recovery.
21. Swipe to Allow modifications - Wipe - Advanced Wipe - Dalvik/Data/Cache - Swipe to Wipe.
22. Back - Back - Back - Install, install kltevzw_NCG_eLLiKat1_0.zip.
23. Reboot System - Do not install.
24. After reboot (8 mins or so) you should see the phone's home screen.
25. Set up a wireless connection or use your SIM-card and internet connection from your provider.
26. Navigate to Settings - Security, find Reactivation Lock and untick it. The phone will ask you for your existing credentials or to register a new Samsung account. Just do it (the second, I guess ).
27. Login to your new account and you will be able to untick Reactivation Lock.
28. When it unticked, the phone is clear and ready to accept any suitable firmware.
Will be glad to hear about your success

Hi I just bought a galaxy s5 used and found out about reactivation lock afterward, is this method working with a s5 with locked bootloader? with any firmware (mine is in MM QC2)
Thank you for the guide anyway I was about to give out

Current firmware version and bootloader status do not matter in this case.
Just move through the guide and never give up

Thank you very much, I followed the guide and I(ve been able to install AEX without problems ! I owe you one

isisky said:
I followed the guide and I(ve been able to install AEX without problems !
Click to expand...
Click to collapse
Oh, really?
I thought my guide is only for Reactivation Lock disabling.
Anyway, you are welcome

Thank you very much. This was exactly what i was looking for. The instructions were very well written and easy to follow.

rialsi6 said:
Thank you very much. This was exactly what i was looking for. The instructions were very well written and easy to follow.
Click to expand...
Click to collapse
You're welcome.
Glad to hear that it helped.

Thanks a Lot
:good::good::good::good:
Someone give a kiss to this men, jajaja
amazin We appreciate

so i can let me phone do ota update to 6.0 and it will not lock my phone ?

buckeyes#1 said:
so i can let me phone do ota update to 6.0 and it will not lock my phone ?
Click to expand...
Click to collapse
Yes, of course.
This is a complete solution, not a workaround/bypass/etc.

bbsc said:
Yes, of course.
This is a complete solution, not a workaround/bypass/etc.
Click to expand...
Click to collapse
my phone is rooted already , i just basically use my root for being able to load custom apk , so i can still do this from doing this above and then take a ota update to 6.0.1 and still be able to load custom apk's?

buckeyes#1 said:
so i can still do this from doing this above and then take a ota update to 6.0.1 and still be able to load custom apk's?
Click to expand...
Click to collapse
Excuse me, I cannot understand what you are asking about.
Reread the first post please and try to be more specific.

bbsc said:
Excuse me, I cannot understand what you are asking about.
Reread the first post please and try to be more specific.
Click to expand...
Click to collapse
im rooted now on android 5.0 , but some of my apps are not allowing usage because im not on 6.0
so im looking for a way to upgrade to 6.0 and keep my phone rooted ,
there is just so much going on in this forum tends to a lot of confusion sometimes

buckeyes#1 said:
im rooted now on android 5.0 , but some of my apps are not allowing usage because im not on 6.0
so im looking for a way to upgrade to 6.0 and keep my phone rooted ,
there is just so much going on in this forum tends to a lot of confusion sometimes
Click to expand...
Click to collapse
Is your bootloader unlocked? If you have an unlocked bootloader you can upgrade all the way to pie by flashing a custom ROM. There are lots of tutorials around. The catch is not all g900v's can be unlocked. You need to find out if your phone is able to be bootloader unlocked by checking you cid. First two numbers of cid= 15 and you can have root on custom ROM till android pie (9.0). First two numbers of cid= || no root for you on (6.0) Lollipop and you can only uprated to 6.1
This explains it all, with details and instructions. Good luck!
https://forum.xda-developers.com/ve...ired-easier-root-method-t3561529/post71147687
Sent from my kltevzw using XDA Labs

buckeyes#1 said:
im rooted now on android 5.0 , but some of my apps are not allowing usage because im not on 6.0
so im looking for a way to upgrade to 6.0 and keep my phone rooted ,
there is just so much going on in this forum tends to a lot of confusion sometimes
Click to expand...
Click to collapse
This thread is about completely another thing.
As for you qutestion, generally, you cannot "keep" sm-g900v rooted while upgrading from 5.0 to 6.0.
You will have to root it again on 6.0.
The rest is said by swiftbones74 in his post above.

bbsc said:
This thread is about completely another thing.
As for you qutestion, generally, you cannot "keep" sm-g900v rooted while upgrading from 5.0 to 6.0.
You will have to root it again on 6.0.
The rest is said by swiftbones74 in his post above.
Click to expand...
Click to collapse
yes i started with this my cid is 11 , so i just ill follow these steps , im just trying to figure out what i can do with this phone ? can i still load my own apk's with a non-rooted marshmallow?

I was rooting my 900v and did not untick reactivation lock. I went back to stock 6.0.1 but the option to untick reactivation lock was grayed out. Thanks to these crystal clear and simple instructions I had it unticked permanently in around a hour . Thanks a bunch!

Will it work on my G900P? I've tried to get rid of that since I got it but there is not much support for this problem in the sprint variant.
EDIT: IT WORKED!!! The only thing I did different was I flashed the combination rom of my device instead of the one on this post. Also I had to wipe data after kltevzw_NCG_eLLiKat1_0.zip flash because it was crashing a lot and turned the screen black after 30 second. So after I wiped data the process was the same as the post. Thank you so much!!!! I'm running lastest Pie rom now.
I didn't expect to kltevzw_NCG_eLLiKat1_0.zip to work because mine is the Sprint variant but after a data wipe I got no errors, so it may work on similar variants with this problem. Now I'm going to start a thread on the Sprint variant linking to this one.

DanniX01 said:
IT WORKED!!! The only thing I did different was I flashed the combination rom of my device instead of the one on this post. Also I had to wipe data after kltevzw_NCG_eLLiKat1_0.zip flash because it was crashing a lot and turned the screen black after 30 second.
Click to expand...
Click to collapse
Well done.
It worked because the "P" variant bootloader is unlocked, so it was able to boot an alien kernel (from the "V" variant).
If it was locked, you would have to replace the boot.img file inside the kltevzw_NCG_eLLiKat1_0.zip with a native "P" 4.4.2 kernel.
It's important, say, for the "A" variant.
Besides, the alien kernel demanded cache cleaning, that's why you had to wipe data.
And it was the right decision to use a native Combination ROM file.
The rest of the files should work on any SGS5 (Qualcomm-based, at least).

It worked .
Thanks !

can anyone help me root my samsung Galaxy a20e

Hi could anyone give me instructions on how to root my samsung Galaxy a20e please

Wazzer21 said:
Hi could anyone give me instructions on how to root my samsung Galaxy a20e please
Click to expand...
Click to collapse
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root

Spaceminer said:
This might help. https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Click to expand...
Click to collapse
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)

triumfanto said:
The third step is doesnt work for me. (Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.)
Click to expand...
Click to collapse
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.

Spaceminer said:
You might not have an unlockable bootloader, or it might just be a different key combo. If you got one that was already carrier branded by Verizon or At&t then you're probably out of luck. You might want to try reading this too. (The middle response.) This is how the regular A20 users are unlocking theirs.
Click to expand...
Click to collapse
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.

triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
Click to expand...
Click to collapse
I love hearing good news! I'm willing to bet that whatever they're doing to get root will also work for you too. You'll have to do a little digging over there. You also have the same chipset as them and they have twrp already! It should be portable to your device without much of an issue. It really sounds like anyone with an A series can rejoice. I'm tempted to get one myself at this point.

Flash failed
Hello,
I have also a Samsung galaxy a20e and I followed the instructions, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normaly, but fails when I use the magisk generated file for the AP . The operation stop when Odin reading the recovery image.
I uncheck the Auto Reboot option like specified
Can someone help me please?

Have a look at this:
https://unofficialtwrp.com/galaxy-a20e-sm-a202fd-root-twrp/
this is what i am trying now, seems to be working to get TWRP and root in one go
(You May also need this: https://www.youtube.com/watch?v=mF2Nxck4FtM
because when i tried this the OEM Unlocking option in Developer Options was missing, follow the instructions in this link, get the OEM Unlock Enabled then follow the first link)

The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?

smda said:
The OEM unlocking option was already active for me. Unfortunately the flash with TWRP that you give still doesn't work. Have you succeed on your side ?
Click to expand...
Click to collapse
Hi,
No I am still having the same issue as you, OEM Unlocked, but the flash at step 7 fails. The firmware that I used is provided by this sammobile. It's works when I use it normally, but fails when I use the magisk generated file for the AP.
It says "Can only flash official images"

1. extract the boot.img from the firmware of your device
2. unzip with zarchiver
3. download magisk manager and choose install then select the boot.img file
4. flash the patched boot.img in Odin
Done
there is no TWRP yet cause it would need to be build from source.

triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!

ParadoxLogic said:
Can you post the files for root? matching the AP via magisk doesnt work, Kingroot doesnt work, I have tried everything, please cam someone help me get this phone rooted!!! the phone is useless as it is as i need titanium backup to work!!!
Click to expand...
Click to collapse
I have the same problem please help to root and put my hand I have tried to do things has this mobile to see if we give a little life thanks

Hello,
Sorry for chiming in, but maybe there is a misunderstanding? The original boot.img file (extracted from the stock firmware) needs to be first patched by the Magisk app. Only after it has been patched, the boot.img file should be flashed by Odin. Maybe the guide over there helps to make it clearer: https://www.getdroidtips.com/root-galaxy-a20-a20e/
EDIT1: I see posts about "vbmeta warning", so there might be some further hurdles, see e.g. there:
https://forum.xda-developers.com/galaxy-a20/help/root-method-twrp-samsung-a20e-help-t4017763
EDIT2: You might also want to have a look into the A20 (i.e. without the "e") section:
https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4
EDIT3: vbmeta.tar attached there:
https://forum.xda-developers.com/showpost.php?p=80188834&postcount=237
Good luck!
PS:
I understood that no TWRP or other custom recovery was needed for this, but I assume that by unlocking the bootloader via the developer options (before flashing) or/and by flashing the patched boot.img (and vbmeta.tar?) file via Odin, the Knox counter is triggered, voiding warranty and some apps not working anymore (e.g. Samsung billing etc.), and OTA updates by Samsung not working anymore. Is that correct?

This thread was started by @Wazzer21. Actually, his first post so far remains the only one. And interestingly, I found this website:
https://www.androidinfotech.com/root-samsung-galaxy-a20e-pie/
...
How to Root Samsung Galaxy A20e Pie 9.0 (SM-A202F, SM-A202K)
First of all, thanks to Wazzer21 – XDA developer for TWRP support and topjohnwu – this genius is a one who discovered and maintaining Magisk. Samsung Galaxy A20e International variants come with a flexible bootloader.
...
Click to expand...
Click to collapse
Er, what does this mean?
When you read further through that page and come to the comments, you learn:
Chris says December 1, 2019 at 3:32 am
This does not work…..at all…
once completing, there is an error VBMETA error…..
Click to expand...
Click to collapse
Selva Ganesh says December 1, 2019 at 11:53 am
The problem is Magisk 20.0. Did you use that Magisk version? If so, Try with Patch version 20.1.
Click to expand...
Click to collapse
Can somebody please confirm this? Or is this all a hoax? Sorry for asking so bluntly, but I have mixed feelings (and still do not want to appear rude or something).
PS:
On this website about rooting the Samsung A20e ("SM-A202")...
https://www.flashfilebd.com/2019/07/samsung-a20-root-file.html
... there are several files for download and the following info:
...
Here You Find Samsung A20e Root File With Magisk Manager Apk. Samsung SM-A202/F/FN/S/K Binary U1 And U2 Root File Available Here.
...
Click to expand...
Click to collapse
What do "U1" and "U2" binaries mean, i.e. how do they differ? There is no explanation (unless I have missed something).

According to some hints from @physwizz in the A20 forum, the root methods described for the A20 also work for the A20e as pointed out in several posts there.
However, currently neither TWRP nor custom kernel seem yet to be available/working for the A20e.

triumfanto said:
Thanks! Linked method works for me.
(1 turn off phone
2 Hold down Volume Up and Volume down both at same time.
3 While holding down both those buttons attach USB cable to computer (easier if you already have it plugged in to the phone)
4 wait for Aqua screen to come up that says to long press (hold down several seconds ) the Volume UP key to unlock bootloader.)
Maybe the root with magisk is possible too.
After few hours later I have a rooted a20e phone! (A202FXXU2ASG1)
When bootloader is really open odin can rewrite original boot.img with the magisk patched one.
TWRP is only need for me now.
Click to expand...
Click to collapse
Hello, i read that you have root your phone, i am trying to do the same thing now but i don't know how please can you give me the process that you followed

I'm curious if at least the 20e version can be rooted, thank you all

ninowebs said:
I'm curious if at least the 20e version can be rooted, thank you all
Click to expand...
Click to collapse
Yes it can be rooted, just install TWRP, then dowbload magisk and flash it in TWRP.

which TPWR?

[RECOVERY] TWRP for Samsung Galaxy A41 [SM-A415F] [BINARY 1 & 2]

TWRP Recovery Project for the Samsung Galaxy A41 [Only for Android 11 Devices, will be upgraded soon.]
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the SM-A415F.​
I am not responsible for any bricked imei, when flashing TWRP backup the EFS & NVRAM partitions to be safe, do not root until having an actually good working backup, if you signal goes restore your backup, if you didn't have a previous backup I got a fix for you , flash your firmware as always but on the CP slot in Odin Flash Tool get the CP slot from a CUD4 firmware corresponding your CSC code.
Click to expand...
Click to collapse
A mantainer is required for this device, I just revived the project but someone with the device needs to mantain it.
Download - You'll always find the latest release in here: https://github.com/Galaxy-MT6768/android_device_samsung_a41xx/releases​Known Issues / Report Issues - https://github.com/Galaxy-MT6768/android_device_samsung_a31nsxx/issues​Telegram support group - http://t.me/a31nsxx​
How to install​
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
​Flashing Disabled vbmeta (To boot a modified system)​
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
​Sources​
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/Galaxy-MT6768/android_device_samsung_a41xx
Note: The device tree should be compatible with SHRP too
Click to expand...
Click to collapse
Special thanks to:​
TeamWin for the Recovery Project.
Akhil1999 for his kernel.
Zillion for re-doing Akhil's lost device tree.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.

I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?

Catoplepas said:
I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?
Click to expand...
Click to collapse
Yeah, just reflash stock firmware via Odin.
Also I should update this build, the latest isn't actually the latest.

Wait until v1.2.0 gets released

Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop

LolUnis said:
Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop
Click to expand...
Click to collapse
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis

Zillion said:
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis
Click to expand...
Click to collapse
Doesn't work the phone still goes into bootloop

LolUnis said:
Doesn't work the phone still goes into bootloop
Click to expand...
Click to collapse
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.

Zillion said:
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.
Click to expand...
Click to collapse
Where can I find the link of the Telegram group?

LolUnis said:
Where can I find the link of the Telegram group?
Click to expand...
Click to collapse
It's a public group

Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.

bestnugnification said:
Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.
Click to expand...
Click to collapse
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.

Zillion said:
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.
Click to expand...
Click to collapse
I guess I'll just repair the screen even if It's not actually worth it. Thanks though.

Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.

abcuky said:
Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.
Click to expand...
Click to collapse
The latest version works on both Android versions