Hello , looking for help to unbrick a partially bricked phone that allows me to turn on and use mostly everything , it seems to reboot itself every once in awhile. I can goto Kies and and try to repair but that doesn't work , also have odin with factory file and that shows Fail every time i try that. Hoping someone can help try to get back to factory settings.
Oh and i have read for 2 days here downloaded files and tried everything i can , but nothing seems to work. And when i restart phone it seems to go back to exactly where i left when it got bad root file or something. In the phone part even after i erase calls , it shows the people that called that day every time it gets restarted.
If anyone can help and walk me through , i'd be greatly appreciated. And i've watched i don't know how many youtube vid's on trying to get this back to factory mode.
Thank you.
just go into download mode and flash stock rom through odin.....
mohit378 said:
just go into download mode and flash stock rom through odin.....
Click to expand...
Click to collapse
I've tried mutiple times and always comes up FAILED.
Tried Kies option also....
Apparantly its stuck in Titanium backup mode and occasionally does a reboot on its own sometimes. But even if i try to reboot after erasing tons of stuff out of it.... it comes back to what it was or how it was. So basically the titanium even though it shows up nowhere in my apps or phone... it keeps reverting my phone back to where it was when it got messed up.....
Try this
redskies4you said:
Hello , looking for help to unbrick a partially bricked phone that allows me to turn on and use mostly everything , it seems to reboot itself every once in awhile. I can goto Kies and and try to repair but that doesn't work , also have odin with factory file and that shows Fail every time i try that. Hoping someone can help try to get back to factory settings.
Oh and i have read for 2 days here downloaded files and tried everything i can , but nothing seems to work. And when i restart phone it seems to go back to exactly where i left when it got bad root file or something. In the phone part even after i erase calls , it shows the people that called that day every time it gets restarted.
If anyone can help and walk me through , i'd be greatly appreciated. And i've watched i don't know how many youtube vid's on trying to get this back to factory mode.
Thank you.
Click to expand...
Click to collapse
I don't know if the fail you get in Odin may be caused by having the wrong settings. I have ran into a few tutorials online that use odin, each one had a specific way. Try running it again with all the options unchecked except for the Auto Reboot. Also make sure you place the correct file(s) in the correct slot. example: any bootloader file goes into the bootloader slot, etc. make sure its checked. Then run again, this may be the only reason your getting a fail, it may have nothing to do with Odin or your phone.
Of course disregard this message if you had already fixed you problem. Also another possible fix would be to use ADB command to push the files to your phone, I suggest looking into it, there is a good amount of info on it online. It could help down the line with future issues to know ADB. Here is a website I found helpful, it is a guide to using ADB sideload to save bricked devices. ------- (android-revolution-
hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html) note: just copy everything after the dashes and in between the parenthesis and paste into url bar on browser. sorry i have to be difficult, first time posting on this site and they wont let me post in a link, but this guide may be the answer to all your phone trouble. Plus I know how you feel, I just bricked my phone too and I know how agravating it is when nothing works.
Good luck and let me know how it goes
Thanks
BAMTek.Inc said:
I don't know if the fail you get in Odin may be caused by having the wrong settings. I have ran into a few tutorials online that use odin, each one had a specific way. Try running it again with all the options unchecked except for the Auto Reboot. Also make sure you place the correct file(s) in the correct slot. example: any bootloader file goes into the bootloader slot, etc. make sure its checked. Then run again, this may be the only reason your getting a fail, it may have nothing to do with Odin or your phone.
Of course disregard this message if you had already fixed you problem. Also another possible fix would be to use ADB command to push the files to your phone, I suggest looking into it, there is a good amount of info on it online. It could help down the line with future issues to know ADB. Here is a website I found helpful, it is a guide to using ADB sideload to save bricked devices. ------- (android-revolution-
hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html) note: just copy everything after the dashes and in between the parenthesis and paste into url bar on browser. sorry i have to be difficult, first time posting on this site and they wont let me post in a link, but this guide may be the answer to all your phone trouble. Plus I know how you feel, I just bricked my phone too and I know how agravating it is when nothing works.
Good luck and let me know how it goes
Click to expand...
Click to collapse
Thanks Bam.... I'm just in need of all stock files Including the PIT file which is like impossible to find it seems to try and get this phone back to factory reset mode..... The phone actually works but anytime it reboots or save anything...ect.... it just reverts back to when it got tripped up. Thanks again for anyone's help.
Related
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Did you try clicking flash in Heimdall, sometimes it looks like it doesn't see the phone, but you click flash and it works. Also, have you tried clearing user data and cache? (I know you said you had factory reset at one point but now that you are stuck might be worth a try.) Looks like a boot loader issue, not sure why Heimdall doesn't see the phone, I've had good luck in the past with it.
I'm tempted to tell you to format the internal sd and try heimdall again, but maybe someone with more experience would have a better idea.
khkaiser13 said:
I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Click to expand...
Click to collapse
Before you go any further,
Read my how to..click on the first link on my sigs.
Read through several times.
There is a BIG difference b/t download mode and recovery.
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
khkaiser13 said:
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
Click to expand...
Click to collapse
Put your phone in download mode. Odin or heimdall back to stock and start over.
Don't worry about anything else as long as you can get into dl mode
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
khkaiser13 said:
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
Click to expand...
Click to collapse
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
qkster said:
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
Click to expand...
Click to collapse
Just to add this to what qkster said! I know you said you know the difference but be sure to have proper drivers installed I personally used GTG’s Ultimate Unbrick with 100% success. If there is any doubt about bad drivers I would also suggest reinstalling them there is a very easy to use Utility called usbdeview that lets you uninstall drivers and start fresh.
I've spent weeks surfing the forums trying to get past the common recovery file rename and replacement with a system manager that is in super user mode etc. I don't know if it's the particular version of the recovery file that I've replaced being bad, but the first time I was soft bricked I was able to physically reset with a guitar wire in that whole ( was weird cuz it seemed like the button wasn't going to work cuz after minutes of turning the phone on and off it just randomly worked) Let me explain better because after chosing a different recovery file it soft bricked again however the reset isnt working. Ok so if I have USB cable in it brings up charging battery logo (showing the battery as dead which isnt true because the time it did reset... when it worked, the icon illuminated green suddenly. If the USB isnt connected upon turn on the samsung comes on indefinitely (forever)... tried with sim in & out etc. If I reset into download mode it just says downloading (let it go for three hours before stopping it once). Ive installed odin and tried to fix it that way... I made a Jig with 3X100k resistors and 1 1ohm 1watt ..( attempting to get the 301k resistance between the 4th and 5th pin in the micro usb connection... Didn't work ( used a voltmeter to test the jig but I didn't know what the reading should be but I saw a difference ( thougt the 1 watt addition was messing it up so I omitted that resistor. Still didnt work.... guess I could splurge and buy a jig online as a back up if I cant beat it differently. Lastly and more promising was downloading ADB and getting it running correctly... at first because of the inability to adjust bugging or not the device wasnt recognized... miraculously I left it alone andcame back and tried it... device is recognized... tried to adb pull recovery.orig file to C: to rename and push back but I didn't see it on the PC to rename after Adb says the pull file command was done. Thanks for your patience with all this info on first message. Im new to this. Im sad that I have to get into this just to take control bake but there is a user and or group that is runing in my background and changing my permissions and running so many processes its like slow motion. doing this so I can run the roms to control my traffic and get some Ram back... I wish I could just ask him to please stop. Thank you for any help.
If I reset into download mode it just says downloading (let it go for three hours before stopping it once)
Click to expand...
Click to collapse
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.
Odin
ApexPredatorBoids said:
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.
Click to expand...
Click to collapse
Odin wasn't recognizing the device before at all, but since I set up ADB and ran the adb sync comand, now when I run Odin it recognizes the device as com5 not com++ (not sure if that matters). I'll try and start a pit and see what happens.
If I went back to stock what kernel do you recomend I flash and do you know a good recovery file to replace the original one to get past the signature verification when reinstalling packets.
Flash entropy's dd kernel. There is no need to replace any recovery file in GB (that's only on froyo).
Sent from my sweet & buttery Infuse
Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
GrabAndSmash said:
Been having problems a while now, they've been progressively getting worse. Seemed to happen after an update.
Basically the phone freezes and reboots. Can be anything, unlocking, playing games, opening internet browser, opening gmail. Just frustrating, the phone just freezes, then reboots and loads up. Progressively getting worse and just gets hotter and hotter which seems to throw it off more. With the exception of a Software problem from the update (Damaged O/S and/or Bootloader), I'm starting to think the phone may be damaged. I've dropped it a fair share of times, but it's in a case :cyclops: so shouldn't be too bad
What I've done so far
- Cleared cache via Recovery Mode, this temporarily fixes it, the phone boots up again normally, but randomly freezes and reboots again
- Booted phone in safe mode - same problems
- Factory Restore --> Phone restores, but even when installing the apps again in goes through 3/4 reboots
I've enabled Dev Options and USB Debugging (and also OEM Unlock). If I try flashing with ODIN I just get a SW Check Revision failed message.
When the phone gets stuck in it's boot, it just displays the initial "Samsung Galaxy S7 Android" screen and nothing else, the occasional Samsung loading screen, but that sometimes freezes too. The times when I can get into the recovery mode, I've looked at the last log files, and there's sometimes errors relating to /mnt and a couple of directories, but I don't know enough about the O/S to troubleshoot and sometimes it fails to get into Manual Mode, I'll see if I can get photos of the last log file. The reboot reason is UNKNOWN
I've installed ADB, when the phone is loaded up into Windows, and I use adb devices it shows up. When I go into download mode, it says "List of attached devices" and then shows nothing. So I'm assuming it's a different issue, otherwise it wouldn't work in windows either
Bit stumped now. The phone isn't rooted, I'm not bothered about losing data, since I backed it up the first time I factory restored, so there's nothing valuable on there. I'm just getting tired of factory restoring it, since I don't think that's the problem. I'm thinking either the Factory Restore image is damaged or the phone is.
Any suggestions would be appreciated.
Phone is UK Based on Giff Gaff network. These are the files I'm trying to use to flash it
The option isn't ticked in ODIN (3.14.4) to Wipe Partition either
AP_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship_meta.tar
BL_G930FXXS4ESAE_CL14843133_QB21796491_REV00_user_low_ship.tar
CP_G930FXXU4ESAE_CL987828_QB11799217_SIGNED.tar
HOME_CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
I read somewhere if I use this file it wipes the data. So haven't tried this
CSC_OXA_G930FOXA4ERKF_CL14843133_QB21796491_REV00_user_low_ship.tar
Click to expand...
Click to collapse
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
cooltt said:
Hello the SW Check error means the firmware your trying to flash is older than the firmware already on device. You can only flash the same or up, never down.
The firmware you've posted is quite old. The unbranded original for United Kingdom you need is BTU. I linked it off Sammobile but if you know how to use Sam Firm tool you can get it much faster direct from Samsung.
If problems persist after flashing this, then yes it's a hardware problem.
https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXS8ETC1/327922
Click to expand...
Click to collapse
Thanks,
I've got the SamFirm download tool because I was irritated waiting for the download, I'll try downloading and flashing it.
Should I flash the lot, or just one specific thing?
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
GrabAndSmash said:
Also, I used Sam Firm to download the firmware for the phone but using the Auto Method.
What is the "Version" I need to enter based on SamFirm, is it listed somewhere, or is it the phone itself? G930FXX8ETC1 ?
Click to expand...
Click to collapse
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Sorry yes, flash all files, you'll have a clean new phone.
First boot can take about 5-10 mins, and the updating, erasing screens are normal.
cooltt said:
You don't need to specify a version just put in SM-G930F, then BTU in region. It will automatically find the correct firmware for download.
Download, let it do its checks. A zip file with 5 files inside, 2xCSC, only one goes in Odin. CSC_home will keep files and settings on device but can often cause problems. I alsway use just CSC for a clean install. Obviously put the other files where they need to go too.
Click to expand...
Click to collapse
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
GrabAndSmash said:
Thank you, I managed to figure it out, I'm sure it's what I did last time, not sure if it just picked up the wrong version somewhere. IT seems to match the info in your post anyway.
I don't give a toss about the data since I'm over writing it all anyway. Do I still ignore the option to wipe the partition in ODIN, or should that be included to?
Click to expand...
Click to collapse
Leave the default options already ticked in Odin. You don't need to change anything there.
cooltt said:
Leave the default options already ticked in Odin. You don't need to change anything there.
Click to expand...
Click to collapse
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Only other possible thing I can think of is the battery. There were alarms in the log file and the phone does reboot more when it gets hot. Given the phone is 4 years old now, I wonder if the battery is damaged and the phone is having a hissy fit
GrabAndSmash said:
Thanks,
Just finished flashing the image now, so going about the restore process to see if it's fixed it or not.
(still think it's buggered though, my phone froze/rebooted even when doing android config)
If needed I'll just keep using it in a semi-working state until I buy a new one and put up with it
EDIT - Just froze / rebooted configuring the main O/S after connecting to google account. New phone time by looks of it
Click to expand...
Click to collapse
Yeah look like battery overheating making it reboot
cooltt said:
Yeah look like battery overheating making it reboot
Click to expand...
Click to collapse
I'll give it a try for now, I've got the correct files for flashing it at least this time thanks, I''ll try replacing the battery in the future, and if I find out it fixes the problems I'll update the post. Or if I figure out what's causing it