Related
So... Like a fool, having successfully rooted my phone a couple of days ago on the I9505XXUBMGA firmware, I saw this appear in Kies when I plugged my phone into Kies this morning. I thought (yeah you know where this is heading) "Oooh shiny new update, must download".
So although I had root I didn't think it would be a problem I'd just re-root afterwards. And hey if it didn't work I'd just downgrade the firmware and repeat the original process.
Trouble is I now have a message saying "SuperSU has been forced to stop for an unauthorized attempt to access system in your device. It may be solved by the policy update service. It may be safe to delete an application obtained from an unauthorized route. Check now?". I then have the option to not show for 30 days and then Cancel, Update or OK. Trouble is now when I attempt to revert the firmware back to an earlier version.
So now when I go into Download mode I see:
Code:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
If I try and Odin a new (stock) firmware on I get a write error from Odin and on the I9505 I get the following below the above text:
Code:
START [224, 1440]
SW REV. CHECK FAIL : fused: 2, Binary : 1
Odin shows:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
So, kind of stuck now. If the phone tries to restart I get the message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". For a while I couldn't get the phone to boot, and Kies doesn't see the phone, but oddly re-partitioning via Odin using the PIT file means the phone will boot. From there I still get the SuperSU message but can switch it off and get into recovery mode, does that mean there is a chance I can re-flash things via adb / fastboot?
Yep I'm an idiot for trying and being the Guinea pig, but as I don't know how to proceed if anyone wants to help out and see if we can get it back and un "Knoxed" (which I think might be the issue) I'm more than happy to help.
Limitations currently are that I am running Windows XP 32-bit via Parallels virtual machine. The unbricking steps seem to indicate needing a 64-bit machine? I could probably do that but would have to get hold of and install 64-bit Windows 7 as a VM.
In terms of Android hacking I'm a noob, but can follow instructions, and am comfortable with a Unix/Linux command line if that's any help to anyone who wants to take pity on me...
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Boolean = True said:
OP, I'm in the same position as you, however I'm still stuck in download mode. Can you tell me EXACTLY what you did with Odin to manage to be able to boot the phone up again? I'd rather be able to use it un-rooted for now than to not use it at all!
Click to expand...
Click to collapse
So, assuming you are stuck at the "there was a problem stage" you need to turn off the phone and get it into download mode (hold volume down, home + power - I guess you know this but just in case). I found this a bit fiddly I think because the phone is auto-rebooting, so try pressing power off and just holding the volume down and home buttons.
Then in Odin I used the PIT file listed in this thread. In the 'Re-partition' section and the boxes for Auto Reboot, Re-Partition, and F. Reset Time were all checked. I left all the other boxes empty (including the Files section). Click start and then after a while the phone reboots. It take a minute or two but if you see the Samsung logo it should boot.
Hope that helps... now to find a way around the MH1 firmware... oh and glad it wasn't just me that was daft enough to go and try it.
No, not just you mate. I had a hell of a time last night. Flash pre-rooted MGG firmware via odin, which bootlooped. I couldn't flash MGA firmware again.
So I flashed Stock MGG which booted but the security measures implemented have stopped me from changing my font using ifont.
I have now flashed MH8 over the top and it's working better than MGG, but still can't use some apps due to the new security measures.
I was able to flash Omega V10 from TWRP and it booted fine, but no wifi and I'm unable to flash LTE modem to correct it.
Looks like I'm stuck unrooted on MH8 for the time being.
There are some instructions on this thread on how to root this firmware, they're a bit lengthy tho.
http://forum.xda-developers.com/showthread.php?p=45283966
Sent from my GT-I9505 using Tapatalk 4
Bugger.
To add insult to injury it appears that WiFi is now no longer working either.
I'll look into the post you linked too, but I can't see how it will update that all, i.e. it says to use Odin which currently fails for me.
Odin doesn't fail for me when flashing kernels or recoveries, just when I try and flash full firmware earlier than MGG which includes the bootloader.
Flash full MH8 firmware from samfirmware, I have no issues except for the security problems.
Sent from my GT-I9505 using Tapatalk 4
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
jd1639 said:
In the odin output, the "fused: 2" shows the update has blown a q-fuse. You won't be able to odin an earlier firmware.
Click to expand...
Click to collapse
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
shrubz said:
No I know, but you can still flash recovery and modem etc. Is it failing at trying to flash older bootloader?
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I hadn't realised that flashing the same or newer would work (it does). But WiFi is still borked... any ideas?
Tiny amount of progress, more out of hope I tried to flash a pre-rooted ROM - obviously this didn't work, but when I reflashed MH8 again I noticed the device made the start up sound (which it hadn't been) and WiFi is now working.
As a bonus if I go into Device Status it is now showing as Official, which is nice!
I think I'll leave it there for now, but will keep an eye out for progress, hopefully the bootloader will be "fixed" in due course.
Chainfire is working on a fix for CF-Root. So hopefully all will be good soon.
Sent from my GT-I9505 using Tapatalk 4
Okay where do I start...
I was given this phone from a friend, and it was working fine,
rooted and no problems at all...
Followed this guide to install the "Google Play Edition" ROM >> http://www.technobuffalo.com/videos/how-to-turn-a-galaxy-s4-into-a-google-edition-phone/
All was working perfectly, then in a backup process using titanium backup, the phone crashed...
I'm stuck in a boot loop with only the Samsung Galaxy logo screen.
I can enter Download mode, but not recovery...
Have tried every ROM that I can think would be appropriate to restore but to no avail...
Even tried philz touch recovery, nothing seems to be working...
Odin always reports either write failed or <ID:0/003> There is no PIT partition.
Have tried writing just the .PIT file from >> http://forum.xda-developers.com/showthread.php?t=2265477
Have tried to recover using Kies, firmware downloads then "Error - F" Phone cannot be located...
The phone gets stuck with a small dot of a process bar in download mode and this read out in the top left of the screen:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
I'm at a total loss how to recover this, and if it's even possible to recover?
I would happily send it somewhere for repair, I have no warranty so i expect to pay, but no idea where to send?
Does any one have any advice or solution to this problem?
Much appreciated.
re: cannot get into recovery.
EvilM0narch said:
Okay where do I start...
I was given this phone from a friend, and it was working fine,
rooted and no problems at all...
Followed this guide to install the "Google Play Edition" ROM >> http://www.technobuffalo.com/videos/how-to-turn-a-galaxy-s4-into-a-google-edition-phone/
All was working perfectly, then in a backup process using titanium backup, the phone crashed...
I'm stuck in a boot loop with only the Samsung Galaxy logo screen.
I can enter Download mode, but not recovery...
Have tried every ROM that I can think would be appropriate to restore but to no avail...
Even tried philz touch recovery, nothing seems to be working...
Odin always reports either write failed or <ID:0/003> There is no PIT partition.
Have tried writing just the .PIT file from >> http://forum.xda-developers.com/showthread.php?t=2265477
Have tried to recover using Kies, firmware downloads then "Error - F" Phone cannot be located...
The phone gets stuck with a small dot of a process bar in download mode and this read out in the top left of the screen:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
I'm at a total loss how to recover this, and if it's even possible to recover?
I would happily send it somewhere for repair, I have no warranty so i expect to pay, but no idea where to send?
Does any one have any advice or solution to this problem?
Much appreciated.
Click to expand...
Click to collapse
During your unsuccessful flashing of the google edition rom you have lost ROOT and the custom and or stock recovery.
That is why you cannot go into recovery mode.
You are lucky that the .pit file did not flash, you could have ended up with a brick (unusable phone).
The .PIT file is the partition information table, if that is changed or damaged you would need to send
your phone to samsung or other phone repair shop to get it fixed.
What you need to do is to download and Odin flash the stock-rooted i9505 rom which can be found here:
http://www.androidfilehost.com/?fid=23060877490003683
This rom is pre-rooted and you will be able to get into recovery mode without any issues.
Once this is odin flashed, be sure to make a nandroid backup before flashing other cwm/twrp zip file roms.
The "phone cannot be located" error most likely means that you either do not have the proper samsung usb
driver installed or you need to check the usb cable connections to your computer and phone.
Perhaps use a different usb cable and a different usb port will fix this issue.
Just in case you need it, here is the link for the official usb drivers for the samsung s4 phone:
http://org.downloadcenter.samsung.c...5728593/MCCI_WHQL_USB_Modem_Driver_4.40.7.exe
Good luck!
No luck
Misterjunky said:
During your unsuccessful flashing of the google edition rom you have lost ROOT and the custom and or stock recovery.
That is why you cannot go into recovery mode.
You are lucky that the .pit file did not flash, you could have ended up with a brick (unusable phone).
The .PIT file is the partition information table, if that is changed or damaged you would need to send
your phone to samsung or other phone repair shop to get it fixed.
What you need to do is to download and Odin flash the stock-rooted i9505 rom which can be found here:
(Removed link due to under 10 posts)
This rom is pre-rooted and you will be able to get into recovery mode without any issues.
Once this is odin flashed, be sure to make a nandroid backup before flashing other cwm/twrp zip file roms.
The "phone cannot be located" error most likely means that you either do not have the proper samsung usb
driver installed or you need to check the usb cable connections to your computer and phone.
Perhaps use a different usb cable and a different usb port will fix this issue.
Just in case you need it, here is the link for the official usb drivers for the samsung s4 phone:
(Removed link due to under 10 posts)
Good luck!
Click to expand...
Click to collapse
Firstly thank you so much for reaching out to help me with this matter. :good:
Sadly no such luck, running odin 3 v1.85
This is the result I had...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMH1-PRE-ROOTED-DEODEX-SuperSlim.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Going to try again using the drivers you have provided (restarting now)
Still no luck...
Odin v1.85
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMH1-PRE-ROOTED-DEODEX-SuperSlim.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
With no readout on the phone (as if the process never took place)
& using v3.07
Odin v3.07
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMH1-PRE-ROOTED-DEODEX-SuperSlim.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Through all these process only AutoReboot was checked...
The last attempt on v3.07 had the same result as a previous flash in which the process bar appears on the phone in download mode, but fails with the same read out on the device..
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
EvilM0narch said:
Okay where do I start...
I was given this phone from a friend, and it was working fine,
rooted and no problems at all...
Followed this guide to install the "Google Play Edition" ROM >> http://www.technobuffalo.com/videos/how-to-turn-a-galaxy-s4-into-a-google-edition-phone/
All was working perfectly, then in a backup process using titanium backup, the phone crashed...
I'm stuck in a boot loop with only the Samsung Galaxy logo screen.
I can enter Download mode, but not recovery...
Have tried every ROM that I can think would be appropriate to restore but to no avail...
Even tried philz touch recovery, nothing seems to be working...
Odin always reports either write failed or There is no PIT partition.
Have tried writing just the .PIT file from >> http://forum.xda-developers.com/showthread.php?t=2265477
Have tried to recover using Kies, firmware downloads then "Error - F" Phone cannot be located...
The phone gets stuck with a small dot of a process bar in download mode and this read out in the top left of the screen:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: ENABLE
START [224, 1440]
ODIN: FLASH READ FAILURE
I'm at a total loss how to recover this, and if it's even possible to recover?
I would happily send it somewhere for repair, I have no warranty so i expect to pay, but no idea where to send?
Does any one have any advice or solution to this problem?
Much appreciated.
Click to expand...
Click to collapse
Are you definitely using PDA (not Phone) mode in Odin when flashing ROMs? Also are you running Odin using 'administrator' mode if using Windows?
Sent from my Nexus 7 using xda app-developers app
PDA
gsmyth said:
Are you definitely using PDA (not Phone) mode in Odin when flashing ROMs? Also are you running Odin using 'administrator' mode if using Windows?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes 100% sure that I'm selecting PDA and Admin privileges.
Honestly I'm baffled I'm now charging the battery now to ensure the phone has enough to attempt this process again.
The battery icon fails to display a meter... Just an empty battery with a loading circle inside, assuming this is because the phone cannot access the images for the battery charging display? (The display that is present when the phone if turned off and you are charging)
I'm still stumped with what to try here. Any suggestions?
I'm sure if I can get at least back into recovery mode I could resolve it, but with odin failing due to pit each time it's just like banging my head against a wall :silly:
Screen Capture
Attached is a capture of the process using odin
Hope this can help in some way...
Edit: wrong thread
EvilM0narch said:
Attached is a capture of the process using odin
Hope this can help in some way...
Click to expand...
Click to collapse
No pit partition = YOUR PARTITION TABLE IS CORRUPTED. flash stock firmware with pit file in Odin 3.04, untick "auto-reboot", when it "pass", take off battery, inset it, boot into recovery, reset the phone, reboot
Sent from my Galaxy Nexus using xda premium
FAIL
samersh72 said:
No pit partition = YOUR PARTITION TABLE IS CORRUPTED. flash stock firmware with pit file in Odin 3.04, untick "auto-reboot", when it "pass", take off battery, inset it, boot into recovery, reset the phone, reboot
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for this, have tried flashing with the rom that Misterjunky provided (with pit from samersh72) and fail
also tried the EE rom I found on the forum that samersh72 provided (with pit from samersh72) fail
tried flashing just the pit alone... fail
**making sure that "auto-reboot" was unticked**
In each process >> re-partition operation failed?
:crying:
I'm now downloading the EE rom direct from sammobile (Although for some reason I'm sure this device was originally Orange network)
Will update the situation when all has downloaded and I can try again.
Thanks to all for your input on this.
EvilM0narch said:
Thanks for this, have tried flashing with the rom that Misterjunky provided (with pit from samersh72) and fail
also tried the EE rom I found on the forum that samersh72 provided (with pit from samersh72) fail
tried flashing just the pit alone... fail
**making sure that "auto-reboot" was unticked**
In each process >> re-partition operation failed?
:crying:
I'm now downloading the EE rom direct from sammobile (Although for some reason I'm sure this device was originally Orange network)
Will update the situation when all has downloaded and I can try again.
Thanks to all for your input on this.
Click to expand...
Click to collapse
re-partition must work. make sure that you are using the right pit for your variant, unzip it before putting it in pit window in odin
flash your original EE official rom from sammobile
Making sure all is right
samersh72 said:
re-partition must work. make sure that you are using the right pit for your variant, unzip it before putting it in pit window in odin
flash your original EE official rom from sammobile
Click to expand...
Click to collapse
Pit variant I have is from you for my device "i9505", so that would be the correct pit file?
Still waiting on the EE official rom from sammobile to download, as long as all is correct I will try again once downloaded.
Flash MH8 or newer...
In my case it was not possible to downgrade... i think that if you flash a mh8 or higher, after that is not possible downgrade because new bootloaders.
Enviado do meu GT-I9505 utilizando Tapatalk 4
MH8
sanespro said:
Flash MH8 or newer...
In my case it was not possible to downgrade... i think that if you flash a mh8 or higher, after that is not possible downgrade because new bootloaders.
Enviado do meu GT-I9505 utilizando Tapatalk 4
Click to expand...
Click to collapse
Reading more on this it does seem you are right, can you elaborate as to what is mh8?
Is this a specific rom? Reading what I could find it seems it will only allow custom roms on the device or a rom that is MH8?
Can anyone shed some light on this?
Going to download the latest BTU MH8 for UK and give that a try? Hopefully I'm making progress as the MH8 rule would explain why it's not working
EvilM0narch said:
Reading more on this it does seem you are right, can you elaborate as to what is mh8?
Is this a specific rom? Reading what I could find it seems it will only allow custom roms on the device or a rom that is MH8?
Can anyone shed some light on this?
Going to download the latest BTU MH8 for UK and give that a try? Hopefully I'm making progress as the MH8 rule would explain why it's not working
Click to expand...
Click to collapse
be aware MH8 firmware will lock your bootloader, so you will not be able to downgrade.
your problem is in partition table. your solution is with the pit file flashed with your stock firmware.
if it fail, see odin troubleshooting in my thread
samersh72 said:
be aware MH8 firmware will lock your bootloader, so you will not be able to downgrade.
your problem is in partition table. your solution is with the pit file flashed with your stock firmware.
if it fail, see odin troubleshooting in my thread
Click to expand...
Click to collapse
I believe I am already flashed to MH8, but I am not sure.
I have tried flashing the pit located in your sig for my GT-I9505 but it always fails?
Is there something else I am missing or not doing correctly? I have been following each guide and double checking the steps before I try anything.
No matter what action i take the pit flash with the file "I9505_pit file.zip" located here >> http://forum.xda-developers.com/showthread.php?t=2265477
always fails? I have no idea why? Or which steps to take.
Sorry to be such a pain,
EvilM0narch said:
I believe I am already flashed to MH8, but I am not sure.
I have tried flashing the pit located in your sig for my GT-I9505 but it always fails?
Is there something else I am missing or not doing correctly? I have been following each guide and double checking the steps before I try anything.
No matter what action i take the pit flash with the file "I9505_pit file.zip" located here >> http://forum.xda-developers.com/showthread.php?t=2265477
always fails? I have no idea why? Or which steps to take.
Sorry to be such a pain,
Click to expand...
Click to collapse
yes this is the right pit file.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Another machine...
samersh72 said:
yes this is the right pit file.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Click to expand...
Click to collapse
Have tried all except another computer, someone mentioned that an XP based machine works best.
Those are like gold-dust around here, I will try this process on a laptop and see if I can get it to work... That seem to be my best bet for now
Again kudos for all of the help and the quick replies. :good:
All hope seems lost....
After finally trying every method on this PC
(All versions of Odin I could find, all usb ports, original usb lead, kies is disabled, drivers un-installed/re-installed)
And having no luck...
I have had some different results on the laptop;
all other versions of odin I tried (v1.83, v1.85, v3.04, v3.06) just fail;
(again all usb ports, original usb lead, kies is disabled, drivers un-installed/re-installed)
And this read out...
flashing pit and rom > Complete(write) operation failed.
flashing only pit > Complete(write) operation failed.
However on Odin3 v3.07
flashing pit and rom > There is no pit partition
flashing only pit > There is no pit partition
and on v3.09
flashing pit and rom > re-partition operation failed.
flashing only pit > re-partition operation failed
I'm at a total loss now. I have a chance to send it back to cash generator as thats where my friend had purchased it from.
Is it worth doing so?
Any one have any thoughts or suggestions to aid this situation?
:crying:
I guess my only option here as I cannot get it to flash, is to either sell the phone in the state it is in.
Or send it back to Cash Generator to see if they will replace/refund it.
:crying:
samersh72 said:
yes this is the right pit file.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Click to expand...
Click to collapse
Okay so just got my device back from my friend with the Jtag, and this is the report he run for me
===============
= JTAG REPORT =
===============
Open serial port...OK
Connecting to the RIFF Box...OK
Connecting to the dead body...OK
Detected dead body: DETECTED
Set I/O Voltage reads OK, TCK Frequency is OK
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Flashing the dead body...
No Resurrection Data is available for the eMMC Chip with Capacity = 0B
ERROR: Failed use to Resurrection Data for the eMMC Chip with Capacity = 0B
ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
Where can I get eMMC chip repaired?
EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?
bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_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> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).
Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.
Possible not a genuine Note 3?
This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..
Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.
Flashed Rom zip. Note 3 back to health.
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.
If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.
Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?
I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?
I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...
Hello everyone,
I'm trying to flash a stock rom on a Verizon GS5. I say trying because so far it hasn't been working, unless I'm doing something wrong, which I think I am. When I got the phone, it had a Sprint rom flashed to the GS5. The original Verizon IMEI under the battery is clean and verified good with Verizon. There is nothing physically or cosmetically wrong with the phone, it powers on sometimes and randomly restarts. When it does turn on, the Sprint Spark logo comes up, the phone boots up normally and then randomly shuts off, taking a long time to be able to power back on. The only way that it says on is by putting it on Download Mode.
When in download mode, it shows as a G900P,
As far as my understanding goes, shouldn't it be a G900V?
I attempted to flash a stock Verizon rom I downloaded and tried to flash it with Odin 3.04 but it fails each and every time. I have installed the Samsung drivers that I got from the website, I restarted the computer, I restarted the phone but Odin give me a fail error.
Then I tried a newer version of Odin 4.43 but I'm not sure I'm using that one correctly but it's not working for me either.
I left the phone in Download Mode and it has been on for about 30 mins (the longest so far without it restarting on me).
Is there something that I'm missing here? Something else I could try to fix this?
Any ideas? Suggestions?
Any help would be greatly appreciated!!
..
-> It's a Verizon Galaxy S5 Phone I got from eBay
-> It's flashed with the Sprint rom version of the GS5
-> The phone restarts on and off, randomly, unless it is in Download Mode
-> I want to flash it back to the original Verizon GS5 rom.
-> I attempted to flash the phone with Odin 3.09 and rom SM-G900V_VZW_1_20140331185350
-> I get an error message when using Odin 3.09, it FAILS
-> The progress bar in the GS5 phone advances a small amount but that's it.
-> I attempted to use Odin 4.43 with the same rom file but that also fails and I get an error message.
-> I researched on Google before signing up and asking for help.
-> I have read many Threads and Posts on several Forums, and I have also tried many tutorials without any luck.
-> I researched how to use Odin, there is lot's of pictures, easy explanations but that's not it.
-> I found a GS5 stock rom, file name mentioned above.
-> Samsung drivers are installed, phone is recognized by Odin.
1.) Am I using the correct rom?
2.) Which version of Odin should I use?
..
SewerDweller said:
Hello everyone,
Any ideas? Suggestions?
Any help would be greatly appreciated!!
Click to expand...
Click to collapse
Download this version of Odin and extract the folder in the zip.
Make sure you have downloaded the correct firmware, extract the MD5 / tar file from inside the firmware.zip file you downloaded and put it in the Odin 3.07 folder
Start Odin.exe, put your phone in download mode and connect to your PC, if you have Kies installed make sure it is not running, Odin and Kies don't mix.
Once you have the Blue ID.COM indicated, click on PDA, find the MD5 / .tar file wait for teh file check Odin runs then click Start, wait for Odin to finish and your phone reboots.
Guide for Odin use here it is from the S3 but the use of Odin is the same for the S5
It took me a while to get it to turn on but here's what I got from trying ag4751's suggestions.
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANI2_G900VVZW1ANI2_G900VVRU1ANI2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
It's the same thing that I was getting before, I'm sorry if I did not explain myself in detail at first.
I have used 2 versions of Odin 3.09 (which I used on my own and got the above message).
3.07 as suggested by ag4751.
I have used 2 different roms and both fail.
->G900V_VZW_1_20140331185350
->G900VVRU1ANI2-20140919141518
@fffft
To answer your question as to what tutorial I followed, I followed ag4751's tutorial/explanation on his reply. It's basic, just like all the other tutorials I googled.
1.) Put the phone in download mode
2.) Open Odin
3.) Select PDA
4.) Wait for the file check
5.) Click start
and then it fails.
That's what @ag4751 suggested, that's what I tried, that's what I tried before, that's what I'm trying now and all that is failing for some reason.
..
..
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Background
AS of March 27, 2015, the most recent firmware for Note Pro 12.2 international version is the Russian P905XXUAOB1 (with CSC905SERAOB1 and Modem905XXUANA7), Since it doesn't seem that any country is in a hurry to push a lollipop update into this device, I made these files to update the tablet to the latest available firmware. The procedure is designed to achieve two thing: 1- by leaving the bootloader untouched, it is reversible to your current version, if you have the firmware corresponding to your current version at your disposal, 2- it gives you root.
This procedure should not in theory wipe your data but DO MAKE A BACKUP, in case.
And no, it doesn't trip the knox.
Upgrade Procedure
All files that you need are available at the link further down. The are zipped but you should unzip them before using them.
1- Backup everything you have on your tablet
2- Reboot the tablet to the "Download Mode" (by pressing down vol + home key when the device is rebooting, right before you see the first splash logo, then push Up Vol to continue).
3- Run PC Odin v3.09 and load these files (remember to unzip the files after downloading) :
BL: leave empty
AP: AP.tar.md5
CP: CP.tar.md5
CSC: CSC.tar.md5
Leave everything else unchanged and Start.
4- Let the tablet reboot. It will first go to recovery to complete the upgrade and then reboots and initializes your apps.
Note 1: This process should not erase your data but I suggest you do a factory reset yourself (provided you have saved you data somewhere)
Note 2: After the upgrade is complete, the tablet may run slow and get hot for about 20 min because all the apps are trying to get set up and catalog your system. However, if after 30 minutes is is still slow and hot, first try to wipe the data for Google Plus App. If that doesn't work you may want to disable Google Plus, or as a last resort do a factory reset.
Note 3: If you end up doing a factory reset, the tablet will start up in Russian. You can change the language to English at the very first step of the initial set up. After that, go to settings and change the keyboard and input language to English. Then everything will be OK.
Note 4: If you try this out and don't like it, download your old firmware (must match or be newer than what you had before) and flash your tablet back to how it was (you have to do a factory reset after the downgrading).
Root Procedure
If you need to root the tablet, do the following after you finish the upgrade procedure:
1- Install towelroot v3 on your tablet, but don't run it. The app is inside a zip file at the download site and you should unzip it with the password 12345
This is done because some systems flag this app as a virus when it clearly is not. There are two versions there in the zip file. Either one should work just fine.
2- Install SuperSU, but don't run it.
3- Reboot to download mode.
4- Run PC Odin and load ANC3_Kernel.tar.md5 in AP field and start.
5- Let the system reboot. You may get some force closings after the reboot but ignore them.
6- Run the towelroot app and make it rain!
7- Reboot to download mode.
8- Run PC Odin and load AOB1_Kernel.tar.md5 in AP field and start.
9- Let the system reboot.
10- Run the SuperSU app and let it update the binaries the "normal" way.
11- Allow it to disable knox for you.
12- If SuperSU freezes up for more than 5 minutes reboot your tablet and run it again. Everything will be fine.
13- Your tablet is rooted now.
Download Link
https://mega.co.nz/#F!491wSaQa!wxjErs3ZamrmEPKjYVi50A
Hi
My p905 is on p905xxuanh3. Is it ok to use your method? Tnx
vvkuz said:
Hi
My p905 is on p905xxuanh3. Is it ok to use your method? Tnx
Click to expand...
Click to collapse
Yes. Make sure a matching nh3 firmware is available from sammobile.com if you think you may want to go back to your existing rom at some point.
successfully updated & rooted a p905 with your instructions,
thanks for your help.
Any idea if I can flash this rom into a P905M? Thanks in advance
andrew.mackew said:
Any idea if I can flash this rom into a P905M? Thanks in advance
Click to expand...
Click to collapse
No, because 905M has different cellular and LTE bands and the modem is different. If you still feel adventurous and want to try it, exclude the CP tar file when you are flashing. Make sure you have your current firmware available to restore in case you soft-brick your tablet.
najoor said:
No, because 905M has different cellular and LTE bands and the modem is different. If you still feel adventurous and want to try it, exclude the CP tar file when you are flashing. Make sure you have your current firmware available to restore in case you soft-brick your tablet.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I really wish to change, I mean, since Samsung stuck us on 4.2.2 so far.. I just wish, at least to get a minimal improvement.
If I get to merge things to have a P905 rom working on my P905M it would be an achievement in direction to break the P905M rom prison.
It worked!
Now I have the latest firmware into my P905M.
Thanks!
najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Background
AS of March 27, 2015, the most recent firmware for Note Pro 12.2 international version is the Russian P905XXUAOB1 (with CSC905SERAOB1 and Modem905XXUANA7), Since it doesn't seem that any country is in a hurry to push a lollipop update into this device, I made these files to update the tablet to the latest available firmware. The procedure is designed to achieve two thing: 1- by leaving the bootloader untouched, it is reversible to your current version, if you have the firmware corresponding to your current version at your disposal, 2- it gives you root.
This procedure should not in theory wipe your data but DO MAKE A BACKUP, in case.
And no, it doesn't trip the knox.
Upgrade Procedure
All files that you need are available at the link further down. The are zipped but you should unzip them before using them.
1- Backup everything you have on your tablet
2- Reboot the tablet to the "Download Mode" (by pressing down vol + home key when the device is rebooting, right before you see the first splash logo, then push Up Vol to continue).
3- Run PC Odin v3.09 and load these files (remember to unzip the files after downloading) :
BL: leave empty
AP: AP.tar.md5
CP: CP.tar.md5
CSC: CSC.tar.md5
Leave everything else unchanged and Start.
4- Let the tablet reboot. It will first go to recovery to complete the upgrade and then reboots and initializes your apps.
Note 1: This process should not erase your data but I suggest you do a factory reset yourself (provided you have saved you data somewhere)
Note 2: After the upgrade is complete, the tablet may run slow and get hot for about 20 min because all the apps are trying to get set up and catalog your system. However, if after 30 minutes is is still slow and hot, first try to wipe the data for Google Plus App. If that doesn't work you may want to disable Google Plus, or as a last resort do a factory reset.
Note 3: If you end up doing a factory reset, the tablet will start up in Russian. You can change the language to English at the very first step of the initial set up. After that, go to settings and change the keyboard and input language to English. Then everything will be OK.
Note 4: If you try this out and don't like it, download your old firmware (must match or be newer than what you had before) and flash your tablet back to how it was (you have to do a factory reset after the downgrading).
Root Procedure
If you need to root the tablet, do the following after you finish the upgrade procedure:
1- Install towelroot v3 on your tablet, but don't run it. The app is inside a zip file at the download site and you should unzip it with the password 12345
This is done because some systems flag this app as a virus when it clearly is not. There are two versions there in the zip file. Either one should work just fine.
2- Install SuperSU, but don't run it.
3- Reboot to download mode.
4- Run PC Odin and load ANC3_Kernel.tar.md5 in AP field and start.
5- Let the system reboot. You may get some force closings after the reboot but ignore them.
6- Run the towelroot app and make it rain!
7- Reboot to download mode.
8- Run PC Odin and load AOB1_Kernel.tar.md5 in AP field and start.
9- Let the system reboot.
10- Run the SuperSU app and let it update the binaries the "normal" way.
11- Allow it to disable knox for you.
12- If SuperSU freezes up for more than 5 minutes reboot your tablet and run it again. Everything will be fine.
13- Your tablet is rooted now.
Download Link
https://mega.co.nz/#F!491wSaQa!wxjErs3ZamrmEPKjYVi50A
Click to expand...
Click to collapse
Hey mate,
Can you make the same with the latest Lollipop for P905? I wish to flash them into my P905M.. Thanks
andrew.mackew said:
Hey mate,
Can you make the same with the latest Lollipop for P905? I wish to flash them into my P905M.. Thanks
Click to expand...
Click to collapse
Hello from Sao Paulo. Please let us know if you have succeed in installing the italian lollipop on your p905M.
js345 said:
Hello from Sao Paulo. Please let us know if you have succeed in installing the italian lollipop on your p905M.
Click to expand...
Click to collapse
Yep I did. But lost signal.. I am testing a few things..
---------- Post added at 01:13 PM ---------- Previous post was at 01:02 PM ----------
Anyone knows if I can flash a P905 modem into a P905M device?
thanks! successful!:good:
Thank you so much! I've been worried about rooting without tripping knox and this worked perfectly.
One question... If I didn't want to upgrade, could I have just flashed the two firm ware to root?
One of the clearest rooting guides I've used.
Thanks,
Zabben W
zabbenw said:
Thank you so much! I've been worried about rooting without tripping knox and this worked perfectly.
One question... If I didn't want to upgrade, could I have just flashed the two firm ware to root?
One of the clearest rooting guides I've used.
Thanks,
Zabben W
Click to expand...
Click to collapse
No because the second firmware in step 8 should match the existing kernel on your device.
najoor said:
No because the second firmware in step 8 should match the existing kernel on your device.
Click to expand...
Click to collapse
Oh right. That makes sense. Great root guide. If I think about upgrading, I will definitely take a peek at your lollypop one.
Upgrade to P905XXSABQC1_P905BTUABOF1_BTU for SM-P905
Hi All,
Need your help, Tried to upgrade my SM-P905 using ODIN V3.13, using the file downloaded P905XXSABQC1_P905BTUABOF1_BTU. connecting ODIN via USB Cable to the tab. Tried all USB Ports, same issue.
but ODIN unable to move forward with error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2365 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> boot.img
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Please help.
After, and if, aboot and boot are flashed, the rest should get flashed with no issues.
99% of the time this kind failure is either due to a bad USB cable or unnecessary physical movement of the device (which affects the connection) during the flashing process.
So my suggestion is:
1- Make sure you have the latest Samsung drivers installed.
2- Find the best quality cable you have and use that.
3- If the problem persists download another firmware (maybe from another region) and try flashing that.
Hope this helps.
felix_sashi said:
Hi All,
Need your help, Tried to upgrade my SM-P905 using ODIN V3.13, using the file downloaded P905XXSABQC1_P905BTUABOF1_BTU. connecting ODIN via USB Cable to the tab. Tried all USB Ports, same issue.
but ODIN unable to move forward with error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2365 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> boot.img
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Please help.
Click to expand...
Click to collapse