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
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.
Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Hundsbuah said:
have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click to expand...
Click to collapse
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?
Contruk27 said:
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?
Click to expand...
Click to collapse
Did you try it with different Odin versions?
Pierre118 said:
Did you try it with different Odin versions?
Click to expand...
Click to collapse
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!
Contruk27 said:
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!
Click to expand...
Click to collapse
No problem. Let us know the result.
I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...
ultramag69 said:
I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...
Click to expand...
Click to collapse
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...
Contruk27 said:
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...
Click to expand...
Click to collapse
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....
ultramag69 said:
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....
Click to expand...
Click to collapse
It's going to be difficult that someone has it, since most people prefer 1 file roms. I will pray to sammobile haha
I'm not an expert, so I don't know if it's something critical for the phone (data mounted) to boot, but whenever I had this problem before with my previous phones, I was able to fix it by flashing a sock rom with odin or going back to the previous rom. So, my main concern now is that after all the flashing I've made, I still can't mount \data.
Hello all,
I had a galaxy note 3 (SM-N9005, 16GB Hong Kong Version) with last updated to KitKat(OTA). For the first time, i decided to take the risk of flashing the ROM manually and downloaded the Poland Lollypop Rom N9005XXUGBOA5_N9005XEOGBOA4_N9005XXUGBOA1_HOME.tar.md5 and flashed the phone using Odin with only Reset and Reboot flags checked. It failed at ext Image error.
After some reading i find out that HongKong have different partition structure and hence require to flash with a pit, i downloaded a pit file
(SM-N9005_HLTE_HKTW_OPEN_16G) from forums here and tried to re flash it with Reset, Reboot and Repartition flags and this time it stucks at error
PIT Fail : Total Sectors (38777344). I can now only boot up in download mode.
Can anyone let me know is there any chance, whether i can bring my phone back to life.
spandita said:
Hello all,
I had a galaxy note 3 (SM-N9005, 16GB Hong Kong Version) with last updated to KitKat(OTA). For the first time, i decided to take the risk of flashing the ROM manually and downloaded the Poland Lollypop Rom N9005XXUGBOA5_N9005XEOGBOA4_N9005XXUGBOA1_HOME.tar.md5 and flashed the phone using Odin with only Reset and Reboot flags checked. It failed at ext Image error.
After some reading i find out that HongKong have different partition structure and hence require to flash with a pit, i downloaded a pit file
(SM-N9005_HLTE_HKTW_OPEN_16G) from forums here and tried to re flash it with Reset, Reboot and Repartition flags and this time it stucks at error
PIT Fail : Total Sectors (38777344). I can now only boot up in download mode.
Can anyone let me know is there any chance, whether i can bring my phone back to life.
Click to expand...
Click to collapse
It sounds like you tried to reflash the HK PIT file - what you actually need is a PIT to suit the firmware you want to flash. If you use the HK pit you need to flash a HK ROM.
Also, make sure you actually pull the battery to get into Download mode. i.e. take out battery, wait 10 secs, then put it in and hold down the keys for DL mode. Restarts don't seem to work properly when flashing BL's and Modems so the physical method is needed.
Start by getting the latest HK version and see if Odin will flash it. THEN look at getting a EU pit file to go with BOA5.
Journyman16 said:
It sounds like you tried to reflash the HK PIT file - what you actually need is a PIT to suit the firmware you want to flash. If you use the HK pit you need to flash a HK ROM.
Also, make sure you actually pull the battery to get into Download mode. i.e. take out battery, wait 10 secs, then put it in and hold down the keys for DL mode. Restarts don't seem to work properly when flashing BL's and Modems so the physical method is needed.
Start by getting the latest HK version and see if Odin will flash it. THEN look at getting a EU pit file to go with BOA5.
Click to expand...
Click to collapse
Thanks for reply!!
Yes, it makes sense. So, i am going to download the Hongkong firmware. Will try it and let you know if i got any luck in bringing it up
spandita said:
Thanks for reply!!
Yes, it makes sense. So, i am going to download the Hongkong firmware. Will try it and let you know if i got any luck in bringing it up
Click to expand...
Click to collapse
I had a HK S3 and had similar problems. Not sure why Samsung makes them so different. I was new to Androids and thought I had trashed my new phone.
But it's a good way to learn - first you find out what has gone wrong and then how to fix it and before you know it, you are on your way to being flash-addicted.
Thank you
@Journyman16 Thank you very much :victory:, i got my phone up again with the hong kong firmware .... I was also looking for pit file for lollipop polland firmware, but didnt find anyone specific to 16gb note...
Can you direct me to some good resource from where i can go through tit bits of flashing? Particularly regarding this numbering system of Android basebands
As you mentioned, i like the whole incident(Learned something new) .... and dont want to gie up on getting lollipop :highfive:
spandita said:
@Journyman16 Thank you very much :victory:, i got my phone up again with the hong kong firmware .... I was also looking for pit file for lollipop polland firmware, but didnt find anyone specific to 16gb note...
Can you direct me to some good resource from where i can go through tit bits of flashing? Particularly regarding this numbering system of Android basebands
As you mentioned, i like the whole incident(Learned something new) .... and dont want to gie up on getting lollipop :highfive:
Click to expand...
Click to collapse
Been a while since I looked at such things but search in Q&A as well as Android Development for things like 'root guide' or perhaps click on the Advanced Search button and look for 'guide' in post headings.
Also as you browse the subjects that interest you there are often links out to tutorials etc. - another reason for always reading a thread before posting.
Good luck on the journey...
Hi. I'll try to be as detailed as possible.
I have been using the Lollipop 5.0.1 I9505XXUHOA7 German ROM that got leaked early last month, and have just had a few niggling issues, like no silent mode.
So, I looked at SamMobile yesterday and found that there are later versions of Lollipop for the S4 that fixed things like silent mode. I obtained I9505XXUHOB7.
However, when using Odin to flash it to my phone, each and every time, it has gotten to the very end of system.img.ext4 (takes about 5 minutes), and then fails at the very end. I've tried a number of things including a different cable and different USB ports, flashing a new recovery and trying to reboot through that, and even obtaining the CSB_signed_Fusion3_EUR_0325_V2.pit file to Re-partition. At this stage, I don't care if I lose files. I keep most stuff backed up. Just really want my phone to be up and running again, and not too sure what to do.
When I flashed the I9505XXUHOA7, it came with Bootloader, PDA, Phone and CSC to use within Odin, whereas any of the newer ROMs don't seem to have anything but the .tar.md5 file to use in PDA.
Any help would be greatly appreciated. Thanks very much.
Mate, when you download the file in Sammobile you only get 1 .tar file.. it comes with everything.. not like the leaked OA7
1. try using the latest odin 10.6 i think, AP to flash Firmware
2. Reinstall drivers to your PC
3. Or try to redownload a firmware again.. latest is OC6... it might be a bad download too..
4. Refrain using .pit file.... no good at all! Specially for official firmware...
I always brick my phone before and i had no issues flashing diff firmwares from diff country
Did you try flashing the OA7 again? The leaked OA7 (4 files + pit) is a service firmware and should fix issues like these (just to make it running again). After success, you should try an other firmware f.e. OB8 (maybe a bad download?)
Bought what I thought was a UK S4 & have been trying to root & load CM, looked a bit more carefully & found it was an AT&T model with i9505 software?
Anyway, after trying many things, I'm going to send it back but I want to wipe the phone first.
This is where the trouble starts as if when it boots into recovery it comes up with the 'System software not auth by AT&T found on phone' .
I've been trying different PIT's to see if that would work (it hasn't) and am trying various ROM's to put it all back to stock so I can wipe it.
I've tried I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 but that came up with an Odin fail & 'sw rev check fail:fused 5, binary:1' on the device?
Am currently downloading a couple of different ROM's but I'm stumbling in the dark - can you help?
Info wise:
FIRMWARE
AP (PDA) i9505xxufnb7
cp i9505xxufnb7
csc i9505chngnd
Phone info gives device type as jfltetmo/jflteatt
knox warranty void 0x1
Bootloader version i337UCUFNB1
Baseband Version i337UCUFNB1
PDA Version i9505XXUFNB7
CSC Version i337ATTFNB1
Andriod version 4.4.2
Root Existance - yes
Build number KOT49H.I9505XXUFNB&
Any other info needed?
Please help!
Cheers
Only time I've heard att non authentic software is cuz the kernel is not stock try flashing stock kernel or redownloading the stock tar and flash in odin again
It is quite common to load I9505 based system firmware onto the I337. The kernel will be an I337 kernel though.
Your boot loader is NB1 so earlier versions of the firmware cannot be flashed. You should return to stock NB1, and that will be sufficient for your purpose, although it is not the latest firmware. See this thread if you haven't already found it.
Thanks guys - that was the thread I've been looking for in the millions here creepyncrawly!
I'd managed to get one of these
AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5
onto the device & booting but it didn't allow me to turn on wifi so I'll get the
ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.rar
and give it a go.
One last question (Assuming that this final bit of software works, what would I need to flash to get rid of the AT&T splash loading screen on bootup? Can that even be done?
Many thanks again chaps!
wow400 said:
One last question (Assuming that this final bit of software works, what would I need to flash to get rid of the AT&T splash loading screen on bootup? Can that even be done?
Many thanks again chaps!
Click to expand...
Click to collapse
It a bit more complex to mod that. I'm not familiar with the specifics on the S4 but on the S2 you had to modify the param.lfs file.