Related
What can we do? I dont want to mess with anything again because i know if anything goes wrong i cant get in to download mode.. But i too want to flash the new roms and gps fixes. Is there anyway to make the hardware buttons unlocked?
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
You can root using clockworks and run some of the patch through clockworks too. Try not to use odin unless you really know what you're doing. A lot have odin hang on them. Other than that, you can flash rom using clockworks.
Sent from my SGH-T959 using XDA App
jonathan3579 said:
Why not use adb? I used it and Odin for the first time two days ago flashing this new patch and it was quite simple. I, like you, have a hardware locked handset. Let's hope it didn't take you nearly the same two hours that it took me.
Click to expand...
Click to collapse
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
exactly my point. this is what happened to me. but think about this lets say i flash a rom right and you know how sometimes it hangs on the vibrant screen and just stays there. and in order to get it back i am going have to use odin. which i cant.......... so i think i wont mess with anything anymore. Rather just wait for official 2.2 ota update.
Chief Geek said:
TWO HOURS! Lucky SOB, took me over 4 hours, but I was at work with nothing better to do then to play with it on and off, google some more, crawl xda, play some more....rinse repeat...
But I don't think there will be an official "fix" as in their eyes nothing is broken. It is as they intended. I'm not really sure if this move was by tmo or samsung, but regardless it's a PITA. I used ADB. The hardest part is getting the drivers in, after that it's easy cake walk thanks to the wealth of knowledge here at xda.
Click to expand...
Click to collapse
Take it back and do a warranty exchange cause the buttons arent working correctly.
I've never tried it because I could never get Kies to connect to my phone, but isn't there a way to update firmware through Kies? I know the i9000 guys use Kies to upgrade, but I think that's only to get drivers and the updates though. I wish Samsung had a better interface than Odin to flash firmware. It's absolute garbage.
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
glensta said:
I received 1 of the new hardware-locked phones and used adb to get into "download mode" - but odin got stuck and I had to unplug the phone and tried plugging it back in and it didn't work. Once I took the battery out, I got the dreaded "phone to pc" icon. I tried a whole lotta combinations all read here on XDA - nothing worked. One I got that "phone to pc" icon - i was screwed. Adb doesn't work at that point.
Basically - I wouldn't use Odin with one of the newer vibrants - only update.zip stuff
*Just a suggestion*
Click to expand...
Click to collapse
This is how I got out of "phone to pc"
get into download mode (i went through it manually, as in plug in the phone, and pressing the volume buttons together at the same time)
Connected to ODIN, and by perfect accident, I clicked on "start" without placing ANY files in ANY spots.
This is what I thought "OMG $h!t" Well my phone was already bricked enough, so i just let it run its course through ODIN. My phone magically rebooted, and it booted into the ROM i had installed before I got the "phone to pc" problem.
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
demo23019 said:
Whats the disadvantage of having a hardware locked phone?
From what I'm reading i cant load custom roms? or can use Oden?
Also I just got mine and im sure its hardware locked but how can I tell
TIA
Click to expand...
Click to collapse
The disadvantage is that it is harder (maybe impossible in some situations?) to get into the Download mode if something goes wrong during a ROM update. You can still load custom ROMS but if something goes wrong, you might not be able to get to Download mode to be able to fix it.
I had the phone ! PC screen on mine when I first tried to unsuccessfully flash Vibrant8. Luckily, my Vibrant doesn't seem to be hardware locked and I was able to get back into Download mode and re-flash it with Odin.
I'm able to access download mode with volume keys and i can access recovery mode so i guess im ok
also date on box is 8/27/10
How do you know whether you have a hardware locked Vibrant or not?
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I trust what you're saying.. but is there any way to test that out without having an already bricked phone? I want to make sure I can recover my phone before flashing your Vibrant hybrid ROM. So after Step 6 do you get the download mode screen? Or does ODIN now show a COM port and it works, even without the little digger guy?
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
johnny12times said:
First off, absolutely no disrespect Eugene, you are an amazing developer and a HUGE contribution to this forum, I personally love your work and have tried many of your ROM's (actually looking at switching up to your newest hybrid rom next), but there are most certainly some of these phones that are hardware locked to the point that you can not get in to download mode, regardless of what you do. The steps you posted definitely work for some, and for non-hardware locked phones, they work beautifully, however, there are some phones that no matter what you do, no matter what order you do it in, you will never get in to download mode short of using ADB. The good news is, the lockout was not intentional, and exchanging your hardware locked Vibrant will generally result in a non-hardware locked phone (from mine, and many other's personal experience).
Click to expand...
Click to collapse
Download Mode is controlled by SBL, so if they truly changed anything that would be the cause.
I would think you could target redbend to update the SBL or even boot.bin bml /stl location.. I've not tried this, nor do I need too.. Just tossing options out there for people to try & don't mind risking a brick..
If you can get the SBL / Boot.bin for the Stock to flash via redbend, then this will solve the HW locks.. Now, Regarding my Phone, I can still get into Download Mode however, only by doing the USB trick &/or ADB reboot download.
I can not get into recovery unless I use clockwork Manager or ADB into
By the way, this is not a Hardware Lock issue as the thread states.. Not being able to get into download Mode like described, is a zImage issue & not the SBL / BOOT.bin
just as a FYI.
~Eugene
Hello, I am new to this android stuff but think I may have a problem and no hardware keys may come into play.
I rooted my phone for no other reason than to remove bloatware
I removed what I new was safe and left alot on the phone just because I was not sure what to remove
Phone was working great and had no problems
I decided I wanted to do a factory reset to remove all my apps and user data etc.....
I did do a titanium back up of my apps so I could easily resinstall if I wanted
I did the reset and now as soon as the phone boots I get TWLauncher force close and just about any other app that tries to load just continuose force close loop
I did not remove the original launcher so I am not sure why this is happening but I cant flash since I cant get into download mode and I cant use ADB since my phone wont let me put into debug what to do?????????????
Click to expand...
Click to collapse
Its happening because you ran a full titanium backup including system data. Yeah, dont do that. Reflash, then reinstall user apps with data, and pick and choose the system ones that are obvious (mms, bluetooth settings, wireless settings, etc.) Then reboot for changes to take effect. When in doubt, dont restore.
Good luck. Although you won't need it if you do what I just told you.
Sent from my SGH-T959 using Tapatalk
Just to share...
eugene373 said:
No No No.......
When you can't get into Download MOde....
assuming you just got a Hang in ODIN Flasher...
1. Un-plug usb from Phone ( But still plugged into the Computer )
2. Pull Battery
3. Let the Phone sit for 15 to 30 seconds
4. Plug in USB to Both Phone & PC if not already
5. Hold Both Volume Buttons
6. Put Battery in while still holding Volume Buttons.
My Phone is HW Locked as well, with a v1 board.
every-time I get odin hang, doing the above always results in letting me re-flash.
These Phone's by Design are hard to brick, unless you>
A. Change SBL
B. Use the Wrong .pit file for Partitioning
C. param.lfs does not Brick the Phone, but Does mess with Screen rendering
~Eugene
Click to expand...
Click to collapse
I had the phone!computer bricked Vibrant, and just got my replacement from Asurion (in fact, of the phones in front of me are from Asurion since my original got stolen 2days after it came out ).
On phone1: The original TMO date is 8/12/2010, while the Asurion date is 8/19/2010. Also the ID is GJ/HLP. This one was HW Locked.
On phone2: The original TMO date is 9/2/2010, while the Asurion date is 9/10/2010. Also the ID is SM/HLP. This one doesn't seem to be HW Loocked, I can get into recovery easily, DL Mode ... not so much . Booting with vol+&- gets me into recovery, but booting with just vol- does nothing ...
Any thoughts?
Hello,
Maybe someone can help..
Samsung s4 i337 32Gb will only show the Samsung logo when turned on and after about 2 seconds nothing, screen blank , ( New Screen ) No lights , though it vibrates when its first turned on,
For what ever reason if I keep messing with it( take batter in and out) , it will boot all the way, Even then after a short time it turns off again, and that's only after a few days of messing with it..
Any ideas ?
on s side note I am a retired computer /electronic engineer and have an idea how these work, I repair them on the side for clients and so forth, but am at a lose with this one, Its my personal and would love to be able to get pics and so forth off it,,
Thank you !!
Is the phone running a stock Samsung rom? Have you tried reflashing a stock rom or performing a factory wipe?
audit13 said:
Is the phone running a stock Samsung rom? Have you tried reflashing a stock rom or performing a factory wipe?
Click to expand...
Click to collapse
yes it's stock and No have not re flashed the rom , wont stay on long enough for a rom flash or a system wipe..
Maybe a battery problem? This happens regardless of whether the phone is or is not connected to a power source?
audit13 said:
Maybe a battery problem? This happens regardless of whether the phone is or is not connected to a power source?
Click to expand...
Click to collapse
Thank you , Yes I have tried a few different battery's with and with out the charger and Nothing changes
It won't stay in download mode either? Was the phone ever dropped? Exposed to moisture? Is it an att phone?
x_MarkV_x said:
Hello,
Maybe someone can help..
Samsung s4 i337 32Gb will only show the Samsung logo when turned on and after about 2 seconds nothing, screen blank , ( New Screen ) No lights , though it vibrates when its first turned on,
For what ever reason if I keep messing with it( take batter in and out) , it will boot all the way, Even then after a short time it turns off again, and that's only after a few days of messing with it..
Any ideas ?
on s side note I am a retired computer /electronic engineer and have an idea how these work, I repair them on the side for clients and so forth, but am at a lose with this one, Its my personal and would love to be able to get pics and so forth off it,,
Thank you !!
Click to expand...
Click to collapse
The same thing happened to my i337 after I installed one app (soft keys) and reboot. Samsung logo showed up for a second and then went dark.
Went to recovery and wipe /factory reset twice did not work.
Finally, went to download mode and odin the NB1 firmware. That solved the problem.
I was on OK2 bootloader then. I do not know what bootloader you are on.
I
audit13 said:
It won't stay in download mode either? Was the phone ever dropped? Exposed to moisture? Is it an att phone?
Click to expand...
Click to collapse
Yes it was dropped, But only form about 2 feet , landed on a shoe and it has a cover, but after that is when I started having issues come to think of it ..
sway8966 said:
The same thing happened to my i337 after I installed one app (soft keys) and reboot. Samsung logo showed up for a second and then went dark.
Went to recovery and wipe /factory reset twice did not work.
Finally, went to download mode and odin the NB1 firmware. That solved the problem.
I was on OK2 bootloader then. I do not know what bootloader you are on.
I
Click to expand...
Click to collapse
problem is , it wont stay on long enough in down loader mode, Plus I do have things I would like to save if I can.,
I just may have to try and find another 32Gb main board or a broken screen phone type thing and start over..
If it wont stay on, I'm not how the data could be pulled from the phone. If USB debugging was enabled, adb commands may be useful in recovery mode.
audit13 said:
If it wont stay on, I'm not how the data could be pulled from the phone. If USB debugging was enabled, adb commands may be useful in recovery mode.
Click to expand...
Click to collapse
I may end up losing the data, So be it..
Would have been nice to figure out what is going on with this one though..
If anyone knows where I can get a i337 32Gb main board, I maybe interested in it..
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.
I have the S7 Edge originally the ATT version but I rooted and flashed the unlocked version firmware. I was trying to unroot the device and restore everything to the factory settings since I am using the trade in program through Samsung and have to send it back in stock. I tried to flash it using Zodin, the Mac version of Odin, but was unable to get it to work because I was not able to get the proper pit file, it always returned with the error that there is a corrupt file. Since I do not have Windows, I could not Flash the firmware using Odin. Out of desperation, I looked online and a website (the article was on Android forums with the title restore stock with flashfire no PC) said that I could use the Android app Flashfire to flash a firmware and return to the factory unrooted settings. I downloaded and inputted the full firmware file for the original AT&T firmware version and checked the boxes to wipe boot, system, internal data, and trusted Zone and also maintain everroot. It seemed to work and was processing with the fast scrolling command text on the black screen but after a few minutes it said there was an error at the very bottom of the screen. Eventually, it restarted but nothing has come up and the screen is black without any light from the LED indicator. I tried to restart it with the power button several times, holding down the power button and the volume down, holding down the home button and the power button, and holding down the power button, volume down, and home button. I left the phone unplugged overnight and plugged it in this morning to see if it would turn on but nothing happens. Any help would be greatly appreciated and I am hoping that I did not brick the phone.
Since Im not sure now if you also tryed to go in download mode again but ussualy you are always able to do that.
If not try to remove battery and put it back in after 10 minuts. And connect it to your laptop and let it charge for a few minuts. Next Hold buttons for dowload mode. Hold em for 5 secconds. Even if still have a blackscreen open samsung kies or switch. One of them has the emergency recovery option. It will detect it then and will say something like you need to repair the software want to continue etc. Lwt it do its thing and make sure you are on the internet. You drink some coffee and give it 30 minuts atleast.
Still not work? Try to put in a spare battery or charge it with another phone. If that not even works. I cant help you.
First of all, I do not have a battery that I can remove. I tried to enter download mode and recovery mode but nothing worked. It will not boot up into any mode.
Just hold the button combination for download mode for 10sec and connect it to a PC with installed smart switch on it. Smart switch should detect your phone, even if the display of the phone stays black.
I tried what you recommended but nothing works still.
I seem to have encountered the same problem, albeit not through exactly the same method. Essentially I managed a full stock firmware flash through ODIN, all the right messages came up and I got a pass from Odin. The phone rebooted and brought up the blue "updating" screen, which very quickly changed to a "removing" screen, at which point the phone froze. When I tried to reboot, the screen went black and now.... nothing. No recovery, no download, no light to indicate that its charging... nothing. My computer doesn't register there is even a device attached.
I've done heaps of flashing and never seen anything like this!
Would greatly appreciate any advice or assistance!
same issue here accept i was just using odin like usual. anyone figure this out yet? the phone was not rooted or anything. i had flashed the g935u firmware and then decided to put it back to stock g935t firmware. then it started doing this.
reflash but this time it check nand erase all
NEVVER EVER CHECK NAND ERASE ALL, dont advise others what you don't know yourself. This is for manufacturer and is not intended for repairing, if you nand erase your phone its just a paper weight then, beyond recoverable. But this issue is caused by wrong partitioning i suppose, but still it must go in download mode, try plugging it in when smartswitch is open in pc while holding home+vol down+power , if it wont detect then i suppose its nand failure due to any reason. And motherboard replacement is required.
Sent from my S7 Edge using XDA Labs
I recommended it because I had the same experience of the black screen and blue led that lights up and I flashed more than 50 times without any result and the solution that was given to me and which walked it's this one
stootie said:
I recommended it because I had the same experience of the black screen and blue led that lights up and I flashed more than 50 times without any result and the solution that was given to me and which walked it's this one
Click to expand...
Click to collapse
If it really did nand erased all, your phone wouldn't even boot, your phone working is a proof it isn't nand erased. What people don't understand is that nand isn't the internal memory, its the non volatile memory holding vital info about functioning of phone just like a bios of computer, so if it is erased you are beyond recoverable damage. Here , i must say i dont know if odin can really nand erase all, because if your phone is working, nand is definitely not erased. And as far as what fixed your issues, there must have been some other reason. But for everyone, leave that option empty just to be safe.
Sent from my S7 Edge using XDA Labs
I was trying to install 935U firmware in my 935V US verizon s7 edge. After installation completed using odin phone rebooted and showed new sim setting something.... after that it went off and now its turning up.
Any help please?
did you find any solution?...plzzz help me i also got the same problem
HEY BRO...FIRST OF ALL , WHOEVER SAID THAT NAND ERASE OPTION AFFECTS PHONE... IM HERE FOR ANSWER. IHAVE FLASHED AND EVERYTIME used nanderase ...my phone feels brand new ..it jst repartitions the size of nand... also adding pit doesnt effect ...your problem is something other ... plug your phone to a good charger whole night.make sure charger is working...then try volume down and home and power into download mode..gudluck
zaighumjawad said:
HEY BRO...FIRST OF ALL , WHOEVER SAID THAT NAND ERASE OPTION AFFECTS PHONE... IM HERE FOR ANSWER. IHAVE FLASHED AND EVERYTIME used nanderase ...my phone feels brand new ..it jst repartitions the size of nand... also adding pit doesnt effect ...your problem is something other ... plug your phone to a good charger whole night.make sure charger is working...then try volume down and home and power into download mode..gudluck
Click to expand...
Click to collapse
Ofcourse it doesn't effect S7 edge, because it DOESNOT wipes the nand.. so its not working simply..
On older phones it will wipe nand totally and thats a dead brick..
First search what nand is.. its the non volatile memory.. or simply nand chip .. if you delete it.. your phone won't be a phone anymore.. its the non volatile memory that is equal to a bios of a computer.. delete non volatile memory and your phone is completely dead..
Thanks to the latest phones that don't erase non volatile memory and instead selecting nand erase with s7 edge simply deletes userdata before flashing.. which is equal to a normal hard reset ..
Sent from my S7 Edge using XDA Labs
Hi, so, I got this phone from a friend, and he told me that the phone was working prorperly, but after someone factory resetted it, he wasn't able to set it up. Constant force close pop-ups where showing up while setting it up, and you weren't able to accept terms and conditions (button grayed out). Also, one thing I noticed. The phone got into "Factory Mode". Idk what that is, but it wouldn't let me to enable wifi or bluetooth. That little Factory mode thingy got me really confused. Also, I wanted to boot into recovery mode, and I wasn't able to do so. After turning the phone off, and doing the key combo to boot into recovery, the phone rebooted itself (very showrtly after doing the startup vibration) and after that, it seemd to get into recovery, but it stayed at the android logo with an exclamation sign and after 3 seconds it rebooted itself to system.
After that I said, "well, last thing to try is flashing stock rom again". And I did so. Using the Frija software to download the latest version of android for this phone (and using the corect CSC for this phone (CTI)). I used odin 3.12.7 (wich I knew it works because of previously using it with other phones) to flash the stock rom again. I made sure that only Auto-reboot and F.reset time were checked, and started flashing. After it finished, it got to the samsung logo, but got stuck there. Nothing happened (I left the phone there for like 30 min). I decided to hard-reboot the phone and try to factory-reset it, but after shutting it down, it started to be really hard to make the phone turn on. I had to unplug the battery and wait like 10 mins to try again, and I still wasnt able to boot into recovery mode. It just got stuck at the "Galaxy Core 2" logo.
After that first boot, the phone never got passed the "Galaxy Core 2" logo. Just stuck there. After that, things just begun to get worse. It was also hard to get the phone to get into download mode, most of the time it just stayed at a blackscreen (im not shure if the phone ever turned on, but it never vibrated) and did nothing. I decided to try other versions of odin. Tried with 3.09 and 3.04. Nothing, and after every flash, it got harder and harder to make the phone boot.
At this point, I can hardly get the phone into download mode, and if I do so, sometimes I get the odin complete write operation failed error, wich the only way that I've found to solve it is to reboot again the phone into download mode.
I know that the battery is working, I have another core 2 (same exact model) and battery is ok. At this moment I don't know what else to do. Please, help me to get this brick of a phone back to working conditions, I dont want my friend to buy a new phone just to use it to recive calls and charge it.
Some extra notes:
As i've read, sometimes this can be caused by the replacement of the digitizer/screen. This phone seems to have one or both of them replaced, since I can see glue residues on the corners of the glass, where it touches with the plastic frame.
If there is anything hardware related thing to try, I can try to open the phone. I have some experience doing so.
EDIT: As I continued reading through this forum, I found out that some people had luck with Odin3_v3.13.1_3B_PatcheD, so I decided to try it out and see. Still, nothing changed. As today, I can only use this phone to charge the battery (it dosent actually show the percentage, only the battery icon with a loading icon inside) and boot into download mode
Although, I have to say that after flashing the stock rom with that version of odin made the phone not that hard to start in download mode. I think that it could be something that got corrupted on the eMMC module and it has to repartition it all again...? Does anyone know how to do so?
Regards
Well, tried almost everithing I know. Downloaded rom again with binary nature, tried with odin version 3.12.7, 3.13.1_3b patched and 3.13.3, but nothing. Extracted the PIT file from the CSC file, did repartition, NAND wipe, and nothing changed. I have to say that its certaily easier to get the phone in download mode, but thats almost it. One thing to note, when i select the NAND wipe, it dosent seems to do anything. I mean, in odin Log screen some things appear related to NAND wiping and such, but its really fast and there are only 2 or 3 lines dedicated to that. Is that OK?
Anyway, please, any recoomendation or thing to try would be great, since this phone is now trash, it dosent matters if it starts to get worse, or even unusable (more than it is rn).
Regards