[help] g360f blocked. Recover data... - Samsung Galaxy Core Prime Questions & Answers

hi at all. I'm new user.
I need your help.
I have an g360f blocked to start screen (samsung logo).
- the smartphone is not recognized on pc (mtp driver installation failed. w7 OS), but the device respond to adb sideload mode (client started on the phone via official recovery)
- Kies don't recognized the smartphone
- I have access to official recovery and odin mode;
i'd like to backup the data on the phone...
Can you help me ?
thks
I downloaded official 5.02 firmware (.tar.md5 format) but via adb sideload failed the sign...

peddu_peddu said:
- the smartphone is not recognized on pc (mtp driver installation failed. w7 OS), but the device respond to adb sideload mode (client started on the phone via official recovery)
- Kies don't recognized the smartphone
- I have access to official recovery and odin mode;
Click to expand...
Click to collapse
If your can use adb to connect your phone, use this command to backup your camera roll folder to PC before flashing a ROM.
adb pull /storage/emulated/0/DCIM c:/Users/(YourCompterUsernameHere)/Pictures

Related

Team win recovery project mounting issues

As teh title says i am using v2.5.0.0 of this recovery rom for my samsung s4 device.
The issue is that i cannot mount my SD card whilst in recovery mode.
It never appears on my windows 8 machine when i connect my device in recovery mode.
I have all the usb drivers for my device installed and that is how i originally put a rom on it when i was running a stock rom.
Now that i did a wipe i obviously cannot mount my device on a normal running stock rom because its removed and i am trying to install a new one.
How can i access and transfer files whilst in recovery mode?
Do i need any additional drivers?
Still cant mount. i notice ond evide manager it says the drivers are missing for SAMSUNG_Android yet i have installed samsung kais!
jonneymendoza said:
As teh title says i am using v2.5.0.0 of this recovery rom for my samsung s4 device.
The issue is that i cannot mount my SD card whilst in recovery mode.
It never appears on my windows 8 machine when i connect my device in recovery mode.
I have all the usb drivers for my device installed and that is how i originally put a rom on it when i was running a stock rom.
Now that i did a wipe i obviously cannot mount my device on a normal running stock rom because its removed and i am trying to install a new one.
How can i access and transfer files whilst in recovery mode?
Do i need any additional drivers?
Click to expand...
Click to collapse
Uninstall KIES and any other samsung usb installed utilities first.
Then download the official Samsung USB drivers for windows here: http://developer.samsung.com/board/download.do?bdId=0000000700&attachId=0000000001
After all the uninstalls are done reboot computer and install the official samsung usb drivers.
Once that's done reboot computer one more time and then your phone should and will
recognize your phone unless you have a bad cable or a non-functioning usb port in computer.
Good luck!

note 4 not detected by pc

Hi everybody,
I formatted my note 4 using twrp and since my phone bootloops. When I connect it via USB, my pc doesn't detect it at all especially Odin (my phone is in download mode). Other devices like my S6 are normally recognised.
I only have access to recovery and download modes.
I tried to reinstall drivers in my pc but nothing changes.
Help please.
did you deleted some apps/bloatware if yes please restore this app called : MtpApplication , this can be the reason your pc cannot recognize your device.
I think you may formated system partition.so just download custom rom and flashi it via recovery

SM-A500FU can't be detected by a PC, booting into recovery boots the system.

Hello,
I have installed a custom rom (Marshmallow) for my SM-A500FU through the adb. Now when I want to install a different rom I have to either boot into TWRP and I can't do that because booting into recovery simply restarts a phone, or I have to boot into Download mode and install it with the adb. The problem is that when the system is running, the phone simply charges, no Windows notifications or devices appear and when the phone is in Download mode Windows detects that a device is plugged in but can't recognize it. I have all the adb drivers, KIES and all that so it's not a problem. Can I somehow boot into TWRP or make Windows recognize my phone so I can use adb?
Thanks.
before installing a rom, have you wiped system, cache, dalvik and data? If yes try with a hard reset and if it doesn't work, too flash stock firmware
Hey,
yes, I wiped everything, I have flashed many roms earlier and I believe I have flashed it properly. I have managed to get into TWRP so I can actually flash FWs. I have only updated my rom to the newest CW13 build there is for my A5. Is there any way to flash a stock FW (for example a XEO KitKat) without ODIN? I can only use ADB through TCPIP and TWRP, so there is no way for me to flash it through ODIN.
Thanks.
so, if you press power+home+vol- it doesn't reboot in download mode, right?
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
whzq said:
It does boot into the Download mode. The problem is that when I plug the phone into my PC in Download mode it says that the USB Device is not recognized in Windows with 'A request for the USB device descriptor failed' error. When I plug it in when the phone is booted normally into android, it just charges, Windows doesn't see it at all.
Click to expand...
Click to collapse
Well, you can't flash samsung firmwares with twrp. Try flashing another rom through twrp
Alright, I have tried to flash multiple ROMs. Currently sitting on a Lollipop. Nothing changed, though. On every single ROM the problem still persists. It's not a problem with the PC as I've tried to connect my A5 to a laptop with freshly installed Windows and KIES and it behaved the same way as on my PC. The cable is fine as well, I have tested it with my old SGS3, it worked just fine on both my PC and laptop. Frankly, I have no idea what to do next, I'm starting to think that the port is physically broken. It's weird though, as I can still charge my phone and there is a response when the phone is in Download mode, just that Windows can't recognize it.
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
zyxw-androidiani said:
Try with adb command "adb reboot recovery" if it doesn't work you can downlaod odin mobile from play store and flash stock firmware!
Do you have odin for windows ?
Click to expand...
Click to collapse
Yes, ihlf his device can boot he can use mobile odin. Have you tried with other PCs, just to see it isn't a problem of your pc?
In my experience usb device descriptor errors are related to the specific PC the error occurs on due to device driver conflicts, but if you get the same error on another pc then it could be the hardware.
I'd certainly be trying another cable first on a fresh PC.
Anyway regardless of all that you can flash the stock firmware with FLASHFIRE available on play as long as you have root.
Sent from my SM-T280 using XDA-Developers mobile app

[HELP] Soft bricked smartphone

Hi everyone,
For some stupid reason a reset the file system i now I'm stuck in the LG logo.
1. I can enter in download mode - in Device manager the PC recognized as LGE AndroidNet USB Serial Port (41)
2. I can enter in recovery mode (Cyanogenmod recovery, which is very based) - in Device manager the PC recognized as Android ADB Interface
So far, so good. BUT. I'tried to flash the phone with LG FlashTool 2014 and i'm stuck at 2%. Ok, i was tried the fix with FixedDownloadcmode.bat, but when nothing is uploading on the phone (which by ADB is recognized as sideload when i'm in recovery mode and apply the ADB connection). I tried to push by ADB but nothing is uploading - error: protocol.......
LGUP recognized my phone as unknown, so this method is not working now.
Via ADB i can't send even TWRP recovery, which is so much flexible than cyanogenmod recovery.
I will be thankful for any help from your side.
Thank you in advance!
https://forum.xda-developers.com/lg-g2/general/alternative-fix-lg-flashtool-stuck-2-t3605753
Same happened to me. Try this if you can reach your storage
https://forum.xda-developers.com/showthread.php?t=2663369
https://www.youtube.com/watch?v=Lg693AYgoTo
ATT 4.4.2 KitKat:
https://mega.nz/#!n0RTUYZD!MVntiPxuyW...
ATT 4.2.2 JellyBean:
https://mega.nz/#!e5RERS4L!FjZyopcvwM...
T-Mobile 4.2.2 JellyBean:
https://mega.nz/#!qsRSBDwD!KKCETp41O1...
Modified DLL file if nothing else works:
https://mega.nz/#!f5xTGKrC!ifBCOAnK4j...
I had a very similar problem with it getting stuck at the logo after pushing supersu to the phone. I followed Supersport every single step of the way in his video. I think his links are the only valid ones online now, so just download them and reflash your phone. If your G2 is anything like mine, drivers will never appear to be installed correctly and it never restarts, only shuts down.
His method is:
1) Download and install LG drivers on PC
2) Download and install the flash tool and patch it
3) Download and load the .tot and .dll files into the flash tool
4) Enter download mode on G2 by holding volume up while connecting USB
5) Switch G2 Com port to 41 in device manager
6) Once Flash tool shows that all ports are ready, power down G2 and disconnect
7) Hold volume up and reconnect to get back into download mode
8) LG Flash tool starts flashing
9) Complete
Note: If your G2 was screwed up as bad as mine, it'll say failed but all the main system files will load to the device before it restarts and it'll even shut itself off while doing it's installation on first reboot. Mine somehow was still revived from this state with his method.
I forgot to add this but couldn't edit my post for some reason.
For D800:
Master archive of 5 files needed to do this:
https://www.androidfilehost.com/?fid=95747613655047114

s8 exynos stuck in Factory Binary, can't connect to adb "unauthorized", nor ODIN

s8 exynos stuck in Factory Binary, can't connect to adb "unauthorized", nor ODIN
Bought an S8 Exynos, tried to change my carrier with the Factory Binary. After installing Factory Binary via odin I now can not get odin to connect to the phone gets stuck at "SetupConnection". Trying to use adb says "unauthorized device" no matter how many times I start and kill adb server...
Is there any way to unbrick this phone now?
PS:
~ I can only get the phone to go to the FACTORY BINARY screens AND stock recovery screen.
~ Tried both modded and unmodded 3.13.1 ODIN
.
supak111 said:
Bought an S8 Exynos, tried to change my carrier with the Factory Binary. After installing Factory Binary via odin I now can not get odin to connect to the phone gets stuck at "SetupConnection". Trying to use adb says "unauthorized device" no matter how many times I start and kill adb server...
Is there any way to unbrick this phone now?
PS:
~ I can only get the phone to go to the FACTORY BINARY screens AND stock recovery screen.
~ Tried both modded and unmodded 3.13.1 ODIN
.
Click to expand...
Click to collapse
Try these of :
https://forum.xda-developers.com/ga...ning-to-ota-oreo-beta-3-t3920885/post79593856
Thank for the reply, I've tried all of these suggestions with odin still "SetupConnection"
1. Keep using Odin 3.13.1
2.Failng at setup connection :.some.things to try
- make sure you have latest Samsung drivers for your PC.
- if you have smart switch uninstall it as it can cause issues. It may be worth while to try using smart switch to see if that will update your phone.
- connect directly to a USB 2 port ( not a USB 3 or any USB hubs) on your PC.
- try a different usb lead ( data )
- try booting into download mode,restart and go straight back into download mode again then connect to PC.
- run Odin in administrator mode on PC.
- try a different PC.

Categories

Resources