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.
After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.
con2vp1 said:
After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.
Click to expand...
Click to collapse
Well if you can still get into download mode you are still safe.
Does it fail mid flash or can´t even recognize your phone?
Reboot your pc and try again.
It will fail on the ABOOT, and i have tried to reboot my pc and still no luck i have attached my model of the phone
con2vp1 said:
It will fail on the ABOOT, and i have tried to reboot my pc and still no luck i have attached my model of the phone
Click to expand...
Click to collapse
Try this guide. It seems to be the same phone as yours.
If you are trying to go back to 4.3 from 4.4.2 then it won't be possible. You will now have to stay in KitKat only and wait for more ROM for KitKat.
Sent from my SM-N900 using Tapatalk
Did you try flashing with update bootloader ticked? If you tried that already then I think you are going to have to wait for the hk version of kit Kat for your phone to work again.
Or try this..... http://forum.xda-developers.com/showthread.php?t=null
Sent from my SM-N9005 using Tapatalk
odin 3.09 tick Phone boot loader update.
hey_joe said:
Try this guide. It seems to be the same phone as yours.
Click to expand...
Click to collapse
which one should i download the .zip or the .rar and they two different file size
con2vp1 said:
which one should i download the .zip or the .rar and they two different file size
Click to expand...
Click to collapse
Both are same.
Rar is just better compressed. I went with it.
Just an idea make sure reactivation lock is not ticked in settings
Sent from my SM-N9005 using xda app-developers app
rcp27 said:
Just an idea make sure reactivation lock is not ticked in settings
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Its not ticked, i might just have to wait to an HK firmware to update this because any other i have tried is not working and it says PIT FAIL when i try this solution http://forum.xda-developers.com/showthread.php?t=2613374. even though i followed the instructions step by step.
Is there another way to flash my device other than Odin? and yes ADB does not work
con2vp1 said:
Its not ticked, i might just have to wait to an HK firmware to update this because any other i have tried is not working and it says PIT FAIL when i try this solution http://forum.xda-developers.com/showthread.php?t=2613374. even though i followed the instructions step by step.
Is there another way to flash my device other than Odin? and yes ADB does not work
Click to expand...
Click to collapse
Can you screenshot your odin configuration that you flashed and post it here?
FeralFire said:
Can you screenshot your odin configuration that you flashed and post it here?
Click to expand...
Click to collapse
This is the Odin config and after the CSC was only applied the phone says PIT FAIL
con2vp1 said:
This is the Odin config and after the CSC was only applied the phone says PIT FAIL
Click to expand...
Click to collapse
Hmm.
Weird.
Do you know how to use heimdall?
Use it to have a look at your pit file and compare it to the one in the CSC zip. See what all is different.
Or just post your pit here.
EDIT: Just noticed that you have a 16GB version. I don't know how to help you there, man. You need a completely different pit file. One that is designed for 16GB. But since that model was only launched in Hong Kong, I don't think you will find one from outside, unless somebody can make one specifically for you. I have been trying to learn to do that, but as of yet, I can't.
Without a proper pit file, your only options are either wait for the Hong Kong Kitkat version or try installing the Sweet ROM.
con2vp1 said:
After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.
Click to expand...
Click to collapse
're using Odin with Note 3 connected to a USB 3.0? if yes, try connecting it to a USB 2.0. already happened to me a few times, and the solution was this. sorry for the bad english.
FeralFire said:
Hmm.
Weird.
Do you know how to use heimdall?
Use it to have a look at your pit file and compare it to the one in the CSC zip. See what all is different.
Or just post your pit here.
Click to expand...
Click to collapse
Well thats an issue because im not sure if this my right PIT FILE for this phone. Because usually it will go smoothly for these manual updates using Odin and this is my first encountering this error. And my fault i didnt backup my ROM which i should have done first before getting excited with this KitKat for my Note 3. That CSC file i got that from this site http://forum.xda-developers.com/showthread.php?t=2613374 and just followed instructions on how to do it, but it will just give me that error when i try to apply that method. But here's the PIT file that i got from that download.
I think its on a wrong region because i got that leaked update here http://www.sammobile.com/2014/01/13...kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and it looks like from Poland? does that matter? because my Note 3 is and HK version?
I have done so many phones rooted them and install custom roms this is the first time it failed on me. And funny thing is its my own cell phone lol
con2vp1 said:
Well thats an issue because im not sure if this my right PIT FILE for this phone. Because usually it will go smoothly for these manual updates using Odin and this is my first encountering this error. And my fault i didnt backup my ROM which i should have done first before getting excited with this KitKat for my Note 3. That CSC file i got that from this site http://forum.xda-developers.com/showthread.php?t=2613374 and just followed instructions on how to do it, but it will just give me that error when i try to apply that method. But here's the PIT file that i got from that download.
I think its on a wrong region because i got that leaked update here http://www.sammobile.com/2014/01/13...kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and it looks like from Poland? does that matter? because my Note 3 is and HK version?
I have done so many phones rooted them and install custom roms this is the first time it failed on me. And funny thing is its my own cell phone lol
Click to expand...
Click to collapse
You gave me the pit file from the zip. I was asking for the one from your phone.
But anyway I found one for the 16GB version somehwere. I am taking a look at it. Will try editing it to fit your needs. Give me a little while.
And yes, it matters, because the pit file determines the sizes of the various partitions. Since yours is a 16GB version, the pit from a 32GB won't work.
View attachment Modded_16GB.tar
Try flashing this tar file. Put it in the CSC part of the Odin.
Though I can't guarantee anything. First time, I am doing anything like this.
FeralFire said:
View attachment 2520563
Try flashing this tar file. Put it in the CSC part of the Odin.
Though I can't guarantee anything. First time, I am doing anything like this.
Click to expand...
Click to collapse
Thanks
Odin just crashed on me while it was on SET PARTITION
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
So first of all, my bad.
I've known for ages that you should never mess with pit files and repartitioning unless you know what you're doing, and although i've been flashing roms for years, I've always followed this advice. Until now.
I have an SM-N9005 and I recently flashed 5.0 saudi arabia rom (N9005XXUGBOEA). It was ok at first but it just wasn't playing nice with my LG G Watch R (constant disconnections, requiring reboots) and that was driving me crazy, so I asked around and some dude told me he had the same problem until he flashed the hong kong rom. So I did that, and odin failed. Then I read the rom needed a pit file to work, and it was late at night already so I must have been tired and I just quickly found HLTE_HKTW_OPEN_16G.pit and flashed it with N9005ZSUGOF2_N9005OZSGOF2_N9005ZSUGOF2_HOME.tar. My phone isn't even 16Gb! The thing is Odin passed but booting was stuck on Samsung screen. I quickly realized my mistake and found HLTE_HKTW_OPEN_32G.pit and reflashed with THAT, hoping it would work, but that failed in Odin.
At this point, I realize I'm just gonna make the problem worse if I continue bumbling on by myself. Can anyone help a poor imbecile?
You're actually lucky that your phone survived! I was at the same situation some years ago with my s2 and I ended up with a dead motherboard... Anyway, do you remember if you have ever done a pit backup, and if not what is your exact model of note3, is it unbranded or not, how many storage does it have etc... As your phone is just stucking on samsung logo, I'm pretty sure its fixable...
Sent from my SM-N9005 using Tapatalk.
Sgmaster said:
You're actually lucky that your phone survived! I was at the same situation some years ago with my s2 and I ended up with a dead motherboard... Anyway, do you remember if you have ever done a pit backup, and if not what is your exact model of note3, is it unbranded or not, how many storage does it have etc... As your phone is just stucking on samsung logo, I'm pretty sure its fixable...
Sent from my SM-N9005 using Tapatalk.
Click to expand...
Click to collapse
Mine is SM-N9005 and unbranded with 32GB, bought from germany. I've never done a pit backup.
I was stuck on samsung logo after flashing the first pit. After flashing the second pit (at the time I thought it would fix the problem, since the first pit was obviously wrong at 16G, and the second pit was 32G) it's now just giving mea "Firmware upgrade encountered an issue" screen. Kies refuses to recognize it (telling me it doesnt support this model) so kies recovery is out of the question.
I was about to try flash the saudi arabia 5.0 rom that I had before in hopes that it might just work again, but I doubt that's all it would take, and I don't want to make the problem worse.
Did yo tried to install a recovery a flash a rom zip?
This PIT help me alot...
HyperShad0w said:
Mine is SM-N9005 and unbranded with 32GB, bought from germany. I've never done a pit backup.
I was stuck on samsung logo after flashing the first pit. After flashing the second pit (at the time I thought it would fix the problem, since the first pit was obviously wrong at 16G, and the second pit was 32G) it's now just giving mea "Firmware upgrade encountered an issue" screen. Kies refuses to recognize it (telling me it doesnt support this model) so kies recovery is out of the question.
I was about to try flash the saudi arabia 5.0 rom that I had before in hopes that it might just work again, but I doubt that's all it would take, and I don't want to make the problem worse.
Click to expand...
Click to collapse
1. Flash via ODIN the latest firmware always for the CSC (region code country) of your device without PIT files (don't play with them). Pit file is used only for re-partitions.
2. Flash better via ODIN Poland firmware if your device is from germany. But without .PIT files like in the pic attached.
Claudio67 said:
Did yo tried to install a recovery a flash a rom zip?
This PIT help me alot...
Click to expand...
Click to collapse
No, I didn't, but I did read that that's what you're supposed to do, maybe? Flash TWRP and then transfer zip to the ext sd. But I'm not sure what zip I'm supposed to flash. Any stock rom?
And what should I do with this PIT?
Thank joku I will try what you said and report back.
Well last pit you used was for hong kong note3 16GB I supposed... "HLTE_HKTW_OPEN_32G.pit and reflashed with THAT, hoping it would work, but that failed in Odin"
Try Joku's solution and check if it works, if it was my device I would also try to flash the pit, and then I will try to flash stock from odin or if it fails a recovery with any sm-n9005 rom zip
Well I flashed Poland rom seemingly successfully (no errors from ODIN) but it's now stuck on Samsung screen again. Which I guess is an improvement! Any tips on what I should try next?
Try factory reset from stock recovery
---------- Post added at 02:16 PM ---------- Previous post was at 01:52 PM ----------
PS If you flashed Lollipop in my experience take alot to boot, 7-10 min
It worked!! Factory reset from stock recovery and a couple of reboots and it's back to life! Thank you all so much!!
Flashed Phoenix,used several days,suddenly wifi disconnected then in a few seconds connected again,it looped and I rebooted to find wifi isn't working at all,stuck at opening and grey button.
Then I flashed back to morphose,still the same.
So I flashed via Odin the latest Chinese official firmware(ZC???OH2) with 11G pit.This time I got about 15 mins of stable connection.After that the problem occurred again,exactly the same.:crying::crying:
Below is what I have done:
Pressing around the sdcard (it is said to be where the wifi chip is located,and it maybe caused by poor contact)
Reboot a thousand times
Changing kernel(kingz,stock,voltaqe)
Wiping cache and Dalvik
Mortifying build.prop to ro.securestorage.support (maybe not exact)from true to false(said to be a solution)
Forgot to mention :
1.the firmware was a repair firmware(five .md5 files)
2.in that firmware not only wifi but also Bluetooth fails to open
Download the latest single tar.md5 file from sammobile.com or updato.com and flash again. Don't forgot to perform a factory reset from stock recovery before letting the stock ROM boot for the first time.
audit13 said:
Download the latest single tar.md5 file from sammobile.com or updato.com and flash again. Don't forgot to perform a factory reset from stock recovery before letting the stock ROM boot for the first time.
Click to expand...
Click to collapse
Thanks for your reply
Should it be 8gb pit or 11gb?
And should it be my region or just the latest firmware no matter from where?
Flash the version for the region that the phone was made for.
Pit file is not needed unless Odin can't read the phone partition information.
audit13 said:
Flash the version for the region that the phone was made for.
Pit file is not needed unless Odin can't read the phone partition information.
Click to expand...
Click to collapse
Sorry for bothering again,but i found it was made for Europe.On updato there seems to be no region "europe",only Germany.So which one shall i flash?
Thanks in advance☺
You can try one for Germany. If it is not made for your phone, Odin will halt the flash process.
audit13 said:
You can try one for Germany. If it is not made for your phone, Odin will halt the flash process.
Click to expand...
Click to collapse
I began to wonder if it is correct that the device is European,for it was bought in offical China mainland market?But imei also showed that?
I am such a noob at coping with this kind of weird issue
Anyway i will download both ones and give a try in several days,the download speed is rather slow from updato:crying:
Sent from my Samsung Galaxy S4 using XDA Labs
Wait, if it was purchased in China, it's probably made for the Chinese market and will need the firmware version made for one of the Chinese carriers. Odin will not flash non-China firmware on a made-for-China phone.
audit13 said:
Wait, if it was purchased in China, it's probably made for the Chinese market and will need the firmware version made for one of the Chinese carriers. Odin will not flash non-China firmware on a made-for-China phone.
Click to expand...
Click to collapse
Attachment is my imei searching result,it is shown made for Europe.Besides,I remember flashing other region firmwares and booted normally
And with China baseband I have very bad signal but after flashing other ones it is far better...so I guess it might be a phone wrongly sent to China market or something like that?
The connection to updato is so unstable that I still haven't finished downloading?
Edit:screenshots removed
Boot into download mode and confirm that the phone is a gt-i9500. If it is, flash the latest ROM from sammobile.com or updato.com for the 9500. You'll probably be okay with any ROM from Europe.
Don't flash with a pit file as a pit file is only needed if you need to re-partition the internal memory for some reason or Odin cannot read the phone's partition information.
Edit your post to remove your imei too.
audit13 said:
Boot into download mode and confirm that the phone is a gt-i9500. If it is, flash the latest ROM from sammobile.com or updato.com for the 9500. You'll probably be okay with any ROM from Europe.
Don't flash with a pit file as a pit file is only needed if you need to re-partition the internal memory for some reason or Odin cannot read the phone's partition information.
Edit your post to remove your imei too.
Click to expand...
Click to collapse
No,still no luck at all,wlan still does not work...Whats more in germany firmware i also get "com.android.media has stopped"
This is killing me,my network provider uses TD-SCDMA for 3G,but i9500 don't support that,so i can only use EDGE network,which is extremely slow.Anyway maybe I'll get another phone next month:victory:
audit13 said:
Boot into download mode and confirm that the phone is a gt-i9500. If it is, flash the latest ROM from sammobile.com or updato.com for the 9500. You'll probably be okay with any ROM from Europe.
Don't flash with a pit file as a pit file is only needed if you need to re-partition the internal memory for some reason or Odin cannot read the phone's partition information.
Edit your post to remove your imei too.
Click to expand...
Click to collapse
Finally discovered something new.I am on miui8,when charging to 100％ wifi connects,and it wont disconnect even unplug the cable until you do a reboot!Dont know if it works on other roms,but it does throw new light on the issue.
But...how does this happen?
This is very strange. I've never come across this situation with any phone.
audit13 said:
This is very strange. I've never come across this situation with any phone.
Click to expand...
Click to collapse
Thank you!It is said that Wifi and bluetooth are on the same chip,so if bluetooth is now always working even wifi is broken then it cannot be a hardware failure,can it?
It could be a hardware failure but now I'm not sure since you got it to work on a custom ROM.
audit13 said:
It could be a hardware failure but now I'm not sure since you got it to work on a custom ROM.
Click to expand...
Click to collapse
After testing for an afternoon I discovered:
Wifi will be unable to use the moment battery drops to 81%,it doesnt turns off,but simply shows no item in the list.
If I plug the charger and restart wifi,then it works properly.
If I restart wifi without charging,wifi will be stuck and I have to charge then reboot the phone to get it on again.
Wow, this is even more strange.
Do you have a cell repair shop that can diagnose it for you?
audit13 said:
Wow, this is even more strange.
Do you have a cell repair shop that can diagnose it for you?
Click to expand...
Click to collapse
Yeah,but i'd rather get a new phone if it takes much time or money to repair it.The phone is still my daily driver,though i love it,it is indeed out of date,plus the problem.Getting something like a Redmi 5A might be a better choice?Moreover the rom is not that stable,battery life is also poor,but i dare not flash another rom for fear that wifi gets totally broken.
Thanks again for your time?
In this case, have you looked into getting a used motherboard?
I'm not sure where you are located but there is a big market in my city for used phones. When I need a motherboard, I look for people selling phones with smashed screens and working internal components.