Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?
Related
Hello.
My Galaxy S4 Gt-I9505 is getting stuck while flashing an Official Rom in Odin 3.09 during System.img.ext4.
<OSM> Leave CS..
<ID:0/007> Added!!
<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> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have done full data / cache wipe and I still get the same problem. Can anyone help ?!
Give us more details. I hope u arent trying to downgrade ur phone
Joku1981 said:
Give us more details. I hope u arent trying to downgrade ur phone
Click to expand...
Click to collapse
The phone is an international GT-I9505. It was previously running 4.2.2.
The software I have chosen to upgrade is the same software I have successfully used to upgrade my other GT-I9505.
I have used the PIT File in order to get access to the recovery mode.
I have tried two different frimware, both downloaded from samfirmware.com.
The phone gets stuck @ system.img.ext4.
I have done this many times before, but this has never happened.
Please tell me exactly what details you need so I can offer you the information in order to help me figure out this mess, it's driving me crazy ....
vBasceanu said:
The phone is an international GT-I9505. It was previously running 4.2.2.
The software I have chosen to upgrade is the same software I have successfully used to upgrade my other GT-I9505.
I have used the PIT File in order to get access to the recovery mode.
I have tried two different frimware, both downloaded from samfirmware.com.
The phone gets stuck @ system.img.ext4.
I have done this many times before, but this has never happened.
Please tell me exactly what details you need so I can offer you the information in order to help me figure out this mess, it's driving me crazy ....
Click to expand...
Click to collapse
Try a different cable/port.
Repulsa said:
Try a different cable/port.
Click to expand...
Click to collapse
If I don't use my laptop's USB 2.0 port, it won't even start the flashing.
To make this easier: I have read most of the basic stuff around the forum (ports, different firmware, wipes, flash pit).
vBasceanu said:
If I don't use my laptop's USB 2.0 port, it won't even start the flashing.
To make this easier: I have read most of the basic stuff around the forum (ports, different firmware, wipes, flash pit).
Click to expand...
Click to collapse
I have some old 4.2.2 as Factory firmware Full Wipe,
MDM Firmware, and some other
I give you them if you need, but you should try a different port
restart your laptop and try
timb3rwolf1973 said:
I have some old 4.2.2 as Factory firmware Full Wipe,
MDM Firmware, and some other
I give you them if you need, but you should try a different port
restart your laptop and try
Click to expand...
Click to collapse
I have got a new USB cable and an SD card so I can apply the update from Recovery Boot.
I would be grateful if you could provide me with the download link to your recover and the information on how to do it.
Regards
vBasceanu said:
I have got a new USB cable and an SD card so I can apply the update from Recovery Boot.
I would be grateful if you could provide me with the download link to your recover and the information on how to do it.
Regards
Click to expand...
Click to collapse
I sent you a private message with a link to my Google Drive - a folder with firmwares
timb3rwolf1973 said:
I sent you a private message with a link to my Google Drive - a folder with firmwares
Click to expand...
Click to collapse
Thanks but it's not needed. AS soon as I tried with a new USB cable, it worked perfectly.
Thanks for your cooperation
vBasceanu said:
Thanks but it's not needed. AS soon as I tried with a new USB cable, it worked perfectly.
Thanks for your cooperation
Click to expand...
Click to collapse
OK
Good Luck
So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.
SageNightmare said:
So basically,got phone last night,tried regular rooting,didn't work,read up some more,tried the whole "Root AT&T Galaxy S4 SGH-I337 on I337UCUFNJ4 Firmware" even though my firmware is I337UCUFNJ5 and not 4,anyway,thread told me to flash I337_NC1_Stock_Kernel using the Odin firmware flashing tool.
I did....used towelroot app 3.0,didn't work,needed internet access (yes I got it straight from their site) fond a 2.0 version,used it,says "you should have root,no reboot required" so since I didn't have wifi on the phone,I went right back into odin and tried to use I337_NJ4_Stock_Kernel and flash it using the Odin tool to get back to the stock NJ4 kernel. Didn't work,failed,now I'm STUCK on nc1 kernel with no wifi access... help? please? this is my first rooting and I am legit clueless to most of this.. also how do I even find my boot loader etc?
EDIT: This might not be in the right thread,if so,please move to appropriate thread moderator.
Click to expand...
Click to collapse
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.
sway8966 said:
Here is the link for the NJ5 kernel.
If you still have problem go here and following the steps to start every thing from NB1.
Click to expand...
Click to collapse
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here
SageNightmare said:
so I tried all of this,but odin fails no matter what sigh.. Odin tells me this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any clue what's wrong? cause I'm really lost here
Click to expand...
Click to collapse
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?
sway8966 said:
Try with different version of odin (the latest is 3.10 I think), use different usb port, use different usb cable.
Did you load your file in the AP (auto partition) slot?
Click to expand...
Click to collapse
Yup I tried all of that except a different odin version,but long story short,I managed to go into town and a friend of mine used a different version of odin and got me nice and sorted out,thanks for help btw
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Remove PIT file and try again.
From Edge of Galaxy Seven
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Not knowing WHAT you are flashing, makes it a little harder to determine what is going wrong.
Go HERE and flash this in Download Mode. This is the latest Stock 935A ROM, This will wipe Everything on the device, and it'll be like it came brand new
norbarb said:
Remove PIT file and try again.
From Edge of Galaxy Seven
Click to expand...
Click to collapse
which is the pit file, sorry for dumb question
Darkboss10 said:
which is the pit file, sorry for dumb question
Click to expand...
Click to collapse
If I remember correctly you need to uncheck PIT in odin and this should help. BTW. What are you trying to flash?
From Edge of Galaxy Seven
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Darkboss10 said:
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Click to expand...
Click to collapse
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
so i do better go with the v4 bootloader and i will check if the pit file is uncheck, what should i put on the re-partition case of odin active or inactive?
by the way thanks for your help
kangi26 said:
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hey i did exactly as you told me , and for first time i guess i have an advance, i still get an error but at least a new error , check it out maybe you know what it is
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
any idea what can be?
i try to flash the G935a...PI2 rom bot without the CSC which i guess is the pit file right?
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
kangi26 said:
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
Click to expand...
Click to collapse
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Darkboss10 said:
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Click to expand...
Click to collapse
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
kangi26 said:
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
if you watch the top corner blue letters it says recovery booting....
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
I'm at a loss man, I'm sorry. I haven't seen that before, I dont get the "Samsung" part when I enter Recovery
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
Can you post screen from download mode?
From Edge of Galaxy Seven
norbarb said:
Can you post screen from download mode?
From Edge of Galaxy Seven
Click to expand...
Click to collapse
There you go . By the way i should mention the phone only turns on download mode when plugged.
Darkboss10 said:
There you go . By the way i should mention the phone only turns on download mode when plugged.
Click to expand...
Click to collapse
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
You need to start by using the latest Odin, 3.12.3 for installing the original ROM. If you try to unlock, you need to go get the PrinceComsy version. PrinceComsy won't work for in-bricking a device, and if you have any of the stock versions of the ROM, you need the 3.12.3 version.
norbarb said:
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
Click to expand...
Click to collapse
I try that . Now i got this error but only on the phone screen and odin is stuck at initialization .. any idea what could be
i download the venom stock rom and the odin file he suggest but that odin is v 3.11.2 , so that was the one that trows me the odin protocol error, i try the same rom but with the v 3.12.3 odin , and it start working but it says fail at the on the recovery image, do that has to do something with my problem that the phone can boot into recovery mode?
here are the logs
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Erase)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Okay so I was trying to update my bootloader and modem using the tutorial I found here. But odin refused to install it and left me with a softbricked device. Now I have tried to flash the new bootloader again, the old bootloader, changed pc, changed usb cord and port, tried heimdall but still not working. Now it starts to install the bootloader and odin log goes like this
<ID:0/005> Odin engine v(ID:3.1203)..
<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> rpm.mbn
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Any help?
It's possibly because the bootloader you are trying to flash is not compatible with your S4 model.
If you can't flash the bootloader separately, flashing a stock ROM package may work. Also, try a different Odin version and also another Windows.
Yeah I tried to flash the stock rom but the same thing happened. I have tried 3 different odin versions and 2 windows.
Could this be because I've changed my usb port? Odin seems to always disconnect my phone after failing and then reconnects again.
Google and download PIT file GT-I9505
Flash bootloader with pit file selected
@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.
Strephon Alkhalikoi said:
@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.
Click to expand...
Click to collapse
It says Product name: GT-I9505
Good. The USB port on the device could cause this if it's damaged or defective. You want to check its connections in the device and also clean the port with a bit of rubbing alcohol to be safe.
Yes I got it solved. I don't know how but I think that the problem was that both usb cables I tried were damaged though they worked before. I tried third usb cable and the same error came up then I tried again and it flashed the stock succesfully. How can I mark this solved?
Go to your first post and change the title. If you can't do that, add a line to the post noting that the problem was resolved.
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
My trusty Galaxy Note 3 N9005 32GB has been giving me a few minor file errors recently, so I re-installed from a nandroid backup (ROM is MagMa NX VX PCE 6.0.1) with Phantom kernel) and it's been great for a few weeks now, performing better than ever in fact.
However yesterday, I glanced at the phone mid-afternoon (after using it fine all day listening to music and reading emails, etc) and it had reverted to the Download screen, reporting "Could not do normal boot, ddi : mmc_read failed."
I can't get into Recovery or use ADB, so I ran Odin on my PC and it showed the device as Added, so I thought I'll re-upload TWRP so I can at least get into Recovery and see what's going on, but although Odin started sending the TWRP .tar file normally, it quickly reported "Get PIT for mapping ... There is no PIT partition". The phone screen showed "UDC START" then "MMC: mmc_read fail". The USB port and USB cable are the same ones I've been using for some recent adb pull backups so they should be OK.
I tried installing a new PIT file (first from a previous backup of my own setup, and then from generic versions for this device) but Odin with AutoReboot, Re-Partition, and F.Reset Time ticked showed:
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone showed:
UDC START
MMC: mmc_read fail
I then tried downloading a 4files repair installation of a stock Lollipop ROM (the most recent I could find for this device, N9005ZSUGPJ2) and used Odin to install the included PIT, AP, BL, CP and CSC files, with Nand Erase All selected too:
<ID:0/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time, the phone showed:
UDC START
MMC: mmc_read fail
ERASING USERDATA PARTITION...
I could really do with some expert help or advice here from anyone who knows more about these things than I do... or do I have an unexpected brick on my hands? Thanks!
Andre
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
here is the procedure you have to follow...
PLEASE.....DO NOT skip ahead, just follow my instructions in sets,
Here are the Files you NEED to download:
Odin3 v3.10.zip
CHARGE the device to 100% Battery BEFORE beginning!
Download and extract the Files.
Open ODIN, place each of the Files in corresponding boxes:
BL = BL
AP = AP
CP = CP (MODEM)
CSC = CSC
Please select these Check-boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS Clear
START!!
After it reboots, WAIT 10 Minutes, Skip the Wizard and perform a Factory Data Reset!
rayman95 said:
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
Click to expand...
Click to collapse
Which phone version, or which 4files?
Phone is a Galaxy Note 3 N9005 (UK 32GB).
File was from https://zfirmware.com/download-samsung-repair-firmwares/ , version http://www.mediafire.com/file/9ux01...3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
I was hoping to be able to use this device until the Note 10 is released, but maybe I'll have to settle for an S10+. Problem is, I prefer my nice Note 3 to anything they have released since (removable battery, no stupid curved-edge display, proper physical front buttons away from the main screen, a bigger - OK, wider - display than anything since, etc)
Andre
andrewilley said:
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
Click to expand...
Click to collapse
From my own experience, this problem is a manufacturing defect that affects a lot of samsung devices produced from Q3 of 2014 until Q2 of 2015. The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
However, I managed to fix a Galaxy S5 with the method I already described. And that has been presented as a momentary solution by several xda users, like here.
I wrote : momentary solution because this error is definitely a hardware failure, a fixed device will only work for a random period then the problem will get worse until the device become completely unusable.
Fortunately, you can buy a new motherboard for less than 30euro. And that's what I recommend you to do.
andrewilley said:
Galaxy-Note3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip[/url] . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
Andre
Click to expand...
Click to collapse
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
zlazaar said:
The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
Click to expand...
Click to collapse
I've been noticing a few file-read errors over the last 5 months or so, which I put down to bad blocks even though e2fsck -cfv showed zero errors. I thought a reformat and nandroid restore had fixed it, but obviously if the problem is lower down that might just have been delaying the inevitable. I suspect that installing a new mobo would not really be a good long-term plan as that could just as easily have the same issue (as they'll all be 4+ years old by now).
rayman95 said:
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
Click to expand...
Click to collapse
I'll try the KitKat version (normally I'd look for a BTU version, but beggars can't be choosers as the saying goes). If I can at least get it running for now and restore my backup via TWRP then I can do a more relaxed and controlled switchover to an S10+.
Andre
Whatever I try, I can't get a new PIT file to re-partition the memory:
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 2252 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
Phone shows MMC: mmc_read fail
Does anyone have a known good PIT file for the UK Note 3 N9005 32GB, along with a matching BL/AP/CP/CSC combo (any ROM version would do) that they would be willing to either upload or point me to?
Thanks,
Andre
I guess I probably should treat this device as a brick now and get it replaced, no other suggestions?
Andre
sammobile forum ??
JJEgan said:
sammobile forum ??
Click to expand...
Click to collapse
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
andrewilley said:
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
Click to expand...
Click to collapse
i send you my french files....
take here my files...
Thanks, I'll download and give them a try when I get back on home wi-fi. I fear I'll probably get the same results, but at least I'll have tried everything before giving up on it.
Andre
File downloaded, thank you. There doesn't seem to be a matching PIT file in there though, just the BL, AP, CP and CSC. Is that correct? As stated earlier in the thread, the PIT seems to be corrupted on my device, so was hoping for all 5 files to match...
Andre
rayman95 said:
take here my files...
Click to expand...
Click to collapse
I did try the 4files in your ZIP, but without a new PIT file I got the same partitioning error as before:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Andre
the pit HERE...
good luck..
rayman95 said:
the pit HERE...
good luck..
Click to expand...
Click to collapse
Many thanks for all your help, but still dead even with the correct PIT I'm afraid.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this phone is on its way to the Great Home for Expired Technology in the Sky.
Andre
Just read some user not this phone replaced eMMC chip.
From Aliexpress