Ok, I used odin to first flash pit and jj4 firmware, the tab then rebooted and the logo was all messed up and fuzzy, I then put it in download mode and flashed jj5 firmware and rebooted. The tab did the same again.
The display is on but nothing being displayed.
How can I flash it to a working rom and where can I get all the files to do this?.
Any help would be great.
Thanks
Its sounds like you did it correctly. Try dowloading JJ4 from the net again and reflash that with odin. You can stil get to the yellow download screen right?
Sent by Roto's Tab
giz2003 said:
Ok, I used odin to first flash pit and jj4 firmware, the tab then rebooted and the logo was all messed up and fuzzy, I then put it in download mode and flashed jj5 firmware and rebooted. The tab did the same again.
The display is on but nothing being displayed.
How can I flash it to a working rom and where can I get all the files to do this?.
Any help would be great.
Thanks
Click to expand...
Click to collapse
What pit did u use. I had the same problem
and i flash using pit 0909. try that see what happens
Sent from my GT-P1000 using XDA App
Where do I get the original stock firmware for the Samsung Galaxy Tab, Tmobile version from, and pit files. I think I bricked my tab. Can anyone help?
samfirmware
Leonid279 said:
Where do I get the original stock firmware for the Samsung Galaxy Tab, Tmobile version from, and pit files. I think I bricked my tab. Can anyone help?
Click to expand...
Click to collapse
Its not on samfirmware or anywhere else but here:
http://files.deodexed.com/ModADroid-Galaxy-Tablet/T-Mobile/T-Mobile_Stock.zip
We can't help unless you explain what you did and what the symptoms are. Don't make us extract the details from you.
So i upgraded my phone with the leaked froyo update.zip and everything went well except for the gps. So i followed the how to "unbrick/bring back to stock" thread so i could downgrade my phone to the di18 firmware. I used odin, the s1_odin20100512.pit and the d700.zimage.stock file. I did not want to wipe out everything, i just wanted to downgrade the kernal back to stock.
When i tried flashing on odin, it failed. now when i try turning on my i get the phone icon with the exclamation mark in the triangle. I wanted to call my girlfriend after flashing my phone but now i cant . Please help me save my phone!
EDIT: Okay not bricked, but it wont load up android
Uploaded with ImageShack.us
superbraut said:
So i upgraded my phone with the leaked froyo update.zip and everything went well except for the gps. So i followed the how to "unbrick/bring back to stock" thread so i could downgrade my phone to the di18 firmware. I used odin, the s1_odin20100512.pit and the d700.zimage.stock file. I did not want to wipe out everything, i just wanted to downgrade the kernal back to stock.
When i tried flashing on odin, it failed. now when i try turning on my i get the phone icon with the exclamation mark in the triangle. I wanted to call my girlfriend after flashing my phone but now i cant . Please help me save my phone!
EDIT: Okay not bricked, but it wont load up android
Uploaded with ImageShack.us
Click to expand...
Click to collapse
Put the phone in download mode again and run odin again.
Sent from my SPH-D700 using XDA App
Thanks for the tip!
Your gonna want to flash the di18.tar in "pda" with odin and only reboot checked, no pit needed. That gets the di18 firmware back, and the only way.. kernel has nothing to do with it..
Sent from my SPH-D700 using XDA App
I am about to do this too.. and dont want to wipe the data only get back to di18 to get the gps working.. so in that case:
1. I dont need pit file at all
2. which .tar to choose? not the255 mb file?
Mine failed the first time to. I followed the directions from http://forum.xda-developers.com/showthread.php?t=773032
I tried it a second time but used the victory pit that came with odin 1.61 and it worked. I think in the instructions their using an older version of odin.
I'm not in anyway an expert and you may not even need to use a pit like another poster said. It worked for me though. When I got done the phone rebooted and it showed it having the eclair d07 build from there it updated itself to dI18.
I believe you still need the pit file. If you are going back to stock DI18, than use this:
Stock Files
The one you were trying to use was the kernel I believe.
Here is the pit file you need:
pit file
I have flashed back to stock about 14 times and I have used these two files successfully every time.
yeah ive done it te same wasy that swanysto has done it also a lot. it always works for me to. i know some sa you don't need the pit unless just doing a kernel but i always use it. just my 2 cents
pull the SD card out before you go into download mode (not just pull it out, make sure to push down and let it pop up to remove it).
help..odin failed during flashing..! and showing firmware encountered an issue and select recovery mode in kies and ty again...??
Post more details.
What ROM/Kernel were you on, what (and exactly how, what in odin did you check/not what did you chose for Phone/Pda/etc) were you flashing, etc
Way to many variables here for us to help and guess.
crawlgsx said:
Post more details.
What ROM/Kernel were you on, what (and exactly how, what in odin did you check/not what did you chose for Phone/Pda/etc) were you flashing, etc
Way to many variables here for us to help and guess.
Click to expand...
Click to collapse
I was on gb stock..then tried a prerooted 3 files stock ddlb2 from devpmnt section..during flashing around 5% completed then failed..in odin pc..me selected biggest tar file on pda then one small in phone and the csc named tar file in csc..is t a soft brick or hard brick..?
Thanks..
swavab said:
I was on gb stock..then tried a prerooted 3 files stock ddlb2 from devpmnt section..during flashing around 5% completed then failed..in odin pc..me selected biggest tar file on pda then one small in phone and the csc named tar file in csc..is t a soft brick or hard brick..?
Thanks..
Click to expand...
Click to collapse
If you were on stock gb, and trying to flash stock pre rooted gb, then the chances of hard brick are quite slim. You should remove the battery, then put it back again, go in download mode and start again. Make sure that Kies is not running in background.
Best of luck
if you can go back into download mode -> flash stock GB
if you CAN'T do that -> bricked
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. 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?)