Related
If you unpack stock firmware file you'll find:
sboot.bin Bootloader
boot.bin Kernel
system.bin Rom
modem.bin Baseband
csc.bin CSC
Hidden.bin Related to CSC
cm.bin
What is this?
am also curious about what the cm.bin is.
seems to look like it is in place only to prevent flashing previous builds. If you come across any information please share.
thanks
I disassembled sboot.bin and cm.bin with IDA. It seems that cm = Cryptography Manager. Preventing flashing previous builds is implemented in sboot.bin (bootloader).
debugfan said:
I disassembled sboot.bin and cm.bin with IDA. It seems that cm = Cryptography Manager. Preventing flashing previous builds is implemented in sboot.bin (bootloader).
Click to expand...
Click to collapse
What happens if i delete cm.bin and flash on my phone?
romeoroad said:
What happens if i delete cm.bin and flash on my phone?
Click to expand...
Click to collapse
Just back up with twrp first, save that to ur pc, then wipe ur internal storage+system+data, that should have ur whole device set!
debugfan said:
I disassembled sboot.bin and cm.bin with IDA. It seems that cm = Cryptography Manager. Preventing flashing previous builds is implemented in sboot.bin (bootloader).
Click to expand...
Click to collapse
I don't think so.
It contains AES-256 DRBG encryption keys. I think it's for fingerprint, signatured keys from Samsung for bootable images (boot.img & recovery.img), bootloader (sboot.bin) and other signed binaries (modem.bin & cm.bin)
and for KNOX private mode.
The sboot.bin prevents the previous build itself.
forumber2 said:
I don't think so.
It contains AES-256 DRBG encryption keys. I think it's for fingerprint, signatured keys from Samsung for bootable images (boot.img & recovery.img), bootloader (sboot.bin) and other signed binaries (modem.bin & cm.bin)
and for KNOX private mode.
The sboot.bin prevents the previous build itself.
Click to expand...
Click to collapse
If this is for fingerprint etc that would explain why CM & AOSP builds couldn't support that sensor specifically.
Hi all
I thinks I've done a big mess. Following the xda guide to install modified ROM via ODIN, I've upgraded BL and Modem to 5.1.1
Now, the red string appears on the left top of the screen: INVALID MAGIC STRING
This is the guide
Do exactly step-by-step the following things:
- Unplug your Phone (IMPORTANT!)
- Turn your Phone completely off (This is IMPORTANT)
- Start your Phone in download mode on this way: Press Vol down + Home + Power buttons till the screen turns on, press Vol Up to continue (Only enter download mode on this way, otherwise it won't work!!)[/B]
- Open Odin 3.10.6 on your PC (Make sure you're using this version of Odin, other versions won't work correctly maybe!)
- Click on the 'BL' button, and load in your BOOTLOADER tar.md5 file for your model
- Click on the 'CP' button, and load in your MODEM tar.md5 file for your model
- DON'T TOUCH ANYTHING ELSE (you can brick your phone if you choose other settings in Odin)
- Now Connect your phone to your computer (DO NOT connect your phone before this step, otherwise it won't work!)
- Click on the Start button
- Wait till it finish flashing.
- Your phone reboots automatically after flashing.
- Always check after flashing: Settings -> About device -> Baseband; that should show the same modem build number noted as here.
And also check if the bootloader got flashed correctly by downloading an AndroidTerminal app, and enter this command: getprop ro.boot.bootloader
Unfortunately, after this procedure I can't rollback to 5.0.2, neither I can't install 5.1.1. stock firmwares (from sammobile) with ODIN. It goes always FAIL:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please anyone of you can help me to unblock my device? Whatever firmware is good if device will work again.
Thanks
Rob
rmastro said:
Please anyone of you can help me to unblock my device? Whatever firmware is good if device will work again.
Thanks
Rob
Click to expand...
Click to collapse
Thanks for the guide, but description of what EXACTLY did you do would be much helpful.
Moreover, the guide mentions Boot loader and modem update. So why system.img?
davebugyi said:
Thanks for the guide, but description of what EXACTLY did you do would be much helpful.
Moreover, the guide mentions Boot loader and modem update. So why system.img?
Click to expand...
Click to collapse
Ok. These the steps:
- Upgraded BL and MODEM 5.1.1 via ODIN following the xda guide
- Got RED message on device reboot INVALID MAGIC STRING
- Then, tried to install stock 5.1.1 firmware via ODIN and got fail (after system.img)
The starting firmware was G920FXXU0AOA5
Thanks
rmastro said:
Ok. These the steps:
- Upgraded BL and MODEM 5.1.1 via ODIN following the xda guide
- Got RED message on device reboot INVALID MAGIC STRING
- Then, tried to install stock 5.1.1 firmware via ODIN and got fail (after system.img)
The starting firmware was G920FXXU0AOA5
Thanks
Click to expand...
Click to collapse
Because that is an old firmware. If you have your BL and Modem updated to 5.1.1 you cannot downgrade back to 5.0.2.
Flash a correct 5.1.1 firmware (COH2 ending maybe).
davebugyi said:
Because that is an old firmware. If you have your BL and Modem updated to 5.1.1 you cannot downgrade back to 5.0.2.
Flash a correct 5.1.1 firmware (COH2 ending maybe).
Click to expand...
Click to collapse
I've G920FXXU2COH2_G920FHUI2COH1_G920FXXU2COH2 file, but it's not working at all
Any suggestion?
Thanks
Hey I had a problem like yours I did the same thing (flashing a 5.1.1 bootloader and modem) and ended up having to flash a stock 5.1.1 rom with odin downloaded from sam mobile but mine kept failing after hidden.img so did some research and found this
https://www.reddit.com/r/GalaxyS6/comments/35zshn/howto_fix_a_failed_odin_flash_softbrick_hiddenimg/
That seemed to fix my problem it booted up no problem completely stock just had to root it again and flash the rom I was after in the first place (xtretolite 5.1.1 deo-dexed)
Thanks Jamie
Unfortunately It went not good. I've done that procedure, extracting the hidden.img and renaming it but after the flash it gives me the same red string INVALID MAGIC STRING.
Don't know what to do more!
Rob
rmastro said:
Thanks Jamie
Unfortunately It went not good. I've done that procedure, extracting the hidden.img and renaming it but after the flash it gives me the same red string INVALID MAGIC STRING.
Don't know what to do more!
Rob
Click to expand...
Click to collapse
Are you sure you have a 920F?
How come then COH2 "does not work at all"?
Invalid Magic String
davebugyi said:
Are you sure you have a 920F?
How come then COH2 "does not work at all"?
Click to expand...
Click to collapse
Hi, yes 920F
The flash procedure fails just after Odin is writing "system.img" like I copied.
There should be a way to erase everything and start again...
That Invalid Magic String, what does it mean???
rmastro said:
Hi, yes 920F
The flash procedure fails just after Odin is writing "system.img" like I copied.
There should be a way to erase everything and start again...
That Invalid Magic String, what does it mean???
Click to expand...
Click to collapse
Every thread I found about Invalid Magic String was about incorrect flash - either firmware or not allowed downgrade.
davebugyi said:
Every thread I found about Invalid Magic String was about incorrect flash - either firmware or not allowed downgrade.
Click to expand...
Click to collapse
So, there's no chance to fix?
rmastro said:
So, there's no chance to fix?
Click to expand...
Click to collapse
There should be a chance
Are you using the latest ODIN? (3.10.7) and running it as admin? Are the usb drivers correctly installed?
Also it would be good to know what is your current bootloader version.
davebugyi said:
There should be a chance
Are you using the latest ODIN? (3.10.7) and running it as admin? Are the usb drivers correctly installed?
Also it would be good to know what is your current bootloader version.
Click to expand...
Click to collapse
Tried with all ODIN version, same result. Anyway I'm trying now with 3.10.7 again
The USB drivers installed, uninstalled and installed again.
The BL version should be 5.1.1, because this stage of the upgrade seems to go fine.
I've also uploaded both BL and Modem with these http://forum.xda-developers.com/showpost.php?p=60112855&postcount=3
rmastro said:
Tried with all ODIN version, same result. Anyway I'm trying now with 3.10.7 again
The USB drivers installed, uninstalled and installed again.
The BL version should be 5.1.1, because this stage of the upgrade seems to go fine.
I've also uploaded both BL and Modem with these http://forum.xda-developers.com/showpost.php?p=60112855&postcount=3
Click to expand...
Click to collapse
I am out of ideas.
I have a 920F as well and used those exact files as you to upgrade first, but not having any issues flashing the COH2 firmware with ODIN.
davebugyi said:
I am out of ideas.
I have a 920F as well and used those exact files as you to upgrade first, but not having any issues flashing the COH2 firmware with ODIN.
Click to expand...
Click to collapse
There should be a way to downgrade
What if I try to install a 5.0.2 firmware?
rmastro said:
There should be a way to downgrade
What if I try to install a 5.0.2 firmware?
Click to expand...
Click to collapse
If you do have 5.1.1 bootloader you van not downgrade anymore - the warning was even in the official OTA update from Samsung.
rmastro did u fix your issue? me facing same problem, getting almost mad coz no solution work with me by now after 15 days
Hello!
I have been searching the net to find a suitable root guide so that I can root my Samsung Galaxy S6.
I'm still running Android 5.1.1, there are no updates. I'm from the UK but I bought my mobile for a little bit cheaper than normal price online and that means that the phone is from Vietnam (but not locked to any network).
I've tried contacting Samsung UK, who have not been helpful and keep telling me to speak with Samsung Vietnam, obviously this would not be possible as I dont speak/write Vietnamese.
All the root guides I have come across dont match my firmware version:
Brand: Samsung
Model: SM-G920F
Android Version: 5.1.1 (lmy47x.g920fxxu3qpa7)
Could someone help me or point me in the right direction?
I'd be really happy with Android 6 stock edition for me phone, not too fussed about the cracked apps.
Thanks in advance!
Bump?
Just update it to latest 6.0.1 ROM (G920FXXU3DPFJ - XME). Install arter97's TWRP and install latest SuperSU zip (2.76 right now) to root the device.
forumber2 said:
Just update it to latest 6.0.1 ROM (G920FXXU3DPFJ - XME). Install arter97's TWRP and install latest SuperSU zip (2.76 right now) to root the device.
Click to expand...
Click to collapse
Please excuse my ignorance, but I am a noob when it comes to rooting, I have not done it before.
I will look at guides.
Where would I find the suitable rom? then I will look for arter97's TWRP and SuperSU zip 2.76
Thanks!
CL4RKY said:
Please excuse my ignorance, but I am a noob when it comes to rooting, I have not done it before.
I will look at guides.
Where would I find the suitable rom? then I will look for arter97's TWRP and SuperSU zip 2.76
Thanks!
Click to expand...
Click to collapse
G920FXXU3DPFJ - XME : http://www.sammobile.com/firmwares/download/76038/G920FXXU3DPFJ_G920FOLB3DPFJ_XME/
arter97 TWRP: http://arter97.com/browse/S6/kernel/21.0/g920fi/arter97-recovery-g920fi-21.0-twrp_3.0.2-0.tar.md5
Odin v3.11.1; http://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
SuperSU zip; https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
forumber2 said:
G920FXXU3DPFJ - XME : http://www.sammobile.com/firmwares/download/76038/G920FXXU3DPFJ_G920FOLB3DPFJ_XME/
arter97 TWRP: http://arter97.com/browse/S6/kernel/21.0/g920fi/arter97-recovery-g920fi-21.0-twrp_3.0.2-0.tar.md5
Odin v3.11.1; http://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
SuperSU zip; https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Click to expand...
Click to collapse
Thank you so much mate Been wanting to update my phone for ages!
forumber2 said:
G920FXXU3DPFJ - XME : http://www.sammobile.com/firmwares/download/76038/G920FXXU3DPFJ_G920FOLB3DPFJ_XME/
arter97 TWRP: http://arter97.com/browse/S6/kernel/21.0/g920fi/arter97-recovery-g920fi-21.0-twrp_3.0.2-0.tar.md5
Odin v3.11.1; http://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
SuperSU zip; https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Click to expand...
Click to collapse
Hello again
Thanks for sending the links........I've tripped the Knox security so it is now void ffs! :crying:
Will this stop anything from working?
I've been trying to look for a guide but not sure which one to follow now.
1) Open ODIN
2) Connect phone
3) Tick "ap" and select G920FXXU3DPFJ_G920FOLB3DPFJ_G920FXXU3DPFJ_HOME.tar.md5
4) Start
I dont care about the rooting just updating to Android 6.0.1
Thanks in advance
P.S Maybe my warranty isnt void pheww!!
but when I try to load the firmware you told me to download for Android 6.0.1 the program shows this error:
"mmd5 error! binary is invalid"
Thanks!
*UPDATE* the file type was .tar.md5, I removed the .md5 so it was just .tar
CL4RKY said:
P.S Maybe my warranty isnt void pheww!!
but when I try to load the firmware you told me to download for Android 6.0.1 the program shows this error:
"mmd5 error! binary is invalid"
Thanks!
Click to expand...
Click to collapse
If your knox is 0x1, your warranty is void.
If Odin gives md5 error, it means the downloaded file is corrupt, you need to redownload it again.
forumber2 said:
If your knox is 0x1, your warranty is void.
If Odin gives md5 error, it means the downloaded file is corrupt, you need to redownload it again.
Click to expand...
Click to collapse
Okay mate, yeah I had a panic but its not void haha! :victory:
Thanks so much for helping me with this, appreciate it
I will try downloading the file again. :fingers-crossed:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Downloaded a new one but this happens when I try to run it?
Okay managed to get this working.
For anyone else who gets the "All threads completed. (succeed 0 / failed 1)" error, I just changed the USB cable.
If you can just use the official Samsung cable in case you swap it for another cable that doesn't work...
On this morning i tried to downgrade my G930F from 7.0 to 6.0.1 but i failed and now i need help.
I installed odin and downloaded the 6.0.1 flies BL, AP, CP and CSC then placed the files to odin. My phone was in the Downloading mode.
And now stands "SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1" on my display.
On Odin:
"<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> param.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
If you need more details then tell me what you want.
So please can anyone help c:
Try flashing the latest stock ROM for your phone.
audit13 said:
Try flashing the latest stock ROM for your phone.
Click to expand...
Click to collapse
Only the AP file?
Thank you.
Android 7.0 (Stock ROM) is running but my IMEI is not invaild what can do now?
Did you not downgrade your phone? I also cannot downgrade my Galaxy S7 exynos.
Did you also have Fail in ODIN device:2 binary:1
edit: I saw you, you also have the same fails.
NexusHD said:
Thank you.
Android 7.0 (Stock ROM) is running but my IMEI is not invaild what can do now?
Click to expand...
Click to collapse
Make sure you're using the latest version of ODIN to flash back to the latest firmware
ODIN 3.12.7 I think is latest and should work
Hi, we try to downgrade the firmware not upgrading
*Detection* said:
Make sure you're using the latest version of ODIN to flash back to the latest firmware
ODIN 3.12.7 I think is latest and should work
Click to expand...
Click to collapse
raffaels said:
Hi, we try to downgrade the firmware not upgrading
Click to expand...
Click to collapse
Use the latest BL and CP and then choose AP and CSC from the downgrade version you want to.
Samsung check the BL version and lock it for downgrading to previous (old) BL version. Correct me if I'm wrong, it based on my experience downgrade to MM.
[/COLOR]
raffaels said:
Hi, we try to downgrade the firmware not upgrading
Click to expand...
Click to collapse
So the phone is still working at this point?
OK, Make sure the phone is actually saying it is the G930F in download mode, a lot are faked
Did you also lose your IMEI Number?
jimbohatake said:
Use the latest BL and CP and then choose AP and CSC from the downgrade version you want to.
Samsung check the BL version and lock it for downgrading to previous (old) BL version. Correct me if I'm wrong, it based on my experience downgrade to MM.
Click to expand...
Click to collapse
jimbohatake said:
Use the latest BL and CP and then choose AP and CSC from the downgrade version you want to.
Samsung check the BL version and lock it for downgrading to previous (old) BL version. Correct me if I'm wrong, it based on my experience downgrade to MM.
Click to expand...
Click to collapse
I've downgraded from Nougat to MM without doing that, I just flashed the 4 normal MM files using CSC and not HOME_CSC, the phone had some errors on boot so I flashed it again, 2nd time it was fine
Never had any errors with ODIN though
Could be later builds of Nougat have locked something like that, not tried to downgrade since then
*Detection* said:
I've downgraded from Nougat to MM without doing that, I just flashed the 4 normal MM files using CSC and not HOME_CSC, the phone had some errors on boot so I flashed it again, 2nd time it was fine
Never had any errors with ODIN though
Could be later builds of Nougat have locked something like that, not tried to downgrade since then
Click to expand...
Click to collapse
I am sure, my phone is not fake, I've got 160k points on Antutu v7 and 5980 points on Geekbench MultiCore. Do you still use MM?
First I did as you told me. Odin stuckt at ERASING: USERDATA Partition after ODIN Flash. I've waited 3-4 minutes then I restarted my phone then I wiped everything. Now everything works good.
Do you think it is a big problem that it stuckt at ODIN?
jimbohatake said:
Use the latest BL and CP and then choose AP and CSC from the downgrade version you want to.
Samsung check the BL version and lock it for downgrading to previous (old) BL version. Correct me if I'm wrong, it based on my experience downgrade to MM.
Click to expand...
Click to collapse
raffaels said:
I am sure, my phone is not fake, I've got 160k points on Antutu v7 and 5980 points on Geekbench MultiCore. Do you still use MM?
Click to expand...
Click to collapse
Not a fake S7, but a lot of the snapdragon models are faked to look like Exynos versions, so the G930F ROM won't work on it if it is snapdragon
You need to check Download Mode to be 100% sure what model it is, whatever model it says in DL mode is the correct model
Vibration doesn't work on MM, do you have any problem with vibration?
*Detection* said:
Not a fake S7, but a lot of the snapdragon models are faked to look like Exynos versions, so the G930F ROM won't work on it if it is snapdragon
You need to check Download Mode to be 100% sure what model it is, whatever model it says in DL mode is the correct model
Click to expand...
Click to collapse
raffaels said:
Vibration doesn't work on MM, do you have any problem with vibration?
Click to expand...
Click to collapse
I'm not on MM, but no I don't remember having any problems with it before
raffaels said:
Vibration doesn't work on MM, do you have any problem with vibration?
Click to expand...
Click to collapse
That's because you're using new bootloader with old android.
The nougat bootloader has some under the hood changes which won't work with MM, vibration was one of them. I assume it just makes a faint whining noise instead? I had the same after rolling back to MM via a TWRP backup.
raffaels said:
First I did as you told me. Odin stuckt at ERASING: USERDATA Partition after ODIN Flash. I've waited 3-4 minutes then I restarted my phone then I wiped everything. Now everything works good.
Do you think it is a big problem that it stuckt at ODIN?
Click to expand...
Click to collapse
I dont know about that sorry, because when im downgrading it doesnt happen to me. if everything works good then its fine
---------- Post added at 08:03 AM ---------- Previous post was at 07:59 AM ----------
raffaels said:
Did you also lose your IMEI Number?
Click to expand...
Click to collapse
i did once, but i flash it again with the latest CP, AP and CSC, i get back my IMEI number.
oh yeah, if you have latest BL and CP on phone, just flash AP and CSC you want ex. MM version
I did it, everything worked on MM fine except vibration. So I had to upgrade it again.
"SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1" means you have flashed wrong firmware version.
When you download firmware look at the fourth number after model code. (for example G930FXXU1AQA3 - fourth number is 1, thats binary number of that firmware).
In download mode you see what is your device binary number, it has to be the same your downloaded firmware has.
Can anyone please build a twrp for j701f android 9.0. It has already got android 9.0 in some countries
I need help with my J701F Core. It continues to tell me not registered on network when I try to use voice or data. I discovered that the IMEI on the sticker is different from when I type *#06#. The sticker has the correct IMEIs. I don't have the 000 type. I searched here to find the solution and it all requires root. Any attempt to root my phone fails. I've tried many options. I flashed twrp through Odin and installed superuser but phone will not boot to OS. I'm sorry if I'm repeating a problem that has been solved but sincerely speaking I haven't found that solution. Any help would be deeply appreciated. Thanks
Put twrp, immediately put the oxygen core v4 or helios v3, when the firmware is loaded, you need to update the version of magisk v19 and you will have root rights
---------- Post added at 06:51 AM ---------- Previous post was at 06:49 AM ----------
oxygen v4 and helios v3 can be downloaded on this forum xda for j701x
How to root my latest j701f andriod pie version
When i flash twrp 3.2.1 latest .tar file through odin it take reboot as usual but it do not start the phone boot and boot again and again please help me becouse i try to many oxygen kernal or file i am gona made
Thats why i posted this
Ajay gorai said:
When i flash twrp 3.2.1 latest .tar file through odin it take reboot as usual but it do not start the phone boot and boot again and again please help me becouse i try to many oxygen kernal or file i am gona made
Click to expand...
Click to collapse
I couldnt root my phone because it needed twrp, and the twrp wouldnt install
It works it completely install
Hype- said:
I couldnt root my phone because it needed twrp, and the twrp wouldnt install
Click to expand...
Click to collapse
brother i really try my tricks
open odin select the zip file to flash before flash untick the auto reboot from option near the log menu
after flash remove the battery and boot into recovery mode
do wipe data if you dont want to lose any data then start recovery
the wipe the data do not wipe internal
after wipe go and select the magisk or supersu as per your need
flash using twrp remember latest need
after flashing clear the wipe cache and boot into the system
and enjoy...
Ajay gorai said:
Open your odin
Select the zip file though AP
Go to option in odin after log menu
Then untick the auto reboot
Then remove the battery
Then turn on your device in recovery mode ...
All work but your device with andriod pie boot not work stuck in samsung j7 nxt menu
Click to expand...
Click to collapse
how about install custom rom??
uchihunt said:
how about install custom rom??
Click to expand...
Click to collapse
for intalling custom it work perfect i use latest twrp 3.2.1
:fingers-crossed:
but for latest j701f pie twrp flash as usual and flash custom rom is done 1000%
Ajay gorai said:
for intalling custom it work perfect i use latest twrp 3.2.1
:fingers-crossed:
but for latest j701f pie twrp flash as usual and flash custom rom is done 1000%
Click to expand...
Click to collapse
give me link twrp tar.md5 please!!
Here's the link
uchihunt said:
give me link twrp tar.md5 please!!
Click to expand...
Click to collapse
https://drive.google.com/file/d/0ByNCDHNtZ8nPUjlUT1ZRS2lrQ2M/view
Flash Boot.tar.md5 In BL And Recovery.tar.md5 In AP
Hype- said:
https://drive.google.com/file/d/0ByNCDHNtZ8nPUjlUT1ZRS2lrQ2M/view
Flash Boot.tar.md5 In BL And Recovery.tar.md5 In AP
Click to expand...
Click to collapse
Is this the twrp for j701f stock pie 9?
Hype- said:
https://drive.google.com/file/d/0ByNCDHNtZ8nPUjlUT1ZRS2lrQ2M/view
Flash Boot.tar.md5 In BL And Recovery.tar.md5 In AP
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1303)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 19 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
why is it when i flash those in odin it will always fail? im on stock android 9 pi j701f
Its not but it works
paul222008 said:
Is this the twrp for j701f stock pie 9?
Click to expand...
Click to collapse
Unselect the reboot option in odin,then flash and when it says success force restart your phone yourself. It worked for me.
Hype- said:
Unselect the reboot option in odin,then flash and when it says success force restart your phone yourself. It worked for me.
Click to expand...
Click to collapse
I did that but it always fail to me. Why?
Are you using the latest version of Odin?
paul222008 said:
I did that but it always fail to me. Why?
Click to expand...
Click to collapse
Sometimes odin can be the reason behind failed updates because of not being updated. Are you using the latest version?
Hype- said:
Sometimes odin can be the reason behind failed updates because of not being updated. Are you using the latest version?
Click to expand...
Click to collapse
Yes the latest version of odin . Can you send me yours you are using? Also in my j701f its says on stock recovery download mode: enabled.
What is that supposed to mean?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hype- said:
https://drive.google.com/file/d/0ByNCDHNtZ8nPUjlUT1ZRS2lrQ2M/view
Flash Boot.tar.md5 In BL And Recovery.tar.md5 In AP
Click to expand...
Click to collapse
btw thanks but,my android 9.0 its okay??
It should work on Android 9.0
uchihunt said:
btw thanks but,my android 9.0 its okay??
Click to expand...
Click to collapse
Unselect the reboot option in odin and once it succeeds manual reboot your device, it should take time but twrp should be installed.
Hype- said:
Unselect the reboot option in odin and once it succeeds manual reboot your device, it should take time but twrp should be installed.
Click to expand...
Click to collapse
It always fail to me
I got the solution for you
paul222008 said:
It always fail to me
Click to expand...
Click to collapse
I found out that the reason for you being unable to flash TWRP is the prenormal kg state.Its a new feature on pie updates that prevent you from flashing custom binaries. Fortunately there's a solution right here in this forum.
https://forum.xda-developers.com/galaxy-s8/how-to/guide-skipping-kg-prenormal-oneui-t3911862
Check it out, hope it helps you