I'll first list specs of my phone so it gives you some information you might need to help me solve my problem.
Verizon Galaxy S4
Android 4.3 MK2
Download mode works properly. Phone will not turn on unless it is plugged in via micro USB. Recovery mode boot loops.
(Recovery mode) I hold volume up and power after I plug in the micro usb to turn the phone on, and it shows the samsung logo, and the blue text pops up in the corner and says "Recovery Booting". After about 2 seconds of it showing that, it'll just black screen and repeat this boot loop of the samsung logo popping up and the blue text as if I have the recovery keys held down.
What led up to all of this is, my phone crashed and it turned off and tried to reboot, and crashed during the reboot. That's where I ran into the problem with the phone not turning on unless it was plugged in(battery is fully charged). At that time, if I plugged it in and didn't touch any keys, it would vibrate, and then a battery icon with a gray circle loading thing would pop up in a frozen picture. Then after about 8 seconds, it'd black screen and boot loop that. I couldn't get into Recovery at that time, but download worked fine. So then I googled a little and I flashed something onto my phone using Odin and Download mode. The file is supposed to make the default boot sequence go to recovery mode. This worked, but since Recovery mode is broken, it doesn't work entirely. After this, I didn't do anything for a day, and then I read some posts and tried flashing both a Wipe and No-wipe stock firmware MK2. Both of which did not work, since still, the phone was defaulting its boot to the broken recovery mode.
So as far as I know, the only way to do anything to the phone is through Odin and Download mode since nothing else works. I'm really hoping I'll be able to fix this, because I'd rather not pay $100 for a new phone :/
Basically what I'm asking for is what I should do next.. My only last thought is(If its possible) to wipe the phone using Odin, then putting the stock firmware back onto it. (The wipe of course getting rid of that stupid file that makes it go into recovery mode.
Baurblades43 said:
I'll first list specs of my phone so it gives you some information you might need to help me solve my problem.
Verizon Galaxy S4
Android 4.3 MK2
Download mode works properly. Phone will not turn on unless it is plugged in via micro USB. Recovery mode boot loops.
(Recovery mode) I hold volume up and power after I plug in the micro usb to turn the phone on, and it shows the samsung logo, and the blue text pops up in the corner and says "Recovery Booting". After about 2 seconds of it showing that, it'll just black screen and repeat this boot loop of the samsung logo popping up and the blue text as if I have the recovery keys held down.
What led up to all of this is, my phone crashed and it turned off and tried to reboot, and crashed during the reboot. That's where I ran into the problem with the phone not turning on unless it was plugged in(battery is fully charged). At that time, if I plugged it in and didn't touch any keys, it would vibrate, and then a battery icon with a gray circle loading thing would pop up in a frozen picture. Then after about 8 seconds, it'd black screen and boot loop that. I couldn't get into Recovery at that time, but download worked fine. So then I googled a little and I flashed something onto my phone using Odin and Download mode. The file is supposed to make the default boot sequence go to recovery mode. This worked, but since Recovery mode is broken, it doesn't work entirely. After this, I didn't do anything for a day, and then I read some posts and tried flashing both a Wipe and No-wipe stock firmware MK2. Both of which did not work, since still, the phone was defaulting its boot to the broken recovery mode.
So as far as I know, the only way to do anything to the phone is through Odin and Download mode since nothing else works. I'm really hoping I'll be able to fix this, because I'd rather not pay $100 for a new phone :/
Basically what I'm asking for is what I should do next.. My only last thought is(If its possible) to wipe the phone using Odin, then putting the stock firmware back onto it. (The wipe of course getting rid of that stupid file that makes it go into recovery mode.
Click to expand...
Click to collapse
are you an unrooted stock ROM??
I'm sure someone smarter then me will know exactly what is going on here but things I'd try in the mean time is another Odin file possibly. I believe Surge has said that if MK2 file doesn't work to try the MJ7 full wipe/Re-Partition one. At this point what you got to lose?
Sent from my SCH-I545 using Tapatalk
decaturbob said:
are you an unrooted stock ROM??
Click to expand...
Click to collapse
I am rooted with safestrap installed. Using the Hyperdrive ROM
Mistertac said:
I'm sure someone smarter then me will know exactly what is going on here but things I'd try in the mean time is another Odin file possibly. I believe Surge has said that if MK2 file doesn't work to try the MJ7 full wipe/Re-Partition one. At this point what you got to lose?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I believe I've already done this? I'm not sure. I'll have to check once I get home later in the day.
Baurblades43 said:
I believe I've already done this? I'm not sure. I'll have to check once I get home later in the day.
Click to expand...
Click to collapse
I would strongly suggest the Full Wipe method back to MK2. As long as you can boot into Download mode this is probably the best way to get a clean OS working again. From there you know the drill, Saferoot, SS, etc.
http://forum.xda-developers.com/showthread.php?t=2578209
Use sp flash tool and install another recovery. That will surely work. Just download sp flash tool and drivers for your device and install these files in your pc. After that download recovery.img and scatter file.txt for your device. First load the scattered file.txt using sp flash tool, now uncheck all the tick box except the recovery. Now click on recovery and select the recovery.img which you have downloaded. Now take out your phone's battery and connect it via usb cable. Make sure you have installed your phone's drivers. Click on download button on sp flash tool. If not works then remove the usb cable and reconnect again. You will see a green circle saying its done. Click on ok. And try to get into recovery again.
Sent from unnamed ROM using xda premium app
naveen6252 said:
Use sp flash tool and install another recovery. That will surely work. Just download sp flash tool and drivers for your device and install these files in your pc. After that download recovery.img and scatter file.txt for your device. First load the scattered file.txt using sp flash tool, now uncheck all the tick box except the recovery. Now click on recovery and select the recovery.img which you have downloaded. Now take out your phone's battery and connect it via usb cable. Make sure you have installed your phone's drivers. Click on download button on sp flash tool. If not works then remove the usb cable and reconnect again. You will see a green circle saying its done. Click on ok. And try to get into recovery again.
Sent from unnamed ROM using xda premium app
Click to expand...
Click to collapse
If he's using Safestrap, it most likely means he can't flash a recovery image. He could brick his phone.
Was just going to say that. I don't know much about that flash tool myself... Is it an alternative to Odin? From the little I read... You can flash an entire rom or just something in particular to repair a phone. Either way I don't think the OP should try that method. Stick with Odin.
Sent from my SCH-I545 using Tapatalk
riker147 said:
If he's using Safestrap, it most likely means he can't flash a recovery image. He could brick his phone.
Click to expand...
Click to collapse
+1, the only safe option is to flash a clean factory image via Odin. Otherwise say hello to your new doorstop if you mess with Recovery on MK2 locked bootloader
Flash new image >> 15-25 minutes
Root >> 2-3 minutes
SS >> 3-5 minutes
HD RLS15 (for example) >> 15 minutes
In about an hour or so phone is back up and running. No brainer..........
cbmggm said:
+1, the only safe option is to flash a clean factory image via Odin. Otherwise say hello to your new doorstop if you mess with Recovery on MK2 locked bootloader
Flash new image >> 15-25 minutes
Root >> 2-3 minutes
SS >> 3-5 minutes
HD RLS15 (for example) >> 15 minutes
In about an hour or so phone is back up and running. No brainer..........
Click to expand...
Click to collapse
The thing is.. I've tried flashing new images before, and all its doing is overwriting my old one, but the stupid factory thing I flashed makes the default path the broken recovery so I don't think this will work.
Baurblades43 said:
The thing is.. I've tried flashing new images before, and all its doing is overwriting my old one, but the stupid factory thing I flashed makes the default path the broken recovery so I don't think this will work.
Click to expand...
Click to collapse
Are you sure you flashed the full wipe tar file? I've successfully used this method numerous times.
http://www.androidfilehost.com/?fid=23269279319198294
Make sure you download to PC first then copy to your external SD card on your phone.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
Are you sure you flashed the full wipe tar file? I've successfully used this method numerous times.
http://www.androidfilehost.com/?fid=23269279319198294
Make sure you download to PC first then copy to your external SD card on your phone.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Umm.. Why would I want to put that on my external SD card? Wouldn't I want to just use it through ODIN?
Oops sorry I meant to leave the tar file on the PC.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
Oops sorry I meant to leave the tar file on the PC.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Haha alright. I'll go ahead and download this file and give it a go. Wish me luck.
cbmggm said:
Oops sorry I meant to leave the tar file on the PC.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Also, can you give me a quick guide on how to flash this through Odin? I just wanna make sure I'm not doing anything wrong.
Baurblades43 said:
Also, can you give me a quick guide on how to flash this through Odin? I just wanna make sure I'm not doing anything wrong.
Click to expand...
Click to collapse
Directions are in the thread: http://forum.xda-developers.com/showthread.php?t=2578209
Oishikatta said:
Directions are in the thread: http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
I followed the directions for everything as they were given and I got the same result I've gotten after flashing anything. Everything works fine, then the big blue "RESET" icon appears on Odin, then the phone reboots, I get samsung logo, and then the blue "recovery booting" text shows up.. and then the screen blacks out, and boot loops that same thing.
Baurblades43 said:
I followed the directions for everything as they were given and I got the same result I've gotten after flashing anything. Everything works fine, then the big blue "RESET" icon appears on Odin, then the phone reboots, I get samsung logo, and then the blue "recovery booting" text shows up.. and then the screen blacks out, and boot loops that same thing.
Click to expand...
Click to collapse
Make sure you're using the Full Wipe image (SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip), and have extracted it to a .tar.md5
Also download the JFLTE_USA_VZW_16G.pit (assuming you have the 16GB version of the S4).
Put the .tar.md5 in the AP section and the PIT file in the PIT section.
Leave the other checkboxes in Odin at their defaults.
Take a screenshot at this point, click Start, and then take another screenshot when it completes or gives an error.
Oishikatta said:
Make sure you're using the Full Wipe image (SCH-I545_VZW_1_20131212083410_mwx72ql56g_fac.zip), and have extracted it to a .tar.md5
Also download the JFLTE_USA_VZW_16G.pit (assuming you have the 16GB version of the S4).
Put the .tar.md5 in the AP section and the PIT file in the PIT section.
Leave the other checkboxes in Odin at their defaults.
Take a screenshot at this point, click Start, and then take another screenshot when it completes or gives an error.
Click to expand...
Click to collapse
Alright. I did a lot between your post and now. All of the information for everything I did is underneath each picture thats posted. So read them carefully.
http://imgur.com/3c4YZoz,CjiLmlY,Gfjx7Tc,TO1xSMV#0
EDIT: I looked up the battery icon problem and I found some interesting news. After all of the struggling with the darn phone, this is a common problem with this phone on 4.3. Its an overheating issue to the PBA(Motherboard I think). Thanks everyone for the help, I'm just gonna send it in and get a new phone.
Related
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.
I'm trying to put some decent firmware on my Galaxy Ace, but have hit a hurdle. I believe I've successfully rooted, but it's all fallen apart when trying to install ClockworkMod recovery.
All of the tutorials mention browsing for the ZIP file on the SD card, but my menu was different. My only option was to install UPDATE.ZIP from the SD card, so I rebooted, renamed the recovery-clockwork-5.0.zip file accordingly, went back into boot loader and then chose that option. It seemed to work.
Now I have no bootloader. Luckily, the handset powers on fine if you just press the power button, but switching it on with the centre front button held down hangs at the startup screen or goes into emergency download mode. I've no idea how to flash a new recovery other than by going through the recovery menu itself. This puts me at a loss as to how to proceed.
Any suggestions would be greatly appreciated.
as your recovery itself is gone you have to get it by odin flash stock firmware
madman_amit said:
as your recovery itself is gone you have to get it by odin flash stock firmware
Click to expand...
Click to collapse
Thanks for the quick reply. Unfortunately, I seem to have properly bricked it now. I foolishly went into ROM Manager and told it to reboot into recovery. Much mucking about later, and I can only get into Emergency Dload mode now.
I've been trying to get hold of Odin and the Cooper_v1.0.ops files, but everything seems to point me to some links on Mediafire, which is asking me for passwords that I don't have.
Seriously panicking now, as I don't have a working phone. Help!
FishyDave said:
Thanks for the quick reply. Unfortunately, I seem to have properly bricked it now. I foolishly went into ROM Manager and told it to reboot into recovery. Much mucking about later, and I can only get into Emergency Dload mode now.
I've been trying to get hold of Odin and the Cooper_v1.0.ops files, but everything seems to point me to some links on Mediafire, which is asking me for passwords that I don't have.
Seriously panicking now, as I don't have a working phone. Help!
Click to expand...
Click to collapse
seriously no one can help you here now..
go claim your warranty from samsung and get replaced board or brand new phone
You have lost recovery.img, Odin it back.
Edit: lie to service centre or buy a new one and add cement
Sent from my GT-S5830 using XDA
Sorry if I'm being dim, but this is only the second time I've tried rooting a phone, and my HTC Desire went off without a hitch.
I'm guessing that I need the recovery.img file from the clockworkmod zip file, but which version of Odin should I be using (I now have 1.83 and 4.38, which boxes should I have ticked, and which of the 'images' boxes should I be using for the upload?
Thanks in anticipation
Are you have GT-S5830 or GT-S5830i? For me it look like you have the newer i version.
FishyDave said:
Sorry if I'm being dim, but this is only the second time I've tried rooting a phone, and my HTC Desire went off without a hitch.
I'm guessing that I need the recovery.img file from the clockworkmod zip file, but which version of Odin should I be using (I now have 1.83 and 4.38, which boxes should I have ticked, and which of the 'images' boxes should I be using for the upload?
Thanks in anticipation
Click to expand...
Click to collapse
If you have used ROM manager your phone is dead
Sent from my GT-S5830 using XDA
Thanks again
I installed ROM Manager, but the only option I used on it was 'Reboot into recovery.' Is that still enough to kill the Samsung, or has it simply set a 'recovery' flag that has it stuck in that mode until a successful recovery?
The label on the back says GT-S5830 rather than GT-S5830i, and I don't recall it showing the 'i' on start-up when it was working. That's what's put me off doing the recovery detailed here: http://forum.xda-developers.com/showthread.php?t=1552792
If all else fails, it's still under warranty. Fingers crossed they just fix it or swap it, rather than digging too deeply into why it went wrong.
FishyDave said:
Thanks again
I installed ROM Manager, but the only option I used on it was 'Reboot into recovery.' Is that still enough to kill the Samsung, or has it simply set a 'recovery' flag that has it stuck in that mode until a successful recovery?
The label on the back says GT-S5830 rather than GT-S5830i, and I don't recall it showing the 'i' on start-up when it was working. That's what's put me off doing the recovery detailed here: http://forum.xda-developers.com/showthread.php?t=1552792
If all else fails, it's still under warranty. Fingers crossed they just fix it or swap it, rather than digging too deeply into why it went wrong.
Click to expand...
Click to collapse
Settings > About phone
Ace-ing all tests.
did u have a download mode?
dredremon said:
did u have a download mode?
Click to expand...
Click to collapse
read the first page bro.
anyway back to OP
you ised rom manager thus makingore problems for yourself. only option bow js lie to servicenter
Sent from my GT-S5830 using XDA
Does it boot or not, or do you get nothing but emergency dl mode?
Sent from my GT-S5830 using XDA
EmoBoiix3 said:
Settings > About phone
Ace-ing all tests.
Click to expand...
Click to collapse
Dude his phone cannot be booted liao..
Sent from my GT-S5830 using Tapatalk 2
Goomanager app flashed a wrong recovery to the phone, now it won't boot but is stuck at the black "Samsung GALAXY Txt" Boot screen. does anybody know how to fix this? i wouldn't mind having to hard reset it. I tried flashing new recovery using adb/fastboot but adb doesn't "see" the device. thanks if you answer!:good:
bdec said:
Goomanager app flashed a wrong recovery to the phone, now it won't boot but is stuck at the black "Samsung GALAXY Txt" Boot screen. does anybody know how to fix this? i wouldn't mind having to hard reset it. I tried flashing new recovery using adb/fastboot but adb doesn't "see" the device. thanks if you answer!:good:
Click to expand...
Click to collapse
I'd try using Odin to flash the stock firmware for your phone (Can be found on Samfirmware).
Sent from my SCH-I535 using xda premium
shimp208 said:
I'd try using Odin to flash the stock firmware for your phone (Can be found on Samfirmware).
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
kudos for you my friend, it worked!
have some cookies
__________
/ YAY \
/ IT'S A \
\ COOKIE /
\__________/
sorry if my art sucks
Unable to enter Download Mode
I flashed a wrong ROM as well, but my problem is that I can't enter Download Mode to re-flash the device with Odin.
Any idea?
Thanks
caraconan said:
I flashed a wrong ROM as well, but my problem is that I can't enter Download Mode to re-flash the device with Odin.
Any idea?
Thanks
Click to expand...
Click to collapse
Are you able to get into recovery mode still? For download mode make sure your holding down the correct key combination to get into download mode. You can also try using a USB Download jig which you can get from here, which when plugged into the phone will force the phone into download mode. As a fair warning the download jig's don't usually work with newer model phones but for a couple bucks it's worth a try. Let me know if you still have questions.
Motherboard dead?
Sorry to invade this post. I would just like to have confirmation on my device and it's pretty similar to what is found here. The only way I can access download mode is by pressing Q+Power and then adding the battery. Odin connects to everything, I can even flash the firmware from Bell for my Galaxy gt-i5510M and it PASS. But I can't still power it up, is the motherboard or something similar dead?
Thanks
jfilippo said:
Sorry to invade this post. I would just like to have confirmation on my device and it's pretty similar to what is found here. The only way I can access download mode is by pressing Q+Power and then adding the battery. Odin connects to everything, I can even flash the firmware from Bell for my Galaxy gt-i5510M and it PASS. But I can't still power it up, is the motherboard or something similar dead?
Thanks
Click to expand...
Click to collapse
If your device can still access download mode and Odin can successfully connect to your device an flash the firmware your device's motherboard is not dead. Try re-flashing the firmware to your device and checking auto-reboot option in Odin this way when the firmware finishes flashing the device will automatically reboot and hopefully power on then.
Thanks for the fast answer, you've been answering 3 people back on this thread, impressive.
Unfortunately I made sure of that, the auto reboot was checked but it doesn't reboot the device. I wanted to put a screenshot but I didn't realize you need around 10 posts to be able to post outside links. I've been looking through xda for a while but never posting.
I'm used to adb, so Odin is a bit new I have to admit. I've put the ops file, callisto in this case, in the appropriate ops , and then the One Package file I got from samfirmware "I5510UGKC5_I5510BMCKC5_BMC". Is there something else I could flash? It wouldn't be like some other phones where I could put down a Custom Recovery, go back to stock, etc. ?
jfilippo said:
Thanks for the fast answer, you've been answering 3 people back on this thread, impressive.
Unfortunately I made sure of that, the auto reboot was checked but it doesn't reboot the device. I wanted to put a screenshot but I didn't realize you need around 10 posts to be able to post outside links. I've been looking through xda for a while but never posting.
I'm used to adb, so Odin is a bit new I have to admit. I've put the ops file, callisto in this case, in the appropriate ops , and then the One Package file I got from samfirmware "I5510UGKC5_I5510BMCKC5_BMC". Is there something else I could flash? It wouldn't be like some other phones where I could put down a Custom Recovery, go back to stock, etc. ?
Click to expand...
Click to collapse
To clarify did you put the firmware in the correct slot in Odin (PDA slot in this case) when flashing? Also double check your flashing the correct firmware for your device, as that could also be part of the problem.
Well you figured some things that were wrong. I was putting it in the one package slot. So I tried in the PDA slot, but it said "Invalid Image Type". From the sticker inside the battery compartment, it does say it's the GT-I5510M, so the 551 from Bell Canada it seems. But it's not easy to find a firmware for it, and the only one I found is at sammobile. There's plenty others under GT-I5510, but they're all European.
Any idea what I could use instead? The full name of the firmware I have is: "I5510UGKC5_BMCKC5_HOMEDOWNLOAD_TEST.tar" or "I5510UGKC5_I5510BMCKC5_BMC.zip" for the zip.
Thanks a lot for following this.
jfilippo said:
Well you figured some things that were wrong. I was putting it in the one package slot. So I tried in the PDA slot, but it said "Invalid Image Type". From the sticker inside the battery compartment, it does say it's the GT-I5510M, so the 551 from Bell Canada it seems. But it's not easy to find a firmware for it, and the only one I found is at sammobile. There's plenty others under GT-I5510, but they're all European.
Any idea what I could use instead? The full name of the firmware I have is: "I5510UGKC5_BMCKC5_HOMEDOWNLOAD_TEST.tar" or "I5510UGKC5_I5510BMCKC5_BMC.zip" for the zip.
Thanks a lot for following this.
Click to expand...
Click to collapse
You can try ignoring the "Invalid Image Type" error and trying to flash anyway just don't unplug your phone from Odin until it fully completes the process.
shimp208 said:
You try ignoring the "Invalid Image Type" error and trying to flash anyway just don't unplug your phone from Odin until it fully completes the process.
Click to expand...
Click to collapse
I did, but didn't work, I should have mentioned that. So the screen is still blank. But another driver got recognized and installed once the firmware was installed, Samsung com 3 if I remember well. I was hoping when I saw that!
jfilippo said:
I did, but didn't work, I should have mentioned that. So the screen is still blank. But another driver got recognized and installed once the firmware was installed, Samsung com 3 if I remember well. I was hoping when I saw that!
Click to expand...
Click to collapse
With the new COM port being recognized try the procedure again and see if it has any different results.
sorry to interrupt you people.. but are you sure that it is a proper firmware file. because the pda file is .tar file. also, try entering the recovery mode and flashing a cwm recovery. then check if the system is mounted.
Sorry I've been away, meaning no phone and laptop with me. Thanks for the replies. I tried to flash again the firmware last week but nothing happened unfortunately.
adisawant said:
sorry to interrupt you people.. but are you sure that it is a proper firmware file. because the pda file is .tar file. also, try entering the recovery mode and flashing a cwm recovery. then check if the system is mounted.
Click to expand...
Click to collapse
I can't access recovery mode, only download mode by simultaneously putting the battery back in and pushing Q+Power. But I am wondering also if it could be a wrong firmware... Can I just flash a custom rom through Odin? Would that make up for it? Anything to having back in working order.
jfilippo said:
Sorry I've been away, meaning no phone and laptop with me. Thanks for the replies. I tried to flash again the firmware last week but nothing happened unfortunately.
I can't access recovery mode, only download mode by simultaneously putting the battery back in and pushing Q+Power. But I am wondering also if it could be a wrong firmware... Can I just flash a custom rom through Odin? Would that make up for it? Anything to having back in working order.
Click to expand...
Click to collapse
i dont think flashing it will help. Just try to download another firmware and flash it.
anyone can sell samsung galaxy 551 i want to buy please call me 7384388281(india/kolkata)
Okay, so I don't know the technical term for what's happened to my phone, although, I can tell you that I cannot turn it on with the power button. The only way to get it on is plug it into my charger via micro usb. Recovery mode is unable to work. I can get into download mode though. And if I don't hit any buttons, it just said "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
I just want to be able to use my phone again, I'm totally alright with having to wipe every bit of data off of it and have it absolutely factory new. How can I do this? I could use Odin or Kies. However, Kies can't recognize my phone and just says "Device not responding. To resolve the issue, reboot the device." I'm tried dozens of times, it just can't find my device.
Please help.. I am phoneless and I could care less about losing data at this point.
Baurblades43 said:
Okay, so I don't know the technical term for what's happened to my phone, although, I can tell you that I cannot turn it on with the power button. The only way to get it on is plug it into my charger via micro usb. Recovery mode is unable to work. I can get into download mode though. And if I don't hit any buttons, it just said "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
I just want to be able to use my phone again, I'm totally alright with having to wipe every bit of data off of it and have it absolutely factory new. How can I do this? I could use Odin or Kies. However, Kies can't recognize my phone and just says "Device not responding. To resolve the issue, reboot the device." I'm tried dozens of times, it just can't find my device.
Please help.. I am phoneless and I could care less about losing data at this point.
Click to expand...
Click to collapse
Some people have had success with pressing the volume keys while in that "Firmware upgrade" error, causing the phone to continue to a normal boot. It's worth a try. Failing that, download the proper ROM image for your phone and flash it using ODIN.
If you don't know what build it has, I'd start with flashing a no-wipe MK2 image.
First, how'd you get to this point. Was this associated with rooting / flashing / something else? When you get into download mode, are you trying to Odin something in? It shouldn't say "Firmware upgrade encountered..." unless you're trying to push something. What happens when you get into recovery mode?
Second, do you know which factory image you started with? That's important, because if you started with an earlier image and flash an newer one, you can't go back. and the earlier the image, the easier the root.
This thread has no-wipe factory images. They're large files, so heads up.
http://forum.xda-developers.com/showthread.php?t=2301259
You need Odin working. Good luck.
Baurblades43 said:
Okay, so I don't know the technical term for what's happened to my phone, although, I can tell you that I cannot turn it on with the power button. The only way to get it on is plug it into my charger via micro usb. Recovery mode is unable to work. I can get into download mode though. And if I don't hit any buttons, it just said "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
I just want to be able to use my phone again, I'm totally alright with having to wipe every bit of data off of it and have it absolutely factory new. How can I do this? I could use Odin or Kies. However, Kies can't recognize my phone and just says "Device not responding. To resolve the issue, reboot the device." I'm tried dozens of times, it just can't find my device.
Please help.. I am phoneless and I could care less about losing data at this point.
Click to expand...
Click to collapse
---------- Post added at 01:53 PM ---------- Previous post was at 01:47 PM ----------
k1mu said:
Some people have had success with pressing the volume keys while in that "Firmware upgrade" error, causing the phone to continue to a normal boot. It's worth a try. Failing that, download the proper ROM image for your phone and flash it using ODIN.
If you don't know what build it has, I'd start with flashing a no-wipe MK2 image.
Click to expand...
Click to collapse
I'd start with a MDK, earlier doesn't hurt, and I believe that's the first factory image released officially
and here's a full wipe image for MDK (erroneously called MKD in the title)
http://forum.xda-developers.com/showthread.php?t=2289325
I'd try the No-Wipe images first
yooeee said:
First, how'd you get to this point. Was this associated with rooting / flashing / something else? When you get into download mode, are you trying to Odin something in? It shouldn't say "Firmware upgrade encountered..." unless you're trying to push something. What happens when you get into recovery mode?
Second, do you know which factory image you started with? That's important, because if you started with an earlier image and flash an newer one, you can't go back. and the earlier the image, the easier the root.
This thread has no-wipe factory images. They're large files, so heads up.
http://forum.xda-developers.com/showthread.php?t=2301259
You need Odin working. Good luck.
---------- Post added at 01:53 PM ---------- Previous post was at 01:47 PM ----------
I'd start with a MDK, earlier doesn't hurt, and I believe that's the first factory image released officially
and here's a full wipe image for MDK (erroneously called MKD in the title)
http://forum.xda-developers.com/showthread.php?t=2289325
I'd try the No-Wipe images first
Click to expand...
Click to collapse
Well initially, yesterday my phone crashed and I couldn't get it back on, unless I charged it and a grey battery icon would pop up and it'd vibrate every few seconds but nothing would happen. I couldn't get into recovery there either. So I got into download mode and I looked for things that could get me into recovery mode so I could factory reset. I flashed something on it using Odin and it worked.. To a point. On startup(plugging phone in) It would bring me into the samsung logo and the blue text in the top right saying recovery, but then the phone would just stop. And it'd be in a boot loop doing this until I unplugged. Now I woke up this morning and I'm getting this new error from Kies. I have the files that I flashed it with last night.
Baurblades43 said:
Well initially, yesterday my phone crashed and I couldn't get it back on, unless I charged it and a grey battery icon would pop up and it'd vibrate every few seconds but nothing would happen. I couldn't get into recovery there either. So I got into download mode and I looked for things that could get me into recovery mode so I could factory reset. I flashed something on it using Odin and it worked.. To a point. On startup(plugging phone in) It would bring me into the samsung logo and the blue text in the top right saying recovery, but then the phone would just stop. And it'd be in a boot loop doing this until I unplugged. Now I woke up this morning and I'm getting this new error from Kies. I have the files that I flashed it with last night.
Click to expand...
Click to collapse
how did it crash in the first place? and also, it's important to know what you flashed through odin to understand what's going on. we may never figure that out so.... it looks like you lost recovery. the only thing left is download mode. (If you can't go into download mode, I don't know any other options.)
read up on which factory image applies to you and odin it. you'll start fresh and then need to root to.
yooeee said:
how did it crash in the first place? and also, it's important to know what you flashed through odin to understand what's going on. we may never figure that out so.... it looks like you lost recovery. the only thing left is download mode. (If you can't go into download mode, I don't know any other options.)
read up on which factory image applies to you and odin it. you'll start fresh and then need to root to.
Click to expand...
Click to collapse
I'm totally fine with losing my root, and my old rom and stuff.. I could care less. I know how to root and its very easy along with getting safestrap going again. However, I was on MK2 and I don't see that in the list of images.
(I wasn't able to put my link in, but I just saw something on a website regarding Odin, and using the "re-partition" check box. I used that(it said to on the instructions) and the thing I just saw said to NEVER use that) I flashed that and with pit. I'm new to odin sooo yeah I don't necessarily know everything that goes on.
Also, the phone crashed in what seemed like a completely random flash... I was literally just on snapchat, things froze up, and my phone started doing the boot animation for Hyperdrive 15(The rom I was running) but it never finished, half way through, the phone turned off.
Mk2 came after those, so do a search. With Odin you shouldn't touch anything except load the file in the second slot. I forget what it's called. Read the Odin tutorials
Sent from my SCH-I545 using xda app-developers app
yooeee said:
Mk2 came after those, so do a search. With Odin you shouldn't touch anything except load the file in the second slot. I forget what it's called. Read the Odin tutorials
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
So this factory image, wouldn't I want one that DOES wipe the phone? Since I just want everything to be clean and new again?
Baurblades43 said:
So this factory image, wouldn't I want one that DOES wipe the phone? Since I just want everything to be clean and new again?
Click to expand...
Click to collapse
maybe, but hopefully this will get you a recovery that you can wipe. there are wipe images out there
yooeee said:
maybe, but hopefully this will get you a recovery that you can wipe. there are wipe images out there
Click to expand...
Click to collapse
Okay, I finally flashed the MK2 no-wipe on it after many hours of downloading. Now it says "RESET" on odin and it showed samsung logo, and the recovery blue text in the top left, but then that just went to a black screen, and now I'm just getting vibrating every 2 seconds with a black screen.
EDIT: Okay so I tried seeing if download mode still worked, and it did, so I just told it to restart the phone from that and now its back to what it was doing originially. It shows the gray battery with the circle loading thing frozen in place, that stays there for a second, then screen goes black, vibrates, and it repeats this.
Baurblades43 said:
Okay, I finally flashed the MK2 no-wipe on it after many hours of downloading. Now it says "RESET" on odin and it showed samsung logo, and the recovery blue text in the top left, but then that just went to a black screen, and now I'm just getting vibrating every 2 seconds with a black screen.
Click to expand...
Click to collapse
Flash full wipe version...also are you flashing as PDA or phone?
jamesd1085 said:
Flash full wipe version...also are you flashing as PDA or phone?
Click to expand...
Click to collapse
Link maybe? I'm fed up with downloading the wrong thing and screwing my phone over.
Flashing as PDA.
Also, read the edit I made to that post to make a more accurate response maybe?
I'll try to find it when I get to my laptop. There's a possibility your phone just bonked hardware wise. Hard to say.
Sent from my SCH-I545 using xda app-developers app
yooeee said:
I'll try to find it when I get to my laptop. There's a possibility your phone just bonked hardware wise. Hard to say.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thank you for all of the help by the way. I really don't want to go from a GS4 to an iPod 3G... Ugh I would die
Baurblades43 said:
Thank you for all of the help by the way. I really don't want to go from a GS4 to an iPod 3G... Ugh I would die
Click to expand...
Click to collapse
Heres the MK2
http://forum.xda-developers.com/showthread.php?t=2578209
Sent from my SCH-I545 using Tapatalk
---------- Post added at 02:34 AM ---------- Previous post was at 02:32 AM ----------
If that doesn't work for you try MJ7
http://forum.xda-developers.com/showthread.php?t=2507253
Those are the only two that you can go back and forth between.
Sent from my SCH-I545 using Tapatalk
Alright so I flashed the full wipe correctly and everything looked like it worked fine. But it just says "RESET" on Odin and its trying to start the phone and it shows the samsung logo but its defaulting to Recovery Mode, but after the samsung logo, and the blue text in the upper left corner "Recovery Booting..." it just black screens and boot loops like that. I believe this is because I flashed a thing on Odin yesterday that was supposed to make the phone go into Recovery(it wasn't working by holding volume and power). Any way to get rid of this stupid default recovery thing?
Baurblades43 said:
Alright so I flashed the full wipe correctly and everything looked like it worked fine. But it just says "RESET" on Odin and its trying to start the phone and it shows the samsung logo but its defaulting to Recovery Mode, but after the samsung logo, and the blue text in the upper left corner "Recovery Booting..." it just black screens and boot loops like that. I believe this is because I flashed a thing on Odin yesterday that was supposed to make the phone go into Recovery(it wasn't working by holding volume and power). Any way to get rid of this stupid default recovery thing?
Click to expand...
Click to collapse
If MK2 is not getting you fixed up try MJ7. That should fix you right up. You should be back to business as usual. Sometimes you just need to try try again lol
Sent from my SCH-I545 using Tapatalk
Mistertac said:
If MK2 is not getting you fixed up try MJ7. That should fix you right up. You should be back to business as usual. Sometimes you just need to try try again lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Full wipe MJ7 or no-wipe? Sorry just clarifying.
I'm wondering if this is the correct file ---> https://www.androidfilehost.com/?fid=23321874045862070
Baurblades43 said:
Full wipe MJ7 or no-wipe? Sorry just clarifying.
Click to expand...
Click to collapse
Full Wipe
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Full Wipe
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Was that the correct file?(Look back at the post you just replied too.
I was a fool and flashed TWRP without using Odin. This is my first Samsung that I have attempted to root. Keeps trying to boot recovery. Any advice?
Could please provide some more details? It sounds like you flashed a custom recovery using the stock recovery. However, if you know your last firmware version, i.e. NH7, NK4, or OC5 you should be able to flash a stock image using Odin.
All I know it was running 4.4.2. I flashed with rom toolbox. I know, big mistake.
Says "recovery booting.....
Recovery is not seandroid enforcing
Set warranty bit : recovery
daswahnsinn said:
Could please provide some more details? It sounds like you flashed a custom recovery using the stock recovery. However, if you know your last firmware version, i.e. NH7, NK4, or OC5 you should be able to flash a stock image using Odin.
Click to expand...
Click to collapse
Running 4.4.2 boot looping " recovery booting....
Recovery is not SEANDROID enforcing
Set warranty bit : recovery
I would just flash a Nk4 or OC5 image in Odin, then use Odin to Flash TWRP.
daswahnsinn said:
I would just flash a Nk4 or OC5 image in Odin, then use Odin to Flash TWRP.
Click to expand...
Click to collapse
I cannot get into Odin on the device itself, will the computer pick it up?
Odin is a PC software to flash images onto devices. Mobile Odin works for somethings but I personally have never used it so I can't say much on the subject.
You need you to get Odin on your PC, make sure you have downloaded the proper images for the device. Then open Odin and where you see the PDA slot, click browse then find where you saved the image and click. Next, boot into download mode, via hold volume down, home button, and power, then plug a usb cable from your PC and wait for all the drivers need, you may need to download them and install them before you can continue. Then you can flash the image.
This is a basic Odin procedure but before you do anything else search for Odin here on XDA and read everything. I can't stress this enough.
jemf1982 said:
I was a fool and flashed TWRP without using Odin. This is my first Samsung that I have attempted to root. Keeps trying to boot recovery. Any advice?
Click to expand...
Click to collapse
Pull battery then reinstall the battery. Now boot into download mode and use the odin program on your computer to flash the custom recovery.
I am not at my PC right now so to save a lot of typing, go to rom flashing basics in the general section. Or click on rom flashing basics in my signature.
daswahnsinn said:
Odin is a PC software to flash images onto devices. Mobile Odin works for somethings but I personally have never used it so I can't say much on the subject.
You need you to get Odin on your PC, make sure you have downloaded the proper images for the device. Then open Odin and where you see the PDA slot, click browse then find where you saved the image and click. Next, boot into download mode, via hold volume down, home button, and power, then plug a usb cable from your PC and wait for all the drivers need, you may need to download them and install them before you can continue. Then you can flash the image.
This is a basic Odin procedure but before you do anything else search for Odin here on XDA and read everything. I can't stress this enough.
Click to expand...
Click to collapse
okay, I guess I am missing something. I've read and read and read over and again. I AM STUCK IN A BOOT LOOP. I CANNOT GET INTO DOWNLOAD MODE. THIS IS WHAT I'VE ALREADY SAID. This is all the device will do over and over again. Read my previous posts to to read what it says
jemf1982 said:
okay, I guess I am missing something. I've read and read and read over and again. I AM STUCK IN A BOOT LOOP. I CANNOT GET INTO DOWNLOAD MODE. THIS IS WHAT I'VE ALREADY SAID. This is all the device will do over and over again. Read my previous posts to to read what it says
Click to expand...
Click to collapse
I have read you're posts and I understand what a bootloop is. Also you haven't mentioned you can't get into download mode. Have you tried power cycling the device? I know you're getting frustrated but outside of give you the help I have and jimz, I or no one else can do anything more.
I apologize if I came off rude. That was not my intention at all. I appreciate that you two ( jimz and daswahnsinn) have tried to help me. I'll look it up ,but in case I can not find it, what is power cycling the device?
jemf1982 said:
I apologize if I came off rude. That was not my intention at all. I appreciate that you two ( jimz and daswahnsinn) have tried to help me. I'll look it up ,but in case I can not find it, what is power cycling the device?
Click to expand...
Click to collapse
Instead of saying download mode, I said I couldn't get into Odin on the device. I guess I should have been more specific. I apologize
daswahnsinn said:
I have read you're posts and I understand what a bootloop is. Also you haven't mentioned you can't get into download mode. Have you tried power cycling the device? I know you're getting frustrated but outside of give you the help I have and jimz, I or no one else can do anything more.
Click to expand...
Click to collapse
Okay I hard power cycled it and it finally let in download mode. Thank you. Flashing NK4 now. I'll let you know how it goes. Thanks again for the help
Okay it is now up and running. Just running 4.4.4 instead of 4.4.2. I guess I'll download the correct image and try again.
No worries I know how frustrating it can be when yiu do something and it goes wrong on a new device.
daswahnsinn said:
No worries I know how frustrating it can be when yiu do something and it goes wrong on a new device.
Click to expand...
Click to collapse
Once again I appreciate the info and insight. Just wish Motorola would follow suit with the bootloader unlock