My Verizon Wireless Galaxy S7 fails to boot and bootloops even after flashing the correct stock firmware using Odin3, and when trying to use the Verizon Wireless Software Upgrade Assistant, the first error shows up as 'DVIF!!' and the second being 'Unsupport dev_type.' The phone was working perfectly fine with no signs of an issue up until some random point about a week ago where it started to bootloop, showing the splash screen, turning off, restarting with the vibration, splash screen, and repeat. The phone ONLY boots into Odin mode, and i've only gotten it into Maintenance Boot mode once on accident. Which did nothing to help.
Some more info:
Model #: SM-G930V
Hardware Revision: 0.6(as read by the OS settings before it bricked)
CPU: Snapdragon
CSC: VZW
Some more issues i've encountered while trying to rig it back together:
When draining the battery to 0 and plugging it in, No battery level indicator or charging light appears. The only real indication i have is when it tells me to plug the phone in, and the lightning bolt above an empty gauge, not even displaying a battery percentage. After a few seconds to a couple minutes, it will try to boot again. Which of course, ends up in a bootloop.
sometimes, when booting, the entire screen will appear "screwed-up", the colors being off or the screen being blurry and mis-matched like a jigsaw puzzle.
This phone was purchased shortly after the launch, and has not had a reset or any need of replacement components.
Before it bricked, i had done these four things:
Install Mobile Performance Meter(data app, sells your information but you get credit for it)
Install My TruConnect(the current carrier i'm on and their app, since the phone was unlocked and i didn't use verizon anymore)
Enable developer mode
Allow USB Debugging
I used to have one of these a few years ago, I still have the Samsung firmware packages many different versions - from what I recall, the device let me downgrade firmware as long as I flashed them in succession, so as long as I could find the next lower version, it would let me flash it, but if I tried to skip any firmware versions, then it would fail to flash with Odin. Why am I telling you this? Because if you say you can still get into Odin mode, you may have a shot at unbriking if you were to successfully flash the next lower version firmware than the current firmware version that you have on it presently - it's worth a shot.
I also remember it was super sensitive to using a non-samsung branded usb cable, vs a real Samsung cable. Seriously, it's no BS. ODIN would stall or fail with one cable tested good on other devices, then using original samsung cable would finish the same operation successfully. Also, sensitive to being used attached to a VM, vs connected to a real PC. I was on a Mac using a Parallels VM running ODIN in Win7, and ODIN would fail even though it would mount the USB device correctly in the Win7 VM and in ODIN - then I ran same setup connected to my Lenovo Win7 laptop, and ODIN had no problems. And of course I'm assuming you're using a version of ODIN compatible with S7.
Although I haven't touched Samsung for a while It's probably the same old routine..
Flash stock rom with odin, straight into fastboot, wipe data/factory reset, turn off, flash AGAIN the stock rom. Its IMPORTANT that you don't let it boot the OS between flashes. Reboot after the second flash and it should go into OS. If it doesn't then the nand has died, which a known Samsung thing, ESPECIALLY if it was rooted.
Artifacting on the screen (dodgy broken looking colours) is most likely a dead nand.
shivadow said:
...If it doesn't then the nand has died, which a known Samsung thing, ESPECIALLY if it was rooted.
Artifacting on the screen (dodgy broken looking colours) is most likely a dead nand.
Click to expand...
Click to collapse
This is what I've been thinking from the start, a dead/corrupted internal memory NAND - But I have experienced this device and other Samsung models that display signs of NAND corruption, but after stubborn ODIN flashing using proper USB cable, the right chosen firmware version, the right USB port, and a fitting version of ODIN, I have unbricked, after repeated failed ODIN flashing attempts. I'm not saying this is your case, only that there is a chance (however small) that it could be your case. If you need to download a few different firmware versions ODIN packages, let me know in a PM.
shivadow said:
Artifacting on the screen (dodgy broken looking colours) is most likely a dead nand.
Click to expand...
Click to collapse
Typically the broken-up artifacting happens when the phone bootloops multiple times for me. Also, the vibration will keep going even after it's attempt to boot. Afterwards it tries to fix itself by restarting, which of course starts up the process again.
Now i might doubt that the NAND is dead, but i wouldn't be surprised. 7 years old, tossed and thrown in a thick rubber case as a work phone in the Home Depot, and pre-1.0 hardware revisions all point towards some problem. Surprisingly the only thing damaged is the front lens cover.
So are you able to hold vol-down or up, HOME button, or POWER btn keys and get it in ODIN mode after it restats trying to "fix itself"? Are you able to get it in ODIN mode by any means?
imonxda said:
So are you able to hold vol-down or up, HOME button, or POWER btn keys and get it in ODIN mode after it restats trying to "fix itself"? Are you able to get it in ODIN mode by any means?
Click to expand...
Click to collapse
Yes. ODIN Mode works perfectly fine with no issue, the only thing that does not work whatsoever is booting. Some smaller things do not work normally but still appear to function, at least i hope.
imonxda said:
I also remember it was super sensitive to using a non-samsung branded usb cable, vs a real Samsung cable. Seriously, it's no BS. ODIN would stall or fail with one cable tested good on other devices, then using original samsung cable would finish the same operation successfully. Also, sensitive to being used attached to a VM, vs connected to a real PC. I was on a Mac using a Parallels VM running ODIN in Win7, and ODIN would fail even though it would mount the USB device correctly in the Win7 VM and in ODIN - then I ran same setup connected to my Lenovo Win7 laptop, and ODIN had no problems. And of course I'm assuming you're using a version of ODIN compatible with S7.
Click to expand...
Click to collapse
I don't have the samsung OEM cable anymore, but i have a decent, although small cable that came with another one of my USB Devices. i've been using that one since, and for now it hasn't provided any fails related to the cable. Only downgrades and recovery using the Verizon Upgrade Assistant appear to fail on the phone's end.
ApolloFJ said:
I don't have the samsung OEM cable anymore, but i have a decent, although small cable that came with another one of my USB Devices. i've been using that one since, and for now it hasn't provided any fails related to the cable. Only downgrades and recovery using the Verizon Upgrade Assistant appear to fail on the phone's end.
Click to expand...
Click to collapse
I can't stress the importance of the cable enough. I had the same situation and I had used other cables that worked fine and showed no signs of having anything wrong, but they failed with ODIN flashing - the same cables worked fine for the S7 to do charging and MTP file transfers, the S7 would say "fast charging" when plugged in, but when used with ODIN, they would fail - untill I got a samsung cable, then ODIN flashing worked.
imonxda said:
I can't stress the importance of the cable enough. I had the same situation and I had used other cables that worked fine and showed no signs of having anything wrong, but they failed with ODIN flashing - the same cables worked fine for the S7 to do charging and MTP file transfers, the S7 would say "fast charging" when plugged in, but when used with ODIN, they would fail - untill I got a samsung cable, then ODIN flashing worked.
Click to expand...
Click to collapse
What I'm saying is, get a samsung cable, get to ODIN mode and flash a proper Samsung firmware - if it's successful, then you're good, if it fails, then you're looking at what @shivadow said, a dead NAND. But if you keep using that cable and using Verizon Upgrade Assistant, and not ODIN flash firmware through proper cable, getting the "phone failing" doesn't prove anything, - you must eliminate the possiblity of your S7 not "liking" the USB cable and eliminate the possibility that your NAND has corruption from bad previous flashing or from Verizon Upgrade Assistant doing something bad because of your USB cable.
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Maybe help with Odin problems
joke19 said:
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Maybe help with Odin problems
Click to expand...
Click to collapse
Wow, super cool, thanks! @ApolloFJ definitely get one of these for use with your S7, I think the 3.13.1 should work fine
imonxda said:
though I see jrkruse recommends Odin3_v3.14.1_3B_PatcheD.7z, so maybe get that instead
Click to expand...
Click to collapse
imonxda said:
Wow, super cool, thanks! @ApolloFJ definitely get one of these for use with your S7, I think the 3.13.1 should work fine
Click to expand...
Click to collapse
Currently trying it out. It passed without issue the first time, working on a second flash to be absolutely sure it works. I Should probably tick the NAND Erase and the Re-partition bits.
I'm starting to be fairly certain the NAND is dead. I've tried almost everything, even writing TWRP to it but that didn't change the recovery system whatsoever. I've even started to give up hope for it. Maybe she'll just rest on a shelf for awhile before i try again, to the same result.
EDIT: I just tried booting into ODIN Mode, and the screen appeared to be on, but no vibration and a few slightly miscolored white dots appeared on the upper-left-center of the screen, the upper-left of the screen, and the bottom to bottom-left of the screen. Are these more indications of a dead NAND? I've never seen this before except for when it does it's crazy weird screen thing, but now it's just the pixels.
EDIT 2: Now i tried completly wiping the NAND with no firmware and it still hasn't changed, splash screen still appears and it still won't boot.
Well I guess it's dead, sorry.
imonxda said:
Well I guess it's dead, sorry.
Click to expand...
Click to collapse
Is there any software/hardware you've found that'll make it boot from the SD Card? Maybe i'll have a chance to save or even give it new life that way.
ApolloFJ said:
Is there any software/hardware you've found that'll make it boot from the SD Card? Maybe i'll have a chance to save or even give it new life that way.
Click to expand...
Click to collapse
On S7 there is nothing I know of. Multirom can install/boot roms from external SD, but it only runs on a minimal number of devices, like many HTC devices and a few google devices, also a few one+ devices and some others, but not S7.
But if your NAND is corrupt, you won't be able to do anything anyway, even if you find something that can boot from external because your internal NAND memory has to be healthy enough to at least have the Samsung firmware installed and working.
You're looking at a paperweight at this stage.
If you want, you can mail it to me and I might be able to succeed to get firmware flashed on it and bring it back to life, but that's a SUPER long shot because if the NAND is too far gone, NOTHING can fix it, short of taking it apart and replacing the main board that contains the NAND chip - this is NOT fun to do at all, and not even worth it 'cause you'd have to find some cheap ebay S7 for parts only that has a Clean IMEI and poach the main board - you might as well buy a used WORKING S7, right?
Related
I have a problem with Galaxy s2. Basically it started to drain my battery like hell.
It gets empty in about 10 hours.
Now when I want to flash the phone once again in order to get everything back as it was when I bought it I cannot. This is due to MTP connection activating itself as soon as I turn on the phone. And I cannot enable usb debugging due to that as it says that I have to remove the USB cable.
In addition my phone charges itself really fast about 2 hours. And when I try to power it on without charger plugged in it gives me charging image and yellow triangle with ! in it and thermometer aside flickering. Does anyone have any ideas how to fix my phone?
Have you tried using CWM to wipe all data + clear all cache, then do a fresh re-install?
Yes I tried it now. It still says my USB is connected when its not. And now it doesnt unlock my sim card.
Factory reset that dont work return phone to a service centre ..
jje
Well thats the case I have voided warranty already. Wondering if there are any chances I could put old rom back before returning it?
Make a DIY USB JIG then flash it back to stock rom and have it checked.
EarlZ said:
Make a DIY USB JIG then flash it back to stock rom and have it checked.
Click to expand...
Click to collapse
Not sure what do you mean by DIY USB JIG but I cannot flash it because I cannot switch USB debugging on... Thats the case it shows me that USB is always connected when it isnt and when USB is connected it doesnt let to switch on USB debugging.
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
JJEgan said:
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
Click to expand...
Click to collapse
Thank you all who have replied. I have now managed to get over the USB issue somehow but still something is wrong either with battery sensor or battery. When I power off my phone it switches on automatically and shows the thermometer and battery charge icon. Anyone else have had this problem? It also charges up to 95% and it bursts to 100% very quickly.
EDIT: Now I tried my friends battery and I did not get the flickering temp error and my friend didnt get it with my battery as well. So something now I'm totally out of ideas.
Service centre .
jje
I am having the same issues here, wonder if the topic creator resolved this in any way? I am thinking of getting a new battery?
Just FYI wear a condom or something on your galaxy S II. As it turns out from service my phone supposedly has liquid damage which does not the warranty apply. I have to pay 240 euros in order to get it fixed :S
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Just order a high from ebay
Sent from my GT-I9100 using XDA Premium App
cmcole101 said:
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Click to expand...
Click to collapse
Well kiss my rosy red butt-cheeks! Speaking from personal experience as tech support, I know empirically to replicate something 52 times prior to asking for assistance. This instance shouldn't have been an exception!
Directly after posting this request for assistance, I decided to try Odin once again and DANGED if this time it found my device even with the "Firmware encountered" error showing. Odin stopped around 90% and forced me to reset my S2, but this time it went right into Download mode with nary a fuss. Now Odin just successfully installed KG6.
So if there is anything to be learned from this experience, either by other users with similar issues or myself, it is "if at 1st you don't succeed, try again and again and again and again."
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Deenybird said:
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Click to expand...
Click to collapse
I use heimdall personally. Never had any problems with it. Do you have all the sgs2 drivers installed?
Also check md5 sums to make sure your download is ok.
Sent from my SGH-I777
I'll try heimdall. Drivers should be fine as kies is installed. Rom should be good as I've tried 2 different download sources
Make sure you install the libusb drivers for heimdall before flashing. The instructions are in the heimdall readme. Good luck
Sent from my SGH-I777
Just wanted to post that my problem is solved.
Summary: My AT&T Galaxy SII showed an error on boot (software upgrade failed. connect to kies...). Kies wouldn't even recognize the device so that route was a no go. So as everyone's recommended method of last resort, I decided to flash the device back to stock via odin. I entered download mode (volume up + volume down and plug in usb) and Odin would recognize the device, I would load the stock rom in the PDA slot and hit start and it would begin normally, but it would always fail after a few seconds on 'NAND write start', or 'factoryfs.img'. So I got a 1 click download solution using odin for reverting my phone back to stock. Same thing, it would recognize the phone, but stall out and fail. I also tried flashing clockworkmod via odin but and same problem. People recommended I try heimdall. It would recognize my device, and then fail after 'kernel 100%'.
I tried both programs on 3 different computers, and must have tried 12 different USB slots amongst all of them. I'm fairly handy with this stuff and I worked for hours on it.
xtra info: I had successfully used odin on my computer to flash a kernel just a week ago so I know my stock usb cable was working etc...
Resolution: So I hung my head and drove to the ATT store. After pressing a few buttons on the device and not getting anywhere they sent me to a nearby Device Support Center. I told the girl at the counter that my phone booted to this error screen and that connecting it to Kies did nothing. She asked if it was ok that in the case that she couldn't fix it she would offer me a replacement. I said that was fine and after 10 minutes in the back room she came out with a replacement (free of charge).
Well that was the good news. For the bad news, unfortunately I still don't know how to fix the problem I had, and don't really know how to avoid it in the future. I thought phone's could only get truly bricked if you messed with PIT files and such. There didn't seem to be anything more I could do than flash with odin or heimdall as those were already last resorts. I know I had the right files, the right drivers, and working usb. No matter how crazy I got with my iphone, a full restore was only a click away by plugging in to iTunes. Somehow I messed up my phone so bad that even the device support center couldn't fix it....? Shouldn't have had to be like that.
Thank yous: Thanks to ATT for having a walk-in store and for so easily offering up a replacement. Thanks to the many people on the web who offered remedies.
tl;dr - phone broke, att replaced, still a mystery
So, you've been flashing stuff and now for whatever reason, your phone won't boot.
Now you're trying to save your poor phone's life with Odin but odin keeps failing.
Here are a few basic steps to go over to try and get Odin to cooperate:
First things First, if the device shows no signs of life whatsoever, you press the power button and it just sits there blank,
i am sorry to inform you, you are bricked and at a point beyond the help of odin. this will require JTAG to fix.
if you are in a bootloop or the phone freezes at some point of the boot sequence, this is what odin can fix.
if you do not have odin, get it HERE
here are the USB DRIVERS
i will not provide links to stock firmwares to use, those are ALL OVER the forum,
this is to help get those flashed not to completely hold your hand
only thing i'll add about which to use is:
DO NOT USE A PACKAGE CONTAINING BOOTLOADERS
IF ODIN FAILS DURING THE WRITING OF A BOOTLOADER THAT WILL BRICK THE DEVICE
STEPS:
Use USB ports connected to MOTHERBOARDno front panel ports, hubs etc...
Use a Known good usb data cable preferably OEM, you may want to have 1 or more spare just in case
right click odin and run as administrator
Have odin ready to go before you touch your phoneAll files in the proper place, now boot to DL mode and connect
If this is still Failing try:
Exiti Odin
Uninstall USB drivers
Reboot PC
Reinstall USB drivers
Switch usb port being used on pc
Rinse and Repeat until either it works or all ports exhausted
If after trying all motherboard ports odin is still cursing at you from Asgard, try one of those spare cables i mentioned earlier.
Sometimes PCs just don't wanna work, if you have the availability of another pc ANYWHERE (even the library or something) try these steps on that machine.
If its still failing on multiple pcs, clean out the usb port on the phone with Q-tip dipped in rubbing alcohol
then blowing it out with compressed air and let dry.
still nothing? you may have a hardware failure in the usb port on the phone.
Standard disclaimer: I AM NOT responsible for anything you've done or will do to your device.... this is merely a reference for you to use to get yourself out of a bind.
thank you, you're welcome, Good luck and happy flashing.
Nice work Studa .... had to fight the urge to quote the op so you knew what I was talking about.
Bubbajoe40356 said:
Nice work Studa .... had to fight the urge to quote the op so you knew what I was talking about.
Click to expand...
Click to collapse
I kind of like seeing everything written out several times . . . it's like deja-vu all over again.
Good job cris, lets hope this gets used!
Lol... I kinda made it for me to use.
I've typed this out a couple dozen times... now I can just link to here
studacris said:
So, you've been flashing stuff and now for whatever reason, you're phone won't boot.
Now you"re trying to save your poor phone's life with Odin but odin keeps failing.
Here are a few basic steps to go over to try and get Odin to cooperate:
First things First, if the device shows no signs of life whatsoever, you press the power button and it just sits there blank,
i am sorry to inform you, you are bricked and at a point beyond the help of odin. this will require JTAG to fix.
if you are in a bootloop or the phone freezes at some point of the boot sequence, this is what odin can fix.
if you do not have odin, get it HERE
here are the USB DRIVERS
i will not provide links to stock firmwares to use, those are ALL OVER the forum,
this is to help get those flashed not to completely hold your hand
only thing i'll add about which to use is:
DO NOT USE A PACKAGE CONTAINING BOOTLOADERS
IF ODIN FAILS DURING THE WRITING OF A BOOTLOADER THAT WILL BRICK THE DEVICE
STEPS:
Use USB ports connected to MOTHERBOARDno front panel ports, hubs etc...
Use a Known good usb data cable preferably OEM, you may want to have 1 or more spare just in case
right click odin and run as administrator
Have odin ready to go before you touch your phoneAll files in the proper place, now boot to DL mode and connect
If this is still Failing try:
Exiti Odin
Uninstall USB drivers
Reboot PC
Reinstall USB drivers
Switch usb port being used on pc
Rinse and Repeat until either it works or all ports exhausted
If after trying all motherboard ports odin is still cursing at you from Asgard, try one of those spare cables i mentioned earlier.
Sometimes PCs just don't wanna work, if you have the availability of another pc ANYWHERE (even the library or something) try these steps on that machine.
If its still failing on multiple pcs, clean out the usb port on the phone with Q-tip dipped in rubbing alcohol
then blowing it out with compressed air and let dry.
still nothing? you may have a hardware failure in the usb port on the phone.
Standard disclaimer: I AM NOT responsible for anything you've done or will do to your device.... this is merely a reference for you to use to get yourself out of a bind.
thank you, you're welcome, Good luck and happy flashing.
Click to expand...
Click to collapse
I unlike bubba will quote the op nice work friend
Sent from my SAMSUNG-SGH-I717 using xda premium
What does it mean to Odin? I kdd....great work
rquiett said:
I unlike bubba will quote the op nice work friend
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Show off
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Awesomeness bump. Great read.
Sent from The Bacon Pope's Oppo Find 5
Phone stuck
Hi, I'm hoping maybe someone can help me figure out what the problem is.
I'm trying to flash CWM Recovery on GTI9105p. I've actually done this before on the same device, but this time it doesn't work. Odin seems to work fine and shows PASS! after 32 seconds, but my phone stays on "Downloading..." with the blue bar full. If I manually reboot the device and try to go to recovery, it stays on Samsung model logo. Otherwise I can boot the phone just fine. What could be the issue?
First off, I found several cases of no PIT partition, but in every case the phone wasn't working, so my case is different
On my first try to root my I9300 the process hung at getting the PIT info. After a while I unplugged, took off battery and the phone booted fine after reinserting the battery. It took me a while to muster the courage to retry rooting and this time I got the "There is no PIT partition" error message. Phone still works fine.
I used Odin 3.07. Could it be the Odin version? Or certainly something interfering with the USB?
Anyway, my main question is, if it gets past the getting PIT part and starts actually flashing, can I feel at ease flashing using this computer (win 8.1), or should I use my ages old XP laptop? I mean if I think I've fixed the issue (which I think is some software interfering with the USB traffic), is it really fixed, if Odin goes past the part of getting the PIT or can it be only partially fixed and the actual flashing will/can still be fuxored?
pkauko said:
First off, I found several cases of no PIT partition, but in every case the phone wasn't working, so my case is different
On my first try to root my I9300 the process hung at getting the PIT info. After a while I unplugged, took off battery and the phone booted fine after reinserting the battery. It took me a while to muster the courage to retry rooting and this time I got the "There is no PIT partition" error message. Phone still works fine.
I used Odin 3.07. Could it be the Odin version? Or certainly something interfering with the USB?
Anyway, my main question is, if it gets past the getting PIT part and starts actually flashing, can I feel at ease flashing using this computer (win 8.1), or should I use my ages old XP laptop? I mean if I think I've fixed the issue (which I think is some software interfering with the USB traffic), is it really fixed, if Odin goes past the part of getting the PIT or can it be only partially fixed and the actual flashing will/can still be fuxored?
Click to expand...
Click to collapse
Have u tried flashing with other versions of odin?
Tried other usb ports like the ports at the motherboard which is at the back.
Have u tried another wire?
Have u tried other files to root the phone?
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
JellyYogurt said:
Have u tried flashing with other versions of odin?
Tried other usb ports like the ports at the motherboard which is at the back.
Have u tried another wire?
Have u tried other files to root the phone?
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
Click to expand...
Click to collapse
Didn't try other versions yet, any specific suggestions on which version is the most recommended to be used with I9300?
I tried all the USB ports on the front, haven't tried one on the back yet, will give that a try as soon as I have the time.
The wire I'm using is the one that came with the phone, I assumed that's the safest bet. I'll try another wire if the ports directly on the mother board don't work.
Haven't tried any other files for root, because AFAIK the process never gets so far as to even try actually flashing the phone. I'm at work now so I can't verify the root file I have, but I double, triple and quadruple checked and it should be the right one for my phone
Thanks for the pointers, will click thanks if your suggestions turn out as fixes for my problem.
EDIT: in case someone reads this and ponders why is nothing happening; the 4.3 update just came OTA for my phone and after that update I think I'm "forced" to install a custom rom. Reason being that the update had some extra bloatware that's causing certain apps to reload completely after only locking the phone and then unlocking. I didn't have this issue before the update. Now I'm reading up on roms and trying to decide which to go with... When I've made up my mind, I'll get back to this issue and hopefully get it fixed, as there's no other way to install a custom recovery, right?
Hi
this is my first post here, so please go easy on me. I am an electronics engineer by trade but pretty old school stuff, although I am familiar with flashing microprocessor based systems. I'm not a complete fool.
I have a problem recovering a Tab 4 SM-T230. It is stuck on the initial page showing "Samsung Tab 4".
Only way to power down is removing the back and disconnecting the battery.
From there I can enter recovery mode but Master Reset doesn't cure it.
So I have Odin 3 installed and have the correct BL, AP, CP and CSC files ready to upload.
In device manager it is showing the tablet is connected and the drivers are okay.
The problem is, there is nothing showing in the ID:COM tabs in ODIN.
I've re-installed the drivers, unplugged/plugged, still can't get it to connect.
Any Suggestions? Am I going about this completely the wrong way?
I know it would probably make sense to just buy another tablet, but this one fits a modified holder used in a specific application, so replacing the tablet suddenly creates an engineering issue as well!
Many thanks in advance
Kevin
Henson25 said:
Hi
this is my first post here, so please go easy on me. I am an electronics engineer by trade but pretty old school stuff, although I am familiar with flashing microprocessor based systems. I'm not a complete fool.
I have a problem recovering a Tab 4 SM-T230. It is stuck on the initial page showing "Samsung Tab 4".
Only way to power down is removing the back and disconnecting the battery.
From there I can enter recovery mode but Master Reset doesn't cure it.
So I have Odin 3 installed and have the correct BL, AP, CP and CSC files ready to upload.
In device manager it is showing the tablet is connected and the drivers are okay.
The problem is, there is nothing showing in the ID:COM tabs in ODIN.
I've re-installed the drivers, unplugged/plugged, still can't get it to connect.
Any Suggestions? Am I going about this completely the wrong way?
I know it would probably make sense to just buy another tablet, but this one fits a modified holder used in a specific application, so replacing the tablet suddenly creates an engineering issue as well!
Many thanks in advance
Kevin
Click to expand...
Click to collapse
Try a different PC.
What version of Odin are you using? You need to use a version that was released around the same time the tablet was new to the market. Your tablet is from 2014 so you need to use Odin 3.09 or Odin 3.10.
Sent from my SM-S767VL using Tapatalk