Related
I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!
Nobody? =\
Razor1973 said:
I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!
Click to expand...
Click to collapse
First of all, I'd say (from my experience) screw Kies. Go straight to flashing the STOCK ROOTED S3 files. Do NOT load any custom bootloaders or anything. This is step one, using Odin to get back to stock root. Here is a link to a tutorial (in case you need it, it has the files too): Click Here
Now once you finish that, go ahead and use Odin to flash the latest CWM or TWRP (up to your preference, I use TWRP). To get the latest TWRP for Odin, go HERE.
After you have the custom recovery, you should make a Nandroid backup in TWRP. Also, at this step, for the love of your sanity teach your dad how to make a backup. This might save you down the road
Now that you have a backup and are rooted, you can start flashing the roms. Make sure that you do NOT flash any bootloader OR modem unless they are the I747UCDMG2 ones. IF you flash those you will be fine.
Hope this helps!
Well, I had no choice by to use Kies because ODIN would always fail or crash. Only after I flashed using Kies could I use ODIN successfully. So I just flashed using Kies again, which allowed me to ODIN (3.07) the AT&T file in that thread you gave me. However, ODIN fails a few seconds into the flash with the following error. Any other ideas? Thank you for the help.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
By the way, phone won't boot up and ODIN will crash or any other attempt, as you can see in my second screenshot (same condition I was describing in my OP). It looks like it goes past the boot flash, but crashes on cache. So I need to flash via Kies again. It's been the only way I can start all this over.
In case it makes a difference, before the first ODIN attempt, the download mode read "CURRENT BINARY: SAMSUNG" and after it failed, download mode read "CURRENT BINARY: CUSTOM".
Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
xSharpi said:
Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Click to expand...
Click to collapse
These are flashabe through recovery, not ODIN. Both bootloader and ROM files are ZIP's and ODIN expects TAR, MD5, SMD, GZ or TGZ in the PDA section.
As I had mentioned, I cannot flash anything through a custom recovery (and I've tried several, including TWRP and CWM) because the recovery complains that the ROM is for a d2att and my device isn't. My device *is* a d2att, only that CM nightly flashed something to it that makes it identify itself as something different, it sounds like.
I really am stuck. So far, the only ROM I have been able to flash is stock 4.1.2 using Kies and nothing after that.
Any other ideas please???
Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
xXshur1kenXx said:
Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Click to expand...
Click to collapse
I just used Kies to flash to stock 4.1.2 successfully (which has always been the case) and then the S3 Toolkit 7.5 to root (screenshots). After the last step, the phone doesn't boot up (same thing always happens when I try to root), so I can't install GooManager or ROM Manager. However, I am able to get into stock recovery, so I will try to follow steps RockRatt recommends and report again. Thank you.
RockRatt said:
A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Click to expand...
Click to collapse
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.
Razor1973 said:
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.
Click to expand...
Click to collapse
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
xXshur1kenXx said:
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Click to expand...
Click to collapse
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).
Razor1973 said:
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).
Click to expand...
Click to collapse
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
xXshur1kenXx said:
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Click to expand...
Click to collapse
It's my dad's phone. LOL
RockRatt said:
Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Click to expand...
Click to collapse
What are you apologizing for??? God, no. It was me who bricked the phone, not you!
I'm about to leave the house and go to this really good cellular repair shop very close to me to see if they do JTAG repairs. I was going anyways to take my original Nexus 7 for a screen replacement. I tried to do it and screwed it up too. hahahaha
Razor1973 said:
It's my dad's phone. LOL
Click to expand...
Click to collapse
My mistake. Meant to say if he could haha. Sorry i couldn't help more. Hope the JTAG works!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
You have been very helpful. Guy doesn't do JTAG repairs. I will keep calling shops in town. If none does, I will ship it. Thanks!
For JTAG repair, have you checked this site? You still have to send the phone in, though.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii/
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
huz666 said:
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
Click to expand...
Click to collapse
If you are getting errors in both odin and cwm, it sounds like it is a root issue. In other words, it sounds like the apps are being denied access to root and therefor cannot flash. Both odin and cwm are able to generate logs so you can tell the reason for the fail. Personally, I would recommend flasing twrp recovery instead of cwm since it seems to simplify alot and is a little better for our device. Without knowing exactly why the flash is failing, i would just recommend to try and re-root the phone again.
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Perseus71 said:
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Click to expand...
Click to collapse
Yes the phone was in downloading mode. I couldn't find any posts that thought that I would brick my phone for sure by downgrading so I thought I would try. Could I go back to the 4.3 Stock ROM with some degree of confidence?
Yes you can go back to 4.3 Stock.
Perseus71 said:
Yes you can go back to 4.3 Stock.
Click to expand...
Click to collapse
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
huz666 said:
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
Click to expand...
Click to collapse
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
serio22 said:
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
.
Thanks for the advice. I think I'll just quit while I'm only slightly behind now and remain on 4.3 Stock. I appreciate everyone's help and suggestions.
Downgrade from CM11 4.4.2 to 4.3 on I747
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
You seriously need to do some reading
Sent from my SGH-T999 using Tapatalk
nitagro said:
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
Click to expand...
Click to collapse
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Perseus71 said:
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Click to expand...
Click to collapse
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
nitagro said:
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
Click to expand...
Click to collapse
Please Read through this Thread. For Future Reference, all Odin Files for S3 in general are looked up by unique Keyword Root66. That thread is the right place for you to post errors or issues. If there's no 4.3 image for your phone there, you can post a request as well.
For your immediate Problem, there is a an alternate ATT StockMod Rom by @saranhai Please see this thread. Pay particular attention to the mandatory requirement of flashing a particular modem beforehand.
Downloaded and installed OTA KitKat update on my note, phone was perfectly stock, not rooted. After installation the phone is stuck in a bootloop and displays "BOOTING RECOVERY..." but cannot boot to recovery, just restarts over and over.
Tried reflashing via ODIN the stock 4.4 update with stock recovery. Also tried flashing TWRP, Philz and the phone will never boot into recovery - it never gets past the Galaxy Note 3 logo screen.
It occurred to me that there could have been some problem with the PIT that occurred during the initial flash but I cannot flash any of the SM-N900T .pit files found floating around the forum either! The phone returns the SECURE CHECK FAILED: PIT error. Seems like the PIT may need to be a signed file in 4.4? Anyone have a signed PIT file?
Bring to tmobile show Em it won't boot. New phone in mail 2 days later. Just did it last week
Sent from my SM-N900T using Tapatalk
Unfortunately I'm not in the US and I don't have t mobile so warranty replacement won't be so easy.
brinks said:
Downloaded and installed OTA KitKat update on my note, phone was perfectly stock, not rooted. After installation the phone is stuck in a bootloop and displays "BOOTING RECOVERY..." but cannot boot to recovery, just restarts over and over.
Tried reflashing via ODIN the stock 4.4 update with stock recovery. Also tried flashing TWRP, Philz and the phone will never boot into recovery - it never gets past the Galaxy Note 3 logo screen.
It occurred to me that there could have been some problem with the PIT that occurred during the initial flash but I cannot flash any of the SM-N900T .pit files found floating around the forum either! The phone returns the SECURE CHECK FAILED: PIT error. Seems like the PIT may need to be a signed file in 4.4? Anyone have a signed PIT file?
Click to expand...
Click to collapse
Did you have any luck acquiring a signed PIT file? Any help is appreciated.
Sent from my SM-P600 using XDA Premium 4 mobile app
NJAZ said:
Did you have any luck acquiring a signed PIT file? Any help is appreciated.
Sent from my SM-P600 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
None so far.
I'm not seeing any PIT files that will flash under the 4.4.2 bootloader.
brinks said:
Downloaded and installed OTA KitKat update on my note, phone was perfectly stock, not rooted. After installation the phone is stuck in a bootloop and displays "BOOTING RECOVERY..." but cannot boot to recovery, just restarts over and over.
Tried reflashing via ODIN the stock 4.4 update with stock recovery. Also tried flashing TWRP, Philz and the phone will never boot into recovery - it never gets past the Galaxy Note 3 logo screen.
It occurred to me that there could have been some problem with the PIT that occurred during the initial flash but I cannot flash any of the SM-N900T .pit files found floating around the forum either! The phone returns the SECURE CHECK FAILED: PIT error. Seems like the PIT may need to be a signed file in 4.4? Anyone have a signed PIT file?
Click to expand...
Click to collapse
Did you ever try using Odin 3.7? I for some reason can flash the PDA file but I have a different PIT file which obviously seems not to work... I think I just need the correct PIT file but am unsure where to get it for 4.4.2... This new update has been a nightmare..
coldcrush390 said:
Did you ever try using Odin 3.7? I for some reason can flash the PDA file but I have a different PIT file which obviously seems not to work... I think I just need the correct PIT file but am unsure where to get it for 4.4.2... This new update has been a nightmare..
Click to expand...
Click to collapse
Yeah, I tried odin 3.7, 3.9 and hemidall. Same results, secure check fail: Pit
Update: Looks like there are two versions of the 4.4BL, the latest of which checks for a signed PIT file. It won't work to flash any 4.4 pit from say, a few months ago. Need a PIT fie from someone who updated their phone in the last 2-3 weeks.
*** Nevermind, after a third Odin flash it worked.
Same thing happened to me, stuck on "BOOTING RECOVERY". Any resolution to this?
No solution that I've found. I've tried flashing multiple SM-N900T pit files found on XDA, all return the SECURE CHECK FAIL: PIT error. The phone will not boot into the stock recovery and returns the RECOVERY IS NOT SEANDROID ENFORCING error with custom recoveries. I've tried the latest versions of TWRP, CWM, etc with the same results.
As this update isn't really out in the wild recently I'd say that updating to 4.4 OTA is a pretty big risk at this point.
Hello everyone, I am in need of some help.
I tried to update my l900 mk4 rooted to NE2 yesterday and it failed and left me in a situation.
My bootloader got updated to NE2 but everything else stayed as MK4.
My issues is when I try to ODIN flash a stock MK4 tar, I get an error Binary:3 Device:2.
After research I getting that everything needs to match up I'm guessing. (I could be wrong)
So what I am needing is a MK4 bootloader to flash via recovery or ODIN or a way to get everything to NE2 (I just need them matching)
Someone has uploaded a MK4 bootloader tar (I cant find the link) but is does not work with ODIN.
If I am completely wrong about all this please chime in, I'm not developer and could have misinterpreted my research.
My status right now is a very early, dirty flash of CM11 (I had a backup) that will not update with nightlys via updater giving MK5 checksum verification error. I am assuming this is related.
Josh
cgi2099 said:
Hello everyone, I am in need of some help.
I tried to update my l900 mk4 rooted to NE2 yesterday and it failed and left me in a situation.
My bootloader got updated to NE2 but everything else stayed as MK4.
My issues is when I try to ODIN flash a stock MK4 tar, I get an error Binary:3 Device:2.
After research I getting that everything needs to match up I'm guessing. (I could be wrong)
So what I am needing is a MK4 bootloader to flash via recovery or ODIN or a way to get everything to NE2 (I just need them matching)
Someone has uploaded a MK4 bootloader tar (I cant find the link) but is does not work with ODIN.
If I am completely wrong about all this please chime in, I'm not developer and could have misinterpreted my research.
My status right now is a very early, dirty flash of CM11 (I had a backup) that will not update with nightlys via updater giving MK5 checksum verification error. I am assuming this is related.
Josh
Click to expand...
Click to collapse
You cant downgrade bootloader without causing issues. Also you don't have to have bootloader, rom, and radio versions match. I am on ne2 bootloader running mk4 rom with the ancient lj1 modem. Not sure what your cm11 issue is not mismatch of versions. You can flash the full ne2 tar with odin if you want but cant go backwards with odin.
Sent from my XT1045 using XDA Premium 4 mobile app
Ah, I see now. So basically the only TAR I can flash is either a NE2 or NK2?
I guess I have something else going on with CM11 and CM12. I cannot update CM11 at all and if I try to flash CM12 I get a boot loop. None of this happened till I tried to upgrade from MK4 to NE2.
Not sure how to fix it, I'm stuck on a Dec of 2013 CM11 rom. Every NE2 TAR I download, both my computers say they are corrupt (I'm thinking it might be a windows 8.1x64 issue)
If you go to androidfilehost.com/dev/jlmancuso and search around you will find a copy of the ne2 tar I uploaded. It should download better/faster. Hopefully it will help you out.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
If you go to androidfilehost.com/dev/jlmancuso and search around you will find a copy of the ne2 tar I uploaded. It should download better/faster. Hopefully it will help you out.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
www.androidfilehost.com/?fid=23501681358546202
cgi2099 said:
Ah, I see now. So basically the only TAR I can flash is either a NE2 or NK2?
I guess I have something else going on with CM11 and CM12. I cannot update CM11 at all and if I try to flash CM12 I get a boot loop. None of this happened till I tried to upgrade from MK4 to NE2.
Not sure how to fix it, I'm stuck on a Dec of 2013 CM11 rom. Every NE2 TAR I download, both my computers say they are corrupt (I'm thinking it might be a windows 8.1x64 issue)
Click to expand...
Click to collapse
Much appreciated.
When I load this into ODIN 3.07 I get a MD5 hash error, and when I load it into ODIN 3.09 I get a binary invalid error.
Josh
You can also get it from here http://samsung-updates.com/device/?id=SPH-L900 , but it will take a long time to download, this is where I downloaded mine from and its worked fine for me many times using odin 3.09.
I rooted my n910p a while back with the emotion kernel and twrp. My phone has been messing up even before rooting which is why I rooted in the first place. All I need to know/want to do is unroot and go back to stock. I understand how to do it with odin but everytime I download the stock rom files I always get an error such as pit partition or something. I just want to unroot so that I can get another phone without them noticing its rooted. I know when you turn the phone on it says things in the top left like android is se enforcing. Is there a way to unroot to where they can't tell its been rooted?
P.S. I know I'm all over the place with this post ive been trying to unroot all day with no luck. Please help somebody!
shutdafup9 said:
I rooted my n910p a while back with the emotion kernel and twrp. My phone has been messing up even before rooting which is why I rooted in the first place. All I need to know/want to do is unroot and go back to stock. I understand how to do it with odin but everytime I download the stock rom files I always get an error such as pit partition or something. I just want to unroot so that I can get another phone without them noticing its rooted. I know when you turn the phone on it says things in the top left like android is se enforcing. Is there a way to unroot to where they can't tell its been rooted?
P.S. I know I'm all over the place with this post ive been trying to unroot all day with no luck. Please help somebody!
Click to expand...
Click to collapse
Which tar file are you trying to Odin? From my understanding, you have to Odin the tar ROM that installed the last pit file. So you might have to download and try each individual one till it takes it. Are you on MM or LP?
ianmb said:
Which tar file are you trying to Odin? From my understanding, you have to Odin the tar ROM that installed the last pit file. So you might have to download and try each individual one till it takes it. Are you on MM or LP?
Click to expand...
Click to collapse
makes sense, but what do you do when you have something like Noterized, like me, and in this case, my build is OB7, but my bootloader and baseband are OE1... I had the same odin error recently, and i am going to try to odin the full OB7 again, but if that does not work, there is no full OE1 rom, it was just a security update... and thanks much for your help, ianmb...
mlongue1 said:
makes sense, but what do you do when you have something like Noterized, like me, and in this case, my build is OB7, but my bootloader and baseband are OE1... I had the same odin error recently, and i am going to try to odin the full OB7 again, but if that does not work, there is no full OE1 rom, it was just a security update... and thanks much for your help, ianmb...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=66566610
Check this out
thanks, man…