Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
bbrou33 said:
Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
Click to expand...
Click to collapse
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
audit13 said:
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
Click to expand...
Click to collapse
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
britt21 said:
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
Click to expand...
Click to collapse
The only ATT DKL3 firmware that I can find is in this thread. WinRar was failing to unpack the .7z file every time I tried. But I'll try again later when I get home
bbrou33 said:
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
Click to expand...
Click to collapse
You can try different stock firmware from sammobile if you are sure you do not have the 4.3 bootloader.
So newb questions and might have been answered but I have been unable to find the answer I'm looking for.
Background:
SGH T999
Original I was on 4.1 stock. I used towelroot and was able to root and all that jazz. I uploaded an old version of CWM to my phone and was unable to flash and ROMs, they would all hang on the Samsung Galaxy SIII screen.
I updated CWM to put on a Cyanogen Mode ROM and all was good. I tried out a couple other ROMs then decided I wanted to go back to stock and see how stock 3.3 or 3.4 was. I tried using Odin to bring back to stock and no luck. I then installed PhilZ recovery and booted to Wicked ROM for 4.1. After this I got current TWRP and tried to update other roms. I went into ROM manager switched over to CWM 6.0.4.5 then updated my kernel. At some point along the way I noticed that on the internal sd card I have a 0 directory inside my 0 directory.
Now when I reboot my phone into Recovery mode I see a Samsung Galaxy SIII screen with the Cyanogen guy on it, then it loads to CWM but nothing is on the screen but the hat, then after a couple of seconds it loads to a Samsung screen quickly, then to the Samsung Galaxy SIII and hangs indefinitely. I'm still able to get the phone to go into download mode fine. Now I'm trying to just bring back to stock but not having any luck. Here's my repro:
1. Put hardware into download mode (HOME + Vol Down + Lock).
2. Open Odin 3.09 as Admin (I'm using Win 7).
3. Connect hardware to computer (Odin recognizes 0:Com5).
4. Place "T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5" in AP field.
5. With only "Auto Reboot" and "F.Reset Time" selected press Start button.
RESULT:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Then on my hardware I get
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Offical
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
SW REV CHECK FAIL : Fused 1 > Binary 0
Click to expand...
Click to collapse
Any idea's how I can bring this back?
tiger_johnson said:
*snip*
Any idea's how I can bring this back?
Click to expand...
Click to collapse
Hmm, if the device is recognized in your PC by ODIN there's still hope. I personally recommend TWRP (LINK for latest ODIN flashable version) for everything as CWM has caused havoc with my phone before. Stay away from it. IF you can still access recovery, do format everything, including the internal SDcard. Also please use the PIT file when trying to use ODIN for the MD5 firmware you're choosing. LINK for the PIT file (choose your model's PIT and put it on the PIT part of ODIN then proceed on flashing the MD5 firmware - credit goes to DocHoliday for the PIT files). That little file can sometimes fix stuff when trying to ODIN the device back to stock firmware. Just giving ideas, don't give up and best of lucks!
You can't flash MD5. It looks like you are currently running MJC base firmware which means you can ONLY flash MJC or NC2 with Odin. Do not try to downgrade via any method or it will hard brick your device.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
"SW REV CHECK: Fused 1" means you currently have MJC. It will change to Fused 2 if you update to NC2. (If I'm remembering all those nemesis right).
Just FYI in case anyone was wondering.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Unlike the other threads I've read here so far, I wasn't upgrading or downgrading anything on my phone. Last night, I was playing Scrabble (lol) and the phone blacked out and now won't power on. I've tried booting to Download mode and can't even do that. The battery was running low at the time, but that's normal for late at night. I believe I had about 9% battery.
The symptoms of my phone are now:
When I have the battery installed, plugging in the charger doesn't seem to do anything (no charging light).
When I remove the battery, plugging in the charger lights the LED as red for 90 seconds.
Plugging the phone into my computer via USB (without battery), the phone connects (as a device for which I do not have drivers) for 90 seconds (same duration as the red light) and then disconnects.
If I hold the power button in for 12-13 seconds (without battery with charger connected), the red light will go out. As soon as I release the power button, the red light comes back on and the 90-second timer restarts. If I have the phone connected to my computer while trying this, the phone disconnects when the red light goes out and reconnects to the computer (as the same device from above) when I release the power button.
Overnight, I left the phone (with battery) plugged in hoping to fully charge the battery and that would somehow miraculously bring my phone back to life this morning -- it did not. Unknown if the battery is fully charged now or not.
Any suggestions on what I might try next?
See if this helps:
http://forum.xda-developers.com/showthread.php?t=2549068
Lithium ion batteries are at their least stable when they're low on charge like you indicated yours was. How old is your battery? Does it have any bulges you can see or feel? If you put in on a table and flick it on the corner does it spin around? The spin test is by no means conclusive that a battery won't function, but it is indicative of some damage. My original Samsung battery spins like a top, but it still holds a charge and makes an ok backup in a pinch. If you know someone else with a working S3 try their battery in your phone. Otherwise, if there is a Batteries Plus or somewhere like that convenient, pop in and try a replacement. Most replacement batteries I've bought for phones or cameras usually come partially charged so you can probably test it right in store; the guys in the stores might know a thing or two as well as a lot of battery shops have started replacing phone screens and batteries that aren't as readily removable like that other variety of smartphone.
The debrick threads suggested above are a good idea too, but like you pointed out, those are usually for people who tried to downgrade our wonderful secure bootloaders.
If none of that pans out, a repair shop might be able to jtag it back to life.
Good luck.
Update
I was reading this unbrick thread and downloaded this debrick img for I747U. I applied the debrick img to a 32GB microSD card and I got the phone to at least do something. What I see is:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
WRITE 159488 SECTORS..
[COLOR="Red"]FLASH WRITE FAILURE
ODIN MODE[/COLOR]
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
[COLOR="Silver"]QUALCOMM SECUREBOOT: ENABLE[/COLOR]
[COLOR="Red"]Warranty Bit: 1[/COLOR]
[COLOR="Silver"]BOOTLOADER RP SWREV: 2[/COLOR]
I can now see the phone in ODIN when I connect with USB.
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.
Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.
audit13 said:
Maybe try flashing a customr recovery and a custom ROM to at least get your phone booted.
I highly recommend Philz Touch for the d2lte.
Click to expand...
Click to collapse
I'm hoping to reflash the stock rooted MJB so I don't lose everything that I had on the phone.
Hossy923 said:
So, I read this thread, which led me to this thread, which led me to download the I747UCUEMJB 4.3 Odin flashable tar, however, I cannot seem to flash it with ODIN. I was running MJB before the phone died.
I'm kinda lost on where to go from here.
Click to expand...
Click to collapse
When I try and flash with the file above with ODIN v3.07, I get:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
At the same time, I get two additional lines on the screen of the phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)
ODIN : flash read failure[/COLOR]
Looking inside the .tar.md5, I do see a PIT file in there.
---
If I flash with ODIN v1.85, I get:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On phone:
Code:
[COLOR="Red"]PIT FAIL : TOTAL SECTORS (0)[/COLOR]
Flashing via Odin is almost guaranteed to require a full wipe to boot.
audit13 said:
Flashing via Odin is almost guaranteed to require a full wipe to boot.
Click to expand...
Click to collapse
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?
Hossy923 said:
As I understand it, flashing via ODIN will only remove my data if I flash the data partition, which this tar.md5 does not have, so I should be good. Even the emergency firmware recovery within Kies doesn't overwrite the data partition (as I found out when recovering my S II a while back).
Do you have any insight as to my post above and why ODIN is giving me the PIT errors or what I should be doing differently to get ODIN to flash my phone?
Click to expand...
Click to collapse
Re-partition is unchecked?
I get the same error in Odin3 with Re-Partition checked and unchecked.
You used a debrick image for the i747u? Did you try an i747 de-brick image?
I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.
Hossy923 said:
I'm going to try and revive this thread (yes, after years). I'm trying to get this phone to work and forgot that I was having problems long ago. :-( I do not care about the data on the phone, I just want to flash a stock image. Any advice is much appreciated.
Click to expand...
Click to collapse
I've come to believe now that my internal SD card has died. All attempts I've made to flash, whether with ODIN or Miracle Thunder have failed. I get a bunch of errors on the screen talking about errors reading or writing firmware/flash. I even tried doing a nand erase with ODIN and that failed. Unless someone has a better idea, I believe the device has hardware damage.
Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!
Downgrade !
bawalker said:
Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!
Click to expand...
Click to collapse
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!
Iceburn1 said:
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!
Click to expand...
Click to collapse
Well that just totally sucks. I was hoping to get down to 5.0.1 to use chainfire root. The Beastmode root kernel patch seems to have slowness and lag issues introduced after installing that kernel patch which I really wanted to avoid.
I used to do roms and such back earlier on in my smart phone days, but I've found Stock to be best, even with touchwhiz. When I root I just want root access, maybe twrp, but even that's not a requirement as the only things I use are wifi tether when on job sites and titanium backup to freeze things like knox, remove bloatware, etc. That's all I ever use root for. So I'm kinda bummed right now over not downgrading. What is Samsung thinking?!
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.
Kernel+Rom
bawalker said:
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.
Click to expand...
Click to collapse
Im using stock rom Hybrid 3.0...http://forum.xda-developers.com/note-4-sprint/development/rom-t2956667....with emotion kernel.....http://emotroid.com/touchwiz-kernel/, use app called Synapse to control kernel, link is below emotion kernel to playstore. You said you liked stock, and this will give you that and the emotion kernel is great, no lag for me at all, use synapse to fine tune it.
I have n910f , i try to flash it but always get odin fails
Any solution to repair it
hbs131415 said:
I have n910f , i try to flash it but always get odin fails
Any solution to repair it
Click to expand...
Click to collapse
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk
samep said:
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CP_N910FXXU1ANK4_REV00_CL_1795169.tar.md5 is valid.
<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> CSC_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<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> AP_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hbs131415 said:
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<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> CP_N910FXXU1ANK4_REV00_CL_1795169.tar.md5 is valid.
<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> CSC_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<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> AP_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And what does your phone display indicate when you get this failure?
Just an observation, I think you're trying to Odin KitKat which may not be possible in Odin if you've updated to Lollipop 5.1 Other 5.0 stock tars attempted may also get blocked to downgrade of bootloader as well like my SM-N910P will. My phone won't get as far as yours did when Odin of KitKat or Android 5.0 stock tar is attempted so that may not be the issue; maybe you haven't had that phone upgraded beyond beyond Android 5.0 yet?
If you had updated to Android 5.1 or higher, you might consider trying a newer stock tar, 5.1 or higher.
They're may be a more logical reason given on your screen at time of failure.
Sent from my SM-N910P using Tapatalk
here the message in the phone
here screenshoot
samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10
hbs131415 said:
here the message in the phone
here screenshoot
Click to expand...
Click to collapse
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
TheMadScientist420 said:
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10
Click to expand...
Click to collapse
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk
samep said:
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.
TheMadScientist420 said:
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.
Click to expand...
Click to collapse
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk
samep said:
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails
TheMadScientist420 said:
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails
Click to expand...
Click to collapse
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk
samep said:
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up
TheMadScientist420 said:
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up
Click to expand...
Click to collapse
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk
samep said:
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried most of that. This thing does have a weird battery issue. Its no loss to me. I got this thing cheap the other day. I keep getting failed to repartition errors. Which seems to come back to the fail to mount system.
I hate to buy a battery. I dont buy cheappies. Due to high failure quality rateS.
I used the pit from samobiles.
Even factory recovery will wip cache. But thats when i get the failed to mount system
new update so i flashed the developer firmware minus the system and data parts. so basicly modem and other partitions included in boot and that takes every time now it litrely fails when i try to flash something to the system partition. when i flash twrp i get failure says no pit for mapping.
even the pit files is failing says there is no pit partition
id say im donr now just saw a mmc read fail on device in dl mode