Database Users

Huawei Honor 4C Index and Troubleshooting Thread

Due to the fact that all guides, rooting threads about the Huawei Honor 4C are scattered all over the XDA and hence are difficult to be searched for when needed, I decided to create an index thread to keep all ROM updates, rooting and unlocking guides in one neat clean thread.
I’ll try my best to keep this thread updated as soon as new information is released from trusted sources or whenever new mods, ROMs, etc. are released.
You can also post your queries here and I'll try my level best to answer them.
Contents:
1. Device Specifications and Variants
i. Specifications
ii. Variants
2. Stock and Custom ROMs
i. Stock EMUI 3.0 and 3.1 Download Links
ii. Upgrading from Kitkat to Lollipop
iii. Downgrading from Lollipop to Kitkat
iv. Flashing Stock ROM in cases of bootloop
v. Flashing Stock ROM when device unable to boot to recovery or update mode
vi. Stock based Custom ROMs and AOSP based Custom ROMs
3. Unlocking Bootloader, Rooting and Custom Recoveries
i. Custom Recovery and SU zips Download Links
ii. Unlocking Bootloader and Relocking Bootloader
iii. Installing Custom Recovery
iv. Restoring Stock Recovery
v. Installing SU Binary (Rooting your Device)
4. ROM Add Ons and Miscellaneous Guides
i. Xposed Framework on EMUI 3.0 and EMUI 3.1
ii. Viper4Android Sound Mod
iii. L Speed Mod for Android Lollipop
iv. Changing Region
v. Extracting Update.APP
5. Credits
Device Specification and Variants​Device Specification
Processor HiSilicon Kirin 620 1.2 GHz Octa-Core ARM 7a-64-bit
RAM 2 GB SDDR
ROM 8 GB (3.2 GB available to Kitkat users / 2.5 GB available to Lollipop users)
Display 5.0 Inch 1280x720 294 dpi IPS LCD Capacitive Touchscreen with Scratch Resistant Glass
Android Version EMUI 3.0 Android 4.4.2 (upgradeable to EMUI 3.1 Android 5.1.1 / EMUI 4.0 Android 5.0 confirmed and will be available in February 2015)
Battery 2550 mAh Li-on Battery (Non-Removable)
Network GSM / HSPDA+ (No LTE)
Camera 13 MP back Geo-tagging, Paronama, HDR, Time-Lapse, Video Recording 1080p at 30 fps / 5 MP front, Video Recording 720 p
GPU Mali 450-MP4 OpenGLS 2.0
Also see attached CPU-Z screenshots for advanced and complete specs.
Variants
Pakistan CHM-U01 B067 (Kitkat) / B120 (Kitkat) / B310 (Lollipop)
India / Malaysia / Indonesia / South Asia CHM-U01 B063 (Kitkat) / B070 (Kitkat) / B302 (Lollipop) / B330 (Lollipop) / B340 (Lollipop) / B350 (Lollipop) / B360 (Lollipop) / B380 (Lollipop) / B390 (Lollipop)
Russia CHM-U01 B060 (Kitkat) / B120 (Kitkat) / B130 (Kitkat) / 304 (Lollipop) / B310 (Lollipop) / B320 (Lollipop)
China Developer Channel CHM-UL00 CHM–TL00 CHM-TL00H v5.9.1 (Lollipop) / v5.9.16 (Lollipop) / v5.10.1 (Lollipop) / v5.10.16 (Lollipop) / v5.11.1 (Lollipop) / v5.11.16 (Lollipop) / v5.12.1 (Lollipop) / v5.12.16 (Lollipop) / v5.12.16 (Lollipop) / v6.1.1 (Lollipop) / v6.1.16
China Stable Channel CHM-UL00 CHM–TL00 CHM-TL00H B181 (Kitkat) / B191 (Kitkat) / B200 (Kitkat) / B211 (Kitkat) / B220 (Kitkat) / B230 (Kitkat) / B231 (Kitkat) / B419 (Lollipop) / B422 (Lollipop) / B425 (Lollipop)
Stock and Custom ROMs​All guides in this section require you to have Stock Recovery installed and device must be completely unrooted unless specified. If you have a custom recovery installed see Unlocking Bootloader, Recovery and Custom Recovery > Restoring Stock Recovery Section for instructions.​Stock EMUI 3.0 and EMUI 3.1 Download Links
Just click on the Version Number to download the respective ROM.
EMUI Emotion UI 3.0 Kitkat 4.4.2
Pakistan CHM-U01 B067 (Kitkat) / B120 (Kitkat)
India / Malaysia / Indonesia / Asia Pacific CHM-U01 B063 (Kitkat) / B160 (Kitkat) / B063 (Kitkat) / B070 (Kitkat)
Russia CHM-U01 B060 (Kitkat) / B120 (Kitkat) / B130 (Kitkat)
China Stable Channel CHM-UL00 CHM–TL00 CHM-TL00H B181 (Kitkat) / B191 (Kitkat) / B200 (Kitkat) / B211 (Kitkat) / B220 (Kitkat) / B230 (Kitkat) / B231 (Kitkat)
EMUI Emotion UI 3.1 Lollipop 5.1.1
Pakistan CHM-U01 B310 (Lollipop)
India / Malaysia CHM-U01 B330 (Lollipop)
Russia CHM-U01 B310 (Lollipop)
Indonesia CHM-U01 B340 (Lollipop)
Asia Pacific CHM-U01 B360 (Lollipop)
China CHM-UL00 CHM–TL00 CHM-TL00H v5.9.1 (Lollipop)
Upgrading from Kitkat to Lollipop
Always try to take OTA updates whenever possible as user data isn't wiped. However, if you want to start anew, just use the below listed methods. ​Backup all important data on internal storage before performing upgrade. Internal Storage will be completely wiped after upgrade. Ensure battery is fully charged or at least 30%. Do not press any button nor attach your phone to charger after the upgrade process is initiated.​Normal Upgrade (Upgrade using the Software Updater)
Download the Lollipop Stock ROM according to your region. See Stock and Custom ROMs > Download Links section for download links.
Ensure your SD card has atleast 3.0 GB of free space.
Extract the downloaded *.zip or *.rar and copy the dload folder (with the UPDATE.APP in it) to the root of your SD card. (In some update packages, there might be multiple UPDATE.APP. Hence copy the UPDATE.APP with has the largest file size)
Insert the SD card (if not already) and navigate to Settings > Update > Menu > Local Update > Full Package:UPDATE.APP . Now finally press Install.
Your phone will reboot to recovery. Wait for the progress bar to finish. When it does you phone will switch off. Hold the power button to switch it back on.
First boot might take some time due to app optimization hence be patient.
Forced Upgrade
Download the Lollipop Stock ROM according to your region. See above section for download links.
Ensure your SD card has atleast 3.0 GB of free space.
Extract the downloaded *.zip or *.rar and copy the dload folder (with the UPDATE.APP in it) to the root of your SD card. (In some update packages, there might be multiple UPDATE.APP. Hence copy the UPDATE.APP with has the largest file size)
Insert the SD card (if not already) and Power Off your device.
Now while holding Volume Up and Volume Down buttons, hold the Power button to power on the device and boot straight to Software Upgrade Mode.
Wait for the process bar to finish. Device will automatically reboot after the upgrade has completed successfully.
First boot might take some time due to app optimization.
Downgrading from Lollipop to Kitkat
Method 1
Download your current Lollipop ROM (see the first section for download links) and the Kitkat ROM you want to downgrade to.
From Lollipop Stock ROM: First copy UPDATE.APP located in 0_CUSTOM_PACKAGE\MiddlePackage\dload to dload directory in the root of your SD card.
Use any of the method posted in Stock and Custom ROM > Upgrading from Kitkat to Lollipop section to flash the Middle Package UPDATE.APP. Skip the copying stuff in those sections.
After the flash has completed, delete the existing UPDATE.APP.
From Kitkat Stock ROM: Copy the Main UPDATE.APP (one with the larger size) to the dload directory in the root of your SD card..
Use any of the method posted in Stock and Custom ROM > Upgrading from Kitkat to Lollipop section to flash the Main Kitkat UPDATE.APP. Skip the copying stuff in those sections.
Method 2
This method requires ROOT SU privileges on your device. Also please make a backup before proceeding.​
Make a TWRP or CWM backup. If something goes wrong, you must have something to restore from.
Download and install Terminal Emulator from Play Store. Open the app and execute the following commands (grant SU privileges when prompted):
Code:
su
mount -o rw,remount /system
Open your favorite File Manager which supports browsing / partition and obviously Root permissions , and navigate to /system.
Search for build.prop and open it.
Find ro.product.model and change it's value to balong.
Save the file and make sure permissions are set to -rw-r--r--.
Reboot you device, flash Stock Recovery and any Kitkat ROM you want. See Unlocking Bootloader, Rooting and Custom Recoveries > Restore Stock Recovery for flashing Stock Recovery instructions and Stock and Custom ROM > Upgrading from Kitkat to Lollipop for Stock ROM flashing methods and instructions (You have to use the FORCED METHOD to flash).
Flashing Stock ROM in cases of bootloop or otherwise
If you are stuck in a bootloop, device keeps on restarting follow this guide.
Before you follow this guide, perform a FACTORY RESET on your device. If this doesn't work, then continue.
Download the ROM version currently on your device or any newer one. See Stock and Custom ROM > Download Link section for download links.
Ensure that you are on Stock Recovery. If not see Unlocking Bootloader, Rooting and Custom Recovery > Flashing Stock Reovery section to flash Stock Recovery.
Use the Forced Upgrade method in Stock and Custom ROM > Upgrading from Kitkat to Lollipop section to re-flash the Stock ROM.
Flashing Stock ROM when device unable to boot to recovery or update mode
Alright! So your phone is completely messed up and you can't boot to recovery or anything. Well this guide is for you! Resurrect that device!​Always use original data cable that came with your device for flashing stuff. It is not necessary but recommended.​Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Flashing the ROM through Fastboot
First download and install Huawei Update Extractor. Visit the official XDA Forum for download, installation instructions and usage.
Extract boot.img, recovery.img and system.img from UPDATE.APP and copy it to any directory on your computer. See Miscellaneous Guides > Extracting Update.APP section for instructions.
Open Command Prompt in the directory where you have extracted the files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Completely power off your device.
While holding Volume Down button, connect your device to PC via USB cable to boot to Fastboot Mode.
Execute these commands one at a time using the command prompt.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Now hold Volume Up button and Power button simultaneously. As soon as you see the Honor logo, release the power button. Your device will now boot into recovery.
Perform a Factory Reset through recovery.
Availability of Stock based Custom ROMs and AOSP based Custom ROMs
Unfortunately, light is pretty dim here. There are no Custom ROMs available for this device. However KangVIP Custom Stock Based ROM is available for the Chinese Variants but I couldn't get the links because they want you to register first. Also, because Huawei hasn't published the chipset source code, so no CM or AOSP based ROM has been developed for this device.
Unlocking Bootloader, Rooting and Custom Recoveries​Custom Recoveries, Stock Recoveries and SU zips Download Links
Recoveries and SU Zips will work on the respective EMUI version regardless of device region.​For Kitkat 4.4.2 EMUI 3.0
SuperSU Binary 2.46 doesn't worked correctly on Kitkat. It is better to use Kingroot. However, you may try flashing it! ​
Cofface Custom Recovery (CWM Based / Unofficial Port) Download Link
Stock EMUI Recovery Download Link
Kingroot Super User Binary + Manager Download Link
For Lollipop 5.1.1 EMUI 3.1
TWRP 2.8.7.0 (Unofficial Port) Download Link
Stock EMUI Recovery Download Link
SuperSU Binary 2.46 + Superuser App Download Link
Unlocking Bootloader and Relocking Bootloader
Unlocking Bootloader will void your warranty. You have been warned!​Getting the Bootloader Unlock Code
First, visit this link. Accept the Unlocking Agreement and proceed.
In a new tab, visit this link and register for Huawei ID. Make sure you are registering using your mobile number.
After the registration is successful, return to the previous tab and log in using your newly generated Huawei ID.
Now provide the information:
Product Model: Go to Settings > About Phone. For ours it is, CHM-U01.
Product Serial Number: Refer to the original device box for serial number.
Product IMEI: Provide SIM1 IMEI.
Product ID: Dial *#*#1357946#*#* from your device and enter the Product ID displayed on the screen.
Finally enter the verification code and retrieve your Bootloader Unlock Code. Save it in a safe place.
Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Unlocking Bootloader
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open a command prompt and execute the following command (replace your_unlock code with yours):
Code:
fastboot oem unlock [I]your_unlock_code[/I]
fastboot reboot bootloader
Voila! You have successfully unlocked your device.
Relocking Bootloader
Relocking the bootloader will not un-void your warranty.​
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Factory reset your device or reflash the stock ROM. See Stock and Custom ROM > Upgrading from Kitkat to Lollipop section for flash methods.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open a command prompt and execute the following command (replace your_unlock code with yours):
Code:
fastboot oem relock [I]your_unlock_code[/I]
fastboot reboot bootloader
Voila! You have successfully locked your device.
Install Custom Recovery
After installing a custom recovery, you will not be able to take OTA updates nor you will be able to reflash the stock rom.​Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Installing Custom Recovery
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Download the custom recovery depending on your Android Version. See the first part of this section for download links.
For Lollipop only: Extract the downloaded RAR archive to get the recovery image.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open Command Prompt in the directory where you have extracted/downloaded the files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Now execute the following command one at a time (replace recovery name with the one you downloaded);
Code:
fastboot flash recovery [I]recovery_name.img[/I]
fastboot reboot
Restoring Stock Recovery
Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Flashing Stock Recovery
Ensure that you have successfully installed all necessary tools and drivers mentioned above
Download Stock Recovery depending upon your Android version. See first part of this section for download links.
For Lollipop only: Extract the downloaded RAR archive to get the recovery image.
Open Command Prompt in the directory where you have extracted/downloaded the file by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Now execute the following command one at a time (replace recovery name with the one you downloaded);
Code:
fastboot flash recovery [I]recovery_name.img[/I]
fastboot reboot
Installing SU Binary (Rooting your device)
Prior to rooting, ensure you have unlocked your bootloader and installed a custom recovery.
Download flashable root zip depending on your Android version. See first part of this section for download links.
Copy the zip to either internal memory or external SD card.
Power off your device and disconnect it from PC or charger.
Now hold Volume Up button and Power button. As soon as you see the Honor logo, release the power button. Your device will now boot into recovery.
For CWM: Use volume buttons to navigate up and down and power button to select. Go to Install Zip > Chose zip from external or internal storage (depends where you copied the flashable zip). Locate the zip file and hit flash. After successful flashing, wipe cache and dalvik and reboot your device. For TWRP: It's all touch based, hence it's easy to navigate. Touch 'Install Zip', locate the zip file, flash it and finally wipe cache and dalvik.
Congratulations you have successfully rooted your device.
ROM Addons and Miscellaneous Guides​Xposed Framework on EMUI 3.0 and EMUI 3.1
On Kitkat EMUI 3.0, Xposed works only when Use System Hooks is disabled in Xposed Settings. This means that modules such as Gravity Box, Minminguard won't work! However, modules that don't modify the UI work without problems.
On Lollipop EMUI 3.1, Xposed works flawlessly and great! See my thread here for instructions and details: http://forum.xda-developers.com/android/general/guide-workaround-running-xposed-t3338765
Viper4Android Sound Mod
Unfortunately, Viper4Android is a no go on EMUI 3.0 and EMUI 3.1. There is partial support i.e. the mod will only work when it is running in background and will not work on stock EMUI apps such as Music. Also be sure that after installing, DTS Sound Engine will be disabled (or won't work in most cases)!
L Speed Mod for Android Lollipop EMUI 3.1
This mod works flawlessly and I'm loving it! Visit the XDA thread for all information.
Changing Region
This is some really risky stuff. If anything goes wrong you'll end up with a bricked device. I have personally tested this and have successfully changed my region from Pakistan to Malaysia. Nothing will go wrong if you carefully follow the instructions!​Prerequisites
Your device must be rooted.
ES File Explorer installed (no other Root Explorer should be used).
Backup of your stock ROM.
OEM Info File Download Link
Instructions
Dial *#*#2846579#*#* from your device to pop up Engineering Menu. Go to Network Information > Country / Vendor Info. I have listed some of the vendors below:
1. hw/spcseas – Malaysia
2. unicomelectric/cn – China
3. hw/meafnaf – Pakistan
4. mts/by – Belarus
Open ES File Explorer, switch to Root Mode and navigate to /data/. Open custom.bin using ES Note Editor. Clear the Vendor Information text in it and enter the text corresponding to the region you want to switch to. In my case as I switched from Pakistan to Malaysia, I cleared hw/meafnaf and inserted hw/spcseas. Save the file and make sure it's permissions are set to rw-rw-rw
Extract the OEM File Info and copy the oeminfo file of the country you are switching to. Using ES File Explorer, navigate to /dev/block/platform/hi_mci.0/by-name/ and paste it there. Replace the file currently present. Don't delete it! Now set it's permissions to rwx-rwx-rwx.
Finally reboot your device and enter Engineering Mode to verify Country/Vendor.
Download the latest ROM of the Vendor you switched to and flash it using Forced Flash Method. See Stock and Custom ROM > Upgrading from Kitkat to Lollipop for details.
Extracting Update.APP
This is a simple and straightforward guide! Follow and follow...​
We'll start by downloading Huawei Update Extractor. Visit the XDA thread and scroll down for links.
Extract the downloaded file in a safe folder and launch HuaweiUpdateExtracter.exe
Make sure Profile is set to Unknown (worstenbrood).
Switch to Extract tab and locate the Update.APP. (Well you must have downloaded the Stock ROM. No! No problem! See Stock and Custom ROM > Download Links section for links).
Hold down Ctrl Button and select the partitions (such as System, Recovery, Boot, etc.) you wish to extract. Then right click on any one of the selections and click Extract Selected.
Browse for a location where you wish to extract the partitions (or images).
Tada! It's done!
Credits
Inshaal Mirza for providing Stock Recoveries and Root Zips.
CarbonTesla.com for providing ROMs versions list and Changing Region guide.
XDA for everything it has taught me.
If you encounter any issues in this guide or you believe I have made an error, please feel free to PM me or comment to notify. Thanks everyone!
Changelog:
25/01/2016 Streamlined Content
02/02/2016 Added another Downgrade Method

Great information. Thx

[email protected] said:
Great information. Thx
Click to expand...
Click to collapse
No problem! Just thought of giving back something to the community....:angel:

hi,
it is not possible to register witch Phone nummer i live in germany and i canty type +49
can me someone help? unlock Bootloader?

rysalf said:
hi,
it is not possible to register witch Phone nummer i live in germany and i canty type +49
can me someone help? unlock Bootloader?
Click to expand...
Click to collapse
Dont worry. PM me your mobile information (see thread for detail) and i'll provide you with the unlock code.

rysalf said:
hi,
it is not possible to register witch Phone nummer i live in germany and i canty type +49
can me someone help? unlock Bootloader?
Click to expand...
Click to collapse
You can register with email, and give your phone infos later.

morpheus133 said:
You can register with email, and give your phone infos later.
Click to expand...
Click to collapse
The problem is, Germany is not on the country list during sign up.. So you can't create a phone account using a Germany phone. Huawei has made it an obligation to use a phone account for unlocking.

mfbcool said:
The problem is, Germany is not on the country list during sign up.. So you can't create a phone account using a Germany phone. Huawei has made it an obligation to use a phone account for unlocking.
Click to expand...
Click to collapse
It is not a problem.
Use email to register!
I am from Hungary. Hungary is not on the list to but I can use the site.

i downloaded b360 lollipop. and theres no middle package for downgrade. help me. i want to downgrade my 4c.

ijameslargo said:
i downloaded b360 lollipop. and theres no middle package for downgrade. help me. i want to downgrade my 4c.
Click to expand...
Click to collapse
Try changing your region to Malaysia and then flash any Kitkat image you like!

mfbcool said:
Try changing your region to Malaysia and then flash any Kitkat image you like!
Click to expand...
Click to collapse
malaysia already

ijameslargo said:
malaysia already
Click to expand...
Click to collapse
Alright... Then try this method (it does the same thing as region change does). You must be ROOTED.
1. Open build.prop located in /system/.
2. Change ro.product.model value to Balong.
3. Restart your device.
4. Now flash away any Kitkat ROM of any region.

mfbcool said:
Alright... Then try this method (it does the same thing as region change does). You must be ROOTED.
1. Open build.prop located in /system/.
2. Change ro.product.model value to Balong.
3. Restart your device.
4. Now flash away any Kitkat ROM of any region.
Click to expand...
Click to collapse
sir my phone is not yet rooted. is there any other way? like flashing middle package?

ijameslargo said:
sir my phone is not yet rooted. is there any other way? like flashing middle package?
Click to expand...
Click to collapse
No manufacturer wants the end user to downgrade to a lower version. You have to be rooted and bootloader unlocked in the first place to downgrade. The middle package is in B330 Lollipop ROM. You may try flashing it but I doubt it will work on B360.

mfbcool said:
No manufacturer wants the end user to downgrade to a lower version. You have to be rooted and bootloader unlocked in the first place to downgrade. The middle package is in B330 Lollipop ROM. You may try flashing it but I doubt it will work on B360.
Click to expand...
Click to collapse
is it ok to flash the middle package in b330 even my phone is not rooted?

ijameslargo said:
is it ok to flash the middle package in b330 even my phone is not rooted?
Click to expand...
Click to collapse
No, you don't need to be rooted. Also this is completely safe. Huawei Recovery won't flash the file it is not compatible so feel completely safe to try it!
I was on B330 Lollipop ROM and I did downgraded mine to Kitkat just for Xposed!

im using b360 lollipop. now i will try to flash the middle package of b330 to downgrade mine to kitkat. im hoping it will work.

@mfbcool If you're challenging my info , Our Phone Support 4G LTE Network!! one thing and 2nd thing, we have Sources for chipset of Our devices but thats are for Arm only not Arm64, so they are less used for us,,, we only need a developer,,, and third and last one, we can never change region as mentioned above and in carbontesla.com, i already read it, but thats not the way!! we needed vendor files which are available only for Pakistani one Rom (B120) and Indian (B390) only,,, not present for chinese or any other region,,, so we cant change region!!
@inshaalmirza
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
@ijameslargo you dont need to be rooted and unlocked bootloader for downgrading, you can downgrade to any version from any Rom,,, if you have done in any way then its ok, if not then tell me, i will guide you!!
@inshaalmirza

inshaalmirza said:
@mfbcool If you're challenging my info , Our Phone Support 4G LTE Network!! one thing and 2nd thing, we have Sources for chipset of Our devices but thats are for Arm only not Arm64, so they are less used for us,,, we only need a developer,,, and third and last one, we can never change region as mentioned above and in carbontesla.com, i already read it, but thats not the way!! we needed vendor files which are available only for Pakistani one Rom (B120) and Indian (B390) only,,, not present for chinese or any other region,,, so we cant change region!!
My turn!
1. So my desktop computer supports WiFi cards but it hasn't one installed so it neither can't search Hotspot networks nor can't create one. Same case here! The Kirin 620 SoC has SUPPORT for 4G networks but the radio module required to make it available is not installed ON THE HARDWARE on our 4C (it's installed on P8 lite though) or IS DISABLED ON THE HARDWARE SIDE.
2. There are more things required to build Custom ROM other than kernel sources (which you are of course mentioning about). You need open source drivers for CPU Management, GPU, WiFi, Bluetooth, Dual SIM card, Graphics Stack, Radio Bands support, NFC, etc. Unfortunately, those aren't included or open-sourced in the source. That's why the only custom ROM ever made for Kirin SoC, the Cyannogen Mod 11 for Honor 6 has no support for Bluetooth, NFC, USSD Execution, etc. The developer for that ROM made seriously tons of patches and spent countless weeks to make it happen. That's also the reason why there is no CM (or any AOSP) ROM for even high end Huawei devices such as Mate 7, etc. These devices however do have KangVIP ROM which is Stock Based Chinese mockoff.
3. I did changed my region from Pakistan to Malaysia successfully. If that didn't worked for you, I'll upload flashable zips probably in few days that will automatically change the region for you
I wish you ever had a Motorola phone which will hard brick on downgrade (yup a dead phone RIP). Unfortunately no manufacturer wants the end user to downgrade because of security patches, exploits, etc. You can always try flashing system.img of a lower version together with boot and recovery to see whether your phone has downgraded.
That 'balong' method I posted is actually an exploit or more preferably a cheat. The phone loses it's identity, model and version and thus any version either higher or lower can be flashed. However it does require root.
Click to expand...
Click to collapse

Great great!! You should know one thing too.... You didnot mention CM12.1 of 4X ?? You know, thats made from our Kernel Sources!! Nd dev made all drivers etc for it.... So just sources enough for it...right...
And i once also changed region to malysia/india, but it got balong build,,, then i flashed vendor file of specified rom,,, it changes to its real build!! Then my region was really changed!! And about 4G,,, our hardware support 4G but software didnot!! See in indian Rom, 3 options 2G,3G,4G available in preferred mode!!
@inshaalmirza

Oreo 8.1 Update T585XXU4CRJ8 problems

Hello all
I installed the latest T585XXU4CRJ8 Oreo 8.1 update over Nougat 7 on the SM-T585. (BTU / UK)
Everything went well using Odin and the Oreo stock rom from the Updato website.
Cleared the cache and factory reset from recovery mode as normal practice. Booted up ok.
The problem is the device doesn't recognise the network sim card anymore (worked perfectly on Marshmallow & Nougat).
I've tried factory reset a few times, no difference.
Removed and reinserted the sim, even tried another sim.
Having checked 'about tablet > software details' , carrier is unknown and the IMEI has dissapeared !
I've tried to reinstall Nougat 7 and Marshmallow 6 back on the SM-T585 and Odin fails every time.
Tried 2 computers and 3 different usb cables.
Even trying to reinstall Oreo 8.1 again Odin fails!
Theres no frp lock activated, and the oem unlock tab is checked, usb debugging enabled too.
I've read somewhere Samsung have done something to Oreos BootLoader file to stop people downgrading back to earlier software.
I know its early days, but if anyone can offer any solutions, it'd be appreciated.:good:
How to change the BL file version, so i can reinstall earlier stock roms back?
The Oreo update seems more hassle than its worth and I didnt expect the sim card to be unrecognised once updated, let alone being faced with the puzzle of how to downgrade the software.
Thanks for reading. :good:

I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading

tsam19 said:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
Click to expand...
Click to collapse
I had the same problem, went from Lineage 14.1 to Oreo stock rom (the flashable one you can find on this site, i flashed also the Bootloader/modem file in the thread). No imei, no baseband. Returned back to lineage and got back imei and baseband, but after my screen was going to sleep (after the regular 1 min) I had only black screen and vertical red lines. I flashed then Resurrection Remix 6.2, Lineage 15, Lineage 16, always the same problem. Then I used Odin and the original firmware of Nougat from SamMobile, at the first attempt i flashed only the AP file. I turned to have the same problem, but this time the lines were white. I flashed all the 4 files again with Odin, problem solved and back to Lineage 14.1 (the only custom rom were everything works)

Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.

tsam19 said:
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
Click to expand...
Click to collapse
just flash the nougat firmware from SamMobile. You have to flash all the 4 files in the zip you are going to download. AP, CSC, etc. Once you have your tablet completely stock you can install again TWRP and flash whatever CUSTOM rom you want.
I easily rooted the phone with odin flashing only the TWRP in AP box (twrp taken from this post https://forum.xda-developers.com/showpost.php?p=78145080&postcount=160) avoid the auto-reboot. You have to put the tab in DL mode, connect it to pc, start odin flash the twrp in AP file e unselect Auto-reboot. As soon as the process is done you have to log in recovery mode at the first boot with home + power + vol up and flash dm-verity. I rooted with Magisk without any problem just flashing the v17.3. Now i' m back to nougat (from Oreo) and i can install whatever custom rom i want. But honestly the only one fully working is Lineage 14.1. Resurrection remix 6.2 has problem with camera and gps don't lock. Same for Oreo version. Tried Pie, same problem.

Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications

tsam19 said:
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
Click to expand...
Click to collapse
Honestly i think this run for Oreo it's not really worth. I said you what I did and now i have no problems. I'm not in hurry to use Oreo (as stock rom). I think Lineage 14.1 is the most stable and fastest rom i tried till now, and most of all everything is working. I think i'll give a try via Odin to the official stock rom when it will be available for download (i live in Germany) but sadly I don't use most of the Samsung bloatware installed by default.

WRP Oreo 8.1 on Galaxy Tab 10.1 (T585)
Then I've tried
twrp_3.2.3-1_sm-t585_29918 which gives only stripes when booting into recovery
Do I have to flash the stock boot/recovery before flashing this one,
or this is broken, as well.
Many thanks for a hint,
Helmut

Hope this helps.
So, as I was trying to search for my Galaxy Tab A6 (SM-T585) for Deodexed Stock ROM, I stumbled upon this thread https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215 just follow the instructions to fully flash Oreo. By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all(Thread here, read the comment:https: //forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) . The TWRP, I think we should leave it be, don't flash an update for the TWRP.
Thanks. Hope this helps.

MiaMOTo SU # said:
By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all
Click to expand...
Click to collapse
Neither does a custom recovery, so not sure what your point is?

I mean if your having problems using MAGISK use the beta version

(Method) For everyone who wants to Downgrade Galaxy S8 to Oreo/Nougat

Hey guys!
I recently read many Questions About downgrading the Galaxy S8 to 7.0/8.0 after we got the 5x Bootloader.
Well many of you say NO but What many of you forgot is that there is a way to Downgrade your phone.
I already had that Problem with my S6 back in 2016, where I wanted to Downgrade it to 5.1. All you Need for a Downgrade is a Combination File.
Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices.
Combination ROM Advantages:
Its help you to repair imie number in some models like S8/S8 plus S7/S7 Edge S6/S6 Edge…
Its very useful in bypass samsung account in too many models.
Its very useful in bypass Google account in too many models.
Its very useful for downgrade in some models.
Its help you to enable usb debugging.
its help to remove any security FRP / Reactivation Lock from Samsung like 2016-2019
You can find Combination Files for Galaxy S8 devices here:
G950U with latest Bootloader: http://www.mediafire.com/file/j8xi2n73zhh37q1/COMBINATION_FA70_G950USQU5ARG4.zip
G950F (currently only for 4x Bootloader): http://www.mediafire.com/file/c37zq...QB19841686_REV00_user_mid_noship.tar.rar/file
Here is a Video of Downgrading a Galaxy S6 Edge with Combination File : https://www.youtube.com/watch?v=dOKJcHU1pXM Should work with S8 too

Hello, nice tutorial!
Want to ask:
"Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices. "
So only Samsung releases these files to public? or are leaked?
I`m asking to check if I should wait or not, I had V4 bootloader but recently by accident with the latest update I got V5

rilley said:
Hello, nice tutorial!
Want to ask:
"Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices. "
So only Samsung releases these files to public? or are leaked?
I`m asking to check if I should wait or not, I had V4 bootloader but recently by accident with the latest update I got V5
Click to expand...
Click to collapse
I would recommend you to wait till the latest Combination File gets public for the G950F/G955F. They do work very good and are also stable. Usually I think Samsung does not public These files online but they get leaked very often. I used the Combination File to Downgrade my S6 from 7.0 with Bootloader 6 to 5.1.1 with Bootloader 2.
Im sorry but I can only explain the function of a Combination Rom along with the Galaxy S6..
Once Cthe latest Combination File is available, do this:
1. Download your Nougat/Oreo Firmware you want to install
2. Download Combination File with the latest Bootloader Version
3. Downlad 7zip, since you Need to edit the firmware you want to install
3b) Extract the firmware you want to install to a new Folder
3c) Delete all files except for boot.img, cache.img, recovery.img and system.img
3d) Open 7zip from your Start Menu and locate the firmware Folder
3e) Mark the remaining files and press the green "Add" Button at the upper left corner and create a tar (Odin Flashable) file
4)Download Odin
5) First uncheck Auto-Reboot
6) Now first Flash the Combination File
7) Afterwards go directly again in Download Mode and Flash the tar- firmware File
8) Reboot your phone and do a wipe
9) Congrats! You now have Stock 7.0/8.0 Back!
Notes: Fingerprintscanner wont work, because it is a part of cm.bin, OTA Updates wont work as well, Dont worry if you see a green text next to the Phone logo while starting it. Thats normal and not an error.
Backup your files before you do that!

I hope it helped you

halloo13 said:
I hope it helped you
Click to expand...
Click to collapse
Yes, many thanks for response!
I guess I will wait until I get the combination of files, but until then I want to switch CSC, found a solution to use THAI sim card, but not sure, if everything goes ok, I guess the new OTA update will be the latest from THAI, there are no changes to get bricked by this method right? ( I will be able to get back to the ROM stock that I have now? )

halloo13 said:
I would recommend you to wait till the latest Combination File gets public for the G950F/G955F. They do work very good and are also stable. Usually I think Samsung does not public These files online but they get leaked very often. I used the Combination File to Downgrade my S6 from 7.0 with Bootloader 6 to 5.1.1 with Bootloader 2.
Im sorry but I can only explain the function of a Combination Rom along with the Galaxy S6..
Once Cthe latest Combination File is available, do this:
1. Download your Nougat/Oreo Firmware you want to install
2. Download Combination File with the latest Bootloader Version
3. Downlad 7zip, since you Need to edit the firmware you want to install
3b) Extract the firmware you want to install to a new Folder
3c) Delete all files except for boot.img, cache.img, recovery.img and system.img
3d) Open 7zip from your Start Menu and locate the firmware Folder
3e) Mark the remaining files and press the green "Add" Button at the upper left corner and create a tar (Odin Flashable) file
4)Download Odin
5) First uncheck Auto-Reboot
6) Now first Flash the Combination File
7) Afterwards go directly again in Download Mode and Flash the tar- firmware File
8) Reboot your phone and do a wipe
9) Congrats! You now have Stock 7.0/8.0 Back!
Notes: Fingerprintscanner wont work, because it is a part of cm.bin, OTA Updates wont work as well, Dont worry if you see a green text next to the Phone logo while starting it. Thats normal and not an error.
Backup your files before you do that!
Click to expand...
Click to collapse
Hi, ok but it means that i cannot use fingerprint or ota update anymore or after dowgrade could i install full stock firmware with odin and recovery functionalities?

Will this trip Knox?

Any idea if I can downgrade from pie on a S8+ on bootloader 6?

I've tried this method on my S7 edge but I've stucked on step - deleting files.
After extracting the firmware I get 5 files- Ap, Bl ect.
When i extract the AP file (previously deleting "md5" from the name, and becoming rar file) there are only 3 new files (nothing for delete if i remembering correctly)
Files i need to delete are on other files from extracted firmware.
At the end I finished on unsuccessful flash.
I want to go back to nougat on my S8+ (955f), but i dont want to take risks, so I did flashing on old device with corect firmware.
I'm really mad at Samsung. Battery life become horrible at pie. Thats why I want to go back to nougat or at least oreo.
I will post some videos after day or two how is possible to downgrade android version on some Samsung devices with higher bootloader version. These methods didn't worked for me but may be they will encourage some of you to make possible the downgrade.

As I promised:
1. Interesting way to downgrade Samsung Device (J series) when touchscreen does not working:
https://www.youtube.com/watch?v=SmfgxoUhflA&feature=emb_title
2. Second method:
https://www.youtube.com/watch?v=ZKg1DC4ul_g&feature=emb_title
As I remember oreo and nougat have pro mode on video recording and faster charging speed. I hope someone to explain is it possible to downgrade S8 and whats are the steps with this method.

so if i want to downgrade to firmware with bootloader v4 but my phone has now v6, will i download combination file with bootloader 6 or 4? I didn't get that part, sorry. i have s8+
edit: ok, 4 didn't work, so i guess need to get 6

Does anyone know the password for the linked Combination file?

Thanks for this thread.
I want to downgrade from Oreo to nougat too, I'm on "U1" security patch, but I don't understand the order of bootloader version... Can you try to explained how to ?
I found this if it can help : https://combinationfirmware.com/combination-samsung-galaxy-s8/

Scylla.bx said:
Thanks for this thread.
I want to downgrade from Oreo to nougat too, I'm on "U1" security patch, but I don't understand the order of bootloader version... Can you try to explained how to ?
I found this if it can help : https://combinationfirmware.com/combination-samsung-galaxy-s8/
Click to expand...
Click to collapse
Since you are on bootloader version 1, you don't need the combination files. If you were past version 2 they would be needed.
Once you update to a new bootloader you can't go back to software on the older bootloader without the combination files.

Kaloob said:
Since you are on bootloader version 1, you don't need the combination files. If you were past version 2 they would be needed.
Once you update to a new bootloader you can't go back to software on the older bootloader without the combination files.
Click to expand...
Click to collapse
Thank you for your reply.
Ok so if im on the right bootloader for Nougat, why can i install this rom ?
[S8/S8+][Nougat][01-Jan-2020][v30] LightROM
In fact i can install it, all seem to be fine, no error in twrp, but at reboot it freeze at bootloader
Thanks for your help bro

Scylla.bx said:
Thank you for your reply.
Ok so if im on the right bootloader for Nougat, why can i install this rom ?
[S8/S8+][Nougat][01-Jan-2020][v30] LightROM
In fact i can install it, all seem to be fine, no error in twrp, but at reboot it freeze at bootloader
Thanks for your help bro
Click to expand...
Click to collapse
If you have an Exynos version, maybe ask around on that thread.
If you have a Snapdragon variant, you can't flash that ROM.

Kaloob said:
If you have an Exynos version, maybe ask around on that thread.
If you have a Snapdragon variant, you can't flash that ROM.
Click to expand...
Click to collapse
I have exynos. Anyway thank for your help, i try to post on that thread and hope someone could figure it out.
Peace

Did anyone find the password for the file?

necklickhia said:
Does anyone know the password for the linked Combination file?
Click to expand...
Click to collapse
Password I had to find it elsewhere: "www.samkey.org/forum" without the quotes

Rooting J701F

I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.

xperia ray said:
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
Click to expand...
Click to collapse
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.

Anlle said:
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Click to expand...
Click to collapse
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.

xperia ray said:
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
Click to expand...
Click to collapse
Thank you, I will try until my phone is rooted. best of luck of me hehehe.

Anlle said:
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Click to expand...
Click to collapse
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/gal...j7nxt-t3974337

xperia ray said:
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
Click to expand...
Click to collapse
Thanks
According to the photos shown, you need to use MiracleBox, as it is prenormal
Try using this tutorial

TWRP, Rooting and Custom Rom HELP SM-T510 Tablet Tab A 10.1

Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)

You don’t unzip the .tar files. Keep them as is.

secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5

My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.

fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.

is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse

fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!

framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?

framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.

lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.

framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.

lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY

framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.

lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!

framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.