Related
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line
UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:
Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
How is that going to take away the udc start?
I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.
Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:
Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.
ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.
re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.
I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick
Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...
Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.
Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?
For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.
sm-n900
sm-900 and pit
Hi guys,
I bought my wife a G900I, flashed it to CM12 5.0.1 and had it working no problem for a week. 2 days ago after watching a FB video the phone rebooted and has seen been stuck in the Boot Loop. Nothing, even the stock firmware seems to want to install.
Tried the following:
philz_touch_6.26.6-klte.tar.md5
openrecovery-twrp-2.8.4.0-klte
CF-Auto-Root-klte-kltedv-smg900i.tar.md5
CWM recovery
Even PIT: SM-G900I_16Gb.pit
Did full WIPE, CACHE, Re-Format via TWRP
Tried the following Stock Roms:
G900IDVU1ANK1_G900ITEL1ANJ1_G900IDVU1ANJ1_HOME.tar.md5
G900IDVU1AND2_G900ITEL1AND2_G900IDVU1AND2_HOME.tar.md5
G900IDVU1ANK1_G900ITEL1ANJ1_G900IDVU1ANJ1_HOME.tar.md5
G900IDVU1ANK1_G900IVAU1ANJ2_G900IDVU1ANJ1_HOME.tar.md5
After flashing via Odin (tried 2x original cables, 3x Windows PCs)
I get the following Errors (see attached). Sceenshot is from Odin 3.07, but I tried 1.85, 3.07 and 3.09 on 3 different computers with 2x different original cables plugged into USB 2.0 at the back of the motherboard - same results, no matter which Stock ROM I choose.
Whats interesting, is that after a few boot loops, you get a Samsung Logo and a sound, but only intermittently. One time it even managed booting into the new 4.2.2 Stock Setup Wizard, but within a second the phone just reboots and keeps boot-looping.
I'm running out of ideas and I thing I tried everything possible.
Any ideas?
1) have you tried Kies?
2) are your firewall and anti virus turned off on the PCs?
3) XP, Vista and 7 have a better track record with Odin than 8.
4) have you tried EVERY USB port with EVERY PC (it *can* make a difference)
5) are you running Odin as an administrator?
6) leave the .pit files well alone for now. If a pit flash goes wrong, you have a totally unrecoverable brick.
Sent from my rooted Kn0x0 SM-G900F S5
keithross39 said:
1) have you tried Kies?
2) are your firewall and anti virus turned off on the PCs?
3) XP, Vista and 7 have a better track record with Odin than 8.
4) have you tried EVERY USB port with EVERY PC (it *can* make a difference)
5) are you running Odin as an administrator?
6) leave the .pit files well alone for now. If a pit flash goes wrong, you have a totally unrecoverable brick.
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Hey keithross39,
1) Yes, I have tried Kies. Updated to latest version. It stays on "Connecting" - I can only get the phone in Download mode since I cannot successfully flash stock via Odin.
I also tried Emergency Firmware recovery in Kies, but I don't have the code. Also tried "Firmware Upgrade and Initialisation" When I put in my model (All Upper Case) and serial number I get an error: 'SM-G900I' Does not support initialising
2) All firewalls are switched off (stopped via windows services), Anti-Virus disabled.
3) All 3 computers that I tried (with 3x different ORIGINAL Samsung cables) are Windows 7 machines
4) I tried ALL USB2.0 ports, front and back of the PCs
5) I run Odin as Administrator
Basically, I can successfully flash various roots and recoveries, be it TWRP, PHILZ, CF-Auto-Root. I can even succesfully wipe and install the CM12 + GAPPS. The end result is that I get a boot loop. If you leave the phone for 20 minutes, every once in a while it actually boots, almost to the GUI, but then resets and gets stuck in boot loops again.
Another interesting observation is that when I get into TWRP and try Wipe and Format, I get all kinds of Read/Write errors.. (see screenshots)
I've been running custom roms on my Galaxy S, S2 and S4 for years now, and have been though everything, never managed to brick any phones yet. This time I am still technically in 'Soft Brick', but after trying so many different Stock Roms via Odin I am starting to suspect maybe faulty hardware? I mean when I first got it, I rooted it and flashed CM12 via PHILZ Recovery. It ran beautifully for just over a week. Then I started getting boot loops. And these "add/remove storage" errors in TWRP are making me suspect hardware..
Hmm.......sounds like you're up against it there fella......The only thing I can suggest is to persevere with what you are trying........Most folks here know that if you are having problems Odin flashing, perseverance is the only thing that works. Odin may not flash on the first X number of flashes, but the time after, it will.........
I still maintain that you should stay away from .pit flashes though......They are strictly "last chance saloon" flashes........
Sent from my rooted Kn0x0 SM-G900F S5
artem1 said:
Hey keithross39,
1) Yes, I have tried Kies. Updated to latest version. It stays on "Connecting" - I can only get the phone in Download mode since I cannot successfully flash stock via Odin.
I also tried Emergency Firmware recovery in Kies, but I don't have the code. Also tried "Firmware Upgrade and Initialisation" When I put in my model (All Upper Case) and serial number I get an error: 'SM-G900I' Does not support initialising View attachment 3116279
2) All firewalls are switched off (stopped via windows services), Anti-Virus disabled.
3) All 3 computers that I tried (with 3x different ORIGINAL Samsung cables) are Windows 7 machines
4) I tried ALL USB2.0 ports, front and back of the PCs
5) I run Odin as Administrator
Basically, I can successfully flash various roots and recoveries, be it TWRP, PHILZ, CF-Auto-Root. I can even succesfully wipe and install the CM12 + GAPPS. The end result is that I get a boot loop. If you leave the phone for 20 minutes, every once in a while it actually boots, almost to the GUI, but then resets and gets stuck in boot loops again.
Another interesting observation is that when I get into TWRP and try Wipe and Format, I get all kinds of Read/Write errors.. (see screenshots)
View attachment 3116299
View attachment 3116300
I've been running custom roms on my Galaxy S, S2 and S4 for years now, and have been though everything, never managed to brick any phones yet. This time I am still technically in 'Soft Brick', but after trying so many different Stock Roms via Odin I am starting to suspect maybe faulty hardware? I mean when I first got it, I rooted it and flashed CM12 via PHILZ Recovery. It ran beautifully for just over a week. Then I started getting boot loops. And these "add/remove storage" errors in TWRP are making me suspect hardware..
Click to expand...
Click to collapse
Usually that error in odin means that there is a problem with the partition of the memory , try to flash your original firmware including PIT file for your device.
Try to find a 3 part or test firmware for your device. These firmwares fully wipe (and I think repartition) your phone rather than simply overwriting what's already there........
Sent from my rooted Kn0x0 SM-G900F S5
Where do you find 3 part or test firmware
---------- Post added at 12:31 PM ---------- Previous post was at 11:58 AM ----------
keithross39 said:
Try to find a 3 part or test firmware for your device. These firmwares fully wipe (and I think repartition) your phone rather than simply overwriting what's already there........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Isn't all three included in the Odin Flash-able Full Stock
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
keithross39 said:
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
I cant seem to find any 3 part firmware for T-Mobile anywhere
For 3 part I don't know however sometimes you need just pit file, try asking here: http://forum.xda-developers.com/showthread.php?t=2737448, there is a collection of pit for galaxy s5
Don't look for a "branded" 3 part firmware.....they're generic unbranded (but device specific)......
And *please* leave the pit flashing as a FINAL resort........
Why will a pit flash work when firmware flashes don't.......and if a pit flash fails part way through, nothing short of motherboard replacement is going to unbrick your phone........
Sent from my rooted Kn0x0 SM-G900F S5
qrono said:
For 3 part I don't know however sometimes you need just pit file, try asking here: http://forum.xda-developers.com/showthread.php?t=2737448, there is a collection of pit for galaxy s5
Click to expand...
Click to collapse
Thanks everyone for posting your suggestions. Latest developments:
- Paid for the Raipidgator Premium DL services 'cause I was getting sick of 8-9 hour long stock downloads
- Downloaded 2x more Stock Firmwares for SM-G900I from the XDA and samsung-updates (all official stock roms)
- Downloaded PIT file from the link above. Shame I could only find 1x PIT for the 900I. Anyways, my understanding of PIT is that its just an XML partition table
Tried PIT + Official ROM at the same time - same result (
My buddy recons my Internal Flash is corrupt. I think so too. Evidence is that I can install the CM12 which is 200 odd Mbs, but I can't install the official ROM via Odin and its 1.5Gb... Also I get read/write partition errors in TWRP when doing wipe+format.
What do you guys recon?
R2D2 is sick when PITTIN
R2D2 is sick when PITTIN
artem1 said:
Thanks everyone for posting your suggestions. Latest developments:
- Paid for the Raipidgator Premium DL services 'cause I was getting sick of 8-9 hour long stock downloads
- Downloaded 2x more Stock Firmwares for SM-G900I from the XDA and samsung-updates (all official stock roms)
- Downloaded PIT file from the link above. Shame I could only find 1x PIT for the 900I. Anyways, my understanding of PIT is that its just an XML partition table
Tried PIT + Official ROM at the same time - same result (
View attachment 3117831
My buddy recons my Internal Flash is corrupt. I think so too. Evidence is that I can install the CM12 which is 200 odd Mbs, but I can't install the official ROM via Odin and its 1.5Gb... Also I get read/write partition errors in TWRP when doing wipe+format.
What do you guys recon?
Click to expand...
Click to collapse
keithross39 said:
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
LATEST SET OF ODIN:
Successfully flashed G900IZTU1BOA1_G900IZZT1BOA1_G900IZTU1BOA1_HOME.tar
See Picture:
Interesting that now Odin has 2x sets of COM ports, as if some how PIT flashing did something to the boot loader? Anyways, after successful Odin (finally) I have the same problem - continuous reboots. Sometimes I see the Samung logo, music plays, but it keeps on rebooting..
Any tips how I can find the "finalized" 3 part firmware for SM-G900I? All I seem to find is the .tar 1x piece firmware files (including the one that flashed successfully above..) Would these be the 3-piece firmwares?
http://www.galaxys5update.com/austr...1anc6-original-4-4-2-firmware-restore-unroot/
keithross39 said:
Don't look for a "branded" 3 part firmware.....they're generic unbranded (but device specific)......
And *please* leave the pit flashing as a FINAL resort........
Why will a pit flash work when firmware flashes don't.......and if a pit flash fails part way through, nothing short of motherboard replacement is going to unbrick your phone........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
I flashed pit for my phone many times and my phone still stuck at the first boot screen. It still can get to download mode and flash-able.
I am starting to think it is possible for a phone to be flash able successfully in Odin, but still be hard bricked.
Hard brick = hardware issue......usually unrecoverable
Soft brick = software issue.......*possibly* recoverable.
If your device was hard bricked, it would show NO signs of life whatsoever, no matter what you did to it......
Sent from my rooted Kn0x0 SM-G900F S5
have you tried to start in recovery and wipe data/cache?
keithross39 said:
Hard brick = hardware issue......usually unrecoverable
Soft brick = software issue.......*possibly* recoverable.
If your device was hard bricked, it would show NO signs of life whatsoever, no matter what you did to it......
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
So its possible to be permanently soft brick and unfix able despite odin being able to flash with no errors?
Ok....So here's a simplification of it........
1) ABACADAE_FA
2) ABACADAEaFA
Imagine number 1 as a firmware you are trying to flash.
Imagine number 2 as a firmware already installed on your device.
Imagine the lower case 'a' in number 2 is a bit of corrupt data that is causing your phone difficulties.
When you flash a firmware with Odin, you are OVERWRITING or directly replacing the software on your device, so the data string that goes ABACADAE and FA will be replaced.......The data called 'a' will be left untouched.....and will still be an issue after the flash.
The TEST firmware is different and does things differently. It's designed to test the firmware on a 'pristine' device, one that has ABSOLUTELY NO TRACE of a previous OS remaining that might interact with it and cause issues. To make sure this happens, the test firmware will COMPLETELY erase EVERY trace of a pre-existing OS during the flash thereby removing any trace of corrupt data (the lower case 'a' in my example).
The bottom line is, if you REALLY can't recover your phone successfully with Odin, and a test firmware for your device hasn't been 'leaked', you have 2 options.....
1) get your device JTAG-ged.
2) send it to Samsung for an out of warranty repair.......
Sent from my rooted Kn0x0 SM-G900F S5
@artem1 just had a look at your firmwares link.......at a guess, without attempting to download, I'd say that these AREN'T test firmwares.....but single file, finalised, carrier branded, official firmwares......sorry fella, just going to have to 'dig deeper'........
Just bear in mind though.........A device has to have it's 'test' firmware unofficially 'leaked' and unless that's the case for your device, you may not find it.........
Sent from my rooted Kn0x0 SM-G900F S5
Hello good people at XDA, it's been quite a while since I have had an android phone, and am currently stuck, I reset my SM-G950W ( Canadian S8 ) and I can't seem to flash stock firmware back onto it. I used a .tar.md5 to flash the current one, but can't seem to find a .tar for the stock firmware, and adding the BL/AP/CP/CSC manually from the downloaded packaged result in odin doing nothing or failing. Could really use some help with my expensive brick :3
tutchthesky7 said:
Hello good people at XDA, it's been quite a while since I have had an android phone, and am currently stuck, I reset my SM-G950W ( Canadian S8 ) and I can't seem to flash stock firmware back onto it. I used a .tar.md5 to flash the current one, but can't seem to find a .tar for the stock firmware, and adding the BL/AP/CP/CSC manually from the downloaded packaged result in odin doing nothing or failing. Could really use some help with my expensive brick :3
Click to expand...
Click to collapse
First make sure u put phone into download mode if u trying to flash something with Odin,use sammobile ,samfirm app for PC or updato.com for faster download speed and download firmware for your model ,use latest Odin 3.13.3 and flash it via Odin while your phone is in download mode
Scorpionea said:
First make sure u put phone into download mode if u trying to flash something with Odin,use sammobile ,samfirm app for PC or updato.com for faster download speed and download firmware for your model ,use latest Odin 3.13.3 and flash it via Odin while your phone is in download mode
Click to expand...
Click to collapse
That's what I've been doing
Odin seems to hang after I press start every time ( doesn't freez , just does nothing for al ong time then fails )
I'm using a G950W which is the Canadian model, but as I said every G950W FW I think I find is just not working. Tried admin mone on odin and new usb ports... I was able to flash the Factory Settings rom on there , but can't seem to get anything else
tutchthesky7 said:
That's what I've been doing
Odin seems to hang after I press start every time ( doesn't freez , just does nothing for al ong time then fails )
I'm using a G950W which is the Canadian model, but as I said every G950W FW I think I find is just not working. Tried admin mone on odin and new usb ports... I was able to flash the Factory Settings rom on there , but can't seem to get anything else
Click to expand...
Click to collapse
Is your phone recognized in Odin (blue light)? Did u installed Samsung USB drivers? Try different USB cable ect
Scorpionea said:
Is your phone recognized in Odin (blue light)? Did u installed Samsung USB drivers? Try different USB cable ect
Click to expand...
Click to collapse
Yes to all that, I think I have the issue of finding the correct firmware now though, I was able to flash a couple things to it, but nothing seems to get me back from factory binary
Morning,
I am working on an SM-J327T1. Trying to flash STOCK ROM with Odin. I am not downgrading, and I am not using the wrong firmware (to my knowledge). I have tried multiple Odin builds, multiple firmware sites, USB ports, etc. I keep getting a fail at cm.bin. It’s been over 8hrs and I’m starting to panic a bit lol. Any suggestions on where to go from here?
Thanks,
Captn
Any one of these builds should work as they are from the sammobile website and ensure you are using the latest build of Odin. And flash the rom using the PDA/AP section, make sure auto-reboot is not enabled (reboot the device yourself, if you cannot remove the battery then use vol-down+power to reboot).
https://www.sammobile.com/samsung/galaxy-j3-prime/firmware/SM-J327T1/TMK/ (if your phone is locked to a carrier or you know the original carrier to your phone, it might be best to pick the firmware of that carrier)
This SHOULD work.