i717 will not boot Samsung logo stays on screen. - AT&T Samsung Galaxy Note I717

After years of great service my i717 will not boot. It shows Samsung, then this changes to a slightly fuzzy version of Samsung and just hangs there.
I am totally new to doing any modifications to phones.
I tried pressing vol up/dn then power and and it showed a screen about downloading a custom something but it didn't look like anything downloaded and this didn't help.
I then tried the genius method of just trying stuff!
I downloaded Odin 1.85.rar and cwm-i717-120305.tar.md5 and installed this as the pda option.
The phone still hangs at Samsung
But now when I hold vol up / dn and power I get a CWM-based Recovery v5.5.0.4 menu.
I put a sdcard in and chose the menu options to format the sd card, mount it and then do a back up to the sdcard.
It listed a lot of files and then rebooted.
When I mount the sd card in a PC it is blank.
I would like to recover my contacts from this phone if possible and I would like to get the phone working mostly so I can read NFC chips for some NFC development I am doing.
Please someone tell me what to do to get the phone to boot and a link to getting started information for someone totally new to phone modding.
Thanks.

What no one wants to help a total noob?
Was I too honest?
Would it have helped if I said I spent two whole days researching this?
About half of the problems with boot loop on i717 seemed to be caused by a stuck power button which obviously was not my problem.
ALL of the other suggestions I found were no help either.
So totally new to this I figured out I should download odgin, and this specific cwm file cwm-i717-120305.tar.md5 and install it with specific options.
I then tried to wipe the cache,
And wipe the dalvik cache,
both didn’t help.
I then tried to do a full back up to sd card.
It ACTED like it did the back up but the sd card when mounted on a PC was blank.
I then did a factory reset and now I have my good old ATT i717 note v1 working again!!
I would have liked to get my contacts but had no help.
This is all I really needed because now I have NXP Taginfo running reading nfc tags which my new J7 doesn’t do even though it says it has NFC support.
I would REALLY like to know why
1) CWM back up looks like it works but ends up with a blank SD card.
2) Boot HANG on second “fuzzy” "Samsung" screen, why is this and how to get a back up of contacts when CWM doesn’t back up.
3) ATT store “help” should have done a simple factory reset on the phone to avoid me having to buy a new phone. But they of course acted like I needed a new phone. This alone makes me want to switch.

Related

Viewsonic G Tablet lock up @ g-tablet screen

I have gotten a g tab from my father in law after he tried to fix it and ended up buying a new one saying "if u can fix it you can have it" I have tried for hours and days to fix it on my own and have now tried to reach out for help
Basic problem:
-When I got the device it would boot to birds and go to g-tablet screen and no further
-Found viewsonic gtablet for dummies tried nearly everything (i believe correctly)
-Called G Tablet Support and got the "send it in to us and we can add the correct software for $60 if there is no problems otherwise the $$ may go up"
-went back to trying to fix on my own
-failed
Basic info:
-able to NVFlash with 0 errors on any packet
-can boot to g-tablet screen but no further
-can boot power & Vol+/vol- no issue
-cannot partition
-cannot wipe data/ factory reset
-can install zip from SD
Help! any ideas are worth a shot when it means (possibly) a free tablet. Eager to fix and try most ideas to get this thing fixed!
Also, This seemed to me a repost but i have looked at, tried, and failed to fix with several different posts/ideas from this site
I've seen a number of posts suggesting that you power off, open the back, pull the battery, wait a few minutes, plug the battery back in and turn it back on. It seemed to work for a number of people.
There is also a reset switch under the back cover.
I honestly don't know if one of these will work, but it's worth a try.
Can't suggest which rom you might try, since there's no way to tell which bootloader you have (v1.1 or 1.2).
I'll have to try pulling the battery plug tomorrow I don't have small enough tools. But I do know that im running 1.2 got that much outta tech support before they went grabbing for mytwallet lol
Here's a thread that explains how to open the GTab. http://forum.xda-developers.com/showthread.php?t=994881
If you are on 1.2 (and are absolutely sure) you might want to start with http://forum.xda-developers.com/showthread.php?t=1525424 to get the latest recovery ClockWork. Do this after you "pull the plug".
If it doesn't work after that, come back and let me know and I'll try to do some more troubleshooting with you. Since you said you actually had NVFlash working before, this might actually get you up and running on the latest stock rom. From there, you can move up to just about anything you want, upto and including Ice Cream Sandwich (ICS). Just remember to check the forum information about what does not work. For example, if you move up to Gingerbread (3.x) or greater, there is a pretty good chance that you won't have camera or mic support at this time. Some roms don't support hardware acceleration at this point, but many do.
Anyway, come back and let me know how it went.
Awesome thanks. I'll be getting into that soon (after I finish cleaning) just wanted to thank you for your interest in helping me
Hey! finally got around to it but pulled the plug and grabbed that cwm recovery u had linked but i'm still hangin on the g-tablet screen. any other ideas?
I'm guessing that the tech support for GTab was wrong and you actually have a 1.1 boot loader.
Try following the thread here http://forum.xda-developers.com/showthread.php?t=974422 on formatting the gtablet and starting over from scratch.
Gregwa
what 1.1 should i use?
Cmdrbubbles said:
what 1.1 should i use?
Click to expand...
Click to collapse
There is no reason to go out of the way to figure out what Bootloader you have. the NVflash files that you found on the ViewSonic Gtablet for Dummies guide will be your best bet. If you can get grab the NVflash files that include CWM recovery those are the ones you need. After NVflash is complete and you see the Gtablet splash screen press and hold the power button till the tablet shuts down. Once shut down you need to reboot into recovery by pressing down the volume + and press the power button to boot up. That should get you into CWM where you need to do a wipe data fatory reset, wipe cache and also wipe dalvic cache under the advance menu. Once that is complete then you need to back out to the main menu in CWM and reboot. Make sure that you do not select Reboot Recovery. Give the device some time and it should boot into the Stock TapUI where you can mess around with it from there.
I would choose 1.2 build 4349 w/CWM preinstalled (Old) NVflash file found here http://viewsonic-gtablet-for-dummie...65610&fw_sig_premium=0&fb_sig_network=fw#2310
Many times in the past the wipe data/ factory reset and wipe dalvik and most anybody those options lock up the tablet. It will just hang on the screen (depending on the option chosen) and not move from there for hours on end... Thoughts on why? Hoping not a hard drive problem
Cmdrbubbles said:
Basic info:
-cannot partition
-cannot wipe data/ factory reset
-can install zip from SD
Help! any ideas are worth a shot when it means (possibly) a free tablet. Eager to fix and try most ideas to get this thing fixed!
Also, This seemed to me a repost but i have looked at, tried, and failed to fix with several different posts/ideas from this site
Click to expand...
Click to collapse
You will need to get your partitioning working. You can boot into recovery? And what happens when you attempt to partition.
If you are able to go past the 3 birds splash screen and see the gtablet screen, then you're on the stock ROM and the problem is most likely with the partitions on the internal SD card (or the card itself). In which case, nvflash will not help you.
Set up ADB and then run these 2 commands and post the output after you've tried one of those operations you mentioned in your 1st post:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
C:\SOME|PATH> [B]adb pull /tmp/recovery.log[/B]

NEXT7P12-8G Not Booting Help Please

I'm new to the andriod side of things but am very computer savy. Can someone please help? My son has this nextbook tablet and today when he turned it on, it hangs up on the second boot image. I went into recovery but didn't want to restore to factory just yet if i didn't have too. I've read so much i am confused. We have four boys, so that means we have four of these tablet, since Christmass. This is the only one not booting for whateer reason now. What can I do? Can i pull image from one of the others and install n this one, or just certan boot files? Please help and thank you for any reply.
Grwx4dad said:
I'm new to the andriod side of things but am very computer savy. Can someone please help? My son has this nextbook tablet and today when he turned it on, it hangs up on the second boot image. I went into recovery but didn't want to restore to factory just yet if i didn't have too. I've read so much i am confused. We have four boys, so that means we have four of these tablet, since Christmass. This is the only one not booting for whateer reason now. What can I do? Can i pull image from one of the others and install n this one, or just certan boot files? Please help and thank you for any reply.
Click to expand...
Click to collapse
I had the same problem with my next 7 premium se 8gig.
Pop your sd card in.
Boot into recovery mode by pressing the power button and the volume down button at the same time.
When recovery comes up, delete the media partition, clear your cache and restore to factory settings.
Choose the option to restart the tablet.
Once it boots it should be back to life though you will lose everything on it.
Beats having a useless tablet though.
It took me only a few hours to reload all my apps and she's been running fine since.
Good Luck.
I got it to go to recover but once at recovery it says upgrading please wait and sits their.
Exact same issue...
Any luck in resolving this yet? I have google for 16 hrs so far, and tried countless methods of restoring my tablet to it's previous glory...
Any help is much appreciated. :fingers-crossed:
sd card
you mention an sd card,where do i get such an sd card?
scarsfromknives said:
I had the same problem with my next 7 premium se 8gig.
Pop your sd card in.
Boot into recovery mode by pressing the power button and the volume down button at the same time.
When recovery comes up, delete the media partition, clear your cache and restore to factory settings.
Choose the option to restart the tablet.
Once it boots it should be back to life though you will lose everything on it.
Beats having a useless tablet though.
It took me only a few hours to reload all my apps and she's been running fine since.
Good Luck.
Click to expand...
Click to collapse

Again with bootloop problems, this time with CWM

Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD

Galaxy S 3 turns on until Galaxy Logo

Hello people,
I am wokring on an international verson of Galaxy S3 GT-I9300 of a friend of mine.
His devise freezed at the Galaxy S 3 logo at the beginning and couldn't go any forward.
He took it to a guy that repairs phones and he told him that it's a hardware problame and needs 150 euro to fix it.
So i asked him if he wants me to give a try and see if it's not a hardware problem.
Anyway i will give you as many details as possible to tell me what you think.
As i said before its GT-I9300, no root, unbranded, but i am not sure about the firmware. Most probably it's at 4.3. No SD card.
The phone starts only until the Galaxy S 3 logo and freezes there.
When i press the power button the phone shuts off but then immediately reboots by itself but again freezes at the Galaxy logo.
I do have access to both recovery and download mode so i believed that i could do something but unfortunately so far nothing.
I have tried to do factory reset but during the process it reboots. I wiped succesfully the dalvic cache and the battery stats but i cannot do factory reset.
I also tried through Kies to do emergency recovery but again during the process it tells me that there is an error with the phone and couldn't go forward.
Then i tried with Odin to root the phone. I have found the correct PDA file (i think) and again started the process but i got FAIL.
Then i tried with custom roms. I have put 2-3 custom roms that i had on my pc. I trasfered them on an external SD card and tried to install them through Recovery mode. The process starts ok and allows me select the options of the installation but at the point where it tries to wipe the data it stops and automatically reboots.
I have tried to install the custom rom without full wipe but again it stops and reboots.
I browsed in a lot of sites but i haven't found anything else so far that could save this phone.
So i open to any suggestions you may have.
Is it really hardware issue?
It's strange though because the phone starts up to a point and i have access on both recovery and download mode.
Thank you very much in advance.
it seems hardware problem....

[Solved] Factory Reset, now boots to language select and then black screen

I have the GT-S7560M through Solo (Bell) and I rooted it shortly after purchase last year. I've been happy with the phone and for the last few weeks an upgrade notice has been appearing but would fail when applied. Some searching suggested the root was interfering. At first I started to look into un-rooting the phone, but then thought that a factory reset would be the simplest, least-risky solution. I had done a factory reset on my last Galaxy phone without a problem so it seemed like a safe choice. I backed up the contact info, etc with Kies (I don't use many apps so I didn't go all out ie Titanium Backup) and removed my SD card.
Now the phone boots to screen asking me to pick a language and press Start. Then it moves on to a black screen with the info bar at the top (clock, cell strength, data xfer) and nothing else. It is auto-rotating. The phone does react to touches with the buttons lighting up, but I can't get anywhere. Kies can see the phone, the phone number, the firmware version and all that. It reports Internal Memory as 84.83MB used of 1.58GB. I can navigate through the phone using Windows Explorer. I did a Restore with Kies but it doesn't seem to have had any relevant effect.
I am able to boot into CWM Recovery. I don't remember doing a back-up with it, and when I ask it to restore from either the SD card or the interal SD it says it can't mount.
At this point I would start thinking about taking the phone back to the store, but a flash counter appears during start-up and I'd rather they didn't see that for obvious reasons.
When I google I just get people who have bricked their phones. I just want my phone to work again. I'm not worried about modifying it further to achieve that.
Yoqui said:
I have the GT-S7560M through Solo (Bell) and I rooted it shortly after purchase last year. I've been happy with the phone and for the last few weeks an upgrade notice has been appearing but would fail when applied. Some searching suggested the root was interfering. At first I started to look into un-rooting the phone, but then thought that a factory reset would be the simplest, least-risky solution. I had done a factory reset on my last Galaxy phone without a problem so it seemed like a safe choice. I backed up the contact info, etc with Kies (I don't use many apps so I didn't go all out ie Titanium Backup) and removed my SD card.
Now the phone boots to screen asking me to pick a language and press Start. Then it moves on to a black screen with the info bar at the top (clock, cell strength, data xfer) and nothing else. It is auto-rotating. The phone does react to touches with the buttons lighting up, but I can't get anywhere. Kies can see the phone, the phone number, the firmware version and all that. It reports Internal Memory as 84.83MB used of 1.58GB. I can navigate through the phone using Windows Explorer. I did a Restore with Kies but it doesn't seem to have had any relevant effect.
I am able to boot into CWM Recovery. I don't remember doing a back-up with it, and when I ask it to restore from either the SD card or the interal SD it says it can't mount.
At this point I would start thinking about taking the phone back to the store, but a flash counter appears during start-up and I'd rather they didn't see that for obvious reasons.
When I google I just get people who have bricked their phones. I just want my phone to work again. I'm not worried about modifying it further to achieve that.
Click to expand...
Click to collapse
You have posted in wrong section
BTW your solution is just flash stock Rom via ODIN , your problem will get solved.
BTW your solution is just flash stock Rom via ODIN , your problem will get solved.
Click to expand...
Click to collapse
I've just finished doing that, and it appears to have worked.
For anyone else with a similar problem who finds this thread:
- Go to the FAQ here: http://forum.xda-developers.com/showthread.php?p=45767157#post45767157
- Download Daver18qc's root kit at the link provided (you'll have to scroll down to the second post). You want this to get Odin; don't worry about the zip's other contents.
- Go here: http://www.sammobile.com/ and register. It's free and all it wants is an e-mail and your country.
- Go here: http://www.sammobile.com/firmwares/ and type s7560m in the search box. The list will automatically update. I'm a Solo customer and chose 'Canada (Bell Mobile)'. When I first tried this in Firefox I would get a screen telling me I wasn't logged in. I tried it in IE (which I never use and so is 'clean') and the download went through.
- Go back to the FAQ http://forum.xda-developers.com/showthread.php?p=45767157#post45767157 and scroll down to 'Short Tutorials' and 'How to Flash with Odin:'.
- One thing it leaves out is that when you boot into Download Mode, you will first get a warning screen that asks you to either press Volume Up to continue or Volume Down to abort and reboot. Not a big deal but it caught me off guard. Odin will not detect the phone until you get past this screen.
- Continue with the Tutorial. After it is done you will have to setup the phone again. But at least it's working now.

Categories

Resources