I have followed the instructions for rooting using ODIN309 and 'samsung tab 8\Odin309\CF-Auto-Root-kona3g-kona3gxx-gtn5100.tar.md5' with no sucesss
<OSM> Please wait..
<OSM> CF-Auto-Root-kona3g-kona3gxx-gtn5100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
the product name on the boot screen is GT-5118. Do I need to wait for the proper .md5 file to be available?
Bought from Amazon, still returnable.
Thanks in advance.
c_# said:
I have followed the instructions for rooting using ODIN309 and 'samsung tab 8\Odin309\CF-Auto-Root-kona3g-kona3gxx-gtn5100.tar.md5' with no sucesss
<OSM> Please wait..
<OSM> CF-Auto-Root-kona3g-kona3gxx-gtn5100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
the product name on the boot screen is GT-5118. Do I need to wait for the proper .md5 file to be available?
Bought from Amazon, still returnable.
Thanks in advance.
Click to expand...
Click to collapse
it will be not returnable if you flash something
it will void your warrenty
Are you certain that this is an actual Samsung device? There are some pretty convincing knock-offs out there. GT-5118 isn't a normal Tab 8.0 model number.
I followed the instructions in his thread, I wonder if Samsung came out with a new OS update to prevent his root.
c_# said:
I followed the instructions in his thread, I wonder if Samsung came out with a new OS update to prevent his root.
Click to expand...
Click to collapse
Why don't you post the info in Settings / About Device so we can tell if it's an option. It worries me that you are following guides without knowing what model you have. That's an inherently dangerous game to play.
sorry for the delay....
es0tericcha0s said:
Why don't you post the info in Settings / About Device so we can tell if it's an option. It worries me that you are following guides without knowing what model you have. That's an inherently dangerous game to play.
Click to expand...
Click to collapse
I have two pics for you to look at...
I posted the odd number (product name on the boot screen is GT-5118). I don't know if this help the possibilities or not.
Again thanks to all for your help
es0tericcha0s said:
Why don't you post the info in Settings / About Device so we can tell if it's an option. It worries me that you are following guides without knowing what model you have. That's an inherently dangerous game to play.
Click to expand...
Click to collapse
settting about device gt-n5110
and ver 4.2.2
kernel version 3.01-1475545
[email protected] # 1
Mon Sep 16 19:33:55kst 2013
build num - jdq39.n5110ouefmi1
Looks like you used the wrong file then. Yours should be the wifi only model and you were trying to use the one that has cellular data.
http://download.chainfire.eu/318/CF-Root/CF-Auto-Root/CF-Auto-Root-konawifi-konawifixx-gtn5110.zip
Related
http://forum.xda-developers.com/showthread.php?t=1083187
Please advise guys on how to install Madmack's ROM? Detailed steps...
I did the following but it didn't work:
1) Connect the USB cable to my GSII
2) Put the phone in Download Mode (It says Downloading - Don't turn off target or something alike)
3) Run Odin
3) Check PDA and browse to madmack-1.5-JPKF1.tar.md5 file
4) Clicked Start
5) I got this log:
<ID:0/010> Added!!
<ID:0/010> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> madmack-1.5-JPKF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Thanks guys..
Ayhamov said:
http://forum.xda-developers.com/showthread.php?t=1083187
1) Connect the USB cable to my GSII
NOT in the instructions
2) Put the phone in Download Mode (It says Downloading - Don't turn off target or something alike)
Yes but also says to click Vol Up to accept .
3) Run Odin
Yes
3) Check PDA does not say check PDA
and browse to madmack-1.5-JPKF1.tar.md5 file
4) Clicked Start
No
Connect USB cable
Then start .
jje
Click to expand...
Click to collapse
In Point 2: Shall I wait the device to finish "Downloading" ??
Ayhamov said:
In Point 2: Shall I wait the device to finish "Downloading" ??
Click to expand...
Click to collapse
No its not downloading read the instructions on the downloading screen.
jje
[ROM][STOCK] Samsung Galaxy S 4.2 WIFI YP-GI1CW ->CODE GI1XXLF1
With the full firmware available, I rooted it simply unpacking factoryfs.img using sgs2toext4 and ext4_utils, injecting SU binary + SuperSU and after repack it, I made a tarball and flashed it throught Odin 3.04.
After that I've installed from GPlay the busybox installer.
Rooted factoryfs.img
Flash using Odin 3.04.
Important: This is only for YP-GI1CW version on XXLF1 !
This is working very good for me, but use at your own risk.
Thanks to zebluk and alice90, who were able to get the first root on this device.
Ozelot64 said:
[ROM][STOCK] Samsung Galaxy S 4.2 WIFI YP-GI1CW ->CODE GI1XXLF1
With the full firmware available, I rooted it simply unpacking factoryfs.img using sgs2toext4 and ext4_utils, injecting SU binary + SuperSU and after repack it, I made a tarball and flashed it throught Odin 3.04.
After that I've installed from GPlay the busybox installer.
Flash using Odin 3.04.
Important: This is only for YP-GI1CW version on XXLF1 !
This is working very good for me, but use at your own risk.
Thanks to zebluk and alice90, who were able to get the first root on this device.
Click to expand...
Click to collapse
Odin says MD5 hash value is invalid
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
MD5 hash value is invalid
CODE_GI1XXLF1_factoryfs_Rooted.md5 is invalid.
End...
edit: works aufter add .tar to the filename
ChaosChris said:
Odin says MD5 hash value is invalid
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CODE_GI1XXLF1_factoryfs_Rooted.md5 is invalid.
<OSM> End...
edit: works aufter add .tar to the filename
Click to expand...
Click to collapse
I don't know why there is this change in the filename, my original is CODE_GI1XXLF1_factoryfs_Rooted.tar.md5.....anyway, I'm reuploading the rar with the correct file inside.
Sorry for the inconvenience
ChaosChris said:
Odin says MD5 hash value is invalid
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CODE_GI1XXLF1_factoryfs_Rooted.md5 is invalid.
<OSM> End...
edit: works aufter add .tar to the filename
Click to expand...
Click to collapse
Ozelot64 said:
I don't know why there is this change in the filename, my original is CODE_GI1XXLF1_factoryfs_Rooted.tar.md5.....anyway, I'm reuploading the rar with the correct file inside.
Sorry for the inconvenience
Click to expand...
Click to collapse
Done, link updated in OP
@ChaosChris: could you please delete the old links in "quote" of your post ? Thx
AW: [ROM][STOCK+ ROOT] Samsung Galaxy S 4.2 WIFI YP-GI1CW rooted factoryfs.img GI1XX
Ozelot64 said:
Done, link updated in OP
@ChaosChris: could you please delete the old links in "quote" of your post ? Thx
Click to expand...
Click to collapse
Yes no Problem
Gesendet von meinem Nexus S mit Tapatalk 2
Hey Ozelot64, your link ti the rooted factory.fs is down.
404: Page not found – the page http://goo.gl/AC4 does not exist.
If you typed in or copied/pasted this URL, make sure you included all the characters, with no extra punctuation.
Click to expand...
Click to collapse
Hey there guys.... Please read this first so I don't get flamed for taking a OTA update on a non rooted phone.
Heres the skinny.... My buddy gave me his old Galaxy S4 (Verizon I545). When I got it from him, it had KIt Kat on it. His phone was not hooked up with Verizon, since he just got a S5 and switched to AT&T. So I popped in my Tmobile sim card and away I went I had NO problems what so ever for three days. I wake up, and BAM it's Lollipop.
NOW, when it's on 4G, I can't send sms messages (but I can recieve them). I CAN send however send and recieve MMS messages. Internet, and phone work perfect. I have tried everything (wipe cached partition, reboot, clear data for messaging app, etc...), no luck
MY GOAL: Being that I live on a rural area (about 20 minute drive to get cell service), I have been using my wifi calling on my Tmobile phone (prior to taking the S4). My master plan was to root and flash a rom (like insane Kit kat) that would enable the wifi calling..... BUT it went to Lollipop before I could do so.
Now I cant send SMS, NOR can I flash it either.... OR could I??? Any help would be appreciated guys (and girls)..
NOTE: I have tried KingoRoot, and Towelroot... none supported my phone...
Thanks for your input in advance
fricci4993 said:
Hey there guys.... Please read this first so I don't get flamed for taking a OTA update on a non rooted phone.
Heres the skinny.... My buddy gave me his old Galaxy S4 (Verizon I545). When I got it from him, it had KIt Kat on it. His phone was not hooked up with Verizon, since he just got a S5 and switched to AT&T. So I popped in my Tmobile sim card and away I went I had NO problems what so ever for three days. I wake up, and BAM it's Lollipop.
NOW, when it's on 4G, I can't send sms messages (but I can recieve them). I CAN send however send and recieve MMS messages. Internet, and phone work perfect. I have tried everything (wipe cached partition, reboot, clear data for messaging app, etc...), no luck
MY GOAL: Being that I live on a rural area (about 20 minute drive to get cell service), I have been using my wifi calling on my Tmobile phone (prior to taking the S4). My master plan was to root and flash a rom (like insane Kit kat) that would enable the wifi calling..... BUT it went to Lollipop before I could do so.
Now I cant send SMS, NOR can I flash it either.... OR could I??? Any help would be appreciated guys (and girls)..
NOTE: I have tried KingoRoot, and Towelroot... none supported my phone...
Thanks for your input in advance
Click to expand...
Click to collapse
Never heard of something like this before... I'd think that there is no way back...
i have the same problem. if there is a rollback to kitkat
If the build number ends with OC1, then there is no going back. If it ends with something else... Possibly hope
XxD34THxX said:
If the build number ends with OC1, then there is no going back. If it ends with something else... Possibly hope
Click to expand...
Click to collapse
Can we do something to fix the sms issue?
eliah1 said:
Can we do something to fix the sms issue?
Click to expand...
Click to collapse
Yes 100%.
http://forum.xda-developers.com/gal...w-lollipop-t3099930/post60868269#post60868269
We are on stock rom and can t root the OC1.
Sent from my SAMSUNG-SM-G900AZ using XDA Free mobile app
XxD34THxX said:
Yes 100%.
http://forum.xda-developers.com/gal...w-lollipop-t3099930/post60868269#post60868269
Click to expand...
Click to collapse
That's awesome.... being a noob and you a senior member, I have a noob question, if we have a non rooted OC1, how can we get into the rom to do it? I thought we couldn't root it yet?
OC1 does not have root or ROM availability. Nothing can me nodded on OC1.
Repair your Device to Match T-Mobile!!
So, this is a Bit risky.....!!!!!!!
The reason is Because the device is trying to Connect to a Verizon APN. If you factory restore the Device to the T-Mobile Variant, It will Work Flawlessly!
BACKUP ALL YOUR DATA!!! This will WIPE EVERYTHING!!!!
These files are intended to be used with ODIN ONLY!! If at any time ODIN FAILS, pull battery, re-insert battery, go back to "ODIN Mode" and try again.
Here are the Two files you will need to Repair the Device to Be a T-Mobile Device!
These packages are Direct from Samsung and includes the PIT for partitioning!!
ODIN v.3.10:
https://drive.google.com/file/d/0B4RU_ZH5QUASSWhaMmdiaFJ1Tm8/view?usp=sharing
SGH-M919 Service Files:
https://drive.google.com/file/d/0B4RU_ZH5QUASbk5TMU9rdGtwTlU/view?usp=sharing
Extract the Two (2) Downloaded Zips
Right-Click on the "ODIN v.3.10.exe" and "Run as Administrator" on your Windows PC.
Click on each of the 4 buttons below and browse to find matching file in extracted image folder:
BL = BL_****.tar.md5
AP = AP_****.tar.md5
CP = CP-MODEM-****.tar.md5
CSC = CSC-****.tar.md5
Check the following boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Put 100% charged device into ODIN Mode, and connect to PC USB with Original Cable.
Check there two boxes in ODIN:
Phone Bootloader Update
Clear EFS Partition
Hit the "Start" button
Once the Device reboots, Wait Ten minutes for Programming to occur.
Perform Two [2] FDR (Factory Data Reset), Just bskip thru the Wizard.
Phone is back to complete stock!!
Just to confirm, and not to doubt you (KaosMaster), have you done this, and can you point me to people who have? I know there is risk involved with any of this, but even a small problem can seem like a huge problem to a cell phone noob like me lol... Honestly, I have a lot of experience logging, and reflashing the ecm computer on my Mistsubishi Evo... Although its not a cell phone, it's the same premise in theory. :laugh: :laugh:
@KaosMaster
Also just to be clear, this will work with a NON rooted phone, that CANT be rooted at this time??
This is the STOCK Method! NO ROOT
fricci4993 said:
@KaosMaster
Also just to be clear, this will work with a NON rooted phone, that CANT be rooted at this time??
Click to expand...
Click to collapse
this will Completely reprogram your device to T-Mobile, yes it has been done before by others if you wanna Google Search!!
Worst case is that ODIN Fails To flash and we have to reload the Verizon Software!
You can reach me on Hangouts if you need any Personal help, being a NOOB!! XD
KaosMaster said:
Click on each of the 4 buttons below and browse to find matching file in extracted image folder:
BL = BL_****.tar.md5
AP = AP_****.tar.md5
CP = CP-MODEM-****.tar.md5
CSC = CSC-****.tar.md5
Check the following boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Put 100% charged device into ODIN Mode, and connect to PC USB with Original Cable.
Check there two boxes in ODIN:
Phone Bootloader Update
Clear EFS Partition
Hit the "Start" button
Once the Device reboots, Wait Ten minutes for Programming to occur.
Perform Two [2] FDR (Factory Data Reset), Just bskip thru the Wizard.
Phone is back to complete stock!!
Click to expand...
Click to collapse
Every file I try to open with ODIN i'm getting a md5Error! Binary is invalid
here is the message box within ODIN
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BL_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> AP_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CP_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CSC-TMB_M919TMBFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BL_M919UVUFNK2_2437203_REV06_user_low_ship.tar.md5 is invalid.
<OSM> End...
OPPS!! Sorry!! ;/
Please rename the file, and just delete the ".md5" portion, and the files should work! I will re-upload shortly!!
KaosMaster said:
Please rename the file, and just delete the ".md5" portion, and the files should work! I will re-upload shortly!!
Click to expand...
Click to collapse
Removed those md5 file extensions but now heres the next issue i have
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on the ODIN MODE (on phone screen) shows this:
ODIN MODE
PRODUCT NAME : SCH-I545
CURRENT BIANARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: Off
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMAC BURST MODE: Enabled
START (224,1440)
ERASING USERDATA PARTITION
SECURE CHECK FAIL : PIT
So I clicked on the PIT button within the ODIN v3.10 and selected the PIT_JFLTE_USA_TMO.pit file andthis was the result
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dragon1018 said:
Removed those md5 file extensions but now heres the next issue i have
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on the ODIN MODE (on phone screen) shows this:
ODIN MODE
PRODUCT NAME : SCH-I545
CURRENT BIANARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: Off
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMAC BURST MODE: Enabled
START (224,1440)
ERASING USERDATA PARTITION
SECURE CHECK FAIL : PIT
So I clicked on the PIT button within the ODIN v3.10 and selected the PIT_JFLTE_USA_TMO.pit file andthis was the result
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I had the same error on my veriso I5454
Ok. Try no repartition, and skip the pit file
KaosMaster said:
Ok. Try no repartition, and skip the pit file
Click to expand...
Click to collapse
Same thing
Ok. I need to find the lollipop version for tmobile. Give me a few
Hi to all!!
My name is lucas, I rooted my S9+ smg9650 with @klabit87 posts and info (TWRP installed). Everything perfect, root working. Today i Wanted to upgrade my ROM from android 8.0 to 10. had problems with data partition but got them repaird with TWRP, but muy problem was that ODIN did not flash the new ROM, it stayed frozen "SetupConnection.." or "initialization.. " and then FAIL, USB debugging and OEM unlock were set. Finally I got tierd and decided that i wanted to set everything to stock, so i made a full buckup, and i dont know why, i flashed a recovery image from a andoid 10 rom, using TWRP app, when rebooted, stays at bootloop, i can use download mode, but cant flash TWRP back with odin, nor any other firmwere. Cant turn phone off, Cant get to recovery mode.
Left cornet message on bootloop., (Same massage on download screen)
RPMB fuse blown
RPMB provisoned
Current binary: custom
System status: custom
FRP lock off
oem lock: off
warranty void: 0x1 (0x30c)
qualcomm secreboot: Enable
RP SWREV : B3 (2,2,2,3,2) K3 S3
SECURE DOWNLOAD : ENABLE
DID: 20208B33D8317411
Any ideas, i beel reading every post i could find online, but cant get to solve this.
any idea could help.
Thanks!!
Canita2000 said:
Hi to all!!
My name is lucas, I rooted my S9+ smg9650 with @klabit87 posts and info (TWRP installed). Everything perfect, root working. Today i Wanted to upgrade my ROM from android 8.0 to 10. had problems with data partition but got them repaird with TWRP, but muy problem was that ODIN did not flash the new ROM, it stayed frozen "SetupConnection.." or "initialization.. " and then FAIL, USB debugging and OEM unlock were set. Finally I got tierd and decided that i wanted to set everything to stock, so i made a full buckup, and i dont know why, i flashed a recovery image from a andoid 10 rom, using TWRP app, when rebooted, stays at bootloop, i can use download mode, but cant flash TWRP back with odin, nor any other firmwere. Cant turn phone off, Cant get to recovery mode.
Left cornet message on bootloop., (Same massage on download screen)
RPMB fuse blown
RPMB provisoned
Current binary: custom
System status: custom
FRP lock off
oem lock: off
warranty void: 0x1 (0x30c)
qualcomm secreboot: Enable
RP SWREV : B3 (2,2,2,3,2) K3 S3
SECURE DOWNLOAD : ENABLE
DID: 20208B33D8317411
Any ideas, i beel reading every post i could find online, but cant get to solve this.
any idea could help.
Thanks!!
Click to expand...
Click to collapse
You'll need to start over with first using Odin to flash an Android 10 firmware package. Note that there is no going back once you do this.
Then follow the posts in the twrp thread to reach a rooted stock Android 10 setup.
If you're having issues with Odin connecting, you'll need to double check your drivers, cables, ports, or possibly even a different PC.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
You'll need to start over with first using Odin to flash an Android 10 firmware package. Note that there is no going back once you do this.
Then follow the posts in the twrp thread to reach a rooted stock Android 10 setup.
If you're having issues with Odin connecting, you'll need to double check your drivers, cables, ports, or possibly even a different PC.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Hi,
Thnx for your reply!! my problem is that i cant flash anything with odin:
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 35 M
<ID:0/009> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 35 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
Tried 3 diffrent ROMS, and tried flashing only TWRP again but cant. i dont know if my bootloader locked and cant run de CROM service, since i cant run android.
i never got to Android 10 working, i am downloading 2 more stock roms (andoid 8) to see if odin flashes them, I tried reseting download moda and start odin as fast as i could (i read that this fixed odin issue somtimes) but with no good result on my side, tried like 30 times, all the USB on my pc, and 2 difrent cables.
Canita2000 said:
Hi,
Thnx for your reply!! my problem is that i cant flash anything with odin:
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 35 M
<ID:0/009> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 35 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
Tried 3 diffrent ROMS, and tried flashing only TWRP again but cant. i dont know if my bootloader locked and cant run de CROM service, since i cant run android.
i never got to Android 10 working, i am downloading 2 more stock roms (andoid 8) to see if odin flashes them, I tried reseting download moda and start odin as fast as i could (i read that this fixed odin issue somtimes) but with no good result on my side, tried like 30 times, all the USB on my pc, and 2 difrent cables.
Click to expand...
Click to collapse
When Odin says it failed, what did your device show? It should show an error or something. I think it would be in red lettering.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
When Odin says it failed, what did your device show? It should show an error or something. I think it would be in red lettering.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Have tried a new Rom, Android 8 (G9650ZCU3ARH4) https://stockfirmware.info/sm-g9650-firmware-samsung-s9-plus-g9650zcu3arh4/
Same error.
<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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 6066 M
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Nothing changed on the download screen, stayed the same the whole process.
Canita2000 said:
Have tried a new Rom, Android 8 (G9650ZCU3ARH4) https://stockfirmware.info/sm-g9650-firmware-samsung-s9-plus-g9650zcu3arh4/
Same error.
<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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 6066 M
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Nothing changed on the download screen, stayed the same the whole process.
Click to expand...
Click to collapse
That firmware is extremely old. You probably should at least try with one of the first versions that are Android 10. Also, if you don't have the Samsung Dex desktop app, install that as well. It should help resolve some driver issues if that is causing problems.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
That firmware is extremely old. You probably should at least try with one of the first versions that are Android 10. Also, if you don't have the Samsung Dex desktop app, install that as well. It should help resolve some driver issues if that is causing problems.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I have the following andoid 10 Roms:
G9650ZHU6DTA7 - debloted - https://forum.xda-developers.com/galaxy-s9-plus/how-to/snapdragon-s9-sm-g9650-android-10-t4048625
G9650ZHS6DTB4 - https://sfirmware.com/downloads-file/135138/SM-G9650_2_20200229043228_tal4inqtnt_fac
In both having the same problem as shown previously, have delted and reinstalled Samsung drivers (Samsung_USB_Driver_v1.7.23.0) and restart PC.
Also downloades Dex, does not recognize any device. Odin still not working.
Canita2000 said:
I have the following andoid 10 Roms:
G9650ZHU6DTA7 - debloted - https://forum.xda-developers.com/galaxy-s9-plus/how-to/snapdragon-s9-sm-g9650-android-10-t4048625
G9650ZHS6DTB4 - https://sfirmware.com/downloads-file/135138/SM-G9650_2_20200229043228_tal4inqtnt_fac
In both having the same problem as shown previously, have delted and reinstalled Samsung drivers (Samsung_USB_Driver_v1.7.23.0) and restart PC.
Also downloades Dex, does not recognize any device. Odin still not working.
Click to expand...
Click to collapse
Man I don't know to be honest. I just upgraded from February patch 10 to April patch myself. Didn't have any issues. You can't go back to Oreo though. You're only able to use Android 10 now due to rollback protection.
If you can, I would try a different computer or even possibly a virtual machine with Windows 10 or windows 7 on it.
Sent from my Pixel 2 XL using Tapatalk
Canita2000 said:
I have the following andoid 10 Roms:
G9650ZHU6DTA7 - debloted - https://forum.xda-developers.com/galaxy-s9-plus/how-to/snapdragon-s9-sm-g9650-android-10-t4048625
G9650ZHS6DTB4 - https://sfirmware.com/downloads-file/135138/SM-G9650_2_20200229043228_tal4inqtnt_fac
In both having the same problem as shown previously, have delted and reinstalled Samsung drivers (Samsung_USB_Driver_v1.7.23.0) and restart PC.
Also downloades Dex, does not recognize any device. Odin still not working.
Click to expand...
Click to collapse
I've been on this issue for a few weeks now trying to see if I can fix it. As of right now I have the same issue. So we'll see. Most say use a hub or another PC and it works. So does on mine. So yea I could. But screw that where's the fun. Let me do some more tests. Because I've tried everything from driver enforcement to bios settings. Drivers and more. And still no go. I can also add upon reboot I get a last USB connected was not recognized. And have to reboot download mode. So I do believe the pc is trying to talk to the device just not fully opening the com\serial port
TheMadScientist said:
I've been on this issue for a few weeks now trying to see if I can fix it. As of right now I have the same issue. So we'll see. Most say use a hub or another PC and it works. So does on mine. So yea I could. But screw that where's the fun. Let me do some more tests. Because I've tried everything from driver enforcement to bios settings. Drivers and more. And still no go. I can also add upon reboot I get a last USB connected was not recognized. And have to reboot download mode. So I do believe the pc is trying to talk to the device just not fully opening the com\serial port
Click to expand...
Click to collapse
I am trying to get fastboot runing, but nothing, only bootloop or download mode, tried reintalling drivers, difrent roms, reseting download mode, canceling download mode.
nothing working so far.
i suspect that USB debbuging locked itself and does not let me flash with odin
Canita2000 said:
I am trying to get fastboot runing, but nothing, only bootloop or download mode, tried reintalling drivers, difrent roms, reseting download mode, canceling download mode.
nothing working so far.
i suspect that USB debbuging locked itself and does not let me flash with odin
Click to expand...
Click to collapse
fastboot isn't available for Samsung devices and USB debugging wont lock you out of going to download mode or recovery.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
fastboot isn't available for Samsung devices and USB debugging wont lock you out of going to download mode or recovery.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Beat me to it
TheMadScientist said:
Beat me to it
Click to expand...
Click to collapse
Thanks, so i wount try anymore with fastboot or ADB,
i will try on a MAC pc i have and Jodin 3. will come back with any news.
on the other hand, afer installing all dirvers i could find online, my device manager shows the phone as "samsung mobile cdc composite device" and shows as working properly. Odin recognizes the phone, but still can flash anything.
Canita2000 said:
Thanks, so i wount try anymore with fastboot or ADB,
i will try on a MAC pc i have and Jodin 3. will come back with any news.
on the other hand, afer installing all dirvers i could find online, my device manager shows the phone as "samsung mobile cdc composite device" and shows as working properly. Odin recognizes the phone, but still can flash anything.
Click to expand...
Click to collapse
Yea it will eventually fail and show that it could not open the com or serial port same here. It's most definitely a windows issue. If we can get known users to chime in when there device is connected in download mode to show me what their devices show in device manager.
Mine shows as Samsung composite USB. And a Samsung modem as well. I've been messing with the modem shown. If you disable that or mess with it while in download mode it won't show added or detected. So I'm thinking it's in that modem driver and not the composite
TheMadScientist said:
Yea it will eventually fail and show that it could not open the com or serial port same here. It's most definitely a windows issue. If we can get known users to chime in when there device is connected in download mode to show me what their devices show in device manager.
Mine shows as Samsung composite USB. And a Samsung modem as well. I've been messing with the modem shown. If you disable that or mess with it while in download mode it won't show added or detected. So I'm thinking it's in that modem driver and not the composite
Click to expand...
Click to collapse
MAC not working, Heimdall could not get my PIT file, and tried using the one inside de CSC and same result, PIT corrupted.
So back to my PC and trying to get the drivers to work.
How should i see my device on device manager? Samsung s9650? Andoid phone? Samsng modem?
klabit87 said:
Man I don't know to be honest. I just upgraded from February patch 10 to April patch myself. Didn't have any issues. You can't go back to Oreo though. You're only able to use Android 10 now due to rollback protection.
If you can, I would try a different computer or even possibly a virtual machine with Windows 10 or windows 7 on it.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Downloaded a device analizer called Temple 1.17.
Shows:
{
"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"
}
Any ideas? is there a way to edit driver to think its reading a 9650?
Edit:
Also tried a new windows 8 partition, with absolitly nothing, justo samsung drivers and odin, same problem, and detects de phone the same way.
sorry if i have spelling mistakes, english is not my native language
I'm trying to flash an S7+ (T970), and after Googling for hours I'm still entirely clueless about what's going wrong here. Odin recognizes my tablet with an indicator in the upper left, but every flashing operation fails with a log like this:
<ID:0/004> 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/004> Odin engine v(ID:3.1401)..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried a manually-compiled build of Heimdall on both Windows and Linux, and that also successfully detects the device but then consistently fails on any operation with "ERROR: libusb error -7 whilst sending bulk transfer".
The tablet is in download mode, and I reboot it in between each attempt just in case that has any effect on things. I've tried at least a dozen USB cables and every USB port I have available across several computers, so it's safe to say that if it's still a cable/port issue then this is a lost cause. I've also tried different versions of libusb on each host system with no change in results. No matter what I do, I can't seem to get any flashing tool to interact with this tablet beyond recognizing that it's connected in download mode.
My goal is to flash an AP ROM that I created with Magisk. I've done this process with Magisk on several other devices, so I know what I'm doing pretty well in general, and I'm pretty confident that the file was created correctly. I'm just completely stumped by the flashing tools for Samsung devices!
It seems like other people have had success using Odin with this device, so I feel like there must be something I'm missing. Is there any way to get Odin to output more information about what it's failing on?
more importantly what does device say when odin fails?