I rooted my phone using odin3 then tryed to flash the sdk23 arm64 xposed framework using flashify
Now im stuck on the samsung word logo 'boot loop' and i don't know how to fix it:crying:
Also have a custom recovery [TWRP]
now i think i broke it :crying: i cant get into the recovery mode i dont why but i went to advance wipe and check all of it
also now doesnt do to the samsung word logo it stays on the samsung galaxy s6 powered by android screen
also when charging no green is seen just a empty battery with lighting bolt
plus KERNEL IS NOT SEANDROID ENFORCING in red in the top left corner.
Think i basicallly wiped everything ohno
I'm struggling to understand why you were using Flashify to install Xposed, especially since you have TWRP. Regardless, you have to try and get it into Download Mode. If you can, you should be able to reinstall the original firmware.
es0tericcha0s said:
I'm struggling to understand why you were using Flashify to install Xposed, especially since you have TWRP. Regardless, you have to try and get it into Download Mode. If you can, you should be able to reinstall the original firmware.
Click to expand...
Click to collapse
i am able to get to download mode (odin mode right?), now how do i reinstall the original firmware? (maybe link me some steps)
1000 tutorials here on xda or youtube.
Basic structure:
find / download firmware
boot to Download Mode
open Odin as admin
place .tar or .tar.md5 file of the firmware in AP slot if one 1 large file or if it is split into multiple ones then they will be labeled obviously for BL, AP, CP, CSC just like in Odin.
Hit start and wait for a bit. If the flash is successful but it is stuck in a boot loop, then reboot to the stock recovery and reset it.
es0tericcha0s said:
1000 tutorials here on xda or youtube.
Basic structure:
find / download firmware
boot to Download Mode
open Odin as admin
place .tar or .tar.md5 file of the firmware in AP slot if one 1 large file or if it is split into multiple ones then they will be labeled obviously for BL, AP, CP, CSC just like in Odin.
Hit start and wait for a bit. If the flash is successful but it is stuck in a boot loop, then reboot to the stock recovery and reset it.
Click to expand...
Click to collapse
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone says
SECURE CHECK FAIL : (BOOTLOADER)
Looks like you're using the wrong firmware. You have to use one for your variant and you typically can't downgrade bootloaders so it's gotta be the same firmware or newer.
es0tericcha0s said:
Looks like you're using the wrong firmware. You have to use one for your variant and you typically can't downgrade bootloaders so it's gotta be the same firmware or newer.
Click to expand...
Click to collapse
<ID:0/003> Odin engine v(ID:3.1100)..
<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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed
i used a file G920IDVU3EPEA_G920IXSA3EPEA_G920IDVU3EPEA_HOME.tar.md5
pretty sure its the right one, the sticker on the back of my phone says its SM-G920I
This fail doesnt have the SECURE CHECK FAIL : (BOOTLOADER) on the phone
Also 'An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software' appears on the phone screen
Never Mind i fixed it i just had to use a differnt cable, think my cable was broken.
Cant get into the recovery mode (hold down the volume up, home and power button at the same time) right?
did a factory reset in recovery mode still have a bootloop
never mind again just didnt have the battery to boot up sorry think its fixed how love ya
xKyono said:
never mind again just didnt have the battery to boot up sorry think its fixed how love ya
Click to expand...
Click to collapse
:good::highfive::victory:
Related
I installed Cyanogen mod, didn't like it so wanted to go back to the stock, as it was "out-of-the-box"
Loaded up odin (latest) put phone into download mode, loaded I9100XWKF3_Kernel kernel, all went well.
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/005> Added!!
Now phone is stuck at the start screen
"Samsung Galaxy S II GT-I9100"
Where do I go from here? Thanks for your time.
Try flashing stock again.
And how would I go about doing that?
I've just redone Odin with XW_NEE_KI4, am I supposed to then boot into the clockwork mod recovery option to install a ROM?
If so, I've downloaded the VillainROM-3.0.0-signed rom, copied it to my SD card, but it isn't showing up.
And I've tried with a different rom only to be told that the file integerity or something along those lines has failed, leaving back at the boot/lock screen.
Can someone tell me how I can get my SD card to show up? Or of a way I can connect my phone to my PC so I can copy the VillainROM-3.0.0-signed onto the phones memory so I can install it via that way?
Thanks, it's rather urgent I get the phone sorted.
arghsarge said:
I installed Cyanogen mod, didn't like it so wanted to go back to the stock, as it was "out-of-the-box"
<snip>
Where do I go from here? Thanks for your time.
Click to expand...
Click to collapse
Just restore your nandroid backup that you made when following the instructions to install CyanogenMod.
Found a little work-around, but if you go into the settings and mount the USB, but don't click mount, your phone will show up as a memory card allowing you to copy any required files.
However, when I copied over the VillainROM-3.0.0-signed to install it and run it I now get the following error.
"E:signature verification failed. Installation aborted."
Any solutions please?
oinkylicious said:
Just restore your nandroid backup that you made when following the instructions to install CyanogenMod.
Click to expand...
Click to collapse
When I try that (and I'm not too sure I created a backup) it says "couldn't open directory, no files found"
Currently downloading GT-I9100_NEE_I9100XWKI4_I9100XXKI2_I9100XXKI1_I9100XWKI4.zip to see if this'll work.
Going through the options, I went to "Fix permissions" I then tried installing the GT-I9100_NEE_I9100XWKI4_I9100XXKI2_I9100XXKI1_I9100XWKI4.zip I downloaded, however it gave me errors.
So I tried the vanilla rom, and it's now installing *something* and it's now said "install from SD card complete."
So, after a few minutes at the dreaded boot/lock screen, I've now got a boot screen for "villiainrom" and it's gone no further.
Good news everyone!
It's now booted and all is well thus far.
gratz! u manage to tame the monster!
arghsarge said:
I installed Cyanogen mod, didn't like it so wanted to go back to the stock, as it was "out-of-the-box"
Loaded up odin (latest) put phone into download mode, loaded I9100XWKF3_Kernel kernel, all went well.
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/005> Added!!
Now phone is stuck at the start screen
"Samsung Galaxy S II GT-I9100"
Where do I go from here? Thanks for your time.
Click to expand...
Click to collapse
Looks like the Problem was, that you were only flashing the stock kernel onto your CM7
so in the end, you had a CM7 rom with a samsung kernel (wich obviously doesen't work)
kaukassus said:
Looks like the Problem was, that you were only flashing the stock kernel onto your CM7
so in the end, you had a CM7 rom with a samsung kernel (wich obviously doesen't work)
Click to expand...
Click to collapse
Exactly!
You must flash FULL firmware (with PDA
Code:
, Phone [modem] and CSC), not only kernel... Next time RTFM first. ;) Cheers!
Thanks in advance for the help!
Can you get to Download Mode?
yes
Can you get into Recovery? If so, custom (version>) or stock?
yes. I just flashed twp on it. I can change this if needed.
What version of the software / firmware WERE you on?
I was on 4.4.2 OTA stock from tmobile but I did root it and had it rooted and running fine for 6+ months without issue.
What did you do to cause it to soft brick?
I have been getting prompted for an OTA update for a while and kept putting it off for fear of knox and the unknown behavior of me having it rooted. I then let my wife use my phone and she clicked approve for the update. The phone then, according to her, rebooted and never booted back up. I originally thought it was a knox issue but after trying a few different recovery methods found online that seemed straight forward (flash custom recovery, install new rom, or install Samsung approved stock rom, delete cache, etc), all my errors seem to be directed to the PIT according to google searches I have done. at this point I can acknowledge I am out of my depth and have no idea where to go next.
Model: SGH-M919
Model name: GALAXY S4
Country: USA (T-Mobile)
PDA: M919UVUFNH7
What versions of the software / firmware have you tried?
4.2.2, 4.4.2, 4.4.4 all from Samsung site.
Why were you trying different PIT files??
because the current error is "secure check fail: PIT" and the google walk throughs suggested trying new PIT files.
What errors are you having?
from which location? odin or the device?
from the device:
secure check fail: PIT
from odin:
big red FAIL in the first box. message output is below.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
toosweetnitemare said:
Thanks in advance for the help!
Can you get to Download Mode?
yes
Can you get into Recovery? If so, custom (version>) or stock?
yes. I just flashed twp on it. I can change this if needed.
What version of the software / firmware WERE you on?
I was on 4.4.2 OTA stock from tmobile but I did root it and had it rooted and running fine for 6+ months without issue.
What did you do to cause it to soft brick?
I have been getting prompted for an OTA update for a while and kept putting it off for fear of knox and the unknown behavior of me having it rooted. I then let my wife use my phone and she clicked approve for the update. The phone then, according to her, rebooted and never booted back up. I originally thought it was a knox issue but after trying a few different recovery methods found online that seemed straight forward (flash custom recovery, install new rom, or install Samsung approved stock rom, delete cache, etc), all my errors seem to be directed to the PIT according to google searches I have done. at this point I can acknowledge I am out of my depth and have no idea where to go next.
Model: SGH-M919
Model name: GALAXY S4
Country: USA (T-Mobile)
PDA: M919UVUFNH7
What versions of the software / firmware have you tried?
4.2.2, 4.4.2, 4.4.4 all from Samsung site.
Why were you trying different PIT files??
because the current error is "secure check fail: PIT" and the google walk throughs suggested trying new PIT files.
What errors are you having?
from which location? odin or the device?
from the device:
secure check fail: PIT
from odin:
big red FAIL in the first box. message output is below.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This typically would be an easy fix, but if 4.4.4 official doesn't straighten it out, it could be a big pain, most likely owing to the fact that you tried to run 4.2.2 on a phone that has had the official 4.4.2 version installed and/or the fact that you were messing with Pits for some reason. Downgrading newer Samsungs, especially since 4.3, is typically not recommended and in most instances is a really bad idea.
es0tericcha0s said:
This typically would be an easy fix, but if 4.4.4 official doesn't straighten it out, it could be a big pain, most likely owing to the fact that you tried to run 4.2.2 on a phone that has had the official 4.4.2 version installed and/or the fact that you were messing with Pits for some reason. Downgrading newer Samsungs, especially since 4.3, is typically not recommended and in most instances is a really bad idea.
Click to expand...
Click to collapse
Thank you for the information. That explains a lot.
Any suggestions to move forward? Thanks!
toosweetnitemare said:
Thank you for the information. That explains a lot.
Any suggestions to move forward? Thanks!
Click to expand...
Click to collapse
Have you tried 4.4.4 yet? If so, and it didn't work, please explain in detail what the error was or where it failed.
es0tericcha0s said:
Have you tried 4.4.4 yet? If so, and it didn't work, please explain in detail what the error was or where it failed.
Click to expand...
Click to collapse
yes I just tried M919UVUFNH7_M919TMBFNH7_TMB. Attached is a screenshot of odin. below is the output from odin.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
when turning on the phone without booting into recovery or download mode, I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I have tried recovery mode in Kies and it does not detect my device.
the little text in the upper left hand corner of the screen says:
odin mode
product name: sgh-m919
current binary: samsung official
system status: custom
knox kernel lock: 0x0
knox warrenty void: 0x1
cso-config-lsb:0x30
write protection enabled:
emmc burst mode enabled
Click to expand...
Click to collapse
entering download mode I get the same little text in the upper left corner of the screen as when just booting the device. The message in the middle of the screen has changed to "Downloading... Do not turn off target!!"
when I try to push the img for 4.4.4 while in download mode, I get the output from odin that I pasted above and the text in the upper left hand corner of the screen has been appended to state:
odin mode
product name: sgh-m919
current binary: samsung official
system status: custom
knox kernel lock: 0x0
knox warrenty void: 0x1
cso-config-lsb:0x30
write protection enabled:
emmc burst mode enabled
start [224, 1448]
bar [240, 1440]
Click to expand...
Click to collapse
and the blue loading bar has stopped moving.
please let me know if there is anything else I can give you for information. Thank you for looking into this with me.
It's odd that it fails after trying to do the recovery. I'd see if maybe I could find the stock recovery and just flash that and then attempt the full Odin restore afterwards. But I wanna say it's because of messing around with the Pit.
I think at this point, your options are:
Find a debrick img for your current firmware (or find someone with a rooted Tmo S4 on the same update and you can make one from it, and follow the basic guide here:
http://forum.xda-developers.com/showthread.php?t=2369125
while substituting the correct files for your phone.
OR, you'll need a JTAG service.
That's what I was afraid of. Thanks for the info.
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
toosweetnitemare said:
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
Click to expand...
Click to collapse
Interesting find. Can't imagine why that would be the trick. Every time I've ever used Odin (on many dozens of Samsungs), it's always been recommended to check that for a full update. Thanks for sharing in case I, or another member has the same thing happen.
Wait, .tar or like the system.img?
toosweetnitemare said:
Figured it out!
I flashed a 4.4.2 IMG via Odin and unchecked "f.reset time".
I kid you not, that let the img be written. *sigh*
Click to expand...
Click to collapse
Can you post the .IMG here please? im running through same issue.
es0tericcha0s said:
It's odd that it fails after trying to do the recovery. I'd see if maybe I could find the stock recovery and just flash that and then attempt the full Odin restore afterwards. But I wanna say it's because of messing around with the Pit.
I think at this point, your options are:
Find a debrick img for your current firmware (or find someone with a rooted Tmo S4 on the same update and you can make one from it, and follow the basic guide here:
http://forum.xda-developers.com/showthread.php?t=2369125
while substituting the correct files for your phone.
OR, you'll need a JTAG service.
Click to expand...
Click to collapse
Just for info. the Model: SGH-M919 will not boot from the SD card, Even if you have the correct debrick.img that was made from the same device.
Good days to everyone!
I've got a situation with my GT-N7100. It doesn't seem to get past the first logo during boot-up, ever.
I've tried the newest MD5 version for that model. "N7100UBUEND1_N7100TCEEND1_N7100UBUEND1_HOME.tar.m d5"
Used the PIT file to Re-Partition and several versions of Odin.
With the PIT file, only version V3.07 hangs at, "Get PIT for mapping..", all other versions seem to fail.
Pit File used: Q1_20110914_16GB.pit
Without the file I get: (Using the tar.md5 packet with V3.07 Odin)
<ID:0/004> Firmware update start..
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
Odin V3.09
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
The phone will not go into recovery mode, the only thing I can get it to do is enter download mode.
How this started? Holding the phone, looking at it. It reset itself and never came back.
I disabled my Anti-Virus... Not sure what else to try. Thank you very much in advance!
***UPDATE*** (I was able to enter recovery mode but it seems to fail to mount anything.)
***UPDATE*** (At wits end, not sure what else to try. I'm thinking the NAND has become corrupt and or unrecoverable. Or unless there was a way to, similar to PC's, do a chkdsk repair. At this time i'm downloading the toolkit and attempt anything through ADB, I feel there is nothing more I could do to Un-Brick the phone. I read about Soft/hard Brick, the phone seems to be Soft Bricked but nothing is allowing me to repair/recover through any download method. Booting into recovery fails to mount everything [as seen in pics].)
Darkie0000 said:
Good days to everyone!
I've got a situation with my GT-N7100. It doesn't seem to get past the first logo during boot-up, ever.
I've tried the newest MD5 version for that model. "N7100UBUEND1_N7100TCEEND1_N7100UBUEND1_HOME.tar.m d5"
Used the PIT file to Re-Partition and several versions of Odin.
With the PIT file, only version V3.07 hangs at, "Get PIT for mapping..", all other versions seem to fail.
Pit File used: Q1_20110914_16GB.pit
Without the file I get: (Using the tar.md5 packet with V3.07 Odin)
<ID:0/004> Firmware update start..
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
Odin V3.09
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
The phone will not go into recovery mode, the only thing I can get it to do is enter download mode.
How this started? Holding the phone, looking at it. It reset itself and never came back.
I disabled my Anti-Virus... Not sure what else to try. Thank you very much in advance!
***UPDATE*** (I was able to enter recovery mode but it seems to fail to mount anything.)
***UPDATE*** (At wits end, not sure what else to try. I'm thinking the NAND has become corrupt and or unrecoverable. Or unless there was a way to, similar to PC's, do a chkdsk repair. At this time i'm downloading the toolkit and attempt anything through ADB, I feel there is nothing more I could do to Un-Brick the phone. I read about Soft/hard Brick, the phone seems to be Soft Bricked but nothing is allowing me to repair/recover through any download method. Booting into recovery fails to mount everything [as seen in pics].)
Click to expand...
Click to collapse
I'd try to install a custom recovery and use that to install new software to see if you can get booted. If the custom recovery can't mount anything, then that might tell us more about what's going on.
es0tericcha0s said:
I'd try to install a custom recovery and use that to install new software to see if you can get booted. If the custom recovery can't mount anything, then that might tell us more about what's going on.
Click to expand...
Click to collapse
Thanks for your response! I am not sure where to find a custom recovery or how I would apply that to the phone. Debugging isnt enabled and I cannot enable it as its stuck in boot. Over half of the features wont work in ADB mode, due to debugging not enabled.
Darkie0000 said:
Thanks for your response! I am not sure where to find a custom recovery or how I would apply that to the phone. Debugging isnt enabled and I cannot enable it as its stuck in boot. Over half of the features wont work in ADB mode, due to debugging not enabled.
Click to expand...
Click to collapse
Just have to get to Download Mode and use Odin to install the custom recovery. Has nothing to do with USB Debugging.
http://forum.xda-developers.com/showpost.php?p=55198275&postcount=2
es0tericcha0s said:
Just have to get to Download Mode and use Odin to install the custom recovery. Has nothing to do with USB Debugging.
http://forum.xda-developers.com/showpost.php?p=55198275&postcount=2
Click to expand...
Click to collapse
I'm still not exactly sure where to get this custom ROM you mention.
I tried another recovery, Note2-CWM-6.0.4.3-GT-N7100. It goes about %75 rather quickly and fails.
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Darkie0000 said:
I'm still not exactly sure where to get this custom ROM you mention.
I tried another recovery, Note2-CWM-6.0.4.3-GT-N7100. It goes about %75 rather quickly and fails.
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Sounds like you might have messed it up from flashing that older Pit file, which might have been Gingerbread or early ICS, being that it's from 2011...
You realize that there is a whole sub forum here devoted to your phone, right? It seems like you haven't tried to do much research here.
Keep in mind I am new to this stuff.
So I am trying to root my phone, Samsung Galaxy J7 (Model SM-J700T, Android 6.0.1), but I cannot get to the TWRP recovery screen despite ODIN saying "Pass". Instead of bringing me to the TWRP it bring me to the Samsung logo with "recovery is not seandroid enforcing" in the top left hand corner, and then brings me back to my home screen.
Here is my log of Odin.
<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 PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Any help asap is very useful
Bump
Bump x2. I really do need help with this.
Bump x3
What img did you use?
Same issue here. Just picked up new Galaxy J7 2016 model SM-J700T and ODIN latest TWRP but no recovery access and same Red RECOVERY IS NOT SEANDROID ENFORCING on boot screen. Most likely there is a change and the TWRP work for all J700 variants except the "T" model until revised I would guess. So, guessing were all stuck till someone catches up and provides a newer TWRP or solution.
Anyone know where to find an extracted stock recovery for the "T" variant to ODIN back for now?
Yeah I just got mine today came home booted windows and followed the post in the thread that showed how to do it and I get the same error. <sigh> guess I should have read more but defiantly need to find the stock recovery or a way to make twrp work....
Created Stock Recovery to Put Back For Now
Since we were all messed up applying TWRP Recovery. Here is the ODIN flashable stock recovery Android 6.0.1. Just created and flashed it back to my T-Mobile SM-J700T and it says Official once again instead of Custom. For those interested in putting your phone back to normal for now. Test booted into Recovery as well.
STOCK T-Mobile Recovery: https://drive.google.com/file/d/0BxGWUugQJLVkNzNvWnFGYTU5VHM/view?usp=sharing
feelx77 said:
Since we were all messed up applying TWRP Recovery. Here is the ODIN flashable stock recovery Android 6.0.1. Just created and flashed it back to my T-Mobile SM-J700T and it says Official once again instead of Custom. For those interested in putting your phone back to normal for now. Test booted into Recovery as well.
STOCK T-Mobile Recovery: https://drive.google.com/file/d/0BxGWUugQJLVkNzNvWnFGYTU5VHM/view?usp=sharing
Click to expand...
Click to collapse
Thanks! Hope it works! (
I am new to all this..
ItsJustRoy said:
Thanks! Hope it works! (
Click to expand...
Click to collapse
I am rooted and like you all, I have no recovery just a red message
"recovery is not seandroid enforcing" I have had no luck with any recovery flash attempts and I also do not have super user but I did when I very first flashed the correct file for root?
I tried to Odin flash the file you have shared as stock recovery image but I am not sure if I am using correct Odin version...
I tried to flash in a newer Odin under AP and when that didnt work I tried Odin v1.85 and selected PDA. Neither of these worked for me.
Please advise on which Odin version to use and then which location to select? Thank you much!!
There has been no real focus on custom development for this phone. I have searched forever and this is the first phone I've bought that Developers are not really focusing on. I also have an s6 Edge+. Because it cost me $800 after taxes. I guess that's worthy!
I have problem too!
[/CODE]
ItsJustRoy said:
Keep in mind I am new to this stuff.
So I am trying to root my phone, Samsung Galaxy J7 (Model SM-J700T, Android 6.0.1), but I cannot get to the TWRP recovery screen despite ODIN saying "Pass". Instead of bringing me to the TWRP it bring me to the Samsung logo with "recovery is not seandroid enforcing" in the top left hand corner, and then brings me back to my home screen.
Here is my log of Odin.
<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 PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Any help asap is very useful
Click to expand...
Click to collapse
Damn me too and need to root for unlock my phone UFFF any help for this model for now ¿?
Thank !!!
Seems I have the same (or similar) issue. Install TWRP with Odin and it always passes install. Then when I try to enter TWRP recovery mode the factory recovery always comes up!
Tried w/ auto-reboot on and off.
Tried, after install, to turn off phone with vol-dwn/home/power THEN immediately (on screen blanking) switch to vol-up/home/power
Tried w/ auto-reboot on.
Tried w/ reboot off to just remove the battery then replace the battery and go into recovery, etc.
Every combination that I can think of, or have read about, all no good. Nothing I do gets me into TWRP recovery, always recovery is the factory Android recovery.
Any ideas, folks?
Thanks!
Specs:
Galaxy j7 (SM-J700T)
Exynos Octa 7580
Android 7.1.1
Bootloader J700TUVU3BQK3
Build: NMF26X.J700TUVU3BQK3
Root access: No
Odin3_v3.13.1
Tried with several TWRP TARs:
twrp-3.2.1-0-j7xelte.img
J700T N-7.1.1 TWRP-Unofficial
twrp_3.0.3-1_sm-j700t_23217
Very simple and hard for me at the same time
Flashed twrp on my galaxy s6edge 925f and that was the only thing i did so far, after 1st reboot it started up, but on second time i tryed to restart phone and wiped system (think ) becouse it ways i dont have os installed, it stuck at samsung logo, smartswtich neither kies recognizes my phone (yes drivers are installed) have downloaded stock firmware and tryed to flash it via odin, but..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed
ok with odin 3.12 i have this error
<ID:0/003> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can please anyone help me out?
managed somehow make it to work, cloes please
if you have samsung kies also installed on your comp it wont work....
I have this problem , can you explain how you fixed it?
aryaazimi72 said:
I have this problem , can you explain how you fixed it?
Click to expand...
Click to collapse
If you have sboot.bin fail this happens when you try to downgrade. Just flash stock firmware through odin. Use odin v3.10.6. Of it sticks on Samsung logo it's normal can take up to 20 minutes for first boot
callumbr1 said:
If you have sboot.bin fail this happens when you try to downgrade. Just flash stock firmware through odin. Use odin v3.10.6. Of it sticks on Samsung logo it's normal can take up to 20 minutes for first boot
Click to expand...
Click to collapse
I dont think i am downgrading... im flashing a bl from a new rom but i had an old rom before this...
I have these errors :
aryaazimi72 said:
I dont think i am downgrading... im flashing a bl from a new rom but i had an old rom before this...
I have these errors :
Click to expand...
Click to collapse
Which rom are you on? And which BL are you flashing?
callumbr1 said:
Which rom are you on? And which BL are you flashing?
Click to expand...
Click to collapse
i tried crisscross and xtrestolite...
now im downloading omega.. maybe that workes...
aryaazimi72 said:
i tried crisscross and xtrestolite...
now im downloading omega.. maybe that workes...
Click to expand...
Click to collapse
Crisscross development has stopped. I recommend CarHD rom it is the best by far.
Make sure your flashing the roms through twrp