I used the odin stock TARs, incorrectly. I think they were supposed to be applied one at a time using the PDA button only, and in conjunction with the PIT file. I unfortunatly also used the PHONE and CSC buttons...which rendered my fascinate unable to connect to the cell network. so... does anybody have a TAR intended for use with the fascinate for the PHONE and CSC buttons? can anyone explain what these two buttons are? I DO HAVE several working stock fascinates with me, so can anyone point me in the direction of capturing correct ODIN tars from these phones for use on my broken phone? THANKS SO MUCH in advance!
Did you try redoing the Odin directions to get to stock?
andrewblanejr said:
I used the odin stock TARs, incorrectly. I think they were supposed to be applied one at a time using the PDA button only, and in conjunction with the PIT file. I unfortunatly also used the PHONE and CSC buttons...which rendered my fascinate unable to connect to the cell network. so... does anybody have a TAR intended for use with the fascinate for the PHONE and CSC buttons? can anyone explain what these two buttons are? I DO HAVE several working stock fascinates with me, so can anyone point me in the direction of capturing correct ODIN tars from these phones for use on my broken phone? THANKS SO MUCH in advance!
Click to expand...
Click to collapse
Sorry. You're SOL. This is why "DON'T USE THE PHONE BUTTON" is posted everywhere. If it was as simple as extracting modem.bin / bml12 from a good device, we would have done it many weeks ago.
There's nothing to be done at this point, you need to exchange the phone.
ilestdevil said:
Did you try redoing the Odin directions to get to stock?
Click to expand...
Click to collapse
Yup. I did. No go.
Odin: Do not use the phone button in odin
namebrandon said:
Sorry. You're SOL. This is why "DON'T USE THE PHONE BUTTON" is posted everywhere. If it was as simple as extracting modem.bin / bml12 from a good device, we would have done it many weeks ago.
There's nothing to be done at this point, you need to exchange the phone.
Click to expand...
Click to collapse
Right. So I do understand this is my fault, but i did not see such a warning in the Fascinate-specific or even ODIN specific articles that I found. There was only one article I found that said not to use the PHONE BUTTON, but i can't even remember where it was and i found it too late.
In some cases of non-fascinate (ie. Galaxy i9000 and older Samsung phones) articles there are specific instructions to actually use the PHONE BUTTON for modem.tar.
SO can the following threads (which are obviously very popular) be updated to reflect this warning and in the case of the more specific ODIN stock restore thread (fallingup/angel12), can we see an update that includes instructions on what to do with all 3 TARs and the 1 PIT?
I don't want to complain (luckily for me this was an extra destined-to-be-returned phone), but I do think that some very small post edits could help prevent other people from ruining their phones.
OH, and what about the CSC button, what does that do? and How do we back .TARs with ODIN? I have seen many people ask these questions, and very very few responses...anybody?
Best,
Andrew
Related
I've managed to get a warranty replacement SGS4G from T-mobile, but I'd still like to figure out if I can recover any data and also verify exactly what I did wrong.
I found a Froyo .tar to flash via Heimdall to recover from a soft brick botched ROM/kernel upgrade. Either I selected the wrong file for the wrong thing in Heimdall or the tar was not compatible with the Vibrant but I think it messed up the bootloader.
The flash completed and then then screen would stay black no matter what I did.
No download mode regardless of buttons held, battery insert order, USB plug/unplug etc. No download mode even with USB resistor jig.
I found AdamOutler's UnbrickableMod stuff and tried the ModeDetect program which never saw the device which I guess confirms the hard-brick. So is the only option left for me to apply the Unbrickablemod (solder etc.)?
I've read people saying that it's almost impossible to brick these phones - is that true?
I assume I cannot recover any data from the internal SD card easily without unbricking.
Did I try to flash the wrong file, or would using an incompatible firmware do this? I'll try to post the exact file I used if I can find it.
[UPDATE]
I was trying to use a stock Froyo firmware from samfirmware that I found linked in a thread in the forums: I9000XXJVR_CL425308_REV03_user_low_ship
...and CFRoot kernel so I wouldn't have to root manually each time I had to reflash (CF-Root-XX_OXA_JVR-v4.1-CWM3RFS).
I thought this was compatible with the Vibrant, but are these only for the Galaxy S I9000?
HAHAHAHAHAHAHAHAHAHAHA, rotflmmfao.
I'm sorry, I needed a good laugh today
At the moment, the possibilities are too varied to narrow down. Could be the Froyo ROM you picked up was made for a different phone, or the program didn't install correctly, or the download was corrupt.
Our phones are virtually unbrickable, it's true. One of the few ways to hard brick them is to mess with the bootloader and fail.
djquick said:
HAHAHAHAHAHAHAHAHAHAHA, rotflmmfao.
I'm sorry, I needed a good laugh today
Click to expand...
Click to collapse
Riff box bro. Don't listen to DJ.
Sent directly to your brain from my cyanomodded not-so-Vibrant
Sadly, no. What you flashed was not compatible with the Vibrant. It's for the international version of the Galaxy S only, the i9000. Sounds like your phone is hard bricked thanks to the i9000 bootloader the flash must have added.
Thanks, stupid mistake on my part.
Noob question then: what must only be used for the specific phone it's made for vs. what can be used with other phones? Firmware, bootloader, kernel, modem, ROM, etc?
Hi folks.
I attempted to root my S2 a few moments ago with the method in http://forum.xda-developers.com/showthread.php?t=1331784 and everything looked like it was going well. It got to the end of the batchfile and rebooted the phone, only this time nothing came up, just a black screen. Then, I noticed some random pixels on the black screen, only a few, and random colours. Then I noticed more of them appearing slowly, filling the screen. I was confused and watched it in horror for a minute until the whole screen was full and the colours were turning white. I switched off the phone and tried again. No good.
The instructions say to try holding volume up, home and power to turn it on so it starts recovery mode but nothing different happens. I tried download mode and at least that responds.
What are my options? I'm new to all this but having read up I thought I understood it. It seems I was very wrong.
Help!?
Considering that's meant for the Galaxy Note, what zImage did you use with it (assuming you did step 1.2, not-yet-rooted.bat)
I used the one linked, called CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM4.zip.
I had seen people posting in the thread that it worked on the SG2 though. Now you mention it I can clearly see the SGN refers to the Galaxy Note. I was feeling reasonably confident about things but now I think I'm either going to scream or cry.
Is there any way I can salvage this?
You mentioned download mode works, so just flash a stock kernel (or CF-Root kernel if that's what you're after anyway) for the correct device as PDA in Odin and hope for the best!
If you do indeed have an I9100 (check before flashing anything else), CF-Root or Official.
Directly flashing a CF-Root kernel in download mode will increment your binary counter though. So probably best to go for stock kernel.
Thank you for your responses.
I have seen the following on that page;
Orange UK ORAKJ4 CSC: *The URL goes here*
(above link modified as I'm a new user)
I'm from the UK and with Orange so I think that's the one, it has the KJ4 in the name too. Do I use Odin for this?
It's a stock kernel you need, not CSC. Carrier branded ROMs/kernels are in a different thread, [ROMS]Official i9100 carrier branded firmware download for Odin Flash. Do you have any idea what your phone was running before? I would hazard a guess that it's actually the BVKJ4 kernel from that thread which would match, based on the one you flashed earlier.
My bad, I didn't see you mentioned Odin in your reply. I'm feeling a bit stressed out and not thinking well. Unfortunately, having looked down the various packages, I'm unsure now which I need. The one I quoted is a "CSC package", whatever that is.
Can you guide me further because I don't know what my old version was originally.
I have looked in the new thread you sent and I think I need the;
Firmware info: PDA:BVKJ4|PHONE:BVKJ4|CSC:ORAKJ4
You are absolutely right, it did start with BV! If I use the branded Orange one I should be back to where I started? Would flashing it increment my counter? It's the least of my worries at the moment, but if there's a way of preventing it, I'm all ears.
Thanks again.
Flashing a stock kernel in Odin should not increase your counter and will hopefully get your device booting again.
If that's the kernel you go for, you should be picking the file Kernel_I9100BVKJ4.tar.md5 (not Kernel_I9100BVKJ4.exe, extract it first) as PDA in Odin. Just make sure your Odin options look like the ones in Intratech's first screenshot in his guide (linked earlier).
Thank you, it's half downloaded at the moment. I'm glad you mentioned having to extract the contents because I'd have tried sending the whole 300mb or so to the phone.
Hopefully then, this will flash ok and I'll be back in business!
I feel very much out of my depth now.
It should only be about 5MB, it's just the stock kernel you need (i.e. the second BVKJ4 link).
Oh, it's finished downloading and I see when extracted it's actually just that one file.
Here we go, fingers crossed...
I saw your post just in time. I have downloaded the stock one, at 5.1mb.
I could have made another horrible mistake if I'd gone ahead with things. I will now attempt to flash the 8mb Kernel_I9100BVKJ4.tar.md5 file from that archive I've just downloaded (the 5mb one).
Have I missed anything?
hollal said:
I will now attempt to flash the 8mb Kernel_I9100BVKJ4.tar.md5 file from that archive I've just downloaded (the 5mb one).
Have I missed anything?
Click to expand...
Click to collapse
I don't think so. Just make sure you follow the instructions from Intratech's thread linked earlier, specifically Flashing Firmware with Odin.
Well, flashing that stock kernel has done wonders. Thank you so very, very much!
I will try to find the thread where I was reading about this zergrush exploit working on this phone. I can only assume I'd read it and read this one after and put the two together by mistake. I don't particularly understand the whole thing which is why I liked the idea of this exploit as it keeps things stock.
I will see if I can find that thread and read it carefully.
I think I'll call it a night now, and get to bed. Thanks again.
You're probably still rooted, since zergRush did its thing earlier, and flashing a kernel shouldn't have changed that. The only thing you did wrong was using a CF-Root kernel (zImage) for a different device. If you'd have used one for the right device, it should have worked fine.
I'm not sure how I'd check for root. I don't have that superuser program available as an app.
You could try running an app which requires root and see if it works, but if you don't see the Superuser app, it seems unlikely it will. Anyway, if you're still feeling up to it, the simplest way to root (in my opinion) is using the same exploit you tried earlier, but from a different thread (and it doesn't come with the risks of using the wrong kernel ;-))
[16/Nov][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v3.0](zergRush Exploit).
Takes about 3 minutes.
I think I've found thread I was reading earlier today...
http://forum.xda-developers.com/showthread.php?t=1321582
What part did the ZergRush affect, if not the kernel? If I use this version, with the correct zImage file if I can find it, then I should be ok second time around.
lol.. the joy of cross posting!
I was going to go to bed but now you've made me want to finish what I started.
Please work....
Hello everyone, my old thread was locked before I could explain and clarify my situation. I have a problem with my display for my I777. It is overly sharp and the the color is faded, this started after I flashed the international firmware using odin to fix a boot loop. I'm still new at this and I made a mistake of using the wrong firmware so I used the Odin One click from this thread http://forum.xda-developers.com/showthread.php?t=1313659 and revert back to stock firmware. However the display still looks terrible and did not change, so if anyone knows how to help me with this it would be much appreciated.
More details: I used the information from the last post in this thread: http://forum.xda-developers.com/showthread.php?t=1266390
and flashed the 3 files with odin. This was able to fix my boot loop, but result in a bad display. The other change that I notice Vol up + Vol down + power does not work, but it changed to Vol down + Power to go in download and Vol up + power for recovery. This also did not change back after using the Odin One click to revert to stock firmware.
And please forgive me for not noticing the sticky, however all the threads linked in the sticky I have already read through searching with google. Thank You.
My suggestion is to follow the return for warranty thread and call att for a warranty exchange. If you followed all the return to stock instructions perfectly, then I don't see how your screen would be permanently damaged that way.
Sent from my SGH-I777 using xda premium
I couldn't find the files you flashed to verify, but from your description, it sounds like you flashed I9100 bootloaders and param.lfs. To recover, go to the Download Repository and flash the I777UCKH7-CL503881 Stock Binaries. You can use the one-click downloader. This will flash the complete I777 UCKH7 firmware including bootloaders and param.lfs. This should correct any display problem caused by firmware (assuming it is not a hardware problem.)
Thank you for the replies, I cannot return this phone cause I have ticked the counter. And I'm 99% sure this is not a hardware error.
And creepyncrawly this is where I downloaded the files from http://hotfile.com/dl/116656855/2ccf2f4/I9100XWKDF.rar.html and followed these instructions from the last post in this thread http://forum.xda-developers.com/showthread.php?t=1266390.
The password for the file is: samfirmware.com
Start Odin and put these in the following
PDA: CODE_I9100XWKDF_CL170898_REV02_user_low_ship.tar
CSC: GT-I9100-MULTI-CSC-OXXKDD.tar
Modem: MODEM_I9100XXKDJ_REV_02_CL996627.tar
Forget the rest of the files. DO NOT SELECT A PIT FILE AND DO NOT TICK REPARITION.
Put your phone into download mode and connect the usb cable. When the Odin box turns yellow press flash and wait until phone reboots. The first boot will take a while... be patient.
Edit: i will now try and flash the stock binaries, hopefully this will work and I think it will. I will report the results after trying.
Firmware downloaded from sammobile will contain the bootloaders and param.lfs. If you look in CODE_I9100XWKDF_CL170898_REV02_user_low_ship.tar you'll see them all in there.
You also flashed the csc. I'm not sure if it will even change things on our phone, but if so, you have to correct that too. CSC is region specific or carrier specific. You might learn more about it in the Hellraiser thread in the ported development forum. It may very well be a non-issue though.
It worked! The colors are back to normal and so is the sharpness. Thank you very much creepy, now I also learned some new stuff about binaries and param.lfs. As for the CSC I do not notice any change, my region is ok and carrier is still At&t. This might be because I flashed a bunch of roms made specifically for the I777 like cognition 777 and unamed,to try and fix the color. I think there is CSC file in the roms and it over wrote the sammobile csc? Correct me if I'm wrong, but all seems to be well again thank you very much all.
Hello everyone,
I did the same mistake again by updating my S2 from GingerBread to IceCreamSandwitch without calibrating the horizontal accelerometere, and now my phone sensor is a bit off "to the left"
(when i play games like " Trial ", the phone is supposed to be in the "normal" position so the rider should not move at all but in my case he is always going back {like am rotating the phone to the left} so i have to rotate the phone about 15 degrees to the right in order to be "normal" )
Unless you have a better solution for this problem cause seriously, why on earth there is only a gyroscope calibration for a device that have more than that sensor >_< !??!
anyway
i would really appreciate if your link me to all the necessary files to downgrade from ICS to GB,
IMPORTANT:
i don't want to root my phone cause i will update to official ICS again
SOLVED
i just need the PDA file which i found my model here : http://www.androidfirmwares.net/
thank you
Maybe post in the dedicated forum for that device lol
You mean you did the same thing on your S2 as you did on your S Advance 6 weeks ago ? If so, go get the rom files you need from Samfirmware, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash Stock firmware'.
If you're still talking about your S Advance then yeah, you're obviously in the wrong place.
MistahBungle said:
You mean you did the same thing on your S2 as you did on your S Advance 6 weeks ago ? If so, go get the rom files you need from Samfirmware, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash Stock firmware'.
If you're still talking about your S Advance then yeah, you're obviously in the wrong place.
Click to expand...
Click to collapse
yes that's exactly what happened (am with S2 now) and i actually tried both Samsung-updates and samfirmwares but the search results contain Roms for 4.1.2, 4.0.3 and 4.0.4 i might be searching in the wrong place though so i would really appreciate it if you post a link for me
thank you very much
If you can't find GB firmware at those two places, you can try AndroidFirmwares.net, but they probably won't have what you want either. If they don't, you're probably SOOL; try Google searches or use something else (or do a bunch of XDA searches, you might get lucky & someone might have uploaded it somewhere & linked to it in a thread way back).
Edit - You need to use the pulldown boxes @ Samfirmware better, there's plenty of GB firmwares available. If there isn't one for your country/carrier, you're going to have to use something else.
MistahBungle said:
If you can't find GB firmware at those two places, you can try AndroidFirmwares.net, but they probably won't have what you want either. If they don't, you're probably SOOL; try Google searches or use something else (or do a bunch of XDA searches, you might get lucky & someone might have uploaded it somewhere & linked to it in a thread way back).
Edit - You need to use the pulldown boxes @ Samfirmware better, there's plenty of GB firmwares available. If there isn't one for your country/carrier, you're going to have to use something else.
Click to expand...
Click to collapse
thanx man i'll keep looking, but just a question, is it really impossible to recalibrate the accelerometer on Android 4.1.2 ?
i am 100% sure that it's not a hardware problem so why there is no way to fix that
No idea, never had a problem with it myself. Hopper8 had issues with it maybe 12 mths ago & searched high/low for a solution went really 'in depth' with it. Maybe search for his threads on that issue/from about that time.
MistahBungle said:
No idea, never had a problem with it myself. Hopper8 had issues with it maybe 12 mths ago & searched high/low for a solution went really 'in depth' with it. Maybe search for his threads on that issue/from about that time.
Click to expand...
Click to collapse
Thank you, i checked that but it seems that he is facing problem with the gyroscope mine is an accelerometer problem (i make casual mobile games for a living and i made a little accelerometer test, it is simple 18 degree "wrong" to the left)
anyway,
i found this website : AndroidFirmwares.net - News and am downloading this firmware the bad news is that i have no idea where to find the .pit file, cause as i remember with my S-Advance (and my old S too) i need a pit file to use with Odin right ? and it's always a very small size,
any help with that please ?
Don't touch a PIT file unless:-
A) You have a specific reason to.
B) You know what you're doing.
I've seen literally hundreds (and no doubt there has been many more I haven't seen) of people flashing PIT files when they absolutely didn't need to brick their phones on here over the past 2 & a bit yrs (almost always a case like yours of simply needing to flash a one part stock firmware to fix, but people have to over-complicate things).
Neither A nor B applies to you, so don't do it. If you think what I've said is overkill, I'm merely trying to save you from having to throw your phone in the bin.
MistahBungle said:
Don't touch a PIT file unless:-
A) You have a specific reason to.
B) You know what you're doing.
I've seen literally hundreds (and no doubt there has been many more I haven't seen) of people flashing PIT files when they absolutely didn't need to brick their phones on here over the past 2 & a bit yrs (almost always a case like yours of simply needing to flash a one part stock firmware to fix, but people have to over-complicate things).
Neither A nor B applies to you, so don't do it. If you think what I've said is overkill, I'm merely trying to save you from having to throw your phone in the bin.
Click to expand...
Click to collapse
Thank you,
so following what you said, i only need to select the downloaded firmware from the PDA button and press start ?
Remark :
i tried that and i got this error :
"Can't open the serial(COM) port."
Since kies is completely closed and am 100% that i have the USB direver installed (phone detected and i've done that before)
i am going to assume that my cable or my ports are the cause of the problem, if you have a better suggestion please illuminate me, otherwise i'll try with different cable/PC tonight and keep you updated, lastly i REALLY hope that an expert android developer or maybe someone that can spread this problem for more people cause it is VERY annoying to have to do this for such a minor problem just because the OS developers have forgot or didn't want to allow us to adjust all the phone sensors ...
Note that after this downgrade, i will have to upgrade again and restore all my previous data,setting, apps again... and that is a real painful waste of time >_< !!!
Hopper8's 'Odin troubleshooting' thread stickied in the General section has all the info/stuff you need to try in order to get a successful flash.
MistahBungle said:
Hopper8's 'Odin troubleshooting' thread stickied in the General section has all the info/stuff you need to try in order to get a successful flash.
Click to expand...
Click to collapse
Thank you very much, changing the cable solved this, the phone is back to stock again :victory:
just in case someone face this,
i got a SplashScreen loop (my SplashScreen is changed from TIM {italian operator} to the default samsung wich is another victory for me :highfive: )
anyway,
that was simply solved by booting into recovery mode and wipe all data
Edit :
Samsung Kies doesn't detect new update anymore, i think that is because i only used PDA in Odine ?
i'll have to update with Odine again (it take less time than kies anyway)
Hey guys, I am a newbie to rooting and I messed up big time. I used TowelRoot.com to Root my Galaxy S4. Everything went smoothly. I did a little research on custom roms and back ups but couldn't fully understand it. Sorry to sound like a complete noob! But I am. Let's get to the point. So I read online about someone editing the system file Build.Prop and got the new Samsung Galaxy S5 Notification bar which I attempted. I ended up screwing up because i edited the NAME of the file and not the actual string attached in the folder. Anyway, now my phone is not starting up. I see the Galaxy S4 Logo then it goes all black. I am able to boot to recovery and also download mode. But I'm stuck here. Is there a easy solution for this? I read about downloading Odin and doing a custom rom / flash. But I wanted to avoid all the difficult stuff if i could. Any suggestions????
that413trini said:
Hey guys, I am a newbie to rooting and I messed up big time. I used TowelRoot.com to Root my Galaxy S4. Everything went smoothly. I did a little research on custom roms and back ups but couldn't fully understand it. Sorry to sound like a complete noob! But I am. Let's get to the point. So I read online about someone editing the system file Build.Prop and got the new Samsung Galaxy S5 Notification bar which I attempted. I ended up screwing up because i edited the NAME of the file and not the actual string attached in the folder. Anyway, now my phone is not starting up. I see the Galaxy S4 Logo then it goes all black. I am able to boot to recovery and also download mode. But I'm stuck here. Is there a easy solution for this? I read about downloading Odin and doing a custom rom / flash. But I wanted to avoid all the difficult stuff if i could. Any suggestions????
Click to expand...
Click to collapse
For future reference, let's not go editing files on your phone when you don't know what you're doing.... just saying.
You're gonna need to Odin flash, which is not difficult, what was your baseband version?
liljoe727 said:
For future reference, let's not go editing files on your phone when you don't know what you're doing.... just saying.
You're gonna need to Odin flash, which is not difficult, what was your baseband version?
Click to expand...
Click to collapse
Not sure cause the phone is turned off. I google searched it's either I545VRUFNC5 or I545VUFNC5. How will I go about finding the correct one? I know my phone was 4.4.2 before it was bricked and that the model number is i545
that413trini said:
Not sure cause the phone is turned off. I google searched it's either I545VRUFNC5 or I545VUFNC5. How will I go about finding the correct one? I know my phone was 4.4.2 before it was bricked and that the model number is i545
Click to expand...
Click to collapse
What did you Google search to get this information? You should have known this prior to doing anything with your phone
If your baseband is NC5, this link http://forum.xda-developers.com/showthread.php?t=2735172 will have your Odin downloads and your wipe/no wipe factory images. Make sure you read through the thread and you should be golden. Also, make sure you only flash the NC5 images, do not click on the links for MJ7 or MDK.
liljoe727 said:
What did you Google search to get this information? You should have known this prior to doing anything with your phone
If your baseband is NC5, this link http://forum.xda-developers.com/showthread.php?t=2735172 will have your Odin downloads and your wipe/no wipe factory images. Make sure you read through the thread and you should be golden. Also, make sure you only flash the NC5 images, do not click on the links for MJ7 or MDK.
Click to expand...
Click to collapse
It worked like a charm! Thank you so much!!
Not to be a dumb A** but saying not to play around with your phone if you don't know what your are doing is ... will there would be no need for this forum. Trying things and getting in trouble is part of learning. Education is expensive.
I sis the same thing this guy did in changing part of the Build.Prop.
aknisley said:
Not to be a dumb A** but saying not to play around with your phone if you don't know what your are doing is ... will there would be no need for this forum. Trying things and getting in trouble is part of learning. Education is expensive.
I sis the same thing this guy did in changing part of the Build.Prop.
Click to expand...
Click to collapse
90 percent of the "problems" people have on here are answered by simply copying and pasting a link to the corresponding thread that can be found in the forums for our device. I am not saying to "remain ignorant and not mess with your phone", but to do research and take the time to read the information, which is readily available, that pertains to what you're trying to do. That's all. Not trying to sound like a jerk or anything.
Jesus loves you!
Odin is very simple to use. You just download the correct tar file for your phone, put you phone into download mode, and hit start and it runs everything it self.
The only downside is you have to start from scratch.
liljoe727 said:
What did you Google search to get this information? You should have known this prior to doing anything with your phone
If your baseband is NC5, this link http://forum.xda-developers.com/showthread.php?t=2735172 will have your Odin downloads and your wipe/no wipe factory images. Make sure you read through the thread and you should be golden. Also, make sure you only flash the NC5 images, do not click on the links for MJ7 or MDK.
Click to expand...
Click to collapse
I so am loving you right now, thanks for the info.
The linked thread did not work for me, and I can't figure out why... was running hyperdrive 18, flashed blackbox 3.2.3 and then I got softbricked. The recovery thread tars keep failing in odin. How do I diagnose this?
Hi guys,
I have the same question. My phone is stuck on Verizon logo and I did some research and it says it soft bricked. I want wipe/reset it using Odin and the OS file. But my question is that my phone was originally US cellular and then flashed to Verizon I545. So should I be using the Verizon OS file or the US Cellular file? Newbie here, appreciate your responses.
P.S. I did not mess with the phone like the original poster, I woke and the phone would not start.
tojikjon said:
Hi guys,
I have the same question. My phone is stuck on Verizon logo and I did some research and it says it soft bricked. I want wipe/reset it using Odin and the OS file. But my question is that my phone was originally US cellular and then flashed to Verizon I545. So should I be using the Verizon OS file or the US Cellular file? Newbie here, appreciate your responses.
P.S. I did not mess with the phone like the original poster, I woke and the phone would not start.
Click to expand...
Click to collapse
if you had the red verizon splash screen at startup then go ahead and
flash the verizon odin package (make sure you use a package the same version or lower as to what was previously on the device) to avoid blowing a qfuse
Thanks, it worked