Database Develop

[Q]

I want to root my SGN but i am confused which metod i should to use?
TNx?
1.2. If you are not rooted yet: Using the zergRush exploit
(while it still works on our firmwares, this exploit will probably be fixed soon! Known to work on KJ1 and KJ4 firmwares)
- Download the attached "InitialRootFlasher.zip" and extract it somewhere
- Download one of the CF-Root kernels, and extract it (repeat) until you end up with a zImage file
- Place the zImage file from the CF-Root kernel in the zImage folder from InitialRootFlasher
- Start "not-rooted-yet.bat" and follow the instructions
1.3. If you are not rooted yet: Flash a modified FACTORYFS
I am providing this method just this once, for the KJ1 firmware. This is the /system part of the KJ1 firmware, modified so at first boot it will flash the KJ1 CF-Root and reboot, without getting you the yellow triangle or increasing the flash counter.
Using a newer firmware? Do this operation first, then flash the newer firmware back using CWM Manager. This is explained in Chapter 3 below.
Download: http://www.multiupload.com/YB9EL8D8O3
- Optional: flash the full KJ1 firmware first
- Unzip the file, you should get "SGN_XX_OXA_KJ1_FACTORYFS.tar"
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (see below)
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done
If you do not know how to get into download mode:
- Turn off the device
- Count to 10
- Hold the "home" (the big physical button in the middle) and "volume down" buttons
- Press and release the power button (keep holding "home" and "volume down" !) to turn the device on
- You should get a download mode screen
- If it tells you to press a button to continue, do so
--- Chapter 2: Getting rid of ODIN ---
This is easy. Find ODIN, and delete it. In the future you should only need it to flash bootloaders, which probably will only really be needed one time: when upgrading from Gingerbread to Ice Cream Sandwich.
--- Chapter 3: Upgrading your firmware ---
My CWM Manager application has a full-fledged firmware flasher built in. Using the flasher from CWM Manager does NOT give you the yellow triangle or increase the flash counter.
3.1. Flashing a new kernel
This is easy. CWM Manager can flash zImage files (on any rooted kernel), zImage files inside a .tar file (only on a CF-Root kernel), and zImage files inside a .tar.zip (only on a CF-Root kernel). Note that zImage must be the ONLY file in an archive, if is is inside a tar or zipped tar.
- Put the zImage (or tar, or zip) file on your SD card
- Open the CWM Manager app
- Select "Flash kernel"
- Select the file you just put on your device
- CWM Manager will flash the kernel and reboot
If you flash a non-CF-Root kernel, you will lose a lot of functionality from CWM Manager. However, the app will (likely) still allow you to flash kernels.
3.2. Flashing a new firmware
Important: This works ONLY on a CF-Root kernel !
CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.
- Download the firmware you want to flash
- If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
- Create a folder named 'firmware' on your external SD card
- Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
- TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
- Open the CWM Manager app
- Select "Flash stock firmware"
- At this point, CWM Manager will tell you about the firmware parts it has found, and which ones it will flash. It will also give you warnings about bootloaders and PIT files if those were found. If some firmware parts are present multiple times, it will ask you which file to use as source.
- If what you are flashing includes both kernel and system parts, CWM Manager will warn you about this as you are about to lose root. It will provide you with three options:
1: Keep CF-Root kernel
Keeps the current CF-Root kernel, only flash the other parts. You will not lose root or CWM Recovery. You can flash a newer CF-Root kernel later (or maybe you have already done so), see 3.1 above.
2: Pre-root system
Flashes both kernel and system parts, but roots system during the flash. You will lose CWM Recovery, but you will keep root (if all goes well). The CWM Manager application will also remain, and allow you to flash the correct CF-Root kernel at a different time (if you have not done so before), see 3.1 above.
3: Flash normally
Doesn't do anything specific. If the kernel you are flashing is not a CF-Root (or similar) kernel, you will lose root, and CWM Recovery.
- CWM Manager will reboot into CWM Recovery, and will flash the firmware, rebooting afterwards.

Go here and just read after 16Nov edit
http://forum.xda-developers.com/showthread.php?t=1329360

[Q] Help me to fix “NULL NULL” after N7000DDLA5

I update to N7000DDLA5, but after that when I type any key from keyboard showing “NULL NULL”.
I found some fix from XDA, by flashing “CSC” file by mobile odin. But from where I will get that CSC file, I have only single N7000DDLA5…..TAR.MD5 file only.
Advise please…

i extract TAR.MD5 with WINRAR. then flash with Mobile odin > Cache > Internal SD-Card > Cache.img
but after restart i am getting below message and issue still persist. please help me....
# MANUAL MODE #
--Updating application..
Successfully updated application.
--Appling Multi-CSC…
Installing Multi-CSC
Can’t access to ‘/system/csc/XSG/system/’.
Successfully applied multi-CSC.

I faced the same problem. Use the latest version of Mobile Odin to flash the whole thing again, you'll be fine. You can also use the CWM app to flash this.
1. If you have an extra memory card, use it. Make a folder named 'firmware' (without quotes) and put your tar.md5 file in it.
2. In the CWM app, select 'flash stock firmware'.
3. Select continue>keep CF Root kernel.
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
I must tell you, this has never worked for me though, and I've always managed to miss the error message thrown up by the recovery, so I can't tell you why

I got this error when updating to la4, not sure what the issue is but I don't use the samsung keybaord anyway I use smart keyboard and the issue doesn't happen with this keyboard, so I'm not t bothered about it

Flash stock firmware method stated above

bloodyhippo said:
I faced the same problem. Use the latest version of Mobile Odin to flash the whole thing again, you'll be fine. You can also use the CWM app to flash this.
1. If you have an extra memory card, use it. Make a folder named 'firmware' (without quotes) and put your tar.md5 file in it.
2. In the CWM app, select 'flash stock firmware'.
3. Select continue>keep CF Root kernel.
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
I must tell you, this has never worked for me though, and I've always managed to miss the error message thrown up by the recovery, so I can't tell you why
Click to expand...
Click to collapse
Bloodyhippo, issue resolved, I follow your steps.
1. Update Mobile ODIN pro (v2.15)
2. re-flash same firmware (N7000DDLA5) whole again.
3. after restart, Samsung keyboard issue resolved. Done!
Many thanks guys.

musheercmr said:
Bloodyhippo, issue resolved, I follow your steps.
1. Update Mobile ODIN pro (v2.15)
2. re-flash same firmware (N7000DDLA5) whole again.
3. after restart, Samsung keyboard issue resolved. Done!
Many thanks guys.
Click to expand...
Click to collapse
Thats what I was going to say. Glad you got it

thnxxxxxxxxxxxx 4 this useful tip

null keyboard characters after rooting my Samsung Galaxy Note
I just got my samsung galaxy note (SGN) and rooted it following the instructions on this page (very good - worked great)
http://forum.xda-developers.com/showthread.php?t=1331784
When the SGN booted it was rooted but the built in samsung keyboard would display null no matter what key i hit.
I did not have mobil odin installed nor could i install it without using my keyboard and i did not want to re-flash a kernel or any other drastic measures... so to fix this easily i went into the android market now (google play store) and then tapped CATEGORIES then TOOLS then TOP FREE and scrolled down to GO Keyboard (i am sure any free keyboard will work - this is just the first one i found) and installed it.
This resolved the Samsung keyboard problem and i can now type normally so i can upgrade to new ROM's etc...
-Mitch SGN / CF-ROOT / CWM / android 2.3.5 / baseband LA4 / kernel KJ1

hi guys
i m new to this site
this small tutorial is when ur restoring ur rooted or normal stock firmware with any other firmwares or unrooting and restoring to stock firmware.
btw its very simple when u update firmware over odin use the latest version and don't forget to check USB debuggin start update process.......
it takes some time.
when ur device is working it will be null null null .........
go to recovery mode wipe factory reset first then wipe partition...
when ur finished with above steps
go to downloading mode and repeat the update of firmware procedure from ODIN again ...
ur phone will be without any errors (for ex: no null in keyboard wen u type
and will be able to update from ur current firmware if updates are available ...
any doubts please feel free to ask thank you.

flash it via pc odin
i flashed it via mobile odin and got the null error too

bloodyhippo said:
If you don't happen to have an extra memory card,create a folder named 'external_sd' at the root of your internal storage (/sdcard/external_sd/firmware/blahblah.tar.md5).
Click to expand...
Click to collapse
I dont have the firmware in "md5" format, but in "TAR", will that work?

[Guide] Update Rooted Note FE from Nougat to Oreo

share my process and trouble shooting for upgrading rooted note fe from nougat to oreo without re-install. I eventually got a solution
my nougat installation had data encryption enabled during setup, not sure if it made difference, or the cause of my trouble below.
the process references the post [SM-N935F/DS] How to flash TWRP & Root with Magisk (Int. Ver.) [Oreo Updated] and mostly used files provided there.
start with rooted nougat with TWRP
1. download latest OREO ROM from sammobile. Mine has CSC code XME
2. unzip to five .tar.md5 files
3. flash BL/AP/CP/HOME_CSC via Odin, turn off auto-reboot
4. exist download, and re-enter download immediately without letting it to boot up (press home+volume down+power immediately)
5. flash TWRP in odin
6. reboot into recovery
7. install in TWRP RMM-path
8. install in TWRP no-verty-opt-encrypt. This is required for me as my data is encrypted
9. reboot and let android complete the update process
--- note, I did not install the /data partition patch mentioned in original thread for OREO, as it led to boot loop and I had to re-flash stock rom --
10. reboot back to TWRP and install magisk to root
This should be it. BUT --
system boots up ok, but I noticed that CSC was not installed. there is not even /system/csc folder. somehow, the csc was not installed during the installation process. I tried multiple time, same results. here is how I got over it
1. from stock rom 's HOME_CSC_xxx.tar.md5 file, remove ".md5" to turn it to a tar file, and use 7zip to unzip it and take cache.img.lz4
2. use lz4 tool to covert cache.img.lz4 to cache.img
3. use SVAImgUnpack to covert cache.img to cache.ext4.img
4. use ext2explore.exe included in SVAImgUnpack to open cache.ext4.img and extract the sec_csc.img (ext2explorer.exe needs to run with admin)
5. use TWRP to install the extracted sec_csc.img
6. open a terminal in TWRP or use adb shell to run the following command cp -dpfr /system/csc/XME/system/* /system
that is it. and it should work.
If you need to enable VoLTE for Verizon or T-Mobile. extract customer.xml file from Galaxy S8 rom CSC's VZW or TMB folder, and copy it to overwrite customer.xml file under /system/csc.

Thx For informations This phones community is quiet silent :/

If you need to enable VoLTE for Verizon or T-Mobile. extract customer.xml file from Galaxy S8 rom CSC's VZW or TMB folder, and copy it to overwrite customer.xml file under /system/csc.
Click to expand...
Click to collapse
Anyone have the T-mobile CSC file to upload here?

prozo said:
Anyone have the T-mobile CSC file to upload here?
Click to expand...
Click to collapse
I need this as well

Don't forget -d: lz4 -d [input] [output]

What happened to the boot.img patching option in Magisk Manager?

I know Magisk can be flashed via TWRP, and that is the preferred way for me, usually. But on Magisk 19.3 I don't see an option to patch the boot.img without flashing the Magisk installer zip from TWRP. I just want to patch the img and flash it via Odin (I have a Samsung device, fastboot not available on those). I would like to keep the recovery as stock and system partition unmodified with dm-verity enabled. That way I can just use system less modules.
I normally prefer Phh's Superuser or SuperSU, I like old fashioned, traditional root without systemless or modules. But there are some tests I would like to run, and modules I would like to try.
Thanks!

It's right there if you press the install button and choose "Install"... If it it isn't on your setup you need to provide more information.
And both phh's and SuperSU are systemless root.

My setup:
Samsung Galaxy Note 4 N910F (international unbranded variant, latest stock Marshmallow firmware)
When I press install in Magisk Manager, it only offers the option to download a zip, no boot.img patching. I need the output file as tar or tar.md5, not img, so it can be flashed with Odin (no need for TWRP if flashed that way).
You're right, Phh is systemless, but it doesn't offer modules. SuperSU can be systemless or forced as system-installed.

So you don't have the "Select and patch a file" option at all? If you're looking for a specific tar file option there isn't one anymore. Just pick the file and let the Manager do the rest.

Didgeridoohan said:
So you don't have the "Select and patch a file" option at all? If you're looking for a specific tar file option there isn't one anymore. Just pick the file and let the Manager do the rest.
Click to expand...
Click to collapse
Hi, I am confused. I did use Manager 7.3.5 with Magisk 19 and now latest 20 .
When I use "select and patch a file". Use a stock boot.img file from my Tab 4 8.0 T330 Android v5.1.1 last version available. Whilst patched file is being created, a message flashes on screen img or tar file can be selected.
The problem is there is No option to "select img or tar file in output" as was the case in earlier versions of Manager v5 or 6. Which I previously used to create either patched img or tar files.
I have created different img files using the same original boot.img, only created using different Manager updates as they are created and released. Each time a new version creates a different file size.
Therefore you comment "tar file option is no more". WHY NOT.???
Next comment Just pick the file and let the Manager do the rest". Please explain or provide link to method you are referring to.
Another Question. Can I use an earlier img or tar file created on earlier Manager version with the latest Magisk version to install Magisk 20 on the Tablet. I have also used "img to tar to md5" convertor software and use ODIN to update the patched boot file, or install TWRP and use patched img file.
Any comments would be appreciated. Cheers

@BeeJ1109 It just means that the Manager will detect what type of file you're providing and outputs an img or tar file depending on the input. Tar in, tar out, etc.
There's no specific option for it in the settings anymore, since it is handled automatically now.

Didgeridoohan said:
@BeeJ1109 It just means that the Manager will detect what type of file you're providing and outputs an img or tar file depending on the input. Tar in, tar out, etc.
There's no specific option for it in the settings anymore, since it is handled automatically now.
Click to expand...
Click to collapse
Hi, Didgeridoohan, Thanks for your reply.
So I understand that if I use boot.img it will convert to patched.boot.img or patched.magisk.img.
If I use boot.tar it will convert to patched.boot.tar or patched.magisk.tar.
Question 1: So you are now saying I have to use another app to convert img to tar before patching or after patching.
Seems to me a backward function of your latest Manager, when previously you had a choice to select which option you received as the output file. So much extra time and effort to achieve the same result.
Question 2: This the case then I have to install latest manager and reinstall older version that worked. Create patched file as tar. Use ODIN to install patched boot file.
Do I need to rename magisk to boot, so ODIN will accept the patched tar file.
I use latest ODIN 13 on my Samsung Galaxy Tabs 4 & S4 and Phones S3, S4, & S8.
Question 3: Will older version created Tar file work with latest version Magisk to Root device, Then update both Magisk and Manager as normal when updates are released.
Or do I root using same version Magisk and Manager that created the patched boot file, then update to latest version.
I have successfully updated Stock and RR or Lineage OS Firmwares for years.
Samsung devices do not allow sideload installs and ODIN is so easy to use to install updates or new versions for all devices.
I also used other methods to root devices ie TWRP, Flashfire, but now Magisk is updated regularly, Hide Apps works on 7.1 thru 10, whereas old apps don't work past Android 4.4.
Thanks for your assistance, Cheers BJ.

@BeeJ1109 I know very little about Samsung so I can't really answer most of your questions, but wouldn't the file be a tar file to start with?
Anyway, if you wish for some functions to work differently than they currently do I would suggest opening a feature request issue in GitHub (with a detailed description of what you want).

Any solution?
Hi there, i know this is an old thread, but i was wondering if anyone found a solution for this.
I am also trying to install Magisk Manager, modifying the boot.img file from my firmware. The problem i find is that the boot.img is inside a boot.img.lz4 (which i open with the modified 7zip), and that is inside another img.tar file.
Now, i seem to understand the old Magisk Manager (version 6 for example), would allow to decide the output file, while the v7 does not anymore. I would just receive a repatched_boot.img file, which i cannot use to flash using Odin.
I also tried installing Magisk v6, but it will force to update upon doing the repatching.
Do you have any other solution?
PS: all reason i'm trying to do this is trying to install (any) TWRP on my tablet SM-P580 will show a blue/black screen.

walty80 said:
Hi there, i know this is an old thread, but i was wondering if anyone found a solution for this.
I am also trying to install Magisk Manager, modifying the boot.img file from my firmware. The problem i find is that the boot.img is inside a boot.img.lz4 (which i open with the modified 7zip), and that is inside another img.tar file.
Now, i seem to understand the old Magisk Manager (version 6 for example), would allow to decide the output file, while the v7 does not anymore. I would just receive a repatched_boot.img file, which i cannot use to flash using Odin.
I also tried installing Magisk v6, but it will force to update upon doing the repatching.
Do you have any other solution?
PS: all reason i'm trying to do this is trying to install (any) TWRP on my tablet SM-P580 will show a blue/black screen.
Click to expand...
Click to collapse
Hi.
Use Magisk Manager to create a modified stock boot.img. as you have mentioned.
What I do is search for Windoows PC "img to tar converter" app. on Google search.
Lots will be found. They a small executable batch file. Which you Right click on the "convert tar".exe file to run on a Windows PC.
Best one will have Input and Output directories. You can inset your patched boot .img file, you have just downloaded for your device. Add this file into Input directory of the app using Windows Explorer File Manager. May have to setup the location of resultant output directory. Then run Img to Tar converter . The application will convert your patched_boot img file into a patched_boot.tar file.
That newly modified .tar can now use ODIN. To install patched_boot.tar onto your connected device via PC USB port using the Latest version of ODIN 3.14.1.
Hope that helps. CHEERS

Question how i can update with rooted S21 Ultra exynos

hello there ..
plz hlp how i cat update software with keep rooted

Unroot and go back to stock.

If it's running well... leave it alone.

You'll have to root again probably.
So it's a waste of time to update it and lose the Root unless there is a major upgrade like Android 12.

As Samsung has NO full project treble there are no a/b partitions. So you can't update and keep root. You need to use ODIN to update and then root again which takes about 5 minutes. Just don't wipe your storage with Odin

If you have rooted with magisk it is easy.
Download latest firmware and extract it.
Copy file starts with AP_xxx to phone.
Open magisk and select install
Select option "Select and patch file"
Browse to AP_xxx file which you have copied to phone and patch it.
Locate file normally named as magisk_patched-xxxx.tar to PC again.
open odin and add files to their specific slot.
For AP slot used magisk patched file
For CSC there are two files, here you need to select which have HOME_CSC file not CSC.
If you flash only CSC this is wipe your device so Use HOME_CSC file.
Once flashing process complete, your device will reboot and Voila.
Enjoy upgraded firmware with root retained and without data wiped.
P.S. While coping file to or from device, use adb push or pull respectively as some user report corrupted file while coping it through MTP.

have you found a solution to root galaxy s21 5G us? 6 bit security?