Extremely sorry to post this thread again - actually I referred all the threads in XDA Developers Forums but though a few of them matched my requirement but it was closed since 2013 - hence reopening again...
I have a Samsung GT-P1000 - Made in Korea (I don't live there - live in India though) - FCC ID: A3LGTP1000 - S/N: R2DB129469E
I will provide complete details to make it coherent to you...
CURRENT STATUS -- Soft Bricked (Symbol: A mobile - A yellow triangle with exclamation - A desktop) - (The only thing I see in the tab now!!!)
BEFORE -- Android 2.3.3 Gingerbread, no mods (no root, no custom boot-loader, etc...) -- Complete Original Tablet
What I tried to do --
Install Android 6.0.1 Marshmallow (Following this guide: https://www.droidthunder.com/galaxy-tab-gt-p1000-android-marshmallow-rom/) but soon failed in the rooting step itself, precisely, while installing cwm13...
Now, what I want to do --
After some research, which I must have done earlier, not sure, but maybe people are trying to say that installing Android 6.0.1 Marshmallow is not possible... I did not go deeper...
Anyway, I thought we will revert back to what it was... to Android 2.3.3 Gingerbread...
The problem I face doing this --
To install Android 2.3.3 Gingerbread back I used,
-- Odin3_v1.83
-- And the PIT, PDA, and Phone files are here (https://drive.google.com/drive/folders/1CLrfcUdk-oZ1N6ZZ90LbDCdMW5KYkHnV?usp=sharing) - (I got these while referring to a YouTube video:
)
-- And also installed the USB drivers (updated)
And then, following the above YouTube video, I came up with this, (After connecting the device with the PC - after around 15 mins the brick screen appears - It shows a yellow color port in odin - and I start), And stops after this log,
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Then I switched the ports aswell, and the only difference from the above error is the id changes from 7 to 6...
Also, tried with Odin_v3.07, Odin_v3.13.1, Odin_v3.09, Odin_v3.12.3, but the same logs...
And then, started researching this error but no answer was up to my requirement (there are same threads in this forum but the answers for them did not work for me)
Any help would be highly appreciated,
Thank You
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
It_ler said:
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
Click to expand...
Click to collapse
Thank You for replying @It_ler , this was my 1st question in this forum and waiting since a month or more, I am glad you put your precious time in this thread.
I am new to this forum, and I see you are pretty experienced in here, I would really really appreciate if you can help me gather more minds into this. I have memories linked with this tab, and all these days I have been eagerly waiting for a reply.
As you said, to check the re-partition in Odin, I see that it automatically gets checked once I start flashing, but the logs remain the same...
Related
Hello, I have a 10.1 that runs on Verizon 4G here in the states. I'm familiar with rooting, as I have done it on other devices, but this was different. I had a update.zip that I used to get back to working condition until I can find the fix.
My model number is SCH-I905
I was in the process of odining the "[stock rom][3.0.1] P7100BUKDF + bootloader unlock" by chainfire. For some odd reason, I keep getting this error.
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
Click to expand...
Click to collapse
I either need to figure why this is not working, and finsh the bootunlock, and proceed to root from there.
If anyone can please help me fix this problem I'd be greatly appreciated. I fly out in a matter of hours and would like to have this fixed by then.
Why are you flashing that version? It's supposed to be for the Galaxy Tab 10.1v (7100, not SCH-I905)
What you want to do is root your device and change your recovery for CWM (stock ROM), just that, right?
If that's what you want, check this thread: http://rootzwiki.com/topic/2242-root-recovery-galaxy-tab-101-lte/
That thread is a little old, but it looks like still works for HC 3.2. If you want a newer version of CWM, don't flash the recovery from the previous link, instead download it from here: http://droidbasement.com/db-blog/ and flash it via Odin.
And have this threads at hand in case something goes wrong
http://forum.xda-developers.com/showthread.php?p=16812034
http://forum.xda-developers.com/showthread.php?t=1205639
Curses all these different verisons. I already flashed SU and flashed CWM via rom managee. Is that the equivilent to what you posted?
Sent from my GT10.1
How did you flashed SU?
I don't have the verizon tablet, but I think that the CWM provided by ROMManager is only for p4wifi, maybe they change it. Anyway, if everything is working fine, then leave it like that. But I prefer flashing cwm with Odin or a flashable (via recovery) zip.
I used this method:
http://forum.xda-developers.com/showthread.php?t=1657758
Root appears to be working, I know I installed root uninstaller and it did grant it access upon opening.
EDIT: Solution for anyone having the same issues I saw below: Step 3, here:
http://forum.xda-developers.com/showthread.php?t=2281949
I'm not deleting the post since someone else may find this useful unless the mods think this post is noise. I do have one questions for the community: I would like to get to 4.4 and ideally, rooted. Does anyone with one of the first Verizon Note 2's have an experience similar to mine or advice on which route to take? Or should I just stick with OTA and forget root?
I need help getting my phone working. My original goal was to get a modified stock 4.4 ROM + root on my phone. My phone was 4.1.1 until I began this process. I tried to root via exynox, that failed, but using CF-Auto-Root (CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.tar) worked. I added CWM, wiped data/cache, and tried to install this kernel: http://forum.xda-developers.com/showthread.php?t=2607652 and this ROM: http://forum.xda-developers.com/showthread.php?t=2765021. Similar to some of the messages in the ROM thread, I was stuck at the red screen. I followed krowley3's strategy here: http://forum.xda-developers.com/showpost.php?p=52982544&postcount=41, I Odin'd back to 4.1, unlocked the phone again, got to 4.3, ran saferoot, tried to flash to 4.4, that failed updating the firmware - failed to write sboot.bin.
I tried the suggestion in this thread: http://forum.xda-developers.com/showthread.php?p=39299305 using the VRALJB update to Odin a new PDA. I did get this within the first month of release and didn't take any OTA, so per the warning, I used that version. No luck. Per advice in a thread I'm trying to find again, I Odin'd this PIT: http://www.mediafire.com/download.php?05cj895zu3tls7z, which worked, tried to Odin the bootloader, but that fails at sboot.bin and says: Complete(Write) operation failed.
The status of my phone: it boots into recovery and I can install 4.1.1 stock. It still fails at the sboot when I try a bootloader. When I try to load the firmware, its stuck at the black screen that says "samsung galaxy note 2" and doesn't continue.
In trying to debug, I opened CASUAL-SuckItVerizon-Injection9 while it was loading (to see if it would spit out any logs) and it did something odd: it when I'm on the black screen, it keeps saying 'connected' and 'disconnected' and the adb server connects and disconnects. I'm not familiar enough with debugging these things to dig further. I can't abb to the phone via command line on Windows 7. When I go to Odin mode on the phone, it says:
Product Name: SCH-I605
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
KNOX WARRANY VOID: 0
AP SWREV: A2
Click to expand...
Click to collapse
I'm reading up on this one: http://forum.xda-developers.com/showthread.php?t=2690033, but I'd REALLY appreciate any advice you can give me. At this point, I want a working phone, rooted and at 4.4 (or 4.3) are nice-to-haves.
Sorry if I'm missing something obvious in the stickies - I'm getting stressed right now.
Ok so I bought this Samsung S6 Edge here in Italy for my wife (the phone model is SM-G925F, carrier free). Yesterday I downloaded and flashed with Odin the last firmware available for my country (5.1.1) but unfortunately this firmware doesn't have the Traditional Chinese language in it (my wife is from Taiwan). So I tried to downloaded a firmware of another country hoping that I could get more languages (I downloaded the Malaysian firmware 5.1.1, *maybe* that could have more asian languages in it). Anyways, I tried to flash this firmware with Odin but near the end it failed on the "hidden.img" file (luckily, flashing again the italian firmware recovered the phone, no brick). Searching on this Forum I read some people suggesting to delete the "cache.img" and "hidden.img" files from the firmware archive and this should solve the "hidden.img" error on Odin. But before doing this I need some clarification:
- Why do we need to delete those files from the (official) firmware archive? What are they for and why they are there if we can delete them safely? Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
- In case I need to delete those files, is it better to use Total Commander (like someone said) or the Unified Android Toolkit? Will this "custom" .tar firmware trip KNOX on my phone (I read some people had this problem)?
Thanks!
DDJ75 said:
Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
Click to expand...
Click to collapse
Also I'm wondering, deleting those .img files from the .tar will delete also some additional rom languages? As I said I want to try an Asian rom (like Malaysia) in the hope that I can find Chinese language on it... that's the only thing I need otherwise the italian firmware would be fine.
DDJ75 said:
Ok so I bought this Samsung S6 Edge here in Italy for my wife (the phone model is SM-G925F, carrier free). Yesterday I downloaded and flashed with Odin the last firmware available for my country (5.1.1) but unfortunately this firmware doesn't have the Traditional Chinese language in it (my wife is from Taiwan). So I tried to downloaded a firmware of another country hoping that I could get more languages (I downloaded the Malaysian firmware 5.1.1, *maybe* that could have more asian languages in it). Anyways, I tried to flash this firmware with Odin but near the end it failed on the "hidden.img" file (luckily, flashing again the italian firmware recovered the phone, no brick). Searching on this Forum I read some people suggesting to delete the "cache.img" and "hidden.img" files from the firmware archive and this should solve the "hidden.img" error on Odin. But before doing this I need some clarification:
- Why do we need to delete those files from the (official) firmware archive? What are they for and why they are there if we can delete them safely? Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
- In case I need to delete those files, is it better to use Total Commander (like someone said) or the Unified Android Toolkit? Will this "custom" .tar firmware trip KNOX on my phone (I read some people had this problem)?
Thanks!
Click to expand...
Click to collapse
Hi, i´m not an expert in dev or codes, but recently I soft bricked my phone, and I did a lot of research here, and tried almost everything to solve my problem.
In my case, my S6 was stuck on android 5.0.2 with bootloader in 5.1.1 and the stock firmware 5.1.1 for my specific device wasn´t released yet. So I couldn't turn on or get the emergency recovery from Smart Switch.
When I flash the firmware from other variants, the process always fails. So I´ve tried everything to flash a 5.1.1 firmware.
First I removed the hidden, then I try to remove the cache... with more research, One guy said to remove the sboot.bin e cm.bin. I try this and fails too...
Than I remove all the files, (hidden, cache, sboot e cm.bin) and works!
Even if fails in Odin, this doesn´t mean that the file is the problem... Maybe the cable is in bad conditions, or the PC itself... Try more than 2 times to flash the same .tar before discard that solution.
- Why do we need those files? Good question, don´t know either.
You can try to delete 1 and flash, try both and flash. A lot of variables are in this situation.
- I advise you to use Total Commander, very easy and fast.
And man, why don´t you simply try to download the language package? For sure you have this option somewhere, or someone knows how to.
rafaelrgm said:
And man, why don´t you simply try to download the language package? For sure you have this option somewhere, or someone knows how to.
Click to expand...
Click to collapse
Well, on Google Play there's an app called "MoreLocale2" which adds more system languages. Problem is that this app needs root access and I want to avoid that...
simply delete hidden img from framework
How to delete a file from framework pls explain how to acces
Please help! I have the galaxy s6 sprint variant and I can not get this to work. The stock firmware does not have any hidden.img files it hasy system,cache,boot,cm,modem,sboot, and rocovery.img.tar.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PROBLEM SOLVED: Downloaded newer version of Firmware and that worked. I feel super super dumb for not thinking of that sooner. I was following an older guide to unroot/restore to stock and the newest available link was VREUMJ9 and apparently that was too old.
I'm trying to send my Galaxy Note 2 in for warranty. It had accepted 4.3 OTA but I had rooted it afterward. So I went to restore to stock and unroot so I could send it in. I had just recently done another Note 2 (My dads) back to stock without a hitch so I figured it would be no big deal. Except I forgot one minor detail that his phone didn't take 4.3 OTA and still had unlocked bootloader. So I opened up Odin 3.07 and put PIT file in PIT and VRAMC3 firmware in PDA and hit start and the flash failed. Took me a few seconds to realize that I flashed the wrong firmware and should've been VRUEMJ9. I was panicing and downloaded VRUEMJ9 and attempted to flash that and it wouldn't even start the flash just failed right away. Now ODIN isn't even recognizing the phone anymore. Am I totally screwed here? I've been googling furiously and it sounds like maybe cause I selected a .PIT file it may have hard bricked my device? I just instinctively did that because it was required to make it work correctly on the last phone I did just a few weeks ago.
I can still access download mode but ODIN doesn't show anything in COM window. Trying to boot phone normally shows "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again" I've tried repeatedly restarting phone and rebooting PC and reinstalling USB drivers. Is "Software Repair Assistant" something I should try? It sounds like Verizon's version of ODIN? http://www.verizonwireless.com/support/knowledge-base-80201/
Any help GREATLY appreciated. I really really really don't have the money to pay full price for this bricked phone Assuming I can't get this fixed and I just send them the phone as-is what are the chances they even notice? Do they test them?
I managed to get ODIN to recognize the phone using a different computer. Upon attempting to flash VRUEMJ9 in PDA of ODIN this happens: http://imgur.com/2msfTEQ
Firmware update start..
sboot.bin
NAND write start!!
FAIL!
All threads completed. (Succeed 0 / Failed 1)
This happens whether I do just the firmware or firmware + PIT. Flashing PIT by itself will succeed and the phone changes to a message saying something about unsupported software and to turn my phone off and take it to Verizon. But it doesn't seem to change anything cause flashing FW still doesn't work. Almost identical error message using ODIN 3.09 figured I would try a newer version of ODIN.
Edit: After reading some more. It sounds like I might have a corrupted NAND which from what I read is only fixable by replacing MB. Is this true? If so how much would it cost to get repaired if I went to a samsung service center?
Hello Everyone,
I've dug myself into a pretty big hole and am hoping to get some direction to dig myself out of it.
I recently moved to a new apartment, and internet service won't be set up until Tuesday evening. In my infinite wisdom, i decided to "take a crack" at installing a custom ROM on my Verizon Galaxy S4 in order to use the tethering option for free.
I used the instructions at this thread to install Safestrap. So far so good.
I then downloaded CM12.1 from this website. (Please note that this is an external link). This is mistake #1, though I did not know that CM12.1 was not compatible with Safestrap.
When I booted into SafeStrap recovery, I was also unaware that the default ROM slot is the stock slot, and I installed CM12.1 in the stock slot. This is mistake #3. What was mistake #2, you ask? Well, I didn't make any backups.
When I tried to boot into the system in the stock ROM slot, I got an error that SafeStrap was disabled. I then installed CM12.1 in a new slot, and I no longer get that error, but after SafeStrap's boot screen, I get an error that says "Secure Fail: Kernel" and "System software not authorized by Verizon Wireless has been found on your system."
So, I can still boot into SafeStrap recovery, I can still boot into Odin mode, and that's about it. I have heimdall installed on my Mac OS X, and I have a Linux computer as well that I can use to fix this problem.
I also wrote down this information before trying to get tethering for free:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
eMC BURST MODE enabled
ANDROID VERSION: 4.4.2
BASEBAND VERSION: 1545VRUFNC5
KERNLE VERSION: 3.4.0 [email protected] #1 FRI MAR 29 13
BUILD NUMBER: KOT49H.1545VRUFNC5
SE FOR ANDROID STATUS: ENFORCING
SECURE BOOT STATUS: TYPE SAMSUNG
SECURITY SOFTWARE VERSION MDF V1.0 RELEASE 2
So again, this has been a series of errors on my part. At this point, I'd like to "Unbrick" the phone.
Thank you!
I think the best course of action is to odin NC5 from this forum if you want a chance to have your data back if not just download the nc5 tar (just search for it) and find a guide on how to use odin.
Edit: Nvm forgot you used heimdall find a guide to use heimdall but the same files work.
I'd have to agree with whowatchlist. Hands-down, a bootloader-mode (as in Odin) flash will absolutely be your best bet. If you give no ****s about data, or you happen to keep the important stuff on an ext. SD, then just flash your appropiate stock TAR file (NC5 if I recall the OP) via Odin or Heimdall.
Data recovery may or may not be possible, I really couldn't say without more information. Whowatchlist's link/method should be first and foremost. If that's a no-go just come on back and we'll go from there and get you all sorted.
Or since you are already on a locked bootloader, why not consider upgrading to Lollipop? And if you're still set on safestrap, you can try out stang50liter. Just something to ponder. The phone is by no means 'bricked', at least not in the traditional sense, just comes down to where you wanna go from here.
The rest of this post is probably going to be largely irrelevent and/or not needed, but seeing as I'm still new to posting on XDA rather than just lurking around, I'm attempting to be extra super duper helpful to build my rep/credibility and show i'm not just another window-licker with my helmet on backwards...so I wouldn't blame you for skipping the rest.
As I'm not all that knowledgable when it comes to Safestrap due to my faith in the BL being unlocked/exploited someday, take this as more of a general reference if you would.
Judging by your terminology and that ever-so-fun phrase "i'm gonna take a crack at it", I'm going to assume that this (android modding) is a relatively new field in which you've wandered? If so allow me to touch on a few key points. If not, disregard etc. etc.
Every bootloader EXCEPT for the original one the device released with, MDK, are all locked. This includes ME7, MI1, MJ7, MK2, NC5, NG6, NK1, OC1, and OF1. In general, if you attempt to flash over it, even with a stock kernel that's been tampered, tweaked or altered in any way, your phone/ODIN will give you the finger. But kernels boot the system (e.g. the "ROM"). TouchWiz (courtesy of Samsung) roms are very different from AOSP-based roms. Of course Cyanogenmod is AOSP-based. Because a Kernel that will boot CM cannot be flashed, trying to flash and boot a CM rom will only end in gnashed teeth, swearing and possibly holes in walls.
Safestrap is a middle man. Because it lies on the /system partition, it avoids poking the Kernel-bear, but it boots before the 'ROM', allowing you to select whatever ROM you want to boot.
So if you ended up replacing your stock rom slot with CM12, I can only imagine you essentially ended up attempting to flash your actual partitions instead of a safestrap container, and following that, the locked BL NOPE'd at the Kernel in the zip, and made you quite the unhappy camper. That's my current theory anyway.
If so, there are options. There's always options!
Anyway if you need help or clarification on anything, or have any other questions just hollar back! Thread or PM works (so I don't clutter the forums with walls-of-text like this.) Hell, I'm in a good mood today, I'd even do a Skype step-by-step walkthrough or something lol.
@whowatchlist / @Atomicmuffin, thank you both for the helping hand.
First, I'm glad to hear that the phone is not bricked in the traditional sense.
Secondly, I don't care about the data. I would just like the phone back to a working state and, if possible, I'd still like to flash something on it.
Thirdly, @Atomicmuffin, that "wall of text" was incredibly helpful.
I'm going to try some of the links that you guys pointed me to, and see what transpires.
My apologies for not getting back on this thread sooner. Unfortunately, there were a lot of changes at the startup I work for this week so it's been a rough ride.
Thank you both - I'll be back with updates.
It's alive! Hey everyone. I just wanted to let you know that the phone is back in operation.
And, the thread that you linked me to (http://forum.xda-developers.com/showthread.php?t=2776189) also helped me understand that I need to use Safestrap, and then only with certain ROMs. Thank you both! I'm going to give this another try, now that I know better. Hopefully all goes well, but if not, I know how to press the reset button.
Stvnx7 said:
It's alive! Hey everyone. I just wanted to let you know that the phone is back in operation.
And, the thread that you linked me to (http://forum.xda-developers.com/showthread.php?t=2776189) also helped me understand that I need to use Safestrap, and then only with certain ROMs. Thank you both! I'm going to give this another try, now that I know better. Hopefully all goes well, but if not, I know how to press the reset button.
Click to expand...
Click to collapse
Hey that's awesome man, glad to hear it and i'm glad my ramblings helped you out! Haha, sometimes I tend to over-ramble and don't know where the line is between helpful and annoying, but what I do know however, is the feeling of being stuck in a spot like that. Weren't no wall-o-texts in my early days. Would have saved me a lot of stress (like when I got cocky and accidentally flashed the wrong firmware, leaving me hard bricked.) All I ask is to just pay it forward!
And Read! Read! Read! Thankfully most people who release stuff on XDA care enough to post massive textwalls that dwarf mine with instructions to keep you on track. So even if you've read enough to recite whatever it is in your sleep....keep reading til you can do it backwards. In a foreign language. And in sign language. Simultaneously. Then you should be good to go!
As a general rule of thumb, I'd suggest sticking with reputable websites like XDA and AndroidFileHost at least until you get familiar, to help avoid blunders like this. There's a lot of misinformation out there in the world beyond, and even more window-lickers who do a one-click root and think they're hot stuff enough to take take their helmet off and start teaching other window-lickers, haha. But I digress...
Safe travels man! And If you got questions just let us know! Oh I almost forgot, so what'd you decide? Gonna stay NC5 and SafeStrap it again?
Edit: A GREAT starting resource is http://xda-university.com
Atomicmuffin said:
Hey that's awesome man, glad to hear it and i'm glad my ramblings helped you out! Haha, sometimes I tend to over-ramble and don't know where the line is between helpful and annoying, but what I do know however, is the feeling of being stuck in a spot like that. Weren't no wall-o-texts in my early days. Would have saved me a lot of stress (like when I got cocky and accidentally flashed the wrong firmware, leaving me hard bricked.) All I ask is to just pay it forward!
And Read! Read! Read! Thankfully most people who release stuff on XDA care enough to post massive textwalls that dwarf mine with instructions to keep you on track. So even if you've read enough to recite whatever it is in your sleep....keep reading til you can do it backwards. In a foreign language. And in sign language. Simultaneously. Then you should be good to go!
As a general rule of thumb, I'd suggest sticking with reputable websites like XDA and AndroidFileHost at least until you get familiar, to help avoid blunders like this. There's a lot of misinformation out there in the world beyond, and even more window-lickers who do a one-click root and think they're hot stuff enough to take take their helmet off and start teaching other window-lickers, haha. But I digress...
Safe travels man! And If you got questions just let us know! Oh I almost forgot, so what'd you decide? Gonna stay NC5 and SafeStrap it again?
Edit: A GREAT starting resource is http://xda-university.com
Click to expand...
Click to collapse
Thanks for that awesome resource @Atomicmuffin. I haven't decided what route to take now that I've got the phone working. My baseband now reads NG6, so and all I really want is the ability to use the phone's hot-spot feature. I'll look into that a bit more.
xxxxxx
link5505 said:
I've been trying to put the stock nc5 file on my s4 with odin but it keeps failing, what gives?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What does the phone display when this happens?