Related
Hi, I was following this guide http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide found on http://forum.xda-developers.com/showthread.php?t=1298691.
I got as far as the Installing the ClockworkMod Recovery, when I got to step 8 'Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.' BUT when the phone tried to reboot it gets stuck on the first Galaxy S screen. I could get in to download mode and recovery mode but nothing else. Does this mean my mobile is bricked? What do I do know?
Thanks in advance
You have flashed a rom, not only root your device. And cyanogenmod is not based on samsung firmware.
Think you shold read some more.
But, how long do you wait on the s logo? It thakes some time to boot up first time when catche is wiped.
If you only want to root you shold search for cf root for your stock rom. If you want to go back, you have to download a stock rom. Found att samfirmware.com
Sent from my GT-I9000 using Tapatalk
No not bricked (nowhere near)............ Reflash...
I have read many times that re-flashing will do the trick. If you have download mode, you can flash any rom onto it, i would use odin as it may be the safest whilst you being in limbo. Then if you want to follow a link for CM 7.1 that is both v.entertaining (my opinion) and clear i suggest you click on the link in my sig...
Robert - Sorry I did mean flash as well as root. I waited around 15-20 minutes, isnt that long enough?
Talon - I have tried to re-flash using the guide method I was originally using but get the same problem. To be honest from looking at Odin information on this forum, it has confused me quite a bit (lot of different advice), not sure if I am doing the right thing.
I did make the mistake of jumping into trying to flash & root my phone. Any help of what to do to get my phone to a working state, would be very much appreciated.
@OP: as long as you can put phone in Download mode - it is not bricked.
ALWAYS, you can restore everything by flashing stock ROM with repartition.
If you will not be able to go to download mode - well... then you have something to worry about
spamtrash said:
@OP: as long as you can put phone in Download mode - it is not bricked.
ALWAYS, you can restore everything by flashing stock ROM with repartition.
If you will not be able to go to download mode - well... then you have something to worry about
Click to expand...
Click to collapse
I'm a bit confused, what would be the best way to do that?
Well find stock FW from below, then flash it using the guides..
Generally now days you get 2 files, Pit either 512 513 or 813 (or something similar). And you get a .tar file or other zip type extension and put that in pda. Then flash
you may get 3 files and a pit file in which case you put it in the appropriate places....
Ive written this guide and telling you it is a GUIDE. Wherever you get your files from there should be instructions as to what to do.
For example you may need to do a factory reset before (unlikely but still) More likely is that you will have to disable lagfix, but you shoudnt have to worry about that. Main thing read the guide and follow the guide from where you get the files. The thread you get it from...read the first and last 5 pages, more if you want to be safe.
Now files, i have links to stock FW below, guide are usually present within them. If not read the thread, but also read the thread and search th thread for answers or the section or the SGS forum.
IF before you were on 2.2.x - try some Froyo from sammfirmware. If you were on Ginger - try Click
Of course, you can search for EAzyBase... but it is more advanced, start from the basics...
OMG, there are tons of tutorials and how to's in here about flashing and rooting phones... who uses heimdall? get Odin for flashing:
1. Install KIES for drivers (you might already have done this).
2. Get a rom from samfirmware/sammobile, I recommend JVP because it has gingerbread bootloaders: http://www.sammobile.com/threads/17-Samsung-I9000-Galaxy-S-Firmwares
3. Get Odin (sorry I coudn't find a link)
4. Get your phone in download mode (VolDown, Home, Power).
5. Connect your phone to PC with USB cable.
6. Set the PDA, CSC and MODEM files in Odin from the firmware you downloaded from step2.
7. Make sure you have "re-partition" enabled and set the .PIT file to use the *512.pit also included in the firmware from step 2.
8. click start.
9. Start your phone and set up the startup wizard.
9. For rooting, get the CF-root for your firmware from here: http://forum.xda-developers.com/showthread.php?t=788108
10. Get your phone into download again.
11. DON'T check repartition in odin, only select the CF-Root file as PDA (you have to use the CF-Root-***.TAR, important to use .TAR and not .ZIP.
12. Flash again, now you are rooted!!
Odin is the saviour tool for all Samsung devices. The method for flashing by Odin differs from device to device.
This thread will give step by step instructions on how to flash a stock rom from Odin on the GT-I9070/p :
A. Download Odin tools from here : http://d-h.st/3zJ
Pass : shaaan
B. Download the stock rom from www.samfirmware.com
Setting up Odin :
1. Make sure you have installed the necessary drivers for this device. The drivers can be installed from within KIES or seperately. (I will upload the drivers shortly).
2. Run Odin as administrator.
3. Setting up the files is divided in two types depending on the firmware type :
a. If the firmware is a multi package file, put the files in the corresponding sections.
ie. CSC file in CSC section, PDA file in PDA section.
b. If the firmware is a single package, add the single file in the PDA section.
4. Now that Odin is setup, put the phone in download mode. To do that, power off the phone and press 'home+power+volume down' buttons together. Keep the buttons pressed till Download mide appears.
5. Now that Odin and the phone are setup, connect the phone to the device. Odin will detect the device and show something like 'com port (1)'
6. Flash the device.
7. The flash will take 5 minutes for a full flash on average.
8. When the flashing is complete, DO NOT remove the device until Odin shows ' PASS '.
9. The device will reboot. Remove the device, go to recovery mode and do a factory/data reset.
That's it. Happy flashing peeps..!!
Awesome guide mate - messing around with our device without Odin is risky !
This should be sticky. A lot of people is asking how to revert to original FW, or similiar questions that is connected to reverting. And it is almost at the end of forum, and thay cant see it.
I pmed the mods to do it. But they won't budge..
Please pm them..
Nice guide!!!
And adding images would be a nice option.
And plz add a point which tells which buttons to press like
"Re-Partition" ,"Auto Reboot","F.Reset Time" ,"Flash Lock"......
Sent from my GT-I9070 using xda premium
Very good guide,good work !
It may be better if you add some images
atishey23 said:
Nice guide!!!
And adding images would be a nice option.
And plz add a point which tells which buttons to press like
"Re-Partition" ,"Auto Reboot","F.Reset Time" ,"Flash Lock"......
Sent from my GT-I9070 using xda premium
Click to expand...
Click to collapse
From what I was able to find in other guides it is ONLY 'Auto Reboot' and 'F. Reset Time' to be checked.
All others to be unchecked.
There are some posts not to bother with that .pit file that is inside Odin .zip file.
Odin package from sammobile got 2 .pit files for 8GB - GT-I9070_EUR_XX_8G and GT-I9070_EUR_XX_8G_20111220_KL6 and one for 16GB
(at least paired with XEO region XXLD1) not only that one we got in link form 1st post.
I was also able to find some info that if you use .pit check also 'Re-Partition'.
Now I am curious about if It would be good idea for me to actually Re-Partition my phone - bought it used (not new) and my PC detects only 4GB of internal SD. Will it increase custom binary counter? (so far it is at 0 and I would rather keep it that way)
Is it going to fix that issue so I will be able to use all 8GB (minus system partition)?
If so how to use it and what .pit file to take?
.pit only, re-partition only and run it once, then single-package as PDA with reboot and F. Reset on another flash run?
Or maybe all at once?
BTW you guys ROCK.
Rooted SGS i9000 2 years ago with this forum and now I am very close to do it again with SGSA.
th3cr0w said:
From what I was able to find in other guides it is ONLY 'Auto Reboot' and 'F. Reset Time' to be checked.
All others to be unchecked.
There are some posts not to bother with that .pit file that is inside Odin .zip file.
Odin package from sammobile got 2 .pit files for 8GB - GT-I9070_EUR_XX_8G and GT-I9070_EUR_XX_8G_20111220_KL6 and one for 16GB
(at least paired with XEO region XXLD1) not only that one we got in link form 1st post.
I was also able to find some info that if you use .pit check also 'Re-Partition'.
Now I am curious about if It would be good idea for me to actually Re-Partition my phone - bought it used (not new) and my PC detects only 4GB of internal SD. Will it increase custom binary counter? (so far it is at 0 and I would rather keep it that way)
Is it going to fix that issue so I will be able to use all 8GB (minus system partition)?
If so how to use it and what .pit file to take?
.pit only, re-partition only and run it once, then single-package as PDA with reboot and F. Reset on another flash run?
Or maybe all at once?
BTW you guys ROCK.
Rooted SGS i9000 2 years ago with this forum and now I am very close to do it again with SGSA.
Click to expand...
Click to collapse
It is normal to have 4GB on internall SD. The rest of it goes to system partition, application partition and RAM I think...
shut_down said:
It is normal to have 4GB on internal SD. The rest of it goes to system partition, application partition and RAM I think...
Click to expand...
Click to collapse
googled a bit more and found it out too :crying:
BTW - both of those 8GB .pit files are identical (according to 'comp' tool in windows) so there is no reason to use re-partition - other than sth went totally wrong and you are trying to recover from brick or sth serious as this .pit file is already on your device.
Just flashed unbranded stock for XEO region - original one was branded.
NOTE to anyone who is still thinking about safety of this method:
After initial reboot - when it was reconfiguring in recovery mode - or however you will call it (just before odin should say 'pass' - still in that little font screen) windows started to reinstall usb drivers - odin log in bottom corner said 'disconnected' and even then my newly flashed ROM is working as it should. I would rather keep it connected till Odin confirms all went as intended but in case of similar issue - do not get heart attack
odin is used for flashing stock roms only???
Kulwinder Singh said:
odin is used for flashing stock roms only???
Click to expand...
Click to collapse
nope it can also be used to flash custom Roms and kernels though flashing custom kernels via odin will increase your bin counter !
Hello guys...
How are you? I´m new on the i9070 threads!!! I´ve had others phones before, like SG2, xperia sola, live with walkman... so, i need the password to descompress odin... i search on thread but i don´t found it...
SORRY I found the password... shaaan
Of what I understand, can I test an unlimited number of stock firmware and the binary counter remain 0?
If I flash an unbranded firmware can I use SIM cards from other providers?
Now my phone is branded and I can not use SIM cards from other providers.
Thanks.
Kulwinder Singh said:
odin is used for flashing stock roms only???
Click to expand...
Click to collapse
Read please, sir!
http://forum.xda-developers.com/showthread.php?t=1985199
:laugh:
Someone help me? LINK
Hi i have downloaded the russian jelly bean 4.1.2 package but when i tries to flash it using odin3 v1.83 it shows me "The Parameter is incorrect" why???
sonimayurp said:
Hi i have downloaded the russian jelly bean 4.1.2 package but when i tries to flash it using odin3 v1.83 it shows me "The Parameter is incorrect" why???
Click to expand...
Click to collapse
Try to remove .md5 from filename.
shut_down said:
Try to remove .md5 from filename.
Click to expand...
Click to collapse
Hmm it worked thx..
Flash JB
Hi, I want to flash Jelly Bean , do i need to use the pit file , or just select one package and then select the rom??
Edit : flashed
This version of Odin does not work when flashing JB to my device.
I successfully used Odin3v3.07 from this post: http://forum.xda-developers.com/showthread.php?t=2086965
Please update this guide. I spent quite a lot of time trying to figure out what was wrong.
Thanks
I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick
Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.
FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...
Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.
Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?
For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.
sm-n900
sm-900 and pit
Hi there
I have HARD bricked my phone (can't use combination keys to get into recovery mode).
I am looking for someone who has a DEBRICK image or who is willing to create and upload one so that I can recover the phone.
The specific software on the phone at the time of death was Android 5.01 and Phone Model is N910GDTU1BOD3.
ALTERNATIVELY, I have another Samsung Note 4 (identical). If you can give me exact step by step instructions and links (so many vague instructions here on XDA) that would help. I promise to create an article here and post recognizing your direct and help!
Many thanks in advance.
Zim
Have you tried putting it in download mode? (vol. down+home+power)
If you can then download frimware from http://www.sammobile.com/firmwares/ and follow the instructions to flash it via Odin.
Hi!
Have you managed to unbrick your Galaxy Note 4? I've got the same problem. Also i've got the detailed instruction how to solve it. But I'm stuggeling to find a working sm-n9100 to make sd-card image.
zimmar said:
Hi there
I have HARD bricked my phone (can't use combination keys to get into recovery mode).
I am looking for someone who has a DEBRICK image or who is willing to create and upload one so that I can recover the phone.
The specific software on the phone at the time of death was Android 5.01 and Phone Model is N910GDTU1BOD3.
ALTERNATIVELY, I have another Samsung Note 4 (identical). If you can give me exact step by step instructions and links (so many vague instructions here on XDA) that would help. I promise to create an article here and post recognizing your direct and help!
Many thanks in advance.
Zim
Click to expand...
Click to collapse
Check this one out: http://forum.xda-developers.com/note-4-tmobile/general/help-test-unbrick-method-note-4-t3379897
I cannot get the image to work with my N4 so if you have two identical phone you might be in luck see the PDF
zimmar said:
Hi there
I have HARD bricked my phone (can't use combination keys to get into recovery mode).
I am looking for someone who has a DEBRICK image or who is willing to create and upload one so that I can recover the phone.
The specific software on the phone at the time of death was Android 5.01 and Phone Model is N910GDTU1BOD3.
ALTERNATIVELY, I have another Samsung Note 4 (identical). If you can give me exact step by step instructions and links (so many vague instructions here on XDA) that would help. I promise to create an article here and post recognizing your direct and help!
Many thanks in advance.
Zim
Click to expand...
Click to collapse
Check this out , there is a guide and the recovery pit file as well .
https://mega.nz/#!qt81HZiS!-XyNN1m_TEi8dvGrjnEQsxClpfzk7nT_0DliYFJDPew
You just have to :
Load "recovery pit" file in pit partition of odin and any marshmallow bootlaoder in BL (the bootloader that is currently there on working phone is preferable ).
Then, insert a 32gb sdhc sd card in working note 4 and go to download mode .
Flash the two files that i have mentioned above .
The working phone is just a medium , it shouldnt be affected , the blank sd card in that phone will get loaded with the two files.
Then , put that sd card in bricked note 4 , try to enter download mode .
If it succesfully enters download mode , congratulations, you created a working debrick image .
Also download a full repair firmware , that is available on xda .
Reporting via N910G
Debrick has been created , and reportedly working :
http://forum.xda-developers.com/showthread.php?p=69319580
Reporting via N910G.
Hi!
Some time ago my n910F tottaly bricked(it was on Norma V11 ROM). After some reserch, i've managed to turn on download mode via microSD card and from there i've tried to flash BL,AP,CP and CSC. Unfortunately odin failed (PIT problem) so i've tried to flash PIT file. It crashed too. Phone restarted and, when it came back to download mode it was looking diffrent. Now there are 2 diffrent errors:
1. There is no PIT binary
2. Device have invalid PIT
What should i do now? I don't have any ideas Maybe awesome community of XDA will help me?
I've got less then 10 posts so to see my video you have to put "https://" before youtube...
youtu.be/eD7sjFtWfps
MarcinMilosz13 said:
Hi!
Some time ago my n910F tottaly bricked(it was on Norma V11 ROM). After some reserch, i've managed to turn on download mode via microSD card and from there i've tried to flash BL,AP,CP and CSC. Unfortunately odin failed (PIT problem) so i've tried to flash PIT file. It crashed too. Phone restarted and, when it came back to download mode it was looking diffrent. Now there are 2 diffrent errors:
1. There is no PIT binary
2. Device have invalid PIT
What should i do now? I don't have any ideas Maybe awesome community of XDA will help me?
I've got less then 10 posts so to see my video you have to put "https://" before youtube...
youtu.be/eD7sjFtWfps
Click to expand...
Click to collapse
Which formware was you trying to flash?
callumbr1 said:
Which formware was you trying to flash?
Click to expand...
Click to collapse
I've been using tutorial that recomended me to use those files:
BL: "BL_N910FXXU1DPI1_CL9117724_QB10791804_REV00_user_low_ship_MULTI_CERT" >> DPI1
AP:"AP_N910FXXU1DPI1_CL9117724_QB10791804_REV00_user_low_ship_MULTI_CERT" >> DPI1
CP:"CP_N910FXXU1DPH1_REV00_CL_2068963" >> DPH1
CSC: "CSC_VFR_N910FVFR1DPF1_CL8447885_QB10051693_REV00_user_low_ship_MULTI_CERT" >> DPF1
All of them failed (Probably not their fault) so i've tried to flash PIT file named "TRLTE_EUR_OPEN.pit" (i think it should be the proper one). Still no luck there. As you can see on the video ODIN fails that flashes
MarcinMilosz13 said:
I've been using tutorial that recomended me to use those files:
BL: "BL_N910FXXU1DPI1_CL9117724_QB10791804_REV00_user_low_ship_MULTI_CERT" >> DPI1
AP:"AP_N910FXXU1DPI1_CL9117724_QB10791804_REV00_user_low_ship_MULTI_CERT" >> DPI1
CP:"CP_N910FXXU1DPH1_REV00_CL_2068963" >> DPH1
CSC: "CSC_VFR_N910FVFR1DPF1_CL8447885_QB10051693_REV00_user_low_ship_MULTI_CERT" >> DPF1
All of them failed (Probably not their fault) so i've tried to flash PIT file named "TRLTE_EUR_OPEN.pit" (i think it should be the proper one). Still no luck there. As you can see on the video ODIN fails that flashes
Click to expand...
Click to collapse
You flashed the wrong pit!
Flash this firmware
https://www.sammobile.com/firmwares/download/116551/N910FXXU1DPL2_N910FBTU1DPL1_BTU/
With this pit at the same time.
https://drive.google.com/file/d/0BzyeAt2hy6XeVWFnVGM0dUNHbGM/view?usp=sharing
Make sure you check repartition in odin options
callumbr1 said:
You flashed the wrong pit!
Flash this firmware
https://www.sammobile.com/firmwares/download/116551/N910FXXU1DPL2_N910FBTU1DPL1_BTU/
With this pit at the same time.
https://drive.google.com/file/d/0BzyeAt2hy6XeVWFnVGM0dUNHbGM/view?usp=sharing
Make sure you check repartition in odin options
Click to expand...
Click to collapse
Still doesn't work PIT file that you gived to me looks exactly the same to the one that i used. Phone keeps saying that there is no pit binary, or "wrong PIT id".
Maybe there is a problem with that download mode? To turn it on i have to eject microSD card, while phone is reading "T-flash". And even then there is no android logo like it is on normal download mode. Only some writings...
Is there a way to flash PIT via microSD? Every time i start phone it keeps saying that it's copying from T-FLASH and after that it's rebooting...
The device bricked not becouse of bad flashing, so i'm starting to think that this is a hardware problem...
MarcinMilosz13 said:
Still doesn't work PIT file that you gived to me looks exactly the same to the one that i used. Phone keeps saying that there is no pit binary, or "wrong PIT id".
Maybe there is a problem with that download mode? To turn it on i have to eject microSD card, while phone is reading "T-flash". And even then there is no android logo like it is on normal download mode. Only some writings...
Is there a way to flash PIT via microSD? Every time i start phone it keeps saying that it's copying from T-FLASH and after that it's rebooting...
The device bricked not becouse of bad flashing, so i'm starting to think that this is a hardware problem...
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114/page30
Read this thread it will help you
little more details plz
MarcinMilosz13 said:
Hi!
Some time ago my n910F tottaly bricked(it was on Norma V11 ROM). After some reserch, i've managed to turn on download mode via microSD card and from there i've tried to flash BL,AP,CP and CSC. Unfortunately odin failed (PIT problem) so i've tried to flash PIT file. It crashed too. Phone restarted and, when it came back to download mode it was looking diffrent. Now there are 2 diffrent errors:
1. There is no PIT binary
2. Device have invalid PIT
What should i do now? I don't have any ideas Maybe awesome community of XDA will help me?
I've got less then 10 posts so to see my video you have to put "https://" before youtube...
youtu.be/eD7sjFtWfps
Click to expand...
Click to collapse
Hello,
Please provide more details. and plz consider these when unbricking....
{No 1 is most important i have been in this situation and only the official firmware accepted the pit file for me}
1. Download your official firmware from sammobile.com and try to flash that with the default pit file. (or try this one: https://dl.dropboxusercontent.com/u/84115590/SM-N910F_32GB.pit ) when you get your phone up and running you can root and flash any custom rom of your choice.
2. Files you trying to flash have really long file names. I know it does not cause a problem but when you are in trouble you must think about all the possibilities. Download files with shorter file names just in case.
3. Try to flash one file at a time.
Try and report will respond.
Thanks!
Hi!
I've got some problems with my PC, and then i had to pass kind of " school leaving exams" so i was absent here, at xda
Now back to the topic:
My phone still don't want to boot. @callumbr1 I've done everything that is in that link, before i even writed here . Thanks to that my phone turns on to the moment that is shown on the video. @hi_blues Everything that i've downloaded was either from sammobile or from some tutrials "how to debrick etc" here on xda. Link provided by you didn't changed anything
2. All of the official firmware that i found has long names, but i think that more important then name of actual file is lenght of path to access it So I've tried flashing directly from C://... but nothing helped.
3. So flashing one file at a time does nothing
Maybe some other ideas? Becouse my n910F bricked i had to switch to my fathers nokia 3310 (the old one). Well, i really lack some features like Camera, Internet or colorfull display