Hello, I have the 128GB version of the Galaxy Tab S5e, and i followed the guide on here to unlock the bootloader and root with magisk. I have the latest magisk, and patched my AP file with what said it was the latest version from frija. But now when i open any kind of file explorer (ive tried 3 different ones, including the native Files app that comes on the tablet) it says storge space is XX.XXGB / 32.00GB. It also says 32GB if i plug it into my pc and check from windows explorer. Any idea why? I also made sure i used the correct CSC when picking my AP file to patch btw
It's says in the guide NOT TO flash the patched AP file alone or odin will resize the data partition. Go back to the guide and flash full firmware again.
Related
If you have checked out, downloaded and flashed RaymanFX's latest CM13 Unofficial Nightly ROM for Note 4 N910C/H/U users here: http://forum.xda-developers.com/not...-cyanogenmod-13-semi-official-builds-t3259878 chances are you failed miserably at getting back to Samsung's Stock Firmware as you have encountered a series of unending bootloops. The bootloops exist because your downgrading from Android 6.0.1 Marshmallow (CM13 ROM) back to Android 5.1.1 Lollipop (Your previous Original Samsung Stock Firmware), however if you've received the Android Marshmallow Update for your Note 4 model number and region as an OTA Update from your device or Manually by downloading it from sammobile.com or any other external link and have flashed it before flashing CM13 no need to worry you won't need a backup of your Samsung firmware (Unless you want one) as you can perform a clean install of your Samsung Marshmallow Firmware via Odin v3.10.7 Here is where the fix lies; i have compiled a series of posts from 2 very helpful XDA Members from the community because from my experience i have managed to rescue my device using their methods which i will mention below.
Firstly if you have made an Efs partition backup from your previous Original Samsung Stock Firmware in the form of a .tar or .img file e.g "efs_backup_2015-06-01_02-37-16.tar" or "efs.img" respectively then you are good to go if not leave this thread.
Also you will need to download a Note 4 N910C/H/U Pit file corresponding to the region of your Samsung Firmware so here is a link to a selection of pit files. You will need to create an account at sammobile or simply sign if you have a current account to see the download links here: http://www.sammobile.com/forum/showthread.php?t=30022
Follow FR34K-B1B0's helpful post on getting back to stock here: http://forum.xda-developers.com/showpost.php?p=65414257&postcount=39 Skip the 1st Step since we are restoring our IMEI using our backed up Efs file and we will be using a different method to restore this backup.AND AFTER ODIN IS DONE FLASHING THE SAMSUNG FIRMWARE there is a chance that your phone will boot to the Stock Recovery and you will notice a message down there saying: "dm verification failed" so simply wipe data/factory reset and wipe cache and then reboot. Afterwards your phone should boot properly. Now close he's post and carry on down here.
After your phone boots up and you have set it you will notice that your mobile is not connected to your specific mobile carrier and you will see the Emergency calls only text on your lockscreen hence the Not registered on network error. Go to Settings--->About device--->Status and scroll down and you will search and find that your IMEI is literally not the one your phone has and that your Serial number is of an Android Serial number given to you from flashing CM13( Since it's a pure stock android software). If you want you can download the Phone INFO App from the Playstore to verify your device's information and if you do so you will notice that your Samsung Serial number is a bunch of 0's like this: 0000000000 or it's not even present hence wiped.
HERE IS THE MOST IMPORTANT PART FOR RECLAIMING YOUR MOBILE NETWORK CONNECTION, your IMEI is wiped and so you must restore it using your Efs backup file which i mentioned previously above. To do so you will need to root your device and the guaranteed way of rooting your device is using Chainfire's CF-Auto-Root Method.
Here are the links to the Odin flashable MD5 files based on your Note 4's Model Number that you must download ---> For SM-N910C: https://download.chainfire.eu/559/CF-Root/CF-Auto-Root/CF-Auto-Root-trelte-treltexx-smn910c.zip For SM-N910H: https://download.chainfire.eu/577/CF-Root/CF-Auto-Root/CF-Auto-Root-tre3g-tre3gxx-smn910h.zip For SM-N910U: https://download.chainfire.eu/557/CF-Root/CF-Auto-Root/CF-Auto-Root-trhplte-trhpltexx-smn910u.zip After downloading the file on to your computer simply load the file through Odin, power off your phone and boot it to download mode then connect your device to your computer and flash the md5 file. After it's done flashing your device will boot to a custom screen with a red android logo then it will boot.
Right now your device is rooted and you will see the Supersu app in your app drawer. Next if your Efs backup is stored on your computer and is of the format .tar simply open it with 7zip or Winrar you will find the .img present then extract it your desktop. In order to restore your IMEI with this .img file we will need an update package that we can flash from a custom recovery(CWM or TWRP). Here is the link to civato's awesome flashable update package: http://forum.xda-developers.com/showthread.php?t=2331853 and you'll find the package down in the attachment. After downloading the attached file, rename your Efs backup file from "efs.img" to "EFS.img" then extract the contents of the downloaded update package to a folder with the same name of the package, copy your EFS.img file to it and use 7zip or Winrar to add the files to an archive(.zip).
Last but not least copy the new repackaged flashable zip to your external or internal sd card. Run Odin and flash your desired Custom Recovery(CWM or TWRP). Boot to the custom recovery and flash the update package and finally reboot system. After booting your phone will have it's Efs partition restored; your IMEI and Samsung Serial number will be back and your mobile network will be back on again. :fingers-crossed:
Special thanks to FR34K-B1B0 for he's helpful post on getting back to stock firmware
And Many Many Thanks to civato for he's really useful Efs restoring update package! :victory:
And last but not least thank you Chainfire for your great CF-Auto-Root Method that helped root our device(s).
Hello!
I'm trying to install a rom which requires me to update/flash my Bootloader & Modem to the MM ones. Now I'm running into a problem where Odin will freeze at certain parts and after a while it fails writing the file .
I've tried odin v3.10 & v3.12, I've tried different USB- cables & ports and I've enabled USB Debugging and OEM Unlock in my developer options. Any other possible suggestions :fingers-crossed:?
Thanks in advance.
I managed a glimpse of the zip file you downloaded from the ROM thread.
1. BL_G935FXXU1BPJG.tar.md5
2. CP_G935FXXU1BPJG.tar.md5
You're using Odin3 v3.12, and it's clearly stated md5 format is an old model of updating home binary. New versions will only accept .tar files. This would explain the write errors you're getting.
Updating of bootloader and modem require .tar files to be flashed using the BL and CP slots respectively. I suspect you would only need to rename the files to .tar for them to work, but pls clarify with the ROM developer.
Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Flash back to stock, flash twrp, flash supersu from twrp.
Thanks for reply.
I did this earlier what you said and everything was OK.
I had TWRP and Root using SU.
The problem isnt rooting itself.
The point is i wanted to tested rooting with CF-AutoRoot method.
And I'm wondering what am I doing wrong.
I did everyting correctly (exact same device model and build version) and ODIN gives me FAIL like i said above.
If Odin is failing, try a different version of Odin, a different USB cable, and different USB port.
I got the same problem with a Sprint Note Edge that I tried to root the same way. I'm currently downloading the stock firmware from sammobile.com to flash a stock ROM.
Thomass30 said:
Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Click to expand...
Click to collapse
Hello
You do not need to generate a CF-AutoRoute, just google and download the original CF-AutoRoute.zip which roots ALL versions of the device, the baseband does not matter.
Ensure debugging is enabled
Place device into recovery (download)
Add device to Odin
Unzip the file, add the .md5 file to Odin and flash, job done.
Hello Everyone,
I'm a long time iphone user since 2013, and I just transferred to Samsung.
Recently I bought a new unlocked S10+ from samsung website. As a AT&T user and I need to use WiFi calling since my reception at work and home is bad. I did some search on the forum and flashed my software to 975U AT&T version, by using the files in SAT-1-9.0 folder in this link(https://androidfilehost.com/?w=files&flid=290649).
After I unzipped the G975U_SAT_1.zip files I got the BL, AP, CP ,CSC files, and I also downloaded the USERDATA file in that folder as well(USERDATA_ATT_G975USQU1ASAT_CL15296297_QB21819666_REV00_user_low_ship_MULTI_CERT.zip).
I try to search online find if I should upload the USERDATA into Odin but I'm unable to find any, but I did it anyway and upload BL, AP, CP, CSC, HOMEDATA all together.
The flash was successful and I was able to get ATT logo during booting and all the apps in the phone. Then I found out the SAT version of firmware is kinda old, there are newer updates available already.
Back in to that website folder, there are SBA and SD3 available as well, in SBA folder there are G975U_SBA_1.zip, 3.5 GB just like the previous SAT one, so I assume this is the main file. They also have USERDATA available as well and I saw the ATT one is in there too.
The SD3 folder doesn't have any "Main file", it only has USERDATA.
I tried to clicked check updates in the phone but it showing me my current software is up to date but apparently it's not(SAT version is back in Feb and there are SBA and SD3 already)?
Then I downloaded a new firmware (SD3) on firmware.science web last night and flashed it using the SD card, it wiped my data but the flash was good and the phone is now showing SD3 version.
My question is:
1. Will I get OTA updates in the future?
2. What does USERDATA do? I'm guess it let your software has specific carrier features, that's why the file name contains carrier brand name, the SBA and SD3 are all carrier updates, so if I want to flash to a newer version, I need to upload newer USERDATA into Odin, is that correct?
3. I flashed the SD3 using the MicroSD card. If I want to flash it using Odin, what should I do?
4. Is the SD3 file on the firmware.science website the same to USERDATA file in SD3 folder on androidfilehost.com?
5. How can I update without losing the data? Yesterday during the SD card flash I have to factory reset before update otherwise it will stuck at "Starting android" forever.
Thank you very much.
Hello,
im trying to flash an AP file, modified via magisk app, to my Galaxy S10+ (Exynos, SM-G975F/DS, FW: G975FXXSEFUL1) via ODIN. I´ve installed the magisk app on this clean Samsung device to modify the AP file.
The bootloader is unlocked. But when ODIN is flashing USERDATA, the Downloadmode says: "official signed binarys only" and stops the flashing. The phone can be restored by flashing the original fw.
I´ve also tried to copy the AP file from an to the phone via adb. Also I tried use another official Samsung firmware (Android 12, G975FXXUEGULB) with the same result.
Can somebody help?
Thanks
Mirko