Related
Since I don't have 10 posts, I am not allowed to post links. You'll have to copy and paste. Sorry!
There are several guides and videos that explain how to root/install a custom recovery, but they all require Odin (of which distribution is of questionable legality), or at least Windows. I made this guide for those that can't or don't wish to use Windows/Odin.
Prepare
If your phone still has the MDC software, let it update to the MDL version. Updating to MDL will not cause any problems with the following process.
Download and install [bitbucket.org/benjamin_dobell/heimdall/downloads] Heimdall 1.4.0 on your PC. (You don't need the frontend)
[techerrata.com/browse/twrp2/jfltespr] Download the latest TWRP version and save it on your PC. (Get the .img file)
Get a TouchWiz-based kernel and save it on your PC. Several are listed in the "TW KERNELS" section of [THREAD="2303917"]inlineboy's directory[/THREAD]. You can also pull the boot.img file out of a TouchWiz based ROM, which is what I did.
The rest of this guide assumes you are in a terminal window, in the directory where the TWRP and kernel IMG files are located.
Verify Compatibility
With phone off and no USB cable connected, hold volume down and power. When you feel the vibration, release power, but not volume down.
Once you see the warning screen, release volume down.
Press volume up once to continue.
Connect the USB cable.
Type the following command:
Code:
sudo heimdall detect
If you don't see "Device detected", something isn't working correctly. Don't continue any further until you resolve that issue.
The following two commands get the PIT file from your phone and verify the MD5 of the PIT file.
Code:
sudo heimdall download-pit --output stock.pit
md5sum stock.pit
If the MD5 is not cc4f7331a6434a93000b3dd2684b7204, then stop. Something is different with your phone. The MD5 may vary when (if) a 32GB or 64GB version is released. I have only tested with the 16GB version.
You can optionally create a human-readable version of the PIT file with the following command:
Code:
sudo heimdall print-pit --file stock.pit > stock_pit.txt
Disconnect the USB cable and power off the phone.
Flash the Recovery and Kernel
Follow the instructions in steps 1-4 of the "Verify Compatibility" section above to get back to download mode.
Verify (again) that Heimdall sees your phone and then flash the new recovery and kernel.
Code:
sudo heimdall detect
sudo heimdall flash --RECOVERY recovery.img --BOOT boot.img
The phone will reboot into the normal Android OS. Power it off and disconnect the USB cable.
Verify Recovery Mode
With the phone off, hold volume up and power. When you feel the vibration, release power, but not volume up.
Once you see the "Recovery booting...." text in very tiny blue letters, release volume up.
Assuming everything worked, you should see something similar to the below TWRP splash screen and then the actual TWRP interface a few seconds later. From here, you can flash the ROM of your choice or just flash zip file mods.
i.imgur.com/r32KChJ.jpg (I'm not allowed to post images either - *sigh*)
Notes
Although I think it should work, I could not get the custom recovery to load without replacing the kernel. I read somewhere that this is a Samsung thing.
If at any time you see "ERROR: Protocol initialisation failed!", just start over.
I used Heimdall 1.4.0 64-bit on Xubuntu 12.04.2 LTS with TWP 2.5.0.2 and the FreeGS4 2.0.0 Agat-FreeGS4 kernel. Other combinations should work, but you may want to try these exact versions if you are experiencing issues.
I have only tried this with the Sprint version of the Samsung Galaxy S4, which is why I posted in the Sprint forum. The process should be the same with other carriers, but you may need to use a different recovery or kernel. If you have success with another carrier, please share your experience in the comments.
The following is the terminal output of the actual flashing procedure: (with the protocol and 3 repeating letter subdomain removed from the the URLs)
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
(Reserved)
thank you. keep up the good work
Very helpful, thanks for writing this up!
I installed only the recovery and had to add '--no-reboot' to get this to work.
md5
i know this thread is old but just trying to get my cell back, if i can be pointed in the right direction would greatly appreciate it. Been trying and searching for days , but basically the md5 i get is d41d8cd98f00b204e9800998ecf8427e . not sure what to do, kinda regret getting rid of windows now
jillythedog said:
i know this thread is old but just trying to get my cell back, if i can be pointed in the right direction would greatly appreciate it. Been trying and searching for days , but basically the md5 i get is d41d8cd98f00b204e9800998ecf8427e . not sure what to do, kinda regret getting rid of windows now
Click to expand...
Click to collapse
Well, you should probably start a new thread after you've exhausted search results (in this forum and Google). When you do start that thread, give some details about the problem you're experiencing and what you've tried.
Unfortunately, you'll find a lot fewer people using Heimdall than Odin. It was a lot of trial an error for me, and that's why I posted this guide. Both programs do a lot of the same things, but with different interfaces.
Hi guys:
For so long I see anyone trying to flash the ROMS on any UBUNTU/Debian Linux O.S. . 4 or 5 years ago I tested something similar that also worked with Win XP. Thank you for the detailed procedure. I think there's no need for images, but links could help.
It's nice to see someone thinking out of "the Windows box", I know it will help everyone follow that with Win10 issues !
Would this work with the OK3 5.0.1 s4? I'm so lost trying to figure out how to root it because the dates.
imcarloslol said:
Would this work with the OK3 5.0.1 s4? I'm so lost trying to figure out how to root it because the dates.
Click to expand...
Click to collapse
I stopped doing OTA updates on this phone, so I never had that version to test with. I've just flashed custom images since initially rooting it.
CF-Auto-Root does what you're asking for. You could probably just use Heimdall instead of Odin with the tar.md5 file Chainfire provides for this phone. As far as I can tell, there is no magic in the Odin files he provides.
DynamicBIts said:
I stopped doing OTA updates on this phone, so I never had that version to test with. I've just flashed custom images since initially rooting it.
CF-Auto-Root does what you're asking for. You could probably just use Heimdall instead of Odin with the tar.md5 file Chainfire provides for this phone. As far as I can tell, there is no magic in the Odin files he provides.
Click to expand...
Click to collapse
Well I guess I can confirm it for you. It works fine with my phone and I updated from OK3 OTA update 5.0.1 to the 6.0.1. I used the basic Odin method to flash cf root. Then I proceeded to download clockwork mod. Flashed it. Updated to 6.x touch. Then I just flashed the cm13 ROM and the Gapps. I also flashed the Capos. Everything works fine. But is there a way to improve data ? I've been getting just 1x if even that. Would I be able to flash the OK3 modem again? What is the lowest firmware I can flash things to? This bootloader is unlocked correct?
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK_2021.7z
Instructions
1, You need working adb on your computer. The latest samsung drivers installed. A Sdcard inserted in the phone preferably a 32 gig or less. Must be at least 1 gig. Phone will be wiped! A data connection or wifi is also required.
2. Download and extract the EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK.7z
3. Reboot phone to download mode (pwr+voldwn+home_button). In Odin_Files folder use odin and flash the COMBINATION_VZW_FA44_N910VVRU2APB1.tar.md5 in BL slot in odin
4. Once phone is booted up and connected to computer run 1Install_KingRoot.cmd. This will install kingo root and kingroot app on phone.
5. Once installed make sure phone has data via cell or wifi. Run kingo root to root phone. Phone may kernel panic and reboot just keep trying. Once root is successful move to step 6 if unsuccessful try kingroot if thats succesful click on root permissions in the kingo root app and click on system adb and change prompt to allow. This is not necessary if rooted with kingo app
6. Make sure phone is connected to computer and run1Replace_With_SuperSu.cmd then once this process finishes run 2UnlockBootloader.cmd. This will change CID to Dev edition and then unlock that bootloader. If first time unlocking phone it will change your cid to dev edition then reboot during process. This is fine you will not loose root. Close cmd window wait for phone to reconnect then run again this time it will unlock the bootloaders when done phone will once again power off. Remove sdcard this is very important so I will say again remove SDCard from Phone your phone will not boot with sdcard in until it is reformated! Reboot to download mode you should notice it says DEV Mode.
7. Reboot phone and now you are ready to choose your bootloader you want to be on for this guide we will assume you want to be on latest QL1 Marshmallow bootloader.
8. Make sure phone is connected and run 3UnlockBootloader_MM_QL1.cmd or what ever one you choose. When done Phone will power off and now the bootloader is updated.
9. Now choose the firmware that matches your unlocked bootloader from below
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
10 Reboot phone to download mode and flash above firmware that matches your bootloader version Im using N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar as example. Extract N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar and use provide odin from EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK and choose N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 or the one you choose and in odin BL slot uncheck auto reboot and flash. When flash is done make sure to reboot to TWRP recovery which will be installed and wipe data then reboot. You are done!
11. Above firmware running magisk root may til you additional steps are needed and download magisk zip. You can skip this step if you want as it is rooted and magisk apk is installed but if you want I will provide magisk zip used in root if you want to reflash
Upgrade Bootloaders For EMMC 15 VZW DEV Unlocked Phones
This process requires flashing back all stock firmware in order to upgrade/downgrade bootloaders. So I have made a special rom just for doing this which should make process easy. Its all done with odin and flashire.
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS_2021.7z
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
Instructions
You must be on EMMC 15 unlocked bootloader if not goto post 1 to unlock bootloader
1. Download the EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS.7z and extract this will contain the zips and special firmware for upgrading bootloader. Download above firmware you want to upgrade/downgrade too.
2. You will probably need to wipe data so reboot to TWRP recovery wipe data then reboot to download mode use provide odin in the Odin_Files folder and choose FIRMWARE_FOR_UPGRADE_DOWGRADE_BOOTLOADERS.tar.md5 and flash in BL slot.
3. This will reflash stock firmware and a prerooted special rom with a flashfire preinstalled and minimal files just to boot rom. Your bootloader will be locked for the time being as this is necessary to upgrade bootloaders.
4. When rom is booted choose the zip that matches the firmware you want to install from the FlashFire_Zips folder and place on phone storage.
5. Open flashfire grant root access choose add zip choose the zip you placed on phone click on reboot tab in flashfire and choose reboot to bootloader in will say dev mode this means your unlocked again
6, Now choose above firmware you downloaded extract the tar.md5 file from the rar file and flash in BL slot in odin Uncheck auto reboot when don flashing force reboot to TWRP recovery and wipe data again then reboot phone. You are now Upgraded or downgraded which ever you choose to do.
Mine
This has been needed in our forum for a long time. Fantastic work, thanks!
jrkruse said:
Mine
Click to expand...
Click to collapse
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx
theohtc said:
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx
Click to expand...
Click to collapse
Maybe ask in the huawei thread.
Sent from some device I modified
How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"
DeeXii said:
How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"
Click to expand...
Click to collapse
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified
jrkruse said:
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified
Click to expand...
Click to collapse
Ok I will reflash...
Yes I had internet access, Kingroot does not even function without it.
Thanks for the fast reply!
---------- Post added at 06:15 PM ---------- Previous post was at 05:54 PM ----------
Can't seem to get passed 35%
---------- Post added at 06:41 PM ---------- Previous post was at 06:15 PM ----------
UPDATE:
I used Kingroot desktop version and it rooted the first try.
On to the next step.
---------- Post added at 07:20 PM ---------- Previous post was at 06:41 PM ----------
How long does N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 take to flash?
It has not errored out at all but it seems to be taking longer than I have ever seen.
It's on tz.mbn.
@jrkruse THANK YOU for putting this into such a simplified method that doesn't require large downloads, multiple command lines, or having to downgrade and re-upgrade just to be able to achieve an initial root, unlock, and TWRP!!! I read through way too many methods that were a MILE long before I happened across this one. The ONLY issue i ran into during this process (should help others), was that I had to insert a newer version (and rename it to match the script) of the KingRoot APK to be able to achieve root on my existing CQL1 firmware. I tried the provided APK many times without success, but a newer version was able to achieve root on CQL1 after only a few attempts/reboots. I downloaded the newer APK (version 5.3.7) from the post provided by @Kingxteam at https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461. If anyone is looking for a simple way to root and unlock CQL1 without having to downgrade first, THIS IS IT!!! Thanks again jrkruse for the automated script, and thank you Kingxteam for the thread and links for a KingRoot APK that works with CQL1!!!
I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.
Jalh said:
I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.
Click to expand...
Click to collapse
Did you install the combo firmware because you don’t loose root when on the combo firmware
Sent from some device I modified
Hello all. I'll start by acknowledging that I am a noob with very little experience but can follow technical instructions to achieve desired results when they are described easily for the uninitiated. That said, I too have 2 Verizon note 4s running marshmallow with build numbers ending in CQL1. Following your tutorial, I was able to get one of my phones to step 4 where as described, it kept showing the kernel panic error no less than 10 times. I took the suggestion of another user and was finally able to achieve root with the Kingroot desktop app on my PC. I then clicked on root permissions and changed the prompt to allow. At this point I proceeded to step 6 and after clicking 2UnlockBootloader.cmd, the phone did not reboot as described and the command window returned the following message:
D:\Desktop\EMMC>adb wait-for-device
You May Need To Accept Root Dialog On Phone ...
Files/n4unlock\: 1 file pushed. 1.2 MB/s (23432 bytes in 0.018s)
cd /data/local/tmp/n4unlock
chmod 777 unlock
chown root.root unlock
./unlock
yes
exit
/system/bin/sh: su: not found
Process Complete.
Press any key to continue . . .
No dialog box appeared on my phone and I'm not sure why it says SU not found or what the significance of that missing item is to the process. Am I missing a step? Assuming I have not unlocked the bootloader with step 6, what now? What should I do at this point to achieve the desired result? I do realize that these are older phones and some might care less but making them work now could help my family in a big way. I'd gladly share some of those savings with anyone willing to help troubleshoot... thanks in advance.
Hanging on 1st BL file
Not my first time but seems like im getting hing up during the first flash. how long does it normally take for this 1st BL to flash over
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 636 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
Hung here for about 10min any help would be great thanks!
jrkruse said:
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Click to expand...
Click to collapse
Working perfectly & really much much easier (than the original method which I have done twice so far so I know what I am talking about)!! Thank you
I have to throw in my hat saying that this method didn't work for me either. Like others I got stuck at the rooting stage, I tried numerous times to get root, it didn't work. I then used the upgraded KingRoot, it worked but step 6. 2UnlockBootloader.cmd script wouldn't take, since it seemingly kept losing root. But don't worry, if you've tried this method and are stuck you can still salvage it by going through the manual methods.
Make sure reactivation lock is off if you have the option (I didn't on the firmware that OP installed on the phone), usb debugging is on and adb devices brings up your phone)
----
Flash back to stock
----
I had to flash it to a stock rom using Odin (stick them in AP and make sure re-partition in options isn't checked) Android version 5.1.1, as going through the steps below (which are basically what's in 2UnlockBootloader.cmd) manually still wouldn't take: https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
----
Root and bootloader unlock
----
I used the android version of KingORoot to root
I used this guide (the files used in this walkthrough are the ones largely used in the others below and downloads faster): https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Which has a video here: https://www.youtube.com/watch?v=cfpehEkhfyg
and a text walkthrough with photos (that I like more) from the same guy here: https://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
(Since I largely used this make sure you put "samsung_unlock_n4-fix" in the fastboot folder)
Mine however began to bootloop (I'm unsure why they tell you to reboot to system on step 19 after installing the systemonly firmware but do it anyways I guess. But you had to install the kernel and superuser in twrp as addressed here: https://youtu.be/dhcV93GuHB4?t=1285
After that it booted up to 5.1.1 download rootcheck to root check it.
----
Rooting for Marshmallow
----
After that's done if you want to flash MarshMallow roms, including rooted stock 6.0.1 then you need to further go through the process here, which is basically doing it all over again:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
(Going through this process will kill your wifi connection, the KingORoot PC program didn't work to re-root mine, so you must have a sim card data connection I guess (or reverse tethering if you can get that to work(I had data so I didn't go through that).
then here when you get to the part about flashing a rom:
https://forum.xda-developers.com/no...firmware-safe-upgrade-to-marshmallow-t3402727
(Flashed with Odin (AP) not TWRP)
Anyway, I'm now rooted and bootloader unlocked. It wasn't too hard, once I found the guides it went pretty smoothly. Good luck!
using this method I get a black screen after booting up any aosp rom... logs from booted lineageos17.1:
https://pastebin.com/7yhL7FzM
I rooted 3 910v phones with this method. and am running unofficial Lineage 18.1 roms on all 3 kingroot for pc worked for me.
I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z
jrkruse said:
I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z
Click to expand...
Click to collapse
Thank you again for making our life easier, the ones who will appreciate your efforts are the ones who have done it manually ROCK ON!
Hello Guyz any solution for rooting our beloved A600FN with android 10 ?
Thx in advance
All our hope are on you @corsicanu
If you want root on stock rom and don't want custom rom you can use magisk's patching firmware feature.
Zeflay said:
If you want root on stock rom and don't want custom rom you can use magisk's patching firmware feature.
Click to expand...
Click to collapse
Without custom recovery?
Show me how you do that, dude!!!
For me we need twrp for a600fn on Android 10... Then we can root...
Envoyé de mon POCO F1 en utilisant Tapatalk
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Yes, but don't forget you didn't flash RMM bypass. So you can easily get KG prenormal state.
Zeflay said:
Yes, but don't forget you didn't flash RMM bypass. So you can easily get KG prenormal state.
Click to expand...
Click to collapse
I'm ok with that.
I just wanted to Root my device.
I don't want to flash custom binaries so it's cool...
No enough dev on this phone so no custom roms for me...
Root is enough
Mastakony said:
I'm ok with that.
I just wanted to Root my device.
I don't want to flash custom binaries so it's cool...
No enough dev on this phone so no custom roms for me...
Root is enough
Click to expand...
Click to collapse
Is gaming still smooth on your device on android 10 just like android 9?
Curcepogi said:
Is gaming still smooth on your device on android 10 just like android 9?
Click to expand...
Click to collapse
I don't know, dude.
This phone is really not designed for gaming (IMO)
I use it as my secondary phone...
My pocoF1 for gaming
Rooting ok but?
I rooting with metod of the 2 or 3 post is ok but I want copy frida in system/bin but is not possible
Is only read
With root explorer (superuser) change in r/w
launch command copy
And the phone reboot
Why?
Help and sorry for my English ?
Where can we get this file (Download your stock rom android 10 from Sammobile or Frija)
Sammobile
---------- Post added at 10:58 PM ---------- Previous post was at 10:32 PM ----------
The last stock rom
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Hi, can you still use samsung account, and fingerprint payment features ?
Thanks in advance.
Samsung account works
Fingerprint too
Don't use paiement features but it should work it you use the good tricks (when rooted)
Envoyé de mon POCO F1 en utilisant Tapatalk
Thanks so much.
It works fine on A605FN too.
Hello, i have a A600FN with Android 10.
First i make OEM-Unlock, so it make a Factory Reset.
I Install the new Firmware from SamMobile with Odin.
After this, i install MagiskManager and Patch the AP from the Firmware.
So i try install the Magisk-Patched.Tar but it failed in Odin
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4760 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> system.img
<ID:0/005> vendor.img
<ID:0/005> userdata.img
<ID:0/005> boot.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I test this with the Boot.img from the AP to, same Error.
Right the now the OEM-Unlock Option is disappeared too. (Yes WiFi is on and i test it to with the 8 days back)
I root lot of more Devices. But this one trigger me.
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Confirmed working Magisk on Android 10 using this method on SM-A605G - A605GDXU6CTC9 XID. Thanks! :good:
Hey! Thanks so much for sharing this info with all the XDA community, all those of us who own an a600fn will be forever grateful, me in front line haha I rooted my phone with this method, but I immediately had this problem:
Booted to the system, everything working just fine, root apps working great, but I installed the BusyBox magisk module and it all went down hill. The phone would not boot properly, only on safe mode, and I had to reinstall the firmware with the root AP file all over again. I installed another magisk module, but it was the same thing: It went on a bootloop, or just wouldn't boot at all, only on safe mode, so I've concluded that is not possible to use them on this phone by rooting this way, meaning no magisk modules for me, since I've already upgraded to android 10 and I can't go back to Pie's bootloader or so I've heard. Im i being overly dramatic? Is there a solution for this? Is it because we can't flash the RMM state file without TWRP wich is not available for this phone with this android version?
btw I'm like super fan of all of you who work so hard in pro of making our phones better, there's no enough (insert anything good or that you just love in here) in the world to thank you all. Have a great day!
I hope for your answer
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
no_means_no said:
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
Click to expand...
Click to collapse
Dude, is TWRP. Uninstall it. I ran into the same problem. That recovery just isn't compatible with the bootloader of android 10 for this phone, and it will never boot if it's on your A6. It's all Samsung's fault, hahahaha
Hope I helped you!
no_means_no said:
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
Click to expand...
Click to collapse
You can have root without recovery tho
I just received my Galaxy Ultra SM-G998B. Anyone had successfully root your gs21 using magisk? How's the safety net?
Like to hear any feedback before rooting my phone.
Tnx
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Try magisk canary
I tried rooting the regular S21 but without success yet ( https://forum.xda-developers.com/t/...e-links-and-flashing-discussion-here.4220563/ )
Try magisk canary
Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?
Ziomus said:
Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?
Click to expand...
Click to collapse
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?
rodrigofd said:
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?
Click to expand...
Click to collapse
thanks for your reply, i updated my OP with all the infos
peterkoarl said:
thanks for your reply, i updated my OP with all the infos
Click to expand...
Click to collapse
Couple things:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed
rodrigofd said:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
Click to expand...
Click to collapse
i used CSC, not HOME_CSC - i thought that would mean that data gets wiped?
i did not manually do anything in regards to formatting. what .. could i do?
rodrigofd said:
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed
Click to expand...
Click to collapse
yeah i remember that as well from older devices; i let it sit for at least 10 minutes on the initial flash to make sure, so im pretty sure its stuck.
i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.
peterkoarl said:
i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.
Click to expand...
Click to collapse
Have you tried patching just the raw boot.img file? (Not tar'ed)
You need to uncompress the boot.img.lz4 file first, so you get a boot.img, copy that file to the phone, and select it with Magisk app.
Then get back the patched *.img file into the PC, rename it back to boot img, put it in a TAR, and flash that TAR with Odin.
peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy
peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Patch the extracted the boot.img first and rename the patched boot to "boot.img" BEFORE (not after) compressing it to tar.
Also ensure to enable OEM unlocking in Developer options before flashing the patched boot tar
thanks for all the replies.
i tried the "boot.img only" approach first; makes no difference. magisk says it patched it fine, renamed it back to boot.img, tar'ed it into boot.img.tar, flashed that via odin without autoreboot. cant even get into recovery after restarting.
EDIT: i WAS able to enter stock recovery now; i realized that since i need to have the pc/usb cable connected to be able to enter download mode, maybe i need the same for recovery - and yes, volup+power while cable is connected does drop me into recovery. however, even after factory reset there, it wont boot.
EDIT2: yes my bootloader is unlocked, oem option in dev is greyed out.
EDIT3: i re-did the boot.img-only approach and made sure that i got into recovery IMMEDIATELY after odin this time; did a factory reset and cache wipe. hit power off. powered the phone back on. stuck on samsung logo. this does not seem to be going anywhere.
i didnt know anything about vbmeta before, starting to google it now.
DaReDeViL said:
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy
Click to expand...
Click to collapse
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....
peterkoarl said:
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....
Click to expand...
Click to collapse
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use
DaReDeViL said:
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use
Click to expand...
Click to collapse
thanks, tried, no difference
looking closer at your img, it seems to hold keys for the SM-G981B (Galaxy S20).
i *guess* i need the same thing for my model - my research into how this is done has unfortunately so far been unfruitful....
some more info; when unpacking stock AP, i get the following files:
24/01/2021 14:22 19.864.283 boot.img.lz4
24/01/2021 14:22 658.262 dtbo.img.lz4
24/01/2021 14:25 1.130 metadata.img.lz4
24/01/2021 14:22 2.769 misc.bin.lz4
24/01/2021 14:22 45.072.126 recovery.img.lz4
24/01/2021 14:25 6.207.213.323 super.img.lz4
24/01/2021 14:25 734.568.963 userdata.img.lz4
24/01/2021 14:25 3.751 vbmeta.img.lz4
24/01/2021 14:25 2.815 vbmeta_system.img.lz4
24/01/2021 14:22 12.136.709 vendor_boot.img.lz4
is it possible that this vendor_boot.img is interfering with magisk?
do i need to touch vbmeta_system somehow?
are any of these "new", as in, magisk cannot handle that stuff (yet)?
Try following this guide for the S20 series as it should be the same theoretically. I'm gonna try it as soon as I get my s21 ultra
Hi everyone!
I think I managed to brick it... Can it be recovered from this?
Model Alcatel 1SE 5030D
Idea was to get it rooted...
I managed to finally unlock the bootloader.
I unpacked the official rom with SPD Tool and then patched the boot.img with magisk in order to flash it with fastboot.
Once this done, phone rebooted and is stuck at the very beginning.
It goes no further than the screen with alcatel logo and powered by android with the message of "lock flag unlocked" at the top left.
Cannot reboot to recovery or fastboot.
Cannot be recognized by windows or linux.
Thank you in advance.
the boot.img is embedded to the rom, sometimes as a payload.bin or an encrypted file (Inside a scatter file) , usually located in /dev/mtd/ or /system/bin , and so on .
To READ the encrypted Boot.Img from the Rom you actually need to read The SCATTER FILE, SPD TOOL, or SP Flashtools are the tools that help you -- LOAD THE ROM and read the scatter file. You could open a whole rom on your own and browse the files inside and you will never find the boot.img , you have to open the rom as a scatter file, as far as i know.
With root you can actually extract the boot.img file if you know the location of it for example:
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img
or
dd if=/dev/block/***** of=/sdcard/boot.img
_____
The problem with these devices is that they dont accept flashing anything into it besides system.img
To allow to flash recovery.img or boot.img , you'll have to input special codes with a special software from the Alcatel Company (we don't have those, cuz they're not leaked)
What you did was trigger a lock, a block to the phone by trying to bypass that security code they placed onto the device.
You took the boot.img out, patched, and then placed back inside/reflashed it as an individual file, with spd tool or adb, if you did with a flashing tool then, this triggered the security of the phone, and maybe other img's got patched and flashed too (or corrupted) such as recovery.img, boot.img, vendor.img , product.img , etc etc, (these are all just regions of the ROM read through the scatter file) ( i guess this locked ur device)
Repairing it :
1) IF YOU can still access into fastboot mode (bootloader) somehow.
** I think just reflashing a new ARM ROM compatible with ur storage partitioning can fix it
(A only or AB )
(try booting the phone and then connecting it to the usb cable , to the pc, and doing
command: fastboot reboot bootloader
or fastboot devices
if you're lucky and its detected , or goes into bootloader you can just do fastboot flash systyem /name/of/rom.img
and this could flash a new rom and revert the boot.img, recovery and everything else to default
thus helping you boot ur phone again.
2) If you can't even access recovery or bootloader (fastboot mode)
** What i think you have to do to repair it is the following, REFLASH the full rom again onto the phone with sp-flash tool
GET the UNPATCHED Boot.img (i hope you made a backup of it), get the whole intact rom, (or any other compatible working rom) the scatter file intact and reflash the WHOLE full rom back again with SP FLASH TOOL
(forget about Placing the PATCHED boot.img in the scatter file) we wanna use the unpatched files, all virgin.
SP FLASH TOOL gives you an option to reflash A WHOLE ROM, i suggest to try reflashing the stock ROM (considering its good) or Reflash another Android ARM AOSP ROM, you can find plenty here in XDA, i can give you links (make sure to HAVE A GOOD ROM this could also be the reason your phone got corrupted, the boot img and files you were handling were probably already corrupted or flashing them simply broke the security code thats about it) that is why you want a ROM that is known, and good for any phone/tablet, preferrably with the same chip as yours or with enough reviews or comments from others, 90% of the roms we can find in google have viruses or are corrupted, specially considering its ALCATEL no one handles this, AND WE ALWAYS WANT TO MAKE SURE OUR PHONE ACCEPTS recovery.img, boot.img , etc without trigering any security codes, if you extracted your own ROM/stock firmware then its alright, thats fine. but you forgot about the security codes, you triggered those i think. Make sure that scatter file loads into SPFT without error, SPFT checks the PRELOADER and DSP_BL and if they aren't in the scatter directory, it will fail and maybe crash. the regions/files can get corrupted. Everything is in green, everything is setup, then you can click " Flash whole rom " this is what you need i think that way you revert everything to default , Boot.img, recovery.img all of it that got locked (you triggered the security code, i think so, because if it wasn't so , it would just boot loop, since yours boot loops and then WARNS you, it means you triggered some code or corrupted something)
3rd option return that Alcatel Toaster, to the company and pay them to repair it , cuz they have the softwares to do all this in just a few clicks.
The issue is the company, they suck hard, and all phones they make are low quality phones .