Related
Okay i feel ultra stupid for asking but..
I have my S3 softbricked and I have downloaded the latest Heimdall and Downloaded a firmware from the samsungupdates website
now I have NO idea what to do. Heimdall frontend only gives options to flash pit and then when i try the package thing, it says Firmware.xml is missing. I only have access to a very crappy iMac right now (512 mb of ram lol) and I need my phone up and running ASAP
Thanks in advance
ProjectA1xx said:
Okay i feel ultra stupid for asking but..
I have my S3 softbricked and I have downloaded the latest Heimdall and Downloaded a firmware from the samsungupdates website
now I have NO idea what to do. Heimdall frontend only gives options to flash pit and then when i try the package thing, it says Firmware.xml is missing. I only have access to a very crappy iMac right now (512 mb of ram lol) and I need my phone up and running ASAP
Thanks in advance
Click to expand...
Click to collapse
If you haven't already worked it out, please read the README. It answers all your questions.
"Failed to confirm end of PIT file transfer" message
Hi everyone,
I wanted to upgrade my Samsung Galaxy S I9000 to Android 4 (as some apps I'd like to use require this) so I did some research as I know that flashing devices can be a dangerous operation.
I'm a MAC (Snow Leopard) and Linux (Ubuntu) user so Odin was not an option for me. I read a great deal of nice things about Heimdall so I decided to try it to flash the ROM and install Jelly Bean.
I first made a backup of my phone.
I then downloaded the program (v.1.31), the xxjvu_heimdall.tar.gz package and opened it in Heimdall (after ungzing it of course).
Everything seemed to be okay (all fields filled as I read they had to) so I switched my phone off, started it on upload mode, connected it to my computer and pressed the "Start" button.
A few seconds later I had this message : "ERROR: Failed to confirm end of PIT file transfer".
As nothing happened in the next few minutes, I disconnected the phone, removed the battery and tried to start the phone.
Nothing.
I then tried to start it in upload mode and it worked (so I believe my phone is "soft bricked").
I've been trying different things along the past 5 or 6 hours : installing v.1.32 of Heimdall, trying to upload only the PIT and BOOT files. But nothing seems to work, I always get the same message.
I read that it could be a problem with Heimdall and my OS X distribution (Snow Leopard). But nowhere did I find a thread where people had been able to deal with this specific situation successfully.
I would be very grateful if someone could give me a hint. I only have access to my Mac for now and won't be able to try it on Ubuntu for a few days...
Thanks in advance,
Gael
You will get better help in the i9000 forums. Cheers
xBeerdroiDx said:
You will get better help in the i9000 forums. Cheers
Click to expand...
Click to collapse
That's true, thanks.
I'll post there and tell the good news... As I just managed to falsh my I9000 using Heimdall v.1.30. Everything went smoothly. So in case someone with the same issue lands on this thread : try the 1.30 if you have problems with the other versions on OS X !
Hey guys, I have a Samsung Galaxy S3 for Tmobile SGH T999 and I had cyanogen on it until it crapped out and got hard bricked. AFter following these links, http://forum.xda-developers.com/showthread.php?t=1949687 and http://forum.xda-developers.com/showthread.php?t=2439367, I was able to unbrick my phone and get into boot recovery mode. However, when i try to flash the stock firmware in odin, I get an error (the error is shown in the attachment). Can anyone please help me? Sorry if im posting something wrong, I am new to this forum. Thank you!
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
DocHoliday77 said:
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
Click to expand...
Click to collapse
I tried this still doesnt work.
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
DocHoliday77 said:
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
Click to expand...
Click to collapse
Sorry i meant failure not error. I bricked it because my cyanogenmod was having problems and i tried to restore it, after i did it completely bricked. Sorry can you please elaborate what is TWRP, MJC or NC2 firmware, im dont have much knowledge about these kind of things. Thank you so much for helping me, it means alot to me and I will do my best to follow your directions.
Ok, ill explain better when I get to my computer. It'll be too much to try to type on this tiny device im using right now!
But for now, TWRP is a custom recovery, like CWM. You use it when flashing roms like CM.
MJC and NC2 are just the different firmware builds you can flash in Odin. We shorthand it by just using the last 3 letters of the build version. T999UVUENC2 is what im referring to when I say NC2.
Take a look at my firmware thread. Its stickied at the top of development. Linked in my sig too.
Let me know if this helps your understanding at all. Ill explain more in what to do shortly.
Thanks for that, it gave me a better understanding. I tried to install flash and this happens when i try to flash twrp or MJC on odin
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
DocHoliday77 said:
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
ojhasha said:
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Click to expand...
Click to collapse
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
ojhasha said:
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
Click to expand...
Click to collapse
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
DocHoliday77 said:
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
Click to expand...
Click to collapse
It was invisibleK's link that was unsafe. I used your 16GB Pit file in here, http://www.androidfilehost.com/?w=files&flid=6471 and i got the same result. I dont remember where i got the other pit. I got stuck on Leave CS on the odin 3.09 and when i click start it failed again with the repartition failed.
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
DocHoliday77 said:
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
Click to expand...
Click to collapse
sorry i didnt respond in a while, I was really busy with homework. I tried what you said and still no sign of success. I brought my phone to a repair shop and they said the motherboard is damaged and it needs to be replaced for 150$. I hope this guy is just bull****ting me, can anyone confirm? I really hope there is still light at the end of the tunnel right now.
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
DocHoliday77 said:
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
Click to expand...
Click to collapse
do you recommend me doing it? or are there more alternatives.
If the memory itself has gone bad, that's your best option. It is possible to change just the memory chip, but the part is probably hard to find and it requires a higher level of soldering skills.
There's a video of this, if I can find it again ill post the link.
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
yellowonion said:
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
Click to expand...
Click to collapse
did you have my symptoms? did you ever fix your phone? if so please share, i want to get my phone back in the cheapest way possible.
PS. I charged my phone today and the red led light showed up, that means my motherboard isnt broken right?
Not necessarily. It means there is a problem and requires special drivers and programs to fix, (or the debrick sd card). It basically just means the computer sees something is plugged in. If the memory has gone bad it could very well still give the red led and/or boot from the sd.
The only good way to verify the board (or memory) needs replacing would be to go to a second shop and ask them to attempt a jtag repair. If they tell you the same thing as the first shop, ask if they can be more specific about what happened when they attempted the jtag repair. At this point though, its a pretty good guess that the memory has gone bad.
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
cameron72 said:
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
Click to expand...
Click to collapse
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
bob23bk said:
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
Click to expand...
Click to collapse
I had already tried the method and file in the forum you linked me to. It failed almost instantly. That's when I turned everything off and tossed it all to the back seat of my work truck before it got thrown at the windshield. I keep seeing people saying they have trwp or whatever. I don't even know what that is haven't researched that. Is it something i need as well?
I've never successfully rooted a Samsung device. I used to do this stuff a lot back with the droid x with Linux and everything was pretty simple. Does Samsung change their bootloader with each update like Motorola did then? I was wondering that when trying to install a firmware of a previous version that maybe that was the problem.
All I wanted root for was to just tweak some things and be happy. It has turned into a nightmare.
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
moonbutt74 said:
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
Click to expand...
Click to collapse
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
cameron72 said:
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
Click to expand...
Click to collapse
okay, hmm, when you say it fails, do you mean odin fails to flash and if so what is the reason/ouput ?
or do you mean that you are now in a recovery bootloop ?
note- though i go the full route of packing recovery.img's for odin flashing, the md5 checksum always seems to
come up as invalid, the working "remedy" is to remove the .md5 extension from the "odin-flashable-recovery".tar.md5 file
by renaming the file to "odin-flashable-recovery".tar
odin will no longer attempt the checksum verification but the recovery file will flash.
make sure you have samsung-usb-drivers for windows installed. on the main page of my devhost archive [link is in my signature]
you will find the tools you need. the possible problem is that the ota you installed may have overwritten your bootloader, for that i don't
have a reliable fix, so if anything make sure you also have the stock recovery ready to go as well as supersu update zip
already downloaded onto your device for rooting.
after you flash the custom recovery [with auto-restart in odin disabled] run the flash and wait for the res-ok message, give it another second or two then disconnect the tab and force reboot to recovery, home,vol-up and power, once in recovery make a full backup, then flash supersu zip and reboot, if you do go into recovery loop, force reboot to odin mode, home,vol-down and power, follow the on screen instruction, now reconnect your tab to pc and use odin to flash back stock recovery.
m
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
moonbutt74 said:
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
Click to expand...
Click to collapse
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
cameron72 said:
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
Click to expand...
Click to collapse
for root look up supersu update zip
ask Restl3ss :silly:
m
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Glad it worked out, recovering from brick does set you free from the stress induced by the disclaimers imo :silly:
Good evening folks. I hope I'm posting in the correct place.
First id like to start off thanking everyone for whatever help I can get. I know I've come to the place where I can get some help.
I apologize in advance If I'm lacking any info in my post.
I REALLY NEED HELP.:crying::crying::crying:
I have a rooted metro pcs galaxy s4
I have recently started having a really slow phone. Slow is a understatement actually.
Everything freezes up and I cant do anything with it. I DO have root access.
Anything I try to do such as enter the phone settings, an app or simply try make a call just seems to take a ton of processing power and eventually glitches or freezes up and force closes themselves.
It reminds me of a computer that doesn't have enough memory in it.
I installed some app in the play store that required root access called adjbrightness and ever since then my phone has been crazy slow with apps and services crashing.
I cannot be certain this app had anythinto do with my problem though.
I cant even make a call Its soooo bad.. GGRRrrrrrrrrr......:crying::crying::crying:
I installed one click kango root about a month ago and definitely haven't had any problems until about a week or so ago.
Since then iv tried everything. I'm pretty good with android phones too. I'm always helping ppl fix slow phones or computers.
I fear I may have force stopped or disabled a critical system function or service by accident.
Iv done the following already...
-Factory reset first then uninstalled the root.
-Ever since I unrooted today, I am unsure if I can or should or even could do a factory reset now. Because if I try to do it upon reboot, a warning states that installing custom roms can be damaging to my phone. Um.... Yikes!
-I formatted and removed my SD card.
-Prior to unrooting I did do factory reset several times without results.
I'm really freaking out.
I know this was something that could happen upon rooting as a risk I was taking.
I feel this issue was somehow due to the root access ultimately and that something in the rom (or what not) is glitching badly or some code is just missing.
- I never installed custom rom or messed with the rom that I know of.
-I never messed with any kernels or clocking methods because that's all too scary for me.
-I really didn't mess with things I didn't understand.
I rooted mainly to save battery and ditch some factory bloatware. I'm sure yall can relate.
Oh and I didn't download anything from porn sites, don't worry. HAHA.
Pleeeeeeese, please PLEASE, help lead me on the right path and I will be your best friend for ever.... I just haven't a clue what the issue could be. :crying::crying::crying:
Thank you so much for any and all help in advance.
THX!!!!! K++
---------- Post added at 04:43 AM ---------- Previous post was at 04:36 AM ----------
I would suggest you download the latest metropcs firmware for your device and flash with Odin. Don't worry about the warning, it's supposed to say that. Hopefully you don't have any important info or media that you haven't backed up. If so, back it up before you flash. After the flash, boot straight into recovery and do a factory reset. After that you will start off fresh and your phone should be back to normal
Sent from my SM-G920T using Tapatalk
please help
thank you for replying. i am having a bit of trouble. while following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2258628
im having trouble running odin with any results. I am stuck at the beginning stages ....
after im told to select pda and then select the TAR file i downloaded.
Im unsure how to select the TAR file...
and if i go ahead and run ODIN i get no results.
Im sorry for any inconvenience.
besthomeguy said:
thank you for replying. i am having a bit of trouble. while following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2258628
im having trouble running odin with any results. I am stuck at the beginning stages ....
after im told to select pda and then select the TAR file i downloaded.
Im unsure how to select the TAR file...
and if i go ahead and run ODIN i get no results.
Im sorry for any inconvenience.
Click to expand...
Click to collapse
Try 3.09, AP=PDA.
lordodin912 said:
Try 3.09, AP=PDA.
Click to expand...
Click to collapse
Thanks so much for your help. I downloaded odin 3.9. I downloaded both the uvuamdl tar and the stock tar file from here. http://forum.xda-developers.com/showthread.php?t=2258628
and when browsing to add a tar file to odin pda/ap option, there no tar files recognized. Iv spent hours trying to figure out what to do. I know I want to use the mdl file
lordodin912 said:
Try 3.09, AP=PDA.
Click to expand...
Click to collapse
I see now that im suppose to extract the tar file from the 7zip/zip archive, yet I see no file with that name or extension to do so. Sorry...
besthomeguy said:
Thanks so much for your help. I downloaded odin 3.9. I downloaded both the uvuamdl tar and the stock tar file from here. http://forum.xda-developers.com/showthread.php?t=2258628
and when browsing to add a tar file to odin pda/ap option, there no tar files recognized. Iv spent hours trying to figure out what to do. I know I want to use the mdl file
Click to expand...
Click to collapse
Just saw this right now and if you still need help I might be able to help. I'm also on MetroPCS. That firmware you downloaded is a t-mobile one and I'm not sure what version it is but download the stock one from this thread http://forum.xda-developers.com/gal...tock-base-metropcs-4-4-4-fni3-galaxy-t2899701 then flash it in Odin . After flashing it set it up and all that stuff and do the software update. It'll update your modem to NK3 which is the latest. I'd say use it for about a week and see if it's good or you can just root it right away if you want. I used CF auto root for M919 to root my M919N (MetroPCS version of the S4). For recovery I use TWRP jfltmo. After that just make a backup and keep it on your computer or SD card just incase something happens again so you can flash the backup. If you want to flash a ROM I recommend Hispasian ROM (currently using) or Insane Hybrid. Both are really stable and fast ROMS.
Howdy folks, I want to start off saying that Thank you so much for helping me. XDA is a awesome place.
"lordodin" is helping me with this issue in another thread i created although I amgetting anxious to figure this out as i cannot make any calls on my phone and today's my day off work. I hope I am not being too rude by posting my question here too.
-Im following the instructions in the official T-Mobile SGS4 thread in order to run odin here.
http://forum.xda-developers.com/show....php?t=2258628
I have odin 3.9 (and 3.07) and know to select the tar file with PDA/AD button.
although i cannot find the tar file.,
I know the fix tp this lies n the step requiring me to extract the tar file from the 7zip/zip archive,
yet I see no file with that 7zip/zip name or extension to do so. Im honestly tried everything AAAARRRRRGGGGGGGGG!!!
I downloaded all files needed.... triangle away, odin zip, and the mdl zip.
I placed all rooting files on desktop to locate easier and I am always running odin in admin.
I see the issue was solved somewhere else by completing the step requiring to me to extract the tar file from the 7zip/zip archive this step is confusing the heck out of me.....
I even download the 7zip unpacking program from the web hoping it may recognize a TAR file I may have missed with no avail. . Is 7zip a file type?
When i unpack the odin file all i see is the following
-Odin3 v3.07 (or the 3.9 version respectively)(application)
-Odin3(configuration setting)
-tmax.dll(app extention)
-zlib.dll(app extention)
As i said "lordodin" is helping me in another thread with this very issue which is super appreciated. Thx lordodin!!!!
AARRRRG please help folks. Iv been reading everywhere and im stuck....
lordodin912 said:
Try 3.09, AP=PDA.
Click to expand...
Click to collapse
Howdy folks, I want to start off saying that Thank you so much for helping me. XDA is a awesome place.
"lordodin" is helping me with this issue in another thread i created although I amgetting anxious to figure this out as i cannot make any calls on my phone and today's my day off work. I hope I am not being too rude by posting my question here too.
-Im following the instructions in the official T-Mobile SGS4 thread in order to run odin here.
http://forum.xda-developers.com/show....php?t=2258628
I have odin 3.9 (and 3.07) and know to select the tar file with PDA/AD button.
although i cannot find the tar file.,
I know the fix tp this lies n the step requiring me to extract the tar file from the 7zip/zip archive,
yet I see no file with that 7zip/zip name or extension to do so. Im honestly tried everything AAAARRRRRGGGGGGGGG!!!
I downloaded all files needed.... triangle away, odin zip, and the mdl zip.
I placed all rooting files on desktop to locate easier and I am always running odin in admin.
I see the issue was solved somewhere else by completing the step requiring to me to extract the tar file from the 7zip/zip archive this step is confusing the heck out of me.....
I even download the 7zip unpacking program from the web hoping it may recognize a TAR file I may have missed with no avail. . Is 7zip a file type?
When i unpack the odin file all i see is the following
-Odin3 v3.07 (or the 3.9 version respectively)(application)
-Odin3(configuration setting)
-tmax.dll(app extention)
-zlib.dll(app extention)
As i said "lordodin" is helping me in another thread with this very issue which is super appreciated. Thx lordodin!!!!
AARRRRG please help folks. Iv been reading everywhere and im stuck....
Sorry if I'm posting in the wrong forum here, but I wasn't sure where to start.
I got an ATT Note 8 unlocked running Nougat that would not come up on the Verizon network using my working SIM card. I had read that there were known issues with this and that an upgrade to oreo would fix things. Googling around I found an upgrade zip file from N950USQS2BQK2 to N950USQU2CQL1. I used the recovery method to upgrade from that file and at first things seems to be fine. I started having lots of issues with apps dying, eg Contacts, Phone and Bixby and started to wonder if perhaps the OS could be further upgraded. I hunted around and installed the samfirm tool and downloaded the file
SM-N950U_1_20181126150901_ouxwmh265r_fac.zip and extracted out all the parts. Using Odin (13.1) I tried to install this file but it got hung installing
system.img.ext4. Realizing that it would likely cause problems I powered off the phone after a couple of hours with no progress. As expected the phone was pretty pissed off when I tried to boot it up. It was stuck in trying to upload a crash file and took a lot of fiddling around to convince it to go back to download mode, thanks to one of the posts from this site I was able to make it work.
I've tried the same file again and it is stuck again at the same place. So the question is should I be using a different file? If at all possible I'd just like to run the standard Verizon load, in hunting around it seems for the latest Oreo I should use N950USQS5CRK1. but I can't figure out where to get that file in the format that Odin uses I've looked on the firmware.science website but have only come up with the zip version that would work with the recovery mode. Unfortunately with the state my phone is currently in I don't think I can get to recovery mode. It is in the endless upload mode, hitting the down & power button will shut it down but it comes right back to the upload screen. Any advice would be greatly appreciated. Sorry for the rambling post.
rphaddad said:
Sorry if I'm posting in the wrong forum here, but I wasn't sure where to start.
I got an ATT Note 8 unlocked running Nougat that would not come up on the Verizon network using my working SIM card. I had read that there were known issues with this and that an upgrade to oreo would fix things. Googling around I found an upgrade zip file from N950USQS2BQK2 to N950USQU2CQL1. I used the recovery method to upgrade from that file and at first things seems to be fine. I started having lots of issues with apps dying, eg Contacts, Phone and Bixby and started to wonder if perhaps the OS could be further upgraded. I hunted around and installed the samfirm tool and downloaded the file
SM-N950U_1_20181126150901_ouxwmh265r_fac.zip and extracted out all the parts. Using Odin (13.1) I tried to install this file but it got hung installing
system.img.ext4. Realizing that it would likely cause problems I powered off the phone after a couple of hours with no progress. As expected the phone was pretty pissed off when I tried to boot it up. It was stuck in trying to upload a crash file and took a lot of fiddling around to convince it to go back to download mode, thanks to one of the posts from this site I was able to make it work.
I've tried the same file again and it is stuck again at the same place. So the question is should I be using a different file? If at all possible I'd just like to run the standard Verizon load, in hunting around it seems for the latest Oreo I should use N950USQS5CRK1. but I can't figure out where to get that file in the format that Odin uses I've looked on the firmware.science website but have only come up with the zip version that would work with the recovery mode. Unfortunately with the state my phone is currently in I don't think I can get to recovery mode. It is in the endless upload mode, hitting the down & power button will shut it down but it comes right back to the upload screen. Any advice would be greatly appreciated. Sorry for the rambling post.
Click to expand...
Click to collapse
Download this odin firmware and FIRST extract it one time and the files for odin will be in the extracted folder and flash. You must flash AP, BL, CP and CSC all at the same time. Fill all the slots in odin.
https://androidfilehost.com/?fid=11410963190603879881
MrMike2182 said:
Download this odin firmware and FIRST extract it one time and the files for odin will be in the extracted folder and flash. You must flash AP, BL, CP and CSC all at the same time. Fill all the slots in odin.
Thanks for this. One question, I had the same issue the last time, there is a CSC and a HOME-CSC file included in the zip archive, which of these should be used with Odin?
thanks again
Click to expand...
Click to collapse
rphaddad said:
MrMike2182 said:
Download this odin firmware and FIRST extract it one time and the files for odin will be in the extracted folder and flash. You must flash AP, BL, CP and CSC all at the same time. Fill all the slots in odin.
Thanks for this. One question, I had the same issue the last time, there is a CSC and a HOME-CSC file included in the zip archive, which of these should be used with Odin?
thanks again
Click to expand...
Click to collapse
Never mind found that in another post.
thx
Click to expand...
Click to collapse
if I wanna odin without losing data I use home instead of CSC correct?
I would suggest also using Samsung Smart Switch before doing it. It gives you the option to back up pretty much your whole phone including just about all your apps, settings and customizations to an SD card. It also saves your custom icon groups too if you do that. The it makes it a breeze to restore after doing an Odin flash. It has helped save me a time or 2.
Eta: After rereading the OP, looks like you may not be able to use this as you need to be able to boot all the way up.
Right, I was not able to boot so smart connect isn't an option, but luckily it's a new phone so no data to transfer. I did run into an issue using Odin with USB C on my laptop to the phone, I think that is how I got into that predicament in the first place with Odin downloads failing to complete. Works fine with USB 2.
Phone is all set now and working fine. Thanks for your help.