[Q] Unbricking i9506? - General Questions and Answers

Hi,
So I got the i9506 and since I've played around with my i9100 for a couple of years rooted, I decided to root my i9506 too. Before doing so, the phone installed 4.3 via OTA. I've been unrooting i9100 over and over while installing custom ROMs and so forth.
But now as I was trying to root my i9506, a problem struck. As I was flashing the Philz FW, it failed and now I'm stuck with "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Well that's a mighty good idea, but for some reason Kies does not recognize my phone. I googled and and some other people have this problem too and I'm yet to find a solution with Kies.
So I arrived to XDA, once again, and tried looking for a solution. Found this topic and already hoped that I was saved. But either my understanding of the whole thing isn't enough or it doesn't have the solution for me, I just couldn't get my phone fixed.
So now I'm stuck with the "Firmware encountered an issue..." screen and I don't have a way out. Could someone please help me out?
Any help is much appreciated!
PS: I'm from Finland.

I downloaded the stock roms 4.2.2 and 4.3 from sammobile and tried those as well, but no help.
Odin always fails when trying to flash something.

Tried with Odin 1.85 after multiple failed attempts with 3.09.
I always get this log, no matter what I pick as the bolded option:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUBML6_I9506NEEBML1_I9506XXUBMK7_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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
Click to expand...
Click to collapse
Do I need a PIT file and if so, is there a certain file I need or am I supposed to use a tool like PIT Magic?
My phone still says the following so I'm not sure my warranty is voided altogether:
Product name: GT-I9506
Current binary: Samsung Official
System status: Official
Knox kernel lock: 0x0
Knox warranty void: 0x0

Resolved.
I was using another microUSB cable to do the job, but after changing to new white cable that came with the phone, it passed! Now all's back to way it used to be before all the trouble. Even my phone name and all are intact.

Related

[Q] HELP...about to toss my note out the F***ING window

I have an N8000, it came with China software 4.0.4.
I have been trying and trying and trying to flash the Nordic Rom. 4.1.2
No matter what i do, odin fails to flash
i have tried:
Clear data/cache multiple times
installed kies
installed drivers
odin 1.85, odin 1,87, odin 3.07
after numerous fails, i tried rooting with chainfires auto-root
auto root took just fine, so i know odin/my pc can talk to the tab
i have tried debugging on/debugging off
i have since unrooted using SU built in function, and still to no avail
odin window shows the following (odin 3.07)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCMA2_N8000OXXCMA1_N8000XXCLL1_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/003> Added!!
if i dont get this thing off the **** chinese software im going to lose my mind
i am due to fly tomorrow and need to have this setup...can anyone help?
ninjamunky said:
I have an N8000, it came with China software 4.0.4.
Usual question on same old posts .
Is it a genuine Samsung Note 10.1 or a fake/ clone .
ID:0/004> Can't open the serial(COM) port.
reads as possible bad connection wrong cable Kies running not using a motherboard port all the usual fail connect answers
jje
Click to expand...
Click to collapse
ninjamunky said:
I have an N8000, it came with China software 4.0.4.
I have been trying and trying and trying to flash the Nordic Rom. 4.1.2
No matter what i do, odin fails to flash
i have tried:
Clear data/cache multiple times
installed kies
installed drivers
odin 1.85, odin 1,87, odin 3.07
after numerous fails, i tried rooting with chainfires auto-root
auto root took just fine, so i know odin/my pc can talk to the tab
i have tried debugging on/debugging off
i have since unrooted using SU built in function, and still to no avail
odin window shows the following (odin 3.07)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCMA2_N8000OXXCMA1_N8000XXCLL1_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/003> Added!!
if i dont get this thing off the **** chinese software im going to lose my mind
i am due to fly tomorrow and need to have this setup...can anyone help?
Click to expand...
Click to collapse
Calm down.............
1 - Are you saying it is from China or had the China 4.0.4 ROM installed?
2 - Why do you want Nordic Rom. 4.1.2 ?
3 - Can you change the language in the "Chinese software" Because there is a Chinese 4.1.2 firmware that you maybe able to install and change it to english.
.
kkretch said:
Calm down.............
1 - Are you saying it is from China or had the China 4.0.4 ROM installed?
2 - Why do you want Nordic Rom. 4.1.2 ?
3 - Can you change the language in the "Chinese software" Because there is a Chinese 4.1.2 firmware that you maybe able to install and change it to english.
.
Click to expand...
Click to collapse
Update:
first, yes its the real deal and not a clone
N8000 model, was loaded with china rom 4.0.4
since last post, i was able to use kies to update to chinese jellybean
i am still not able to update to a different country rom(i am currently pulling UK rom from sammobile)
latest error code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCMA2_N8000OXXCMA1_N8000XXCLL1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I dont want the chinese rom as i have no interest in QQ, its horribly written services, or government spyware.
i am about to head back to the states and would like access to my google services(which are not installed in the chinese rom)
i buy alot of electronics over here for use at home as some things just aren't available back home(unlocked devices)
i have used this same pc to flash on my P7500, GS2, and even was able to use odin to root earlier(which i haev undone)
i killed kies and all its services
still cant flash a different countries firmware, or at least the one i have, so i am downloading a different one.
the device has been able to update via kies, register, etc
i know the usb is a direct solder to my motherboard, not a daughter board, i have tried 2 ports
its the cable that was in the box(all accessories appear to be genuine), i have also tried my P7500 cable, and my spare charging cable...nothing is working
would i have better luck with mobile odin?
any help...im measuring my departure time in hours at this point
ninjamunky said:
Update:
first, yes its the real deal and not a clone
N8000 model, was loaded with china rom 4.0.4
since last post, i was able to use kies to update to chinese jellybean
i am still not able to update to a different country rom(i am currently pulling UK rom from sammobile)
latest error code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCMA2_N8000OXXCMA1_N8000XXCLL1_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I dont want the chinese rom as i have no interest in QQ, its horribly written services, or government spyware.
i am about to head back to the states and would like access to my google services(which are not installed in the chinese rom)
i buy alot of electronics over here for use at home as some things just aren't available back home(unlocked devices)
i have used this same pc to flash on my P7500, GS2, and even was able to use odin to root earlier(which i haev undone)
i killed kies and all its services
still cant flash a different countries firmware, or at least the one i have, so i am downloading a different one.
the device has been able to update via kies, register, etc
i know the usb is a direct solder to my motherboard, not a daughter board, i have tried 2 ports
its the cable that was in the box(all accessories appear to be genuine), i have also tried my P7500 cable, and my spare charging cable...nothing is working
would i have better luck with mobile odin?
any help...im measuring my departure time in hours at this point
Click to expand...
Click to collapse
btw:
Current Firmware
4.1.2
Baseband N8000ZCCMB1
Build JZO54K.N8000ZCCMB1
trying to flash
Sammobile N8000XXCMA2_N8000OXXCMA1_N8000XXCLL1_HOME.tar.md5
downloading
Sammobile N8000XXCMA2_N8000OXXCMA1_BTU.zip
ninjamunky said:
Update:
I would try mobile odin
jje
Click to expand...
Click to collapse
thanks, ill give it a go, i appreciate someone responding to my call
if anyone thinks of any other advice also happy to hear it
not as familiar with mobile odin, same firmware files or will i download a new one through mobile odin?
Give me ur address and I can wait outside that window.
Sent from my GT-N8010 using Tapatalk 2
aalupatti said:
Give me ur address and I can wait outside that window.
Sent from my GT-N8010 using Tapatalk 2
Click to expand...
Click to collapse
well played...id probably do the same if i weren;t so frustrated at the moment lol
well between these helpful forum members...and of course the "geek god" chainfire...there will not be any flying tablets in suzhou tonight
thanks all

[Q] Galaxy S4 SGH-I337 (Soft Brick) (Complete (Write)/NAND Write Odin Error)

So I was previously running the MF3 baseband on my SGH-I337 (ATT) and couldn't install any custom ROMs until I tried safestrap. I installed the Google Play Edition ROM and it worked successfully, except the WiFi wouldn't turn on. I could have flashed modem files but I was advised multiple times not to do so. Anyways, I was removing the ROM through safestrap and accidentally wiped my system and all its files I think. Now my phone is stuck in a bootloop (constant Samsung logo) and I can't recover with ODIN because I get an error (shown below). Also, I could only find a TAR file which ends with either MK2 or MDL, my phone was previously MF3, could this be the cause of any problem? Any fixes?
Additional Info:
1) I cannot boot into stock recovery, I'm always forced into download mode.
2) ODIN gives the error everytime I try to flash the stock ROM that I downloaded.
3) I've tried flashing the 16GB PIT file with little luck, the operation finished successfully but I'm still not able to flash anything else because:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm quite new to all of this, any help is greatly appreciated. Sorry if I'm leaving out information, just ask if needs be.:laugh:
My i337 is doing the same thing, except I started on mk2. I see tons of folks asking about complete write fail on google, so I know this is a bigger issue that hasn't been identified yet...but when I get this POS working, I am selling it and NEVER buying anything with a locked bootloader (or the AT&T logo) again. I wish I had researched better and chosen a tmobile S4 to use on at&t.
I got the exact same error like you do in Odin with flashing a new PDA / Recovery. Cannot get rid of error messages, status 7, fail in odin and so on, but my phone isnt in boot loop like yours..

[Q] OTA 4.4.2 update failed, Samsung Experience no help, Please help me

I did the verizon pushed update to 4.4.2 today on my SCH I535 S3 which was totally stock with encryption. After the install finished "upgrading apps" it then did a re-boot and asked for my encrypt pin then showed the outline Andy. Then after a couple of vibrations it re-boot again and will continue this cycle until battery is removed. After sitting on the phone for several hours and conversing with Samsung and Verizon they pointed me to Samsung Experience in a Best Buy and if that doesn't work I have to send it to Samsung for re-flash. They said they couldn't get their software to recognize my phone. The guy there recommended using odin to download a stock rom.
I have downloaded odin 3.07 and have downloaded a 4.3 stock rom. I set up odin with auto reboot and F. reset time checked and nothing else. I select the .tar.md5 in the bootloader and here is my odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I535VRUCNC1_I535VZWCNC1_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECURE BOOT: ENABLE
BOOTLOADER AP SWREV: 2
SW REV CHECK FAIL : Found 2 > Binary 1
Please tell me how to recover my phone. I am new to this so give me detail please.
I believe since u pushed the 4.4.2 ne1 update u need to Odin the 4.4.2 ne1 tar file, not the 4.3 file
Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!
4theluvof2 said:
Thanks so much! I tried the 4.4.2 tar file and... it worked. I thought that since the 4.4.2 update is what failed I'd have to go back to the 4.3 but that was clearly flawed thinking on my part. I can't believe that it worked and best of all everything is still there! I still have all my apps and data, as if nothing at all happened.
Thanks so much for your suggestion!
Click to expand...
Click to collapse
No problem!! Glad it worked, hit that thanks button if you don't mind!
SCH-I535
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz
hammadsalik said:
hey did you get back on 4.3 or not???? plz if u did then refer me link plzzzzzzzz
Click to expand...
Click to collapse
No I didn't get the 4.3 working. I did get the 4.4.2 working though. I am not sure how exactly you'd revert back to an older version, Sorry.

Galaxy S3 SCH-I535- Stuck In Odin Mode After Trying To Downgrade To 4.3

Screwed up, need some help. (4.4.2 to 4.3 attempt gone bad)
Hello everyone out there! Long time lurker, first time poster.
So I've had what seems to be a soft brick on my verizon s3 (SCH-I535) and it is time to just lay it out here because (as always) I can't find the fix to MY problem (so selfish I know )
So let's start at the very beginning..
I have had my s3 for awhile now and I ended up rooting the phone to stay on 4.3. The biggest reason for this was to keep FoxFi working (I have no internet where I live and tethering is the only option). Once FoxFi was working for 4.4 I decided to go ahead and update but first I had to unroot which wasn't a big deal. I unrooted and voila! I was on 4.4.2!
Okay so I just tried ThePagel's methosd
When I upgraded, I noticed my FoxFi was VERY slow all of a sudden and being a gamer, I didn't like this one bit! So I thought to myself "Hey, just flash back to your 4.3 file."... as I hear all of your collective heads shaking in disappointment, followed by facepalms, I now see the error of my ways.. Attempting to flash back to 4.3 of course hung my phone up in Odin (It was stuck at SetupConnect I believe) and this led to my soft brick. Bummer...
So what have I attempted? Well I kept seeing this thread pop up, http://forum.xda-developers.com/showthread.php?t=2586319 but it's talking about the OTA for 4.3.... I was 4.4.2. I also attempted to fix the issue via this thread: http://forum.xda-developers.com/showthread.php?t=1840030 and alas, it fails me as well.
Now as far as errors for these trails, let's get down to what I see on my phone and what I see on odin..
When trying the Hero's method, Odin fails with this log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, I get this log: (Under download mode of course)
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
(In grey)
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP (or AP, can't tell) SWREV: 2
(in red)
SW REV CHECK FAIL : Fused 2 > Binary 0.
Right now I am downloading the file needed in ThePagel's fix but it is VERY slow (only dial up and satellite internet I **** you not, out here). When that gets done I will come back here and post the same logs for both the phone and ODIN should it not work.
I see there are a lot of fixes out there for various things but the problem is, I don't know exactly what is wrong with my phone. Of course if I try to turn it on normally I get the yellow triangle so the fact it turns on means it is a soft brick. I have also read a lot of threads talking about custom recovery but I don't know how this works. Does custom recovery get me back into recovery mode? Or is this only for when your phone is rooted. Anyway, I'd love to pick some brains on this matter and maybe someone sees something in the errors that I do not.
I apologize for my ignorance... all I wanted to do was go back to 4.3 and root it to stay there.. if this can not be done and I am forced to stay with 4.4.2, I will do so.. but any advice for either would be a great welcomed sight. Send links to threads and what have you if you don't want to type, other than to call me an idiot, I deserve it for not reading and understanding everything fully before attempting this flash.
Okay I just tried ThePagel's method and this is what I get:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCNC1_I535VZWCNC1_2198062_REV09_user_low_ship.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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, everything looks the same except the last line reads:
SW REV CHECK FAIL : Fused 2 > Binary 1.
So.....what do you guys think?
****UPDATE****
I was able to find a stock, no frills 4.4.2 kitkat and I flashed that. My phone is back working again. Is there a way to delete this thread?
I don't believe there is any way to delete the thread without getting a forum moderator to do so.
Personally I would recommend against deleting it. Better would be using it as a teaching example for others who find themselves in the same predicament, especially since you added how you fixed the issue. It may also help some from making the same error.

Samsung Galaxy note 10.1 GT-N8020 'Downloading... Do not turn off target!!'

HI there.
I have had the GT-N8020 for around two years on contract with a major provider here in Australia.
My wife used it mostly over that time. Myself, I only realised how great a piece of hardware that it is only in the last couple of months since she now has an S5. I have claimed it daily, lighter than my laptop.
It is out of warranty. Samsung has organised a courier to pick it up, I just have to ring courier.
I asked for a costing as it is out of warranty. No reply on that. We will fix it. I have no doubt in that. But at what cost? The lady did not give an answer even after asking a couple of times. That in itself rings alarm bells. Anyway, VOIP, lag and language barriers, very frustrating. I was transferred from my phone provider to Samsung technical support. I did not ring Samsung directly.
I do not wish to send my device away to be fixed if I can fix it myself. I have been wanting to mess with Linux on the device at some point anyway. So here is my opportunity. I am not sure if I can recover my data that is on the tablet which at this point seems impossible.
What have I done so far?......
Researched a bit and ended up here on XDA. Read “Root & Recovery Install Guide” on here.
I a not sure which ODIN N8020 firmware I need, 'touch, ohne touch or stock. The links are dead anyway for my firmware. Could you recommend another location to get usable firmwares.
I installed the USB drivers
Installed Odin3 v1.85 – cycling power I can see my device being added and removed from the log window. All good there
Installed Kies – no version recognises my device
Installed SmartSwitchPC – did not recognise my device
I downloaded SuperSU v2.67
I have left the tablet to go completely flat and turn off. I then plugged in the charger which immediately brings back the Downloading nag screen. Grrrrr.
Will the tablet still charge if left plugged in?
If it cannot charge then sending it away might be my only option.
Are firmwares country specific or can I use any compatible one?
I am hoping it fully charges. When I plug it into the USB port the device will turn off after a few minutes, as it is still low power. Not sure if it can charge via USB. Currently left tablet plugged into charger, tablet is showing the green Android 'Downloading' nag screen.
In ODIN MODE
Product: GT-N8020
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
Samsung Galaxy note 10.1 white colour. 4G and wifi 16gb.
I am unable to get into recovery mode as there is NO 'Home' button on the note 10.1.
I am pretty sure it had 4.4.2 on it.
Thanks
Lee
Ok I found an Australian OPS - Optus firmware.
I flashed the file using Odin and it seems my device has no PIT partition.
There is no PIT partition! eep I guess this is why it stopped booting in the first place.
ODIN output
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020XXUDNK1_N8020OPSDNL1_N8020XXUDNL1_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>
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Now to find a PIT file...
EDIT: Found a PIT file but still have the same issue of no PIT partition.
Tried different versions of Odin with the same result.
Edit2: JTAG - another option I would consider. Researching but any advice is welcome.
Thanks
Leenux said:
Ok I found an Australian OPS - Optus firmware.
I flashed the file using Odin and it seems my device has no PIT partition.
There is no PIT partition! eep I guess this is why it stopped booting in the first place.
ODIN output
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8020XXUDNK1_N8020OPSDNL1_N8020XXUDNL1_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>
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Now to find a PIT file...
EDIT: Found a PIT file but still have the same issue of no PIT partition.
Tried different versions of Odin with the same result.
Edit2: JTAG - another option I would consider. Researching but any advice is welcome.
Thanks
Click to expand...
Click to collapse
My n8010 got same problem, anyone ? any idea?
Answers as posted in post you copied .

Categories

Resources