Database Users

Samsung Galaxy S5. Cant flash stock rom and Update it with kies.

The Samsung Galaxy S5 (SM-G900F) is stuck at the boot screen and keeps restarting. I cant go into recovery mode. I can only go into the download mode. I tried to flash it with odin and update it with kies. But none of it works.
At the download mode screen it says:
ODIN : flash read failure
Error: There is no pit binary
Odin screen:
<ID:0/013> Odin engine v(ID:3.1101)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013>
<ID:0/013> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help will be appreciated

Got your back.
Hey man just make sure you closed odin completely.
1. Start Kies
2.Click Tools-> Firmware upgrade and initilazation
3.Type in model of your phone for example sm-g900i which is my Australian S5 then it will ask you for your SN which is a 16 digit code serial number located on the back of your phone when you remove the battery.
Then just follow steps until it asks YOUR phone to be connected... DONT connect it yet...first put it in download mode; phone turned off; press home but, power but, and vol down bot at same time then press vol up key to enter download mode.
Connect phone; then just wait 1 hour and voila you got your phome with latest stock firmware.
Please reply to us if this worked for you as this can help new users to determine what to do.
Cheers
Sorry but English is not my first language, hope i made myself clear.
If there is anything else i can do to assist please let me know.:laugh:

Which Kies works with the S5? Because neither seem to be working
I'm having pretty much the same problem, had a bad flash and can't boot into recovery or get it detected in Kies
And I can't flash stock Marshmallow or Lollipop till I finish downloading them
Going through firmware upgrade and installation option and putting in the model just causes Kies to freeze using either version

WalkableBuffalo said:
Which Kies works with the S5? Because neither seem to be working
I'm having pretty much the same problem, had a bad flash and can't boot into recovery or get it detected in Kies
And I can't flash stock Marshmallow or Lollipop till I finish downloading them
Going through firmware upgrade and installation option and putting in the model just causes Kies to freeze using either version
Click to expand...
Click to collapse
Kies will automaticlly download the correct atock fw.....just use Kies lite versiom which is the one i used a couple of days ago and had exactly the same problem as you i actually had a corrupter pit file so there was no partition being found...again install and use lite kies for samsung then just dlow the steps ut should automatically download the firmware and install it into samsung at the same time you shpuld not remove the cable whatsoever during download and installation and actually make sure yu have the drivers for samsung installed and that the usb cable you are using is original....hope it works if you need a detailed guide with instalation steps let me know or heck i cpuld even help out with a video just let me know.
Hope you get it sorted and if you do please let us all know so in the furute people can see the answer.
Cheers.

It's alright I fixed it now, still couldn't get Kies to work
I flashed the latest version of Lollipop (no carrier) to the phone, which initially sent it into a bootloop. But that enabled recovery again so I did a data and cache wipe, flashed the same ROM from ODIN again and it worked

G950f - After TWRP stuck on logo, no recovery, odin says 'no PIT patrition'.. help!

Hi all, i've also posted this on sammobile but have had little response. I installed TWRP on my S8 (G950f) and when it rebooted got stuck on the logo screen. I cannot enter recovery mode, only download mode. I've tried flashing with the latest Odin and it fails at the start with error DeviceInfo. So i installed an older version of Odin and now receive the error 'Set PIT file'. I cannot find a PIT file online for the G950f and upon reading it seems this is taken from the CSC file when 'repartition' is selected. I've done this to no avail, still 'Set PIT File' is displayed. I'm certain that the firmware is correct as it's been used before with success. For some reason this TWRP seems to have effed things up. I'm close to putting the phone on Ebay and never touching samsung again
This is my Odin log:
ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005>
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
This is my Downloading Page text:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G950F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: Official
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = S2MM005 hw: 6 boot: 7 main:3C
WARRANTY VOID: 1 (0x030c)
RP SWREV: B:1 K:1 S:1
DID = 02b50c50a9c2
EVT 1.1
LOT_ID = NBV6P
CHIP_ID = 02b50c50a9c2
nASV_Table_Version: 8
nASV_Group_CPUCL0: 9
nASV_Group_CPUCL1: 8
nASV_Group_G30: 3
nASV_Group_MIF: 9
nASV_Group_INT: 9
nASV_Group_CAM_DISP: 9
nASV_Group_CP: 9
nASV_Group_PMIC: 0
nASV_Group_PMIC_CP: 0
PMIC_ID = 2(e4)
LPDDR4 manufacturer = Samsung
LPDDR4 process ver = D18
LPDDR4 size = 4gb

Have you tried https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857 ?

Hi, i've downloaded the file mentioned but it's a zip file and there's no BL file contained within it. I can't install via recovery as my phone wont enter recovery.

holidayaddict1 said:
Hi, i've downloaded the file mentioned but it's a zip file and there's no BL file contained within it. I can't install via recovery as my phone wont enter recovery.
Click to expand...
Click to collapse
Download the BL from https://www.sammobile.com/devices/ or using https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647

OK I've gotten somewhere (i hope). Followed your suggestion and after repeatedly pressing the Start button in ODIN have managed (somehow) to get into TWRP. However when i click 'install' the 'internal memory' displays as 0 with no option to select it.
Where do i go from here? Looks as if the internal storage is corrupt

The pit file is located in the CSC_OXM_G950FOXM1... file. Open it with winrar or 7zip and extract it.

Sjant said:
The pit file is located in the CSC_OXM_G950FOXM1... file. Open it with winrar or 7zip and extract it.
Click to expand...
Click to collapse
Do i need to exit TWRP then? I feel like i'd gotten somewhere

holidayaddict1 said:
Do i need to exit TWRP then? I feel like i'd gotten somewhere
Click to expand...
Click to collapse
Yes, you need to use Odin, or alternatively Smart Switch.

Sjant said:
Yes, you need to use Odin, or alternatively Smart Switch.
Click to expand...
Click to collapse
I've (kinda) managed to sort it!
Looked online and downloaded the files for AQF7 (just the BL and CP files) and whilst in download mode clicked start, held the 3 download buttons down again and hammered the start button in odin.. that made it boot into TWRP. However this just proved there was no partition there as the internal memory read zero.
So i downloaded the firmware for my device (XEU) and opened the CSC file with 7-zip and took out the .PIT file then in ODIN I JUST added the .PIT file and BL files. Pressed start and it worked but still only booted to the logo screen.
Next i added the AP file in ODIN and flashed that. This now went without a problem as the .PIT file had done its job repartitioning the phone.. The phone then restarted and booted to the welcome screen.
Some oddities which i don't understand are that in my Settings menu i now have an option 'T roaming' which shouldn't be there. and also a service provider option for 'KT twophone' whoever that is.
Confusing as i selected my countries (UK) XEU firmware.
My phone says 'international' on the boxes label so whether it's different firmware i'm not sure (couldn't find an international firmware on sam mobile).
*Edit..
I discovered that the additional options in the settings menu were due to me not flashing the CSC file so i reflashed all files at once (ensuring that odin had been reset first) and everythings back to normal.
Interestingly i wonder if i flashed a USA CSC file, would it give me access to the additional content available through the samsung USA store - they seem to have more AOD's, addons etc

Well Derr... because i discovered that android pay didn't work i felt like i had no option but to install TWRP... tried it, followed the instructions perfectly and it failed on DeviceInfo so now i'm back to the beginning.. stuck at the galaxy logo screen ( getting fed up of this phone now

holidayaddict1 said:
Well Derr... because i discovered that android pay didn't work i felt like i had no option but to install TWRP... tried it, followed the instructions perfectly and it failed on DeviceInfo so now i'm back to the beginning.. stuck at the galaxy logo screen ( getting fed up of this phone now
Click to expand...
Click to collapse
It got worse, however i've fixed it. I kept getting stuck in a boot loop despite having a successful flash. I just happened to check the files being flashed and realised that the BL file was the AQF7 bootloader and the other files were from my countries firmware. so i reflashed just the BL file for my country and the phone has now started
It looks as though flashing with TWRP won't work on my device for some reason as it seems to delete or corrupt the PIT. It's then a pain to get it all back working again.
Any other options to install TWRP?
Thanks

holidayaddict1 said:
I've (kinda) managed to sort it!
Looked online and downloaded the files for AQF7 (just the BL and CP files) and whilst in download mode clicked start, held the 3 download buttons down again and hammered the start button in odin.. that made it boot into TWRP. However this just proved there was no partition there as the internal memory read zero.
So i downloaded the firmware for my device (XEU) and opened the CSC file with 7-zip and took out the .PIT file then in ODIN I JUST added the .PIT file and BL files. Pressed start and it worked but still only booted to the logo screen.
Next i added the AP file in ODIN and flashed that. This now went without a problem as the .PIT file had done its job repartitioning the phone.. The phone then restarted and booted to the welcome screen.
Some oddities which i don't understand are that in my Settings menu i now have an option 'T roaming' which shouldn't be there. and also a service provider option for 'KT twophone' whoever that is.
Confusing as i selected my countries (UK) XEU firmware.
My phone says 'international' on the boxes label so whether it's different firmware i'm not sure (couldn't find an international firmware on sam mobile).
*Edit..
I discovered that the additional options in the settings menu were due to me not flashing the CSC file so i reflashed all files at once (ensuring that odin had been reset first) and everythings back to normal.
Interestingly i wonder if i flashed a USA CSC file, would it give me access to the additional content available through the samsung USA store - they seem to have more AOD's, addons etc
Click to expand...
Click to collapse
Hey mate. I am in the exact same boat as you, I am new to this and need some help. Where did you get your files, could you link them to me please? I don't know what I am meant to be doing and my back up didn't work properly so I can't even just go back to stock

Note 4 SM-N910K bootloader question. Please Help!

I just got a Note 4 (Korean variant). I plan to root it with CF auto-root and flash a ROM. I am on MM update and my build number is same as the one as in the CF auto-root so I have worries about that. However, I wanted to check my bootloader first and the dialer trick won't work so I installed adb on my laptop. When I enter the command "adb devices" my device would read and thus I proceeded with the command "adb reboot-bootloader". My phone then would ONLY Restart and when typing the command "adb fastboot-devices" nothing would appear. What am I doing wrong? Can someone please help me because it would like to know if my bootloader is locked before proceeding with rooting since my main reason of rooting is to flash a custom ROM. :crying:

AJtheAndroidNoOb said:
I just got a Note 4 (Korean variant). I plan to root it with CF auto-root and flash a ROM. I am on MM update and my build number is same as the one as in the CF auto-root so I have worries about that. However, I wanted to check my bootloader first and the dialer trick won't work so I installed adb on my laptop. When I enter the command "adb devices" my device would read and thus I proceeded with the command "adb reboot-bootloader". My phone then would ONLY Restart and when typing the command "adb fastboot-devices" nothing would appear. What am I doing wrong? Can someone please help me because it would like to know if my bootloader is locked before proceeding with rooting since my main reason of rooting is to flash a custom ROM. :crying:
Click to expand...
Click to collapse
Bootloader is not locked.
Just get twrp recovery and flash via odin.
Boot into twrp.
Then flash supersu.zip from twrp.
Thats it you will be rooted and ready to flash any rom.
Twrp N910K/S/L
https://www.androidfilehost.com/?fid=24052804347844773
Supersu.zip
https://mega.nz/#!TE1VFIQD!XoaYaXoLfMDjxvO-uYvDnxejNC-QQlYex0P_UWlDCZ0

Trex888 said:
Bootloader is not locked.
Just get twrp recovery and flash via odin.
Boot into twrp.
Then flash supersu.zip from twrp.
Thats it you will be rooted and ready to flash any rom.
Twrp N910K/S/L
https://www.androidfilehost.com/?fid=24052804347844773
Supersu.zip
https://mega.nz/#!TE1VFIQD!XoaYaXoLfMDjxvO-uYvDnxejNC-QQlYex0P_UWlDCZ0
Click to expand...
Click to collapse
So I don't have to worry about the bootloader? What should be ticked in Odin (and what version of Odin preferably)?
P. S (Out of Topic) isn't there anything to be worried about the emmc error on my Note 4 SM-N910K?

AJtheAndroidNoOb said:
So I don't have to worry about the bootloader? What be ticked in Odin (and what version of Odin preferably)?
P. S (Out of Topic) isn't there anything to be worried about the emmc error on my Note 4 SM-N910K?
Click to expand...
Click to collapse
Dont worry just follow the steps given below correctly.
1 download odin version 3.10 is stable in my opinion.
2,download Twrp & supersu.zip.( do not extract any file ) move supersu file to phone and Twrp to pc
3,open odin and go to options and uncheck autoreboot.
4,choose AP tab in odin and upload Twrp file.
5, put your device into download mode.
6 connect device in your pc and hit start.
7,once odin shows pass remove battery then insert again.
8,now boot into twrp by pressing 3 buttons (volume up+home+power)
9,in twrp go to install and search for supersu file where it's located.
10, swipe confirm to flash supersu.zip and reboot system.
Your device may reboot twice so dont worry its normal dont touch anything until it reboot to system.
Go to app drawer you will see supersu icon open it and thats it you are rooted 100% with Twrp recovery to flash custom roms.

Trex888 said:
Dont worry just follow the steps given below correctly.
1 download odin version 3.10 is stable in my opinion.
2,download Twrp & supersu.zip.( do not extract any file ) move supersu file to phone and Twrp to pc
3,open odin and go to options and uncheck autoreboot.
4,choose AP tab in odin and upload Twrp file.
5, put your device into download mode.
6 connect device in your pc and hit start.
7,once odin shows pass remove battery then insert again.
8,now boot into twrp by pressing 3 buttons (volume up+home+power)
9,in twrp go to install and search for supersu file where it's located.
10, swipe confirm to flash supersu.zip and reboot system.
Your device may reboot twice so dont worry its normal dont touch anything until it reboot to system.
Go to app drawer you will see supersu icon open it and thats it you are rooted 100% with Twrp recovery to flash custom roms.
Click to expand...
Click to collapse
BTW, I am on Marshmallow 6.0.1. Is there no problems? So sorry for my repetitive questions. :crying:

AJtheAndroidNoOb said:
BTW, I am on Marshmallow 6.0.1. Is there no problems? So sorry for my repetitive questions. :crying:
Click to expand...
Click to collapse
No problem This method works on any os 4.4.4/5.0/5.1.1/6.0.1.
Make sure to follow all steps correctly and most importantly make a backup of your whole device from twrp to microsd card before start flashing any roms or stuff just in case if anything goes wrong you will be able to restore it.

Trex888 said:
No problem This method works on any os 4.4.4/5.0/5.1.1/6.0.1.
Make sure follow all steps correctly.
Click to expand...
Click to collapse
Once I pressed start it is stucked at
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
What to do?

AJtheAndroidNoOb said:
Once I pressed start it is stucked at
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
What to do?
Click to expand...
Click to collapse
Did you got samsung usb drivers installed on your pc ?
Close odin and open again
Upload twrp file into odin
Remove battery and insert again
Boot into download mode
Hit start
If it hapoens again just restart your pc and try again

Trex888 said:
Did you got samsung usb drivers installed on your pc ?
Close odin and open again
Upload twrp file into odin
Remove battery and insert again
Boot into download mode
Hit start
If it hapoens again just restart your pc and try again
Click to expand...
Click to collapse
Wooooot! I just changed USB ports and tried again. Now I have SuperSU and custom TWRP recovery! Thank you very much, to be honest I was scared to try and doubted at first but now I know it does work. Thank you! I can now flash custom ROMs without any problems right?

AJtheAndroidNoOb said:
Wooooot! I just changed USB ports and tried again. Now I have SuperSU and custom TWRP recovery! Thank you very much, to be honest I was scared to try and doubted at first but now I know it does work. Thank you! I can now flash custom ROMs without any problems right?
Click to expand...
Click to collapse
Yes you can but make sure roms that you are going to flash are compatible with your model otherwise you will face some issues.
Dont forget to backup your current rom from twrp.
Congrats and enjoy the freedom and power of root

Screenshot of proof!
Trex888 said:
Yes you can but make sure roms that you are going to flash are compatible with your model otherwise you will face some issues.
Dont forget to backup your current rom from twrp.
Congrats and enjoy the freedom and power of root
Click to expand...
Click to collapse
Woooot! Here's a screenshot
https://imgur.com/a/NHnjd

AJtheAndroidNoOb said:
Woooot! Here's a screenshot
https://imgur.com/a/NHnjd
Click to expand...
Click to collapse
Don't forget to thanks @Chainfire for supersu root and Team win recovery project (TWRP) who made this possible.
All the credits goes to them.

Downgrade MM to LLP

How to downgrade MM to LLP for SS J5 2015?
Thanks <3

kysieucute said:
How to downgrade MM to LLP for SS J5 2015?
Thanks <3
Click to expand...
Click to collapse
Hi maybe this helps
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801

Vmb265 said:
Hi maybe this helps
https://forum.xda-developers.com/galaxy-j5/how-to/6-0-1-5-1-1-bootloader-modem-j500xx-t3566801
Click to expand...
Click to collapse
I have read but still do not understand because I am a new member and not very familiar with something like this. Can you tell me more about downgrade MM to LP?
Thanks

kysieucute said:
I have read but still do not understand because I am a new member and not very familiar with something like this. Can you tell me more about downgrade MM to LP?
Thanks
Click to expand...
Click to collapse
Okay so do you just want to downgrade to LLP for flashing so other Rom or you actually want to use LLP as your daily driver?:cyclops:

Vmb265 said:
Okay so do you just want to downgrade to LLP for flashing so other Rom or you actually want to use LLP as your daily driver?:cyclops:
Click to expand...
Click to collapse
sorry you. I am a Vietnamese person so I do not know much about English. I have to google translate. Please do not abbreviate or anything. I do not understand. sorry to bother you. Can you give me specific instructions on how to downgrade from MM to LP. If you can write more specifically thank you. thank you

Okay so assuming that you actually want to use Lollipop version on your j5,here Ive tried to provide some steps to do that:
NOTE: This will erase your data so make a backup
Step 1: Find your device model(like j500f/m/fn/h) and download the lollipop rom accordingly from herehttps://www.sammobile.com/firmwares/
Just search the model number
Step 2:Get Odin3 on your computer from here http://odin3.en.lo4d.com
Step 3:After downloading all files, now you need to set your j5 into download mode- Just switch off and the hold Vol down+Home+Power at the same time
Step 4:Connect your device via USB(UniversalSerialBuzz )cable to your computer and open odin application,the dialog box should show 'Added!'
Step 5: Select AP option and browse the ROM file you downloaded previously
Step 6: Let it verify things and after a while hit the Start button and let it do its thing!
Step 7: After the process is complete the device should boot up in lollipop (it'll take a while!)
Step 8:Enjoy Lollipop!
I hope that helps,also if you need anymore assistance feel free to ask!

Vmb265 said:
Okay so assuming that you actually want to use Lollipop version on your j5,here Ive tried to provide some steps to do that:
NOTE: This will erase your data so make a backup
Step 1: Find your device model(like j500f/m/fn/h) and download the lollipop rom accordingly from herehttps://www.sammobile.com/firmwares/
Just search the model number
Step 2:Get Odin3 on your computer from here http://odin3.en.lo4d.com
Step 3:After downloading all files, now you need to set your j5 into download mode- Just switch off and the hold Vol down+Home+Power at the same time
Step 4:Connect your device via USB(UniversalSerialBuzz )cable to your computer and open odin application,the dialog box should show 'Added!'
Step 5: Select AP option and browse the ROM file you downloaded previously
Step 6: Let it verify things and after a while hit the Start button and let it do its thing!
Step 7: After the process is complete the device should boot up in lollipop (it'll take a while!)
Step 8:Enjoy Lollipop!
I hope that helps,also if you need anymore assistance feel free to ask!
Click to expand...
Click to collapse
Is this normal like flash ROM 6.0?
I tried flashing the stock 5.1.1 LP and it crashed in the aboot.mbn section

kysieucute said:
Is this normal like flash ROM 6.0?
I tried flashing the stock 5.1.1 LP and it crashed in the aboot.mbn section
Click to expand...
Click to collapse
Yes it is the same process,maybe try to install Samsung drivers or update then from control panel settings.

Vmb265 said:
Yes it is the same process,maybe try to install Samsung drivers or update then from control panel settings.
Click to expand...
Click to collapse
error file aboot.mbn !!!!
driver OK
how to fix ?
Everything is full .... until the flash is defective. I think samsung blocked this !!!
Thank you for the fast reply tried to install the LL version through Odin but it shows me some errors
**Whenever i try to downgrade i get the same error about aboot.mbn and on the phone screen sw rev check fail labootlfused 2 binary 1**
-HERE IS THE LOG-
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100).
<ID:0/004> File analysis
<ID:0/004> SetupConnection..
<ID 0/004. Initialzation..
<ID:0/004> Get PITT for mapping.
<ID:0/004> Firmware update start.
<ID:0/004> SingleDownload.
<ID 0/004> aboot. mbn
<ID 0/004 NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID: 01004
<ID:0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 failed 1)
END

Hey...
Goto Settings-->About Phone--> Tap on Build number 5-6 times..
Then goto settings --> Developer options--> enable oem unlocking..
Remove screen lock protection example pattern or pin code and flash Lollipop Firmware with any Flasher Odin recommended

afaqktk2 said:
Hey...
Goto Settings-->About Phone--> Tap on Build number 5-6 times..
Then goto settings --> Developer options--> enable oem unlocking..
Remove screen lock protection example pattern or pin code and flash Lollipop Firmware with any Flasher Odin recommended
Click to expand...
Click to collapse
when flashing error in aboot.mbn file

kysieucute said:
when flashing error in aboot.mbn file
Click to expand...
Click to collapse
Try other firmware.. i mean doqnload firmware again from another site

afaqktk2 said:
Try other firmware.. i mean doqnload firmware again from another site
Click to expand...
Click to collapse
I have tried with a lot of different versions and still have errors on that file. I think samsung blocked downgrade the android version

kysieucute said:
I have tried with a lot of different versions and still have errors on that file. I think samsung blocked downgrade the android version
Click to expand...
Click to collapse
After enabling developer options u can flash it.. enable developer options and try
---------- Post added at 07:24 AM ---------- Previous post was at 07:16 AM ----------
If this doesnt work try to flash other partitions except aboot.

afaqktk2 said:
After enabling developer options u can flash it.. enable developer options and try
Click to expand...
Click to collapse
Why do I see everyone saying that flash fw LP as normal !! I made a full error in the file aboot.mbn !!! unlock oem + driver is full
ROM 4 file or 1 file or 5 file same thing

kysieucute said:
Why do I see everyone saying that flash fw LP as normal !! I made a full error in the file aboot.mbn !!! unlock oem + driver is full
ROM 4 file or 1 file or 5 file same thing
Click to expand...
Click to collapse
That something tricky .. dont know why..
But aboot.mbn error comes when FRP lock is enabled...

afaqktk2 said:
That something tricky .. dont know why..
But aboot.mbn error comes when FRP lock is enabled...
Click to expand...
Click to collapse
I have activated it since I knew naughty the phone. and rom flash 5.1.1 still get error at aboot.mbn

kysieucute said:
I have activated it since I knew naughty the phone. and rom flash 5.1.1 still get error at aboot.mbn
Click to expand...
Click to collapse
In download mode there is written FRP lock...
What is FRP lock status if it is ON then itll give aboot.mbn

afaqktk2 said:
In download mode there is written FRP lock...
What is FRP lock status if it is ON then itll give aboot.mbn
Click to expand...
Click to collapse
I am a new member so I do not understand. Can you now write down the steps that will help me? thank you very much !!

The error u mentioning i mean aboot.mbn failed is mostly because of when FRP lock is enabled..
So if u press vol down + power combo then vol up..
In download mode there will be text see there FRP lock is enabled or disabled

ROOT Samsung Galaxy Tab S5e SM-T725

i search a Root for the Samsung Galaxy Tab S5e SM-T725 , for install a Mod PlayStore .....

Are you asking if there is root for the Tab 5se yet?

yes ... is there a root for the tab S5e?

Yes, there is root for the S5e, it is complicated atm...
https://forum.xda-developers.com/galaxy-s10/development/magisk-root-galaxy-s10-series-t3918699
DerZero said:
yes ... is there a root for the tab S5e?
Click to expand...
Click to collapse

I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?

DerZero said:
I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?
Click to expand...
Click to collapse
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.

nsx2brz said:
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.
Click to expand...
Click to collapse
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.

AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
A few caveats with XAA:
For 'OEM Unlock' to show, you must be connected to WiFi to unlock the Bootloader.
And if you 'Factory Reset' after unlocking it, it disappears completely.
If you change the date, time or year, it doesn't return until you reconnect to WiFi.

Interesting, just got mine today tempted to try this.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
Please let us know how it went!

I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.

AHE_XDA said:
I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.
Click to expand...
Click to collapse
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.

Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
AHE_XDA said:
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.
Click to expand...
Click to collapse

nsx2brz said:
Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
Click to expand...
Click to collapse
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.

best would be a root of CF-AUTOROOT or a TWR and a ROOT.ZIP -.-

https://forum.xda-developers.com/ga...ragon-root-waiting-discussion-t3919024/page24
Post #235 is where is says what worked. Good luck! I probably won't have time to try mine until next month.
AHE_XDA said:
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.
Click to expand...
Click to collapse

I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.

PewPewK said:
I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.
Click to expand...
Click to collapse
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.

btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
Because my installation process was hardly linear (I ran into many problems along the way), I can't guarantee that these are exclusively the exact steps you would need to take to get it working. But I think this should be a compilation of all the final (working-ish) steps I took.
(1) Setup tablet for first time, go to settings, enable developer mode, and flick the OEM Unlocking switch.
(2) Turn off the Tab S5e and boot into Download Mode by holding Power and Vol Up + Vol Down. Then hold up on the Vol Up button (not just a quick press) as it says to enter Bootloader Unlocking Mode. Follow the instructions there to fully unlock the bootloader.
(3) The tablet will be formatted at this step. After the bootloader is fully unlocked, make sure you boot back into the Tab S5e and perform the set up again. Enable developer options and make sure that the OEM Unlocking switch is turned on. Yes, again. This step is necessary apparently due to some changes Samsung made with their new VaultKeeper service? If you don't you may soft brick the device.
(4) Install @ianmacd's Magisk Manager application on your Tab S5e. Download is here. [Update: TopJonWu's official Magisk build should now work fine.]
(5) Download the latest Tab S5e firmware build. I found my copy here. Extract from it the AP file. Transfer this file to your Tab S5e.
(6) Back in Magisk Manager, go to settings and look for "Update Channel." Here's where I'm a little uncertain of what I did that finally got it to work, so I'll recommend two steps...
(7a) Select the ianmacd update channel and return to the home screen of Magisk. [Update: This shouldn't be necessary anymore, especially if you installed the official Magisk Manager earlier.] Click install, then choose the patch file option. Locate the AP file you transferred earlier and wait for it to finish creating a "magisk_patched.tar" file. Transfer this file to your computer and rename it "magisk_patched_ianmacd.tar," then delete the old magisk_patched on your device.
(7b) Do the same for the Canary (debug) update channel. Patch the AP again, and locate the patched file, copy it to your computer, and rename it to something clear.
(8) This is an odd step I had to follow to avoid errors flashing. It turns out of the several times I tried making the patched images, I almost always inevitably had some file in the archives getting corrupted. So open up both magisk_patched.tar's and test them for errors. I did this in 7-Zip, but there's probably ways to do it in WinRAR, too. If it gives you any error, take a note of which file it failed on because that guarantees your flashing will fail in later steps. In fact, the reason I recommended doing two different methods for patching magisk above was because the first ianmacd patch I tried had a corrupt recovery.img. What I ended up doing to fix it was extracting a working (non-error checking) recovery.img, vbmeta.img, and boot.img from the two different patched Magisks and then recombined them myself into my own Magisk tar. I also kept the meta-inf folder in there for good measure, though I don't think it's necessary? So in the end, I had what I called a "magisk_patched_lite.tar" that contained exactly three images: recovery.img, vbmeta.img, and boot.img, along with the meta-inf folder and ensured 7-Zip did not return any errors on the archive.
(9) Reboot the tablet to Download Mode. Press Vol Up to start. Attach the Tab S5e to your computer, and start Odin (I used v3.13.1_3B_PatcheD).
(10) Put some working archive of the patched magisk in the AP slot and uncheck "Auto Reboot." I don't know if the 'lite' version is sufficient for your first flash, but I suspect that it is (it would not be sufficient if you're pre-patching an updated firmware for the Tab S5e). Let Odin rip and see if you get any errors.
(11) Assuming Odin was successful, hold Power and Vol Down to exit Download Mode, then immediately switch to Power and Vol Up once the screen shuts off. Continue holding these until you are greeted with Recovery mode.
(12) Use the volume keys to select Factory Reset/Wipe Data. Execute that to make sure the tablet is properly formatted.
(13) Use the reboot into system option at the top of recovery. Hold Power and Vol Up until the "Bootloader is Unlocked" warning screen shows up, then release.
(14) If you're lucky, you should eventually see a red warning message about not having Samsung software installed. That's a good sign. My tablet fumbled around these steps and looked like it was gonna bootloop for a while? But eventually, it ran its course and booted.
(15) You hopefully have root installed now. Set up the tablet one last time, install the ianmacd Magisk Manager again and open it up. If it says Magisk is installed, great job, otherwise... I don't know where the issue is because this rooting sequence is way more complicated than for other devices! At some point, I think after a reboot, Magisk Manager asked if it could do some additional setup stuff. Obviously let it do that.
Click to expand...
Click to collapse
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Also important! Fundmentally, this version of root works very differently from what you may be used to. See here for detailed information. Normally root is installed onto the boot partition, but Samsung did some ****y stuff this generation to be "compliant" with Google's new rules, but still do things in their own special way, so now to achieve root Magisk has to live on the recovery partition.
Magisk living on the recovery partition means that in order to boot with Magisk enabled, you have to boot into recovery. So to boot with root, hold power and vol up until you see the "bootloader is unlocked" warning screen, then release. If you hold Vol Up, you will be taken to recovery, which will boot the system partition with root enabled. Otherwise, your tablet will boot the system partition without root. So if you do not do this step, root will not work (i.e. you'll boot into system without Magisk).
Hope this helps you achieve root.

Great Instructions.
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
PewPewK said:
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Hope this helps you achieve root.
Click to expand...
Click to collapse

btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
netjetman said:
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
Click to expand...
Click to collapse
Yep, good point. I forgot to include that because in the original e-mail thread, it was already known and implied. But I'll add it to the post here so folks will catch that. Annoying for sure, but at least it works.