Related
I installed this ROM from this forum "[ROM][DEVTEAM][GSM][20/10/11]GSM GalaxyTab Honeycomb team-- HoneyComb RC1 UPLOADED!!". I'm new on Galaxy Tab but I have anothers htc phones with androids. I had installed clockwork recovery on it and I did wipe all and I installed the zip rom.
First time it works, but it didn't show keyboard and I couldn't skip initial configuration. So, I tried to wipe all and install the zip again.
Now I can't power my tab. I pressed power button for minutes. I connect USB and it don't do anything. But if I connect USB I can wait for a time and it shows a big battery icon and if I press the volume down button(only) I can go to download mode and use ODIN(it takes some time to "power on").
I tried to install some firmwares that are on this forum but anything works. As a curiosity, Odin only takes 7 second to make the repartition and pit operation. And another 7 second to make the tar operation.
If I plug the USB and I don't touch anything. Tab powers on and shows logo "Samsung Galaxy Tab" and I can power it off perfect(the problem is power on again)
(I've searched a lot on forums, nothing works for me).
If you are willing to go back to gingerbread 2.3.5 you can try this build by przekret
http://forum.xda-developers.com/showthread.php?t=1334152
(Warning: I have not been able to successfully root the 2.3.5 firmware - still looking for ways to root it).
or you can download any official firmware at http://fus.nanzen.se/
1a. Download Fus Check Downloader 2.1 and downloaded a Firmware for your region. It will automatically decode the .enc2 file to.zip file
1b. or download this 2.3.5 (unrooted and hard to root version from above link)
2.a. Extract the .zip file generated from decoding file to a folder and I got
tar.md 5 file.
3. Start Odin - put the .md5 to PDA and leave everything else as is.
4. Go to download mode on the G-tab
and click start. It takes about 6 to 7 minutes to do the flashing.
Can't guarentee if it would work, but good luck.
btw, have you check this one?
http://forum.xda-developers.com/showthread.php?t=1133590
Bad times my friend.
Another solution would be to install the Overcome 4.0 rom - it may be enough to fix whatever has gone wrong.
Just search for it on Google - plenty of instructions on their website (odin install too).
If your Honeycomb experience has left a bad taste in your mouth you should look at @technomaner's CM7 port. Very good rom and actually useable as an everyday rom too.
Sent from my GT-P1000 using XDA App
Thanks for replies. I'll try your solutions soon and i'll post my results. (Now I have white screen when I connect my tab to usb, but I can go to download mode with patience).
The most extrange for me is that ODIN only takes 7 seconds in flash another firmwares. I'm sure that something is wrong.
PD: I had seen the post about hard brick or software brick. The hard brick solution I won't try it, but software solution I tried to download samfirmware but I only get a pit file. I didn't see a file with the tar archive.
yappoe said:
If you are willing to go back to gingerbread 2.3.5 you can try this build by przekret
http://forum.xda-developers.com/showthread.php?t=1334152
(Warning: I have not been able to successfully root the 2.3.5 firmware - still looking for ways to root it).
or you can download any official firmware at http://fus.nanzen.se/
1a. Download Fus Check Downloader 2.1 and downloaded a Firmware for your region. It will automatically decode the .enc2 file to.zip file
1b. or download this 2.3.5 (unrooted and hard to root version from above link)
2.a. Extract the .zip file generated from decoding file to a folder and I got
tar.md 5 file.
3. Start Odin - put the .md5 to PDA and leave everything else as is.
4. Go to download mode on the G-tab
and click start. It takes about 6 to 7 minutes to do the flashing.
Can't guarentee if it would work, but good luck.
btw, have you check this one?
http://forum.xda-developers.com/showthread.php?t=1133590
Click to expand...
Click to collapse
Oh my ****ing god!! thanks so much! I did your steps with fus check downloader and I put my tab charging on a electric plug and it works now!
yappoe said:
If you are willing to go back to gingerbread 2.3.5 you can try this build by przekret
http://forum.xda-developers.com/showthread.php?t=1334152
(Warning: I have not been able to successfully root the 2.3.5 firmware - still looking for ways to root it).
or you can download any official firmware at http://fus.nanzen.se/
1a. Download Fus Check Downloader 2.1 and downloaded a Firmware for your region. It will automatically decode the .enc2 file to.zip file
1b. or download this 2.3.5 (unrooted and hard to root version from above link)
2.a. Extract the .zip file generated from decoding file to a folder and I got
tar.md 5 file.
3. Start Odin - put the .md5 to PDA and leave everything else as is.
4. Go to download mode on the G-tab
and click start. It takes about 6 to 7 minutes to do the flashing.
Can't guarentee if it would work, but good luck.
btw, have you check this one?
http://forum.xda-developers.com/showthread.php?t=1133590
Click to expand...
Click to collapse
Thank you! I had the same trouble!
Always glad to help fellow g-tab owners .
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 started a thread needing help with my wifi but it has developed into not even being able to boot at all; it stops at the galaxy logo and either freezes or keeps booting. I have gone to the Odin page with all the different things to do and flashed the file to get back to the original rom but that is really where the trouble began. right now the only thing I can do with my phone is get into download mode, I can't even get into recovery. I have flashed a pit file that worked the first time but I don't know if that is part of the problem or not. Can someone please give me some directions, thanks
Also the phone won't boot at all unless hooked up to a power supply, the battery alone doesn't do anything.
nate39 said:
Hi, I started a thread needing help with my wifi but it has developed into not even being able to boot at all; it stops at the galaxy logo and either freezes or keeps booting. I have gone to the Odin page with all the different things to do and flashed the file to get back to the original rom but that is really where the trouble began. right now the only thing I can do with my phone is get into download mode, I can't even get into recovery. I have flashed a pit file that worked the first time but I don't know if that is part of the problem or not. Can someone please give me some directions, thanks
Click to expand...
Click to collapse
More info is needed. What firmware / bootloader are you on? Was it rooted? Did you have a custom recovery installed? What version of ODIN are you using?
StoneyJSG said:
More info is needed. Which GS3 do you have? What firmware / bootloader are you on? Was it rooted? Did you have a custom recovery installed? What version of ODIN are you using?
Right now, it sounds like you might need to use enewman17's ODIN debrick file.
Click to expand...
Click to collapse
It is the AT&T s4. To be honest I don't know what firmware I am on, it is the one the Odin page said to use if you want to go back to stock. I never rooted it. The bootloader would be whatever the latest update was for this phone. I can't get into it to tell you anymore. I am using ODIN 10, the latest one. thanks
Well I finally got into recovery and did a factory reset, now it boots into the AT&T white splash screen before it just turns off. I am also wondering if my battery just died for some reason?
nate39 said:
It is the AT&T s4. To be honest I don't know what firmware I am on, it is the one the Odin page said to use if you want to go back to stock. I never rooted it. The bootloader would be whatever the latest update was for this phone. I can't get into it to tell you anymore. I am using ODIN 10, the latest one. thanks
Click to expand...
Click to collapse
ODIN 10? Try using ODIN 3.09 and see if that helps. The latest update would be Android 4.4.4 NJ4 firmware. This link should help you, it will give you root with safe strap recovery though: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
I meant 3.10, I will try the older version. What file should I flash?
nate39 said:
I meant 3.10, I will try the older version. What file should I flash?
Click to expand...
Click to collapse
Check out the link I posted in my last post. It should help you get your phone fixed.
I have been there. I went to the very last option which seems to be what I need unless I am missing something.
Neither odin 3.09 or 3.10 will even flash any file now. it either says invalid md5 or fails when it attempts it.
Well, I finally got it to boot into android but it is flaky at best. It is android 4.3 instead of 4.4 where it was initially. The wifi still doesn't work and now the keyboard keeps crashing everytime I do something. The build is jss15j1337ucuemk2 which I know is older than I had before. Does this give anyone a better idea of what I need to do? If I can get a stable flash then can I flash a modem file to fix the wifi? I really need some direction, thanks
Turns out the battery was completely drained which was causing some of the boot problems, I don't now how that happened but I am charging it now.
Well after using odin 3.8* I got it to install some older firmware ending in mk2 rather than the nc1 or nf4 that I had before the trouble. After I got it to boot, I went back into download mode and flashed the modem file and now everything works execpt I had to force stop Samsung keyboard and use swype. I would like to upgrade my firmware but since for a couple of more weeks it won't have a sim card I can't upgrade OTA. For some reason Kies says that firmware upgrade and initialization isn't supported with this model which makes no sense to me. It also says my firmware is up to date
Does anyone know how to flash to the latest firmware without me going through this nightmare again? thanks
nate39 said:
Well after using odin 3.8* I got it to install some older firmware ending in mk2 rather than the nc1 or nf4 that I had before the trouble. After I got it to boot, I went back into download mode and flashed the modem file and now everything works execpt I had to force stop Samsung keyboard and use swype. I would like to upgrade my firmware but since for a couple of more weeks it won't have a sim card I can't upgrade OTA. For some reason Kies says that firmware upgrade and initialization isn't supported with this model which makes no sense to me. It also says my firmware is up to date
Does anyone know how to flash to the latest firmware without me going through this nightmare again? thanks
Click to expand...
Click to collapse
If I were in your shoes I'd flash the nb1 tar file in Odin, any vein should work. See this for the tar file http://forum.xda-developers.com/showthread.php?p=56453100. You can then ota to the latest firmware which is 4.4.4, nj4
Sent from my Nexus 9 using XDA Free mobile app
thanks, and as far as you know this doesn't mess wifi up?
nate39 said:
thanks, and as far as you know this doesn't mess wife up?
Click to expand...
Click to collapse
I assume you ment WiFi and not wife? Can't help you with the wife but Wi-Fi should work fine
Sent from my Nexus 9 using XDA Free mobile app
nate39 said:
Well after using odin 3.8* I got it to install some older firmware ending in mk2 rather than the nc1 or nf4 that I had before the trouble. After I got it to boot, I went back into download mode and flashed the modem file and now everything works execpt I had to force stop Samsung keyboard and use swype. I would like to upgrade my firmware but since for a couple of more weeks it won't have a sim card I can't upgrade OTA. For some reason Kies says that firmware upgrade and initialization isn't supported with this model which makes no sense to me. It also says my firmware is up to date
Does anyone know how to flash to the latest firmware without me going through this nightmare again? thanks
Click to expand...
Click to collapse
Download a firmaware for your region from sammobile and flash it via odin 3.10. It will solve most of your problems
Muthumbi said:
Download a firmaware for your region from sammobile and flash it via odin 3.10. It will solve most of your problems
Click to expand...
Click to collapse
Sammobile isn't going to have anything for the i337 unless you're on mdl
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sammobile isn't going to have anything for the i337 unless you're on mdl
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I agree. But google has basically all he needs. More so rapidgator
I haven't found anything from Samsung to download. If I flash a newer build, do I also need to flash a modem file and a bootloader or can I just flash the PDA? thanks for explaining this to me.
And can I do a dirty flash so I don't have to lose everything again?
well, now I see that there is no sound. so I guess I will have to flash again.
nate39 said:
well, now I see that there is no sound. so I guess I will have to flash again.
Click to expand...
Click to collapse
There's. Something I'm yet to understand. Did you finally manage to boot into recovery? If so, flash a custom recovery (I recommend philz touch recovery) then use it to make complete wipe.
Then boot into download mode and flash latest pda firmware in the compressed file you downloaded. Ps: make sure it's from your region.
May be if you provided me with your region I'd get you all the files required
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?)
Hey guys, sorry I have been away for so long and am not updated... anyway, I have been downloading different 5.1.1 roms (samfirmware and sam updates) for my N910C and everytime I try to unzip, it says the file is corrupt...
Can anybody please tell me what has changed? Whay can't I unzip the downloaded files?
I only want the official rom, and am not rooting my phone for now.
Thanks
xdm9mm said:
Hey guys, sorry I have been away for so long and am not updated... anyway, I have been downloading different 5.1.1 roms (samfirmware and sam updates) for my N910C and everytime I try to unzip, it says the file is corrupt...
Can anybody please tell me what has changed? Whay can't I unzip the downloaded files?
I only want the official rom, and am not rooting my phone for now.
Thanks
Click to expand...
Click to collapse
I recommend using Samfirm
thanks for the recommendation. My question has not been answered though, what has changed, and why do we need to use another tool now? Thanks
If you want to know the changelog for stock 5.1.1 then I strongly recommend you read it. Google is your best friend. What are you talking about another tool?
There is only one tool for Samsung to flash stock roms and it's called odin so nothing has changed there. If you are using kies to upgrade then expect the worst as the outcome seems like random events. 25% of the time kies ****s up.
Zionator said:
If you want to know the changelog for stock 5.1.1 then I strongly recommend you read it. Google is your best friend. What are you talking about another tool?
There is only one tool for Samsung to flash stock roms and it's called odin so nothing has changed there. If you are using kies to upgrade then expect the worst as the outcome seems like random events. 25% of the time kies ****s up.
Click to expand...
Click to collapse
I am not asking about changelog, I am asking why are the downloads from samfirmware and samsung-updates , when I try to unzip them are all corrupt.. then someone recommended the tool above to download the firmware... that is why I am asking what is changed, and why do I need a tool to download the firmware now??? Whay can't I just download straight from samfirmware and unzip the file like it was before?
BIG thanks
I had the same problem, the zip file corrupted while trying to unzip. But I just waited until WinRAR finish unzipped it. And successfully flashed the md5 with Odin.
I had the same problem with Winrar.
With 7zip no problem.
And I install the new Rom.
Everything is Ok.
Sent from my SM-N910F using XDA Free mobile app
No problem with WinRar here. Check your Internet Connection: if it's unstable, the file will be downloaded and even MD5 hashes could match, but the file still will be corrupted and if you manage to unzip it it could lead to multiple errors in odin.
Thanks to those who tried to help... I donwloaded the new WinRAR and donloaded the 5.1.1 "SEE" and flashed it on my phone... worked perfectly and I have not wiped my phone after flashing, seems to be working great...