PLEASE HELP I just flashed boot_CWM_I747MVLUEMK5.zip to update my bootloader and now phone has no service. Please help! I used to be on i747Mdlv4 or somthing like that
EDIT: I my phones does not have a IEMI number, but i have a back up of the EFS.tar. Can i flash the EFS.tar with TWRP?
I tried to flash a rooted version of 4.1.2 and i get this
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_RWC_I747MVLDLK4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Did you flash an updated modem to go with the bootloader?
audit13 said:
Did you flash an updated modem to go with the bootloader?
Click to expand...
Click to collapse
I fixed it. I am on 4.3 rooted with the updated bootloader.
It was 2 hours of hell but its all good
xXFl4sh said:
I fixed it. I am on 4.3 rooted with the updated bootloader.
It was 2 hours of hell but its all good
Click to expand...
Click to collapse
Glad to hear you got it sorted:good:
audit13 said:
Glad to hear you got it sorted:good:
Click to expand...
Click to collapse
Hey one quick question, can i flash d2lte on d2can?
xXFl4sh said:
Hey one quick question, can i flash d2lte on d2can?
Click to expand...
Click to collapse
Most ROMs will work unless the ROM specifically requires an i747 bootloader. You can determine which bootloaders are supported by the ROM by extracting and examing the assert lines in the updater script.
audit13 said:
Most ROMs will work unless the ROM specifically requires an i747 bootloader. You can determine which bootloaders are supported by the ROM by extracting and examing the assert lines in the updater script.
Click to expand...
Click to collapse
On this thread http://forum.xda-developers.com/showthread.php?t=2630316 on the second post it says,
"Q - Can I flash this on my (d2att,d2spr,d2tmo,d2cri,d2mtr,d2usc,d2vzw)?
A - Yep"
So I tried to flash but it failed. I have no idea what to do.
EDIT: I tired it again and it failed because my phone is d2can
xXFl4sh said:
On this thread http://forum.xda-developers.com/showthread.php?t=2630316 on the second post it says,
"Q - Can I flash this on my (d2att,d2spr,d2tmo,d2cri,d2mtr,d2usc,d2vzw)?
A - Yep"
So I tried to flash but it failed. I have no idea what to do.
EDIT: I tired it again and it failed because my phone is d2can
Click to expand...
Click to collapse
What recovery are you using? I had issues with TWRP so I switched to Philz Touch.
What error are you getting? Are you flashing this from a stock ROM? Are you wiping cache, Dalvik, and data before flashing?
audit13 said:
What recovery are you using? I had issues with TWRP so I switched to Philz Touch.
What error are you getting? Are you flashing this from a stock ROM? Are you wiping cache, Dalvik, and data before flashing?
Click to expand...
Click to collapse
TWRP 2.7.0.0
The error I am getting is a build prop error (the rom is d2can compatible) . Yes I am flashing from a stock rooted rom. Yes I have wipe, dalvik and cache before flashing.
You can try changing the assert lunge to d2can from d2att.
what do you mean asset lunge? I have tried changing it from build prop.
EDIT: how can i change my d2can recovery to d2att?
xXFl4sh said:
what do you mean asset lunge? I have tried changing it from build prop.
EDIT: how can i change my d2can recovery to d2att?
Click to expand...
Click to collapse
Sorry, my phone changed the word "line" to lunge".
You can unzip the ROM (I use 7-zip) and remove the assert line from the updater script file or remove the assert line.
I recommend flashing your phone with the tar version of Philz Touch rather than TWRP. Philz is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
audit13 said:
Sorry, my phone changed the word "line" to lunge".
You can unzip the ROM (I use 7-zip) and remove the assert line from the updater script file or remove the assert line.
I recommend flashing your phone with the tar version of Philz Touch rather than TWRP. Philz is here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Click to expand...
Click to collapse
Sorry to post late but I fixed the problem
xXFl4sh said:
Got it working. Here's how I fixed it.
I changed the build prop to d2att and then I used goo manager to download the d2att img.
Click to expand...
Click to collapse
Glad you got it to work. Have you tried the Validus ROM, I use it on a Nexus 4 and Motorola Atrix HD and I really like it. It's fast, stable, and the dark UI is really nice.
Related
Hey fellow sgh-m919v owners in Canada!
Need some help here!
I am trying to Flash my eastlink wireless sigh-m919v back to stock and uproot it but it keeps failing in different times depending on the Rom I'm flashing.
On the older firmware I downloaded from sammobile.com it almost finishes then gets to modem.bin and says fail(auth) with a big red fail sign. On the phone it says secure check fail:mdm
When I try the newest one it doesn't even want to start. Odin starts then fails right away stating. Fail at sbl2.Mbn and Secure check fail: sbl2 on the phone.
Note when I go into download mode it does state that my phone is a sghm919v, current binary custom, system status custom, csb-oem_config_lbs:0x38 or 0x30. Too small to tell.
Note. I'm able to install custom roms and recoveries fine but not stock roms.
What am I doing wrong? Can someone give me step by step instructions? I'm using a Partially installed stock Rom and want it to be fully installed.
Any help is appreciated
Are you sure you are using the correct Rom...???
There is always the possibility the OS (operating system) you are attempting to install is not the correct one, and thus producing a conflict, and also a negative out come.
Can you post your Model, Make and Carrier, possibly the weblink where you are getting you update from.
Just to get a second opinion, and rule out that you are indeed getting the right download. As each Carrier is hardware sensitive, as to the type of Android OS it supports...
Well im not 100% sure im using the right one but 98% sure I am using the right one.
My phones downlosd mode says its a sgh-m919v. Canadian model of t mobile m919
I got the roms from sammobile.com
I used the firmware ending in esk thinking that meant eastlink but yesterday I doenloaded the wind, mobilicity and videotron versions of samr ftimware to see if yheres any differrnce.
Have yet to try. Will try soon
mikeogden198181 said:
Well im not 100% sure im using the right one but 98% sure I am using the right one.
My phones downlosd mode says its a sgh-m919v. Canadian model of t mobile m919
I got the roms from sammobile.com
I used the firmware ending in esk thinking that meant eastlink but yesterday I doenloaded the wind, mobilicity and videotron versions of samr ftimware to see if yheres any differrnce.
Have yet to try. Will try soon
Click to expand...
Click to collapse
Try to see if you can get your product code
http://forum.xda-developers.com/wik..._Galaxy_S_Series#How_To_Find_Product_Codes.3F
baseballfanz said:
Try to see if you can get your product code
http://forum.xda-developers.com/wik..._Galaxy_S_Series#How_To_Find_Product_Codes.3F
Click to expand...
Click to collapse
download mode states that my product code is a sgh-m919v
just tried flashing the other m919v firmwares from wind, mobilicity and videotron, no luck - fails at modem.bin. whats going on why does it keep failing. very frustrated
this is where it always fails:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919VVLUAMDJ_M919VYVLAMDJ_M919VVLUAMDJ_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
bump! any help would be greatly appreciated guys!
Same issue
mikeogden198181 said:
bump! any help would be greatly appreciated guys!
Click to expand...
Click to collapse
I have the same issue... any resolution?... Need some help here... is our bootloader locked?
ryanmillet said:
I have the same issue... any resolution?... Need some help here... is our bootloader locked?
Click to expand...
Click to collapse
It might be all possible that you just have a simple hardware issue.
Instead of trying the latest, can you humor the conversation by trying the first update on the SamMobile site...!!!
Anything but the last or latest, try to roll back as far as you can...!!!
modem.bin is the radio file. does your phone boot into android and work fine after failing at modem.bin or it does not boot.
You can also try different version of Odin say 3.04 or a different usb port or both.
edit
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.
munchy_cool said:
modem.bin is the radio file. does your phone boot into android and work fine after failing at modem.bin or it does not boot.
You can also try different version of Odin say 3.04 or a different usb port or both.
edit
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.
Click to expand...
Click to collapse
Nice reply, munchy_cool...!!!
Sent from my SGH-M919 using XDA Premium 4 mobile app
Getting somewhere...
grassy-sneakers said:
It might be all possible that you just have a simple hardware issue.
Instead of trying the latest, can you humor the conversation by trying the first update on the SamMobile site...!!!
Anything but the last or latest, try to roll back as far as you can...!!!
Click to expand...
Click to collapse
OK... so Odin flashing just doesn't work...
the latest based firmware MG1 stops almost instantly with an Sb2 error....
the oldest based firmware MDJ stops at modem install "secure check fail mdm"
I am however able to flash any custom recovery and from there install anything I want via CWM
Now... I was interested in flashing an alternative modem on my M919V (as my research leads me to understand that LTE is disabled on my device) I really wanted to just flash the M919 Modem...
so I searched and searched for a way to flash the modem to another one... all of reading said not to do it... it's too risky, ect.... BUT... some said it can be done and claimed success.... so I gave it a try...
Odin flash of ANY modem gives an error... same "secure check fail mdm" No CWM modem flash exists... I did find some other devices that had CWM modems to flash but flashing them gave a Baseband "unknown" IMEI "unknown"... so that was super scary... until I repacked the CWM modem zip with my device modem and I was back in business....
Long story short... you can't flash anything Via Odin in this phone really except a recovery... everything else pretty much fails which leads me to think either it was something to do with the partition scheme or the bootloader... I'm unsure as I really am not a developer just a daring competent xda rom addict...
IF you are on M919V and wish to flash modems (granted you will want to only flash a modem specific to M919V) examples would be the MG1 or MDJ... I have found a method that works everytime... you will need to have root via CF-ROOT or a custom rom which has root (that you flashed via CMW after to odin flashed a recovery)
here is the link to the instructions...
http://www.alliance-rom.com/communi...-non-hlos-bin-temporary-flashing-method.8676/
I hope this will shed some more light on our device... I really just wish I could convert my device fully to a M919 as this device (M919V) seems to have some weird issues... OR... better yet... a 9505G :highfive:
---------- Post added at 10:07 PM ---------- Previous post was at 10:02 PM ----------
munchy_cool said:
modem.bin is the radio file. does your phone boot into android and work fine after failing at modem.bin or it does not boot.
You can also try different version of Odin say 3.04 or a different usb port or both.
edit
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.
Click to expand...
Click to collapse
Tried with 3.04 (instead of 3.09) here is my log - on the device it says "secure check fail: mdm"
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
munchy_cool said:
could also be that the firmware file is not fully downloaded.can you check the md5 on the file to be same as that from sammobile.
Click to expand...
Click to collapse
I still want to see if it is not a software issue by trying or playing around with OFFICIAL firmware, before I assume it is just faulty hardware refusing to corporate with your attempts to restore your Canadian Phone.
Again, munchy_cool, Thank you...!!!
Also have you called Samsung, and explained to them and I quote "That your phone failed during an OS update, and you tried to roll back using a download file from SamMobile, and even then you have experienced no success...!!!", just to see if they have on record of the same issues...???
--Just a though..., as I would hate to keep beating around the bush.
---------- Post added at 09:10 PM ---------- Previous post was at 09:04 PM ----------
Also I notice you have multiple choices to download, what one do you say is your version.
-SamMobile-
SGH-M919V - Canadian Firmware
ryanmillet said:
Tried with 3.04 (instead of 3.09) here is my log - on the device it says "secure check fail: mdm"
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
means the modem is invalid for this phone, as mentioned a few posts above there are multiple firmwares for your s4 , you need to know which carrier your s4 is ..there might be checks in the firmware to stop it from being flashed onto another carriers phone even if model number is same.
munchy_cool said:
there might be checks in the firmware to stop it from being flashed onto another carriers phone even if model number is same.
Click to expand...
Click to collapse
Thus the concern of a hardware conflict/issue with being successful in your flash using Odin.
Android devices are not all the same, they change depending on what country you are in especially if you are using a STOCK ROM. Every country has a different setup requirement when it comes to establishing a valid connection, so thus the hardware/software conflict.
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 12:21 PM ---------- Previous post was at 12:12 PM ----------
grassy-sneakers said:
Thus the concern of a hardware conflict/issue with being successful in your flash using Odin.
Android devices are not all the same, they change depending on what country you are in especially if you are using a STOCK ROM. Every country has a different setup requirement when it comes to establishing a valid connection, so thus the hardware/software conflict.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Besides that I cannot tell which is yours (meaning Firmware - SamMobile) your post suggest EastLink...??? Is this East Canada...? In East Canada what Carriers to they provide you...?, and what Model# is your phone...?
Maybe we can help to narrow down your Firmware you need...???
If you can also provide your OS - BASEBAND version, under Settings - More - About - Baseband Version.
You should be able to get this from a Custom Rom as well...!
Sent from my SGH-M919 using XDA Premium 4 mobile app
grassy-sneakers said:
If you can also provide your OS - BASEBAND version, under Settings - More - About - Baseband Version.
You should be able to get this from a Custom Rom as well...!
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My baseband has been flashed as I described in my earlier post... M919VVLUAMDJ.... My Carrier is unknown as I bought this phone unlocked for cheap on kijiji... but the guy said he worked for samsung and it was a spare... (Eastlink was the intended carrier...) although this model has 4 carriers it could potentially be... Eastlink, Wind mobile, ect.... The Op has the EXACT same model number and the EXACT same issue as me... he also has tried flashing literally EVERY firmware available on Sammobile website...
ryanmillet said:
My baseband has been flashed as I described in my earlier post... M919VVLUAMDJ.... My Carrier is unknown
Click to expand...
Click to collapse
(Eastlink was the intended carrier...) although this model has 4 carriers it could potentially be... Eastlink, Wind mobile, ect....
Click to expand...
Click to collapse
The Op has the EXACT same model number and the EXACT same issue as me... he also has tried flashing literally EVERY firmware available on Sammobile website...
Click to expand...
Click to collapse
I have confirmed that M919VVLUAMDJ, is the correct firmware for Canadian model phones, still at a miss, is this is a hardware description, given it is specifically found, i.e. provided visually in the OS.
and you say you have tried EVERY firmware...???
Have you read this yet...???
RUN OTHER CARRIER ROMs on AT&T/TMO/Canadian S4 devices
grassy-sneakers said:
I have confirmed that M919VVLUAMDJ, is the correct firmware for Canadian model phones, still at a miss, is this is a hardware description, given it is specifically found, i.e. provided visually in the OS.
and you say you have tried EVERY firmware...???
Have you read this yet...???
RUN OTHER CARRIER ROMs on AT&T/TMO/Canadian S4 devices
Click to expand...
Click to collapse
I'm downloading all the other firmware for my phone to see what one matches.... I'll let you know the results
Hello Please if possible be very Noob friendly with your instructions, thanks
Ok I have a rooted Samsung Galaxy S3 AT&T on Firmware 4.3
So I noticed the 4.4.2 Update came out and i really want to update to it but I couldn't OTA because it would say update failed later discovered this is because my S3 is rooted
Now I am in the middle of trying to unroot my galaxy s3 and am very confused i tried doing backup and reset obviously that didnt work i am very confused on how this Odin software works so if you someone could give me very noob specific directions it would be greatly appreciated!
Thanks in Advance
Just open the SuperSU app and select Full Unroot. Let it do its thing and you're unrooted.
Or follow enewman17's thread for how to update.
I believe unrooting will only be successful if none of the AT&T apps were removed from the device. I forgot about that point and I had to flash the 4.3 stock image in order to successfully install the OTA update to 4.4.2. The OTA will try to patch all that ATT bloat during installation; if its not there it will fail.
DocHoliday77 said:
Just open the SuperSU app and select Full Unroot. Let it do its thing and you're unrooted.
Or follow enewman17's thread for how to update.
Click to expand...
Click to collapse
Yah i already did that but it would still fail the update at 24%
mwrobe1 said:
I believe unrooting will only be successful if none of the AT&T apps were removed from the device. I forgot about that point and I had to flash the 4.3 stock image in order to successfully install the OTA update to 4.4.2. The OTA will try to patch all that ATT bloat during installation; if its not there it will fail.
Click to expand...
Click to collapse
Could you please give me a download link or something to the 4.3 stock image for odin?
Everytime i download one it always some weird files that i do not know how to utilize through odin
So if you could give me a stock 4.3 that would be great thanks
nkhaira said:
Could you please give me a download link or something to the 4.3 stock image for odin?
Everytime i download one it always some weird files that i do not know how to utilize through odin
So if you could give me a stock 4.3 that would be great thanks
Click to expand...
Click to collapse
I used this method in post #1 to go back to stock 4.3: http://forum.xda-developers.com/showthread.php?t=2565972
Contrary to other posts...I only had Auto Reboot checked and that worked for me.
This will also wipe all data from your device...make sure you backup pics/vids/contacts/etc. before you do this.
After you take the OTA update, I can also confirm that TowelRoot will successfully root the ATT GS3 running KitKat. Although the documentation says no reboot is required...I needed a reboot after rooting with towelroot.
mwrobe1 said:
I used this method in post #1 to go back to stock 4.3: http://forum.xda-developers.com/showthread.php?t=2565972
Contrary to other posts...I only had Auto Reboot checked and that worked for me.
This will also wipe all data from your device...make sure you backup pics/vids/contacts/etc. before you do this.
After you take the OTA update, I can also confirm that TowelRoot will successfully root the ATT GS3 running KitKat. Although the documentation says no reboot is required...I needed a reboot after rooting with towelroot.
Click to expand...
Click to collapse
But isnt that for the Sprint Galaxy s3
I have the SGH-i747 AT&T LTE USA Version?
nkhaira said:
But isnt that for the Sprint Galaxy s3
I have the SGH-i747 AT&T LTE USA Version?
Click to expand...
Click to collapse
My sincerest apologies. Correct. I used that link for you because the instructions were clear and concise. The firmware download should be good from here: http://stockroms.net/file/GalaxyS3/SGH-I747/StockROMS.net-SGH-I747_ATT_1_20120522193451.zip
mwrobe1 said:
My sincerest apologies. Correct. I used that link for you because the instructions were clear and concise. The firmware download should be good from here: http://stockroms.net/file/GalaxyS3/SGH-I747/StockROMS.net-SGH-I747_ATT_1_20120522193451.zip
Click to expand...
Click to collapse
Just to make sure this is the file i put in odin so i can go back to stock 4.3 update (non rooted) and update OTA to 4.4.2 right?
nkhaira said:
Just to make sure this is the file i put in odin so i can go back to stock 4.3 update (non rooted) and update OTA to 4.4.2 right?
Click to expand...
Click to collapse
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)
mwrobe1 said:
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)
Click to expand...
Click to collapse
Thank you for being responsive and helpful
I have started the file download i have slow internet speed at my house but it should download in 30 minutes and in a hour i will update this thread if it worked thanks!
mwrobe1 said:
Correct...make sure you put your phone in download mode as well (Hold down Volume Down, Center Home, and Power buttons together for about 10 seconds...When your screen turns off, let go of the Power button but keep holding down Volume Down and Center Home buttons....When you see the warning screen, hit Volume Up button...Connect a microUSB cable from your phone to computer...Run Odin...click on “PDA”, then choose the file you downloaded...click on Start once Odin "loads" the file...wait 10-15 minutes for the flash too occur...after coming back from a reboot you should be on stock 4.3)
Click to expand...
Click to collapse
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
That is the error message i am getting.. when i am trying this
nkhaira said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
That is the error message i am getting.. when i am trying this
Click to expand...
Click to collapse
I'll try to locate the exact MD5 I used and give you a link later today/this week. Sorry for the trouble.
mwrobe1 said:
I'll try to locate the exact MD5 I used and give you a link later today/this week. Sorry for the trouble.
Click to expand...
Click to collapse
Ok As soon as possible would be appreciated currently this is my only phone and i need to use it and I factory reset it yesterday thinking it would get rid of the root i would like to install all my apps and everything as soon as possible thanks
Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.
DocHoliday77 said:
Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.
Click to expand...
Click to collapse
Thanks for your reply So since this in too many different files what do i do to combine them (noob)? i know its something to the extent of extracting them into one folder?
Could you give me instructions on that
DocHoliday77 said:
Your Odin flash failed because you tried to flash a much older firmware. LEM. You need to flash the 4.3 firmware. You can use this thread. http://forum.xda-developers.com/showthread.php?t=2722660
Enewman17 has one too I think. Not sure where exactly right now though.
Click to expand...
Click to collapse
Ok i got all the files combined now i see a csc a AP file and alot of the file catergories from Odin do i only need the AP file for PDA or do i need to insert each corresponding file into each corresponding category in Odin?
I don't have this device so its apparently a little different than I'm used to in this regard. Check post 13 of that thread to see if that helps. Otherwise someone more familiar with that particular process will need to chime in.
DocHoliday77 said:
I don't have this device so its apparently a little different than I'm used to in this regard. Check post 13 of that thread to see if that helps. Otherwise someone more familiar with that particular process will need to chime in.
Click to expand...
Click to collapse
Thank You So much!!
Sorry for late reply but the download you sent me worked and after 10 minutes i was on stock 4.3 upgraded to 4.4.2 without any problems!!!
THANKS!!!
Hi guys, i just purchased the at&t samsung galaxy tab s and got it unlocked. I'm loving it so far, however one thing annoy me is att get rid of the stock phone call and messaging feature. So i wonder if the international lte rom has that option, so i can make phone call and text?
BADBOY1412 said:
Hi guys, i just purchased the at&t samsung galaxy tab s and got it unlocked. I'm loving it so far, however one thing annoy me is att get rid of the stock phone call and messaging feature. So i wonder if the international lte rom has that option, so i can make phone call and text?
Click to expand...
Click to collapse
if you have the 10.5 LTE, I have uploaded latest stock T805 firmware here:
http://forum.xda-developers.com/showthread.php?t=2902557
just flash using ODIN.
Tapatalked from my GALAXY S5
[email protected] said:
if you have the 10.5 LTE, I have uploaded latest stock T805 firmware here:
http://forum.xda-developers.com/showthread.php?t=2902557
just flash using ODIN.
Tapatalked from my GALAXY S5
Click to expand...
Click to collapse
Thanks, will it be compatible with my tablet? I dont want to brick it, also do i need root before flashing the rom?
BADBOY1412 said:
Thanks, will it be compatible with my tablet? I dont want to brick it, also do i need root before flashing the rom?
Click to expand...
Click to collapse
what tablet do you have? no you don't need root.
here is a guide that you can use
http://androidxda.com/flash-samsung-stock-rom-using-odin
ODIN: https://www.google.se/url?sa=t&rct=...=RK0ekg44IHkrmWq59-3jkg&bvm=bv.77648437,d.bGQ
[email protected] said:
what tablet do you have? no you don't need root.
here is a guide that you can use
I have the AT&t version of the galaxy tab s 4gLTE, modelSM- T807A.So i can just flash the T805 rom on top of my existing rom?
Click to expand...
Click to collapse
BADBOY1412 said:
[email protected] said:
what tablet do you have? no you don't need root.
here is a guide that you can use
I have the AT&t version of the galaxy tab s 4gLTE, modelSM- T807A.So i can just flash the T805 rom on top of my existing rom?
Click to expand...
Click to collapse
well it should work, same Exynos 5420 SoC, so just flash it
turn off your tablet, put it on download mode by holding down the home button + volume down and power until you see download mode.
Click to expand...
Click to collapse
[email protected] said:
BADBOY1412 said:
well it should work, same Exynos 5420 SoC, so just flash it
turn off your tablet, put it on download mode by holding down the home button + volume down and power until you see download mode.
Click to expand...
Click to collapse
i tried to flash it with oDin but it failed,i think it has something to do with the MD5,it fail. The status is Leave CS after check MD5,and then fail when i clicked start
Click to expand...
Click to collapse
BADBOY1412 said:
[email protected] said:
i tried to flash it with oDin but it failed,i think it has something to do with the MD5,it fail. The status is Leave CS after check MD5,and then fail when i clicked start
Click to expand...
Click to collapse
hmm, strange, I used it yesterday and flashed my T805, do you choose PDA in ODIN? also do you get the message that your tablet is added in ODIN?
also your quotes looks ****ed up
you can also try to re-download the file again.
Click to expand...
Click to collapse
so you flash your t805 tablet with the t805 rom? i think it failed bc of the different variant. My tab s is t807a so maybe the MD5 doesnt match. Thanks alot for your effort though
BADBOY1412 said:
so you flash your t805 tablet with the t805 rom? i think it failed bc of the different variant. My tab s is t807a so maybe the MD5 doesnt match. Thanks alot for your effort though
Click to expand...
Click to collapse
yes, but try to download the ROM again and see if it works.
[email protected] said:
yes, but try to download the ROM again and see if it works.
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1ANH1_T805XEF1ANH1_T805XXU1ANF6_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Thats the message i received
hmm, it seems that something is blocking it from flashing, maybe there is something with the T807A that don't allow other stock ROMs to be flashed
I got a tab S SMT 800 of course the first thing I did was to root the tablet with Odin3 I was in a hurry even did not apply the system update. Now when I try I get "The operating system on your device has been modified in an unauthorized way bla bla" How can I apply this OTA without re flashing a stock firmware?
Im not sure if you can. But there is a way to set your system status back to officail with root. Doing this method will allow to update with the ota bit i can nit confirm if the ota update will install properly. First download xposed installer, and install it. Then search for a module in xposed called wanam xposed and download and install and reboot. Then open the wanam xposed app and go tab secuirty hacks and tap fake system status till it saids official. Then now just reboot. Now try the ota update. It may install, it may not. Hope this helps
DUHAsianSKILLZ said:
Im not sure if you can. But there is a way to set your system status back to officail with root. Doing this method will allow to update with the ota bit i can nit confirm if the ota update will install properly. First download xposed installer, and install it. Then search for a module in xposed called wanam xposed and download and install and reboot. Then open the wanam xposed app and go tab secuirty hacks and tap fake system status till it saids official. Then now just reboot. Now try the ota update. It may install, it may not. Hope this helps
Click to expand...
Click to collapse
Thank you. I followed your instructions, but it did not work, It did removed the nasty "The operating system on your device has been modified in an unauthorized way bla bla"after it re download the update but came back with Failed to update software.
I ran into this thread on the S5 http://forum.xda-developers.com/showthread.php?t=2728568&page=2 where people succeed by using the stock tar with odin
but do I do not where to find the stockcar for the tab S SMT 800
guliver6 said:
Thank you. I followed your instructions, but it did not work, It did removed the nasty "The operating system on your device has been modified in an unauthorized way bla bla"after it re download the update but came back with Failed to update software.
I ran into this thread on the S5 http://forum.xda-developers.com/showthread.php?t=2728568&page=2 where people succeed by using the stock tar with odin
but do I do not where to find the stockcar for the tab S SMT 800
Click to expand...
Click to collapse
Did you check the Sammobile website first?
Reckoning said:
Did you check the Sammobile website first?
Click to expand...
Click to collapse
Nothing for USA there the closest is Canada
guliver6 said:
Nothing for USA there the closest is Canada
Click to expand...
Click to collapse
I think usa is XAR or celluar south. Idk
DUHAsianSKILLZ said:
I think usa is XAR or celluar south. Idk
Click to expand...
Click to collapse
I got this \T800XXU1ANK1_T800XAR1ANI1_HOME.tar.md5 but I am getting the RED flag fail in odin
guliver6 said:
I got this \T800XXU1ANK1_T800XAR1ANI1_HOME.tar.md5 but I am getting the RED flag fail in odin
Click to expand...
Click to collapse
What does odin say when falshing it. Like the text box in odin when it flash it.
DUHAsianSKILLZ said:
I think usa is XAR or celluar south. Idk
Click to expand...
Click to collapse
DUHAsianSKILLZ said:
What does odin say when falshing it. Like the text box in odin when it flash it.
Click to expand...
Click to collapse
Here the Odin reply:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T800XXU1ANK1_T800XAR1ANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
guliver6 said:
Here the Odin reply:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T800XXU1ANK1_T800XAR1ANI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
I honestly have no idea whu it does that. People been havent problems with odin. Can your tab still boot? It seems like it didnt even flash. Maybe a bad drivers.
DUHAsianSKILLZ said:
I honestly have no idea whu it does that. People been haven't problems with odin. Can your tab still boot? It seems like it didn't even flash. Maybe a bad drivers.
Click to expand...
Click to collapse
Good news this time everything went smooth did not have to reset factory and the tablet says
"Software update: the latest updates have already been installed", just lost the root but I flashed the auto root again and its is perfect.
Thank you everybody for your help.
guliver6 said:
Good news this time everything went smooth did not have to reset factory and the tablet says
"Software update: the latest updates have already been installed", just lost the root but I flashed the auto root again and its is perfect.
Thank you everybody for your help.
Click to expand...
Click to collapse
So what did you do? Did you flash it again? Or exactly what did you do to fix it? I just wanna know since whenever andriod l is out.. I can flash it correctly.
DUHAsianSKILLZ said:
So what did you do? Did you flash it again? Or exactly what did you do to fix it? I just wanna know since whenever andriod l is out.. I can flash it correctly.
Click to expand...
Click to collapse
Honestly not sure,I turned off the tablet hold the 3 buttons to put int in download mode and the the odin worked its magic just waiting for android 5.0 now
guliver6 said:
Honestly not sure,I turned off the tablet hold the 3 buttons to put int in download mode and the the odin worked its magic just waiting for android 5.0 now
Click to expand...
Click to collapse
Probably out of the topic but since I started this thread I need to give an explanation
If you wander why Guliver6 is currently disabled it is because on XDA
I created a double account by error so on my demand the previous account show disabled, so from now on I will use only guliver365 for subsequent follow up.
guliver6 said:
Honestly not sure,I turned off the tablet hold the 3 buttons to put int in download mode and the the odin worked its magic just waiting for android 5.0 now
Click to expand...
Click to collapse
Probaly needed to reconnect the cable again. Happens all the time with my ipod and ipad.
app
There is a app that will hide your root. it works very well.
Its named hidemyroot and works without reboot. :good:
I got my S3 from my brother since my Nexus 5 is currently broken, and with the S3 he installed CyanogenMod though it doesn't have root. So I decided to try and root it, but probably messed something up and now I'm stuck on the Cyanogen loadup screen, been waiting there for a solid 3 hours, and finally decided to try to fix it. I've tried using Odin3 3.0.7, trying to flash stock rom but I'm currently getting this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Does anyone know what to do at this point? I've tried multiple different stock roms in case one of the stock roms had a problem. However, I flashed TWRP no problem, and I have that working for my recovery. What should I do at this point to get my phone back to Stock ROM?
Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.
The error happens when trying to flash aboot.mbn because, as @DocHoliday77 noted, LK3 cannot be flashed if the phone is running a 4.3 or newer bootloader.
I advise flashing TWRP and a custom ROM. This will allow you to boot the phone and determine the phone's bootloader version.
Flinze said:
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.
Click to expand...
Click to collapse
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes, I am able to access recovery with TWRP working, I just don't know where the terminal emulator is. (sorry i'm not very experienced w/ TWRP)
Also one thing to note, I can't install any sort of ROMS or can't flash anything through TWRM for some reason. When I swipe to flash a rom, what happens is that it just automatically goes back to the TeamWin logo page thing, and then I'm back on the home screen of TWRM (which shows all the buttons like install, wipe, backup, restore, mount, etc.) So I can't flash through TWRM, and if possible can someone link me a custom rom that supports md5, .tar, with those file extensions since the roms I've tried all are zips of .img files. (unless there is a way to convert it to md5, .tar, etc. extentions so that I can use ODIN on my computer to flash it)
edit: what I mean by md5, .tar is a PDA file so that I can use ODIN. if possible I just want my phone to run again w/ any roms... I've been phoneless for a few days now
You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Okay, when I typed the command getprop ro.bootloader what is get is:
I747MVLDLK4
I've tried flashing the stock recovery through TWRP, but it just again doesn't work as I explained in the previous post. So I tried using ODIN to flash it after converting it into a md5 file so that ODIN can read it and now when I try to enter recovery my screen is just black.
Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/
audit13 said:
Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/
Click to expand...
Click to collapse
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!
Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.
Flinze said:
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!
Click to expand...
Click to collapse
Glad to hear you got it going!
audit13 said:
Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.
Click to expand...
Click to collapse
Don't even worry about cred on this stuff man! You do plenty enough to be just as deserving! @dawgdoc too!
And tbh, I'm really glad you chimed in on that one! Since I'm not as familiar with which variant has which build number for the I747/I747M, (and since I'm usually used to just glancing at the last 3 characters), it probably would've taken me another 2 or 3 posts to have realized that was the problem. I Definately didn't catch it that first time!
So in the spirit of giving credit where it's due, you do deserve it here and in many, many other threads! Thanks!
Sent from my SGH-T999 using Tapatalk