HELP!! Galaxy Core Prime only boots into download mode, need to recover data - Miscellaneous Android Development

Phone is stock, SM-S820L, not rooted or anything as I'm a noob, however a slightly more educated noob after watching the videos making fun of noobs from xda as well as reading the slang terms and adb noob guides.
So I can say with confidence, my phone is NOT bricked nor bootlooping. I was not trying to do any kind of flashing or rooting, I was just updating maps and cue my problem.
Phone turns on and after a minute of blank screen with no splash screen no boot animation, it shows a red letter "movinand checksum confirmation fail" error message. Same error shows up if I try to charge the phone, not sure if it's charging or not.
The phone will NOT boot into recovery, only download mode.
I need to recover data from my phone to my pc. That is my priority/main concern.
After I do that, I would then like to know how to root my phone, install clockwork cyanogen whatever so I don't have to go through this again.
Help me xda grand masters, you're my only hope.

Man to fix this issue flash stock ROM for you device
Enviado de meu GT-S7392L usando Tapatalk

KYLEVE said:
Man to fix this issue flash stock ROM for you device
Enviado de meu GT-S7392L usando Tapatalk
Click to expand...
Click to collapse
How can I flash stock rom if no matter which computer or cable I use the phone is never seen?

android n said:
How can I flash stock rom if no matter which computer or cable I use the phone is never seen?
Click to expand...
Click to collapse
try to install samsung usb drivers

KYLEVE said:
try to install samsung usb drivers
Click to expand...
Click to collapse
I don't know if you're trolling or serious but the computer does not see the phone, at all, there is no trying to install drivers or wrong drivers installed or unknown device in device manager. The drivers/kies/Odin not recognizing the phone are irrelevant as the computer has to see the phone first.
And I didn't mention this earlier but. .. I already installed the correct drivers from Samsung, drivers is not the issue.

android n said:
I don't know if you're trolling or serious but the computer does not see the phone, at all, there is no trying to install drivers or wrong drivers installed or unknown device in device manager. The drivers/kies/Odin not recognizing the phone are irrelevant as the computer has to see the phone first.
And I didn't mention this earlier but. .. I already installed the correct drivers from Samsung, drivers is not the issue.
Click to expand...
Click to collapse
already tested to see if the problem and the cable? or try placing another cell in the odin. poe and also be the usb ports

Related

AP Fastboot Flash Mode not being detected on pc

I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.
greatanomaly said:
I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.
Click to expand...
Click to collapse
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.
1BadWolf said:
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.
Click to expand...
Click to collapse
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...
greatanomaly said:
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...
Click to expand...
Click to collapse
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.
stuck on boot logo
1BadWolf said:
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.
Click to expand...
Click to collapse
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Gr8mobiPro said:
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Chill man..nothing to worry about..please install motorola drivers..it should work.
its still not working
nishant203 said:
Chill man..nothing to worry about..please install motorola drivers..it should work.
Click to expand...
Click to collapse
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:
Use Virtual PC
I still have the same issue. I have installed Windows 7 on VM Ware workstation i.e virtual desktop and then followed the below steps :-
-Reboot your Virtual PC
-Install Motorola drivers.
-Reboot your computer
-Install RSD Lite
-Reboot your computer
-Boot your phone into Fastboot mode
-Connect your phone to your computer using a high-quality (preferably OEM) cable.
-Let your PC install any necessary drivers. When it finishes it should tell you that the device "Fastboot Edison S" is ready for use.
-Turn your phone off, disconnect the cable
-Reboot your computer
-Boot your phone back into Fastboot mode
-Wait a couple seconds then connect your phone to your computer
-Wait a couple more seconds, then look at the bottom text that's displayed on your phone. It should say
This means that your phone is connected to your computer.
-Open up RSD Lite
-Wait a couple seconds. At the top of the list should be your phone (under model it should say "Fastboot Edison S")
-If you've done all this and everything has worked out for you, flash the fxz! Make sure to follow the instructions in the noob thread as specifically as possible
Gr8mobiPro said:
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
This seems to be happening more lately. it IS a driver issue of some sort, that is for sure. I would just use one of the scripts, or moto-fastboot manually. they do the same thing as rsd but through command line either with your own typing, or a .bat script.
This may also work better in linux, so you can try downloading a live cd/usb of ubuntu and seeing if it is recognized. no need for drives with linux, just download one of the scripts that includes the moto-fastboot utility. Let me know if you need more help.
same issue
i am having the same issue with my at&t atrix 2. it is soft bricked due to an upgrade from gb to jbleak. ap fastboot flash mode (s) oa.65 battery ok ok to program connect usb data cable same message i have installed different motorola usb driver versions. i have also soldered the 4 pin to the 1 red+5v factory usb cable
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE6DkvEZi41YPAYKVPqH_AlA4f4cQ
but still my pc says unable to recognize usb device. i dnt what to do any more. im in mexico and purchasing a new phone is very expensive i need help is there something any one can do i am sure my device is not completely bricked i just cant get the mofokin pc to recognize the mofokin phone in fastboot

[Q] Nexus 5 does is dead???

I installed latest CM rom and unfortunately xposed framework on top.
after that my device does not start and seems to stack in CM logo for ever.
I can get to recovery but does not find any backup files! Seems like scdard is empty or not recognizable.
I tried to push a new rom for with adb from fastboot but my pc does not seems to find the phone. Like adb debugging is not enabled on the phone.
I also fails when I try to erase the device from recovery.
Any help is welcome.
Boot in fastboot and flash a factory image. Best way to fix pretty much anything.
mortenmhp said:
Boot in fastboot and flash a factory image. Best way to fix pretty much anything.
Click to expand...
Click to collapse
does for find the device any more, so i cannot flash anything
Try to reinstall the universal drivers, and try different usb ports on your computer.
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
You need to make sure you're in the bootloader.
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
Hi, your phone is ok, just empty. the problem is on the computer. You need to fix the driver for nexus 5. You probably have them installed since you unlocked the phone. just keep your phone connected and on recovery mode.
go to device manager, look for nexus 5. Choose "update driver"
"Browse my computer for driver...,
"let me pick from a list of device drivers"
choose any ADB driver, and install it.
Many more ways to do it
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
If it can boot to the bootloader, and it still cant find the device, the problem is either with your computer(driver) or with the usb hardware on the phone(highly unlikely since it happened after you messed with software)
mortenmhp said:
If it can boot to the bootloader, and it still cant find the device, the problem is either with your computer(driver) or with the usb hardware on the phone(highly unlikely since it happened after you messed with software)
Click to expand...
Click to collapse
problem solved.
i tried the exact same process on my imac and worked perfectly!
( i had already reinstalled the drivers on my pc with no luck...)
sprkrt said:
problem solved.
i tried the exact same process on my imac and worked perfectly!
( i had already reinstalled the drivers on my pc with no luck...)
Click to expand...
Click to collapse
He he this deserves a headline
Apple recovered my nexus from death lmao
Glad that you worked it out.
Sent from my Nexus 5 using Tapatalk

[Q] Urgent! Stuck at bootloader but cant do anything

Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Same here. Any help for us would be great. Thanks.
shd128 said:
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Click to expand...
Click to collapse
kijp15 said:
Same here. Any help for us would be great. Thanks.
Click to expand...
Click to collapse
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
smit.sanghavi said:
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
Click to expand...
Click to collapse
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
kijp15 said:
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
Click to expand...
Click to collapse
I disabled USB debugging. Rebooted to bootloader. Fired up 'fastboot devices' on cmd and could see my phone. This tells me that I do not need USB debugging on fastboot.
If you see an unknown device in Device Manager while in fastboot then use Universal Naked Driver to install the drivers. But since you don't, you'll need another PC to do this stuff. Once drivers are installed, you can do a 'fastboot reboot recovery' to get into recovery and fix the the problems. The first thing I advice is to flash a touch recovery. The rest is up to you.
Flash back the original soju firmware back onto your device by first using "nexus s root toolkit v.1.8.2 by wugfresh". It may take a little of your time downloading the roms and installing the drivers but trust me it should be working and your phone will boot into stock android 4.1.2. You can then root your device and install custom recovery as normal. Anything do pm me :laugh: ps, click the bricked option one the software is loaded up and remember to connect your device only and remove other phones from your computer

[Help] Google Nexus 5 might be bricked

Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html
doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow
Did you install those libraries properly?
Freshly baked from my Nexus 5
This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.

Stuck on logo screen

I have a rooted Sm-g610f and I flashed twrp using the app, and I'm kinda stuck now. when I start up the device the logo screen appears and it just stays like that until the battery runs out, I cant access recovery, I cant flash a new rom because usb debugging is off and which means the device wont get detected on odin i can ONLY access download mode. I would really appreciate any kind of help
Celverboy said:
I have a rooted Sm-g610f and I flashed twrp using the app, and I'm kinda stuck now. when I start up the device the logo screen appears and it just stays like that until the battery runs out, I cant access recovery, I cant flash a new rom because usb debugging is off and which means the device wont get detected on odin i can ONLY access download mode. I would really appreciate any kind of help
Click to expand...
Click to collapse
Just because USB debugging is off doesn't mean Odin won't detect your phone. One of the biggest reasons Odin may not detect your phone is that you don't have Samsung's developer drivers, so make sure you look and install those.
ShaDisNX255 said:
Just because USB debugging is off doesn't mean Odin won't detect your phone. One of the biggest reasons Odin may not detect your phone is that you don't have Samsung's developer drivers, so make sure you look and install those.
Click to expand...
Click to collapse
I actually do have the drivers installed
Celverboy said:
I actually do have the drivers installed
Click to expand...
Click to collapse
Try a different port or cable too. Also, make sure you opened odin as admin and you opened it before plugging in the device. Worth a try...

Categories

Resources