Hello everyone.
My friend has a Samsung Galaxy J5 (2016):
- Her phone is currently in a boot loop
- I've tried a soft reset
- "wipe cache partition", no luck.
- OEM Unlocking was OFF, bootloader locked
- USB debugging was OFF
- no root, no TWRP/CWM installed
Now it's a hand warmer with SAMSUNG blinking on it...
We just want the data (documents, photos) from the internal storage.
Any hope?
What happened for it to bootloop?
If you want to backup restart the phone in fastboot and use command
adb pull (directoryhere)
I would have
adb pull /sdcard/
Depending on your rom or phone it changes
Related
As the title suggests, after installing Kit Kat (OTA) and waiting for the device to finish the process, my Nexus 4 is now stuck on the Nexus splash screen. Have let it sit for 20+ minutes now and it will not go any further.
Some assistance is welcome
Thank you
By the way, the phone is completely stock; no root/locked boot loader...and the OTA was pushed to me, not sidel oaded.
Same problem...
Reboot into recovery and wipe cache. (Hold VOL - and Power), in Recovery, (hold Power first then VOL +) to enable the menu.
Be careful with the factory reset option, which in this case will wipe your entire device.
You can also use the adb sideload feature to sideload the OTA package manaully that might fix it. You can download them here with insrtuctions on how to flash: http://forum.xda-developers.com/showthread.php?t=2145848. You might need adb drivers to have your device recognize, http://developer.android.com/sdk/win-usb.html
eksasol said:
Reboot into recovery and wipe cache. (Hold VOL - and Power), in Recovery, (hold Power first then VOL +) to enable the menu.
Be careful with the factory reset option, which in this case will wipe your entire device.
You can also use the adb sideload feature to sideload the OTA package manaully that might fix it. You can download them here with insrtuctions on how to flash: http://forum.xda-developers.com/showthread.php?t=2145848. You might need adb drivers to have your device recognize, http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Clearing Cache did not work...Will have to try other options.
same problem too
I have the same problem too... but now it´s even worse because (after touching all the recovery menu) my N4 gets stuck in the Google screen, and it cannot conect to my PC (but it does charge the phone when connected to the computer)
Any help please!!??? I´m completely lost
thank you
luiiinho said:
I have the same problem too... but now it´s even worse because (after touching all the recovery menu) my N4 gets stuck in the Google screen, and it cannot conect to my PC (but it does charge the phone when connected to the computer)
Any help please!!??? I´m completely lost
thank you
Click to expand...
Click to collapse
Download the OTA package and follow the Scenario #1 steps from here to flash the OTA manually: http://forum.xda-developers.com/showthread.php?t=2145848
If after that and wiping data in recovery the phone won't work, then you need to do a factory reset in recovery (you will lose all your data).
After factory reset, if it still don't work you need to manually flash the factory image. See the guide links in my signature.
Same case, nothing works
Hello I've LG G2 D802 32gb edition, it's stock and rooted(without recovery).
I was using this app called "Disable service By WangQi, I re-enabled all Bluetooth services that I had disable earlier, rebooted the phone and it has struck on infinite restart mode ever since.
I barely get time to enter my password and it restarts 2 secs later. It restarts even in safe mode.
How do I backup all user data(photo ,videos, etc) ?
Can I temporarily flash custom recovery and save all my user data via USB MASS STORAGE option (if there any) And then Factory Reset the device?
I've latest 4.4 Kit Kat from LG.
TL;DR , My D802 keeps restarting (not bootlooping IMO) after showing home screen for 2-3 secs, I want to retain my user data before performing a Factory reset, Can I pull my files using ADB from /sdcard/ ?
Thanks!
I dont think its possible to flash a custom recovery in this case, all i can think of is go into stock recovery and use adb sideload and try to pull your data... Once you enter to stock recovery on the first reboot its going to be factory resetted (caution)
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
After messing up a rom flash somehow (phone was stuck on a gray screen after logo), I used the stock recovery factory reset function, but after doing so my phone is stuck in an 'erase loop'. The phone alternates between the "Erasing..." screen (with the little droid) and the "Bootloader Unlocked" screen.
I can enter the main menu for recovery mode, but if I try to go into the actual recovery mode (where you can wipe and install from sd/adb) the loop starts up again. I haven't seen this issue mentioned many other places, but the one forum I did find (for a different phone) just said to wait it out (20+ hours).
I was wondering if anyone else had ever encountered this, or if anyone had any suggestions for me.
TCZaro said:
After messing up a rom flash somehow (phone was stuck on a gray screen after logo), I used the stock recovery factory reset function, but after doing so my phone is stuck in an 'erase loop'. The phone alternates between the "Erasing..." screen (with the little droid) and the "Bootloader Unlocked" screen.
I can enter the main menu for recovery mode, but if I try to go into the actual recovery mode (where you can wipe and install from sd/adb) the loop starts up again. I haven't seen this issue mentioned many other places, but the one forum I did find (for a different phone) just said to wait it out (20+ hours).
I was wondering if anyone else had ever encountered this, or if anyone had any suggestions for me.
Click to expand...
Click to collapse
Try flashing TWRP recovery image using fastboot. I presume you have bootloader unlock otherwise you wouldn't ended up in this mess in first place.
First reboot your phone into the bootloader (POWER+VOL-) from here you can connect your phone to PC and issue fastboot commands.
Code:
fastboot flash recovery /path/to/TWRP.img
After that don't reboot the phone , just select from the already present bootloader the Recovery option... And from there try to factory reset !
If that doesn't work, and the phone doesn't boot (bootloops), you might have the /system partition messed up. At this stage get your hand on the latest Stock Firmware for your phone and flash all the system chunks (no data will be lost, but might need to wipe cache after if you get too many Force Closed)
That is for sure if you want to have stock, you could also try and flash using TWRP a custom ROM, that by itself will restore your system partition ( wipe system before flashing to be sure, by going into wipe -> Advanced -> tick System and the two Cache options and Wipe)
Hope I was clear, ask if you need more step-through details!
Thank you very much, flashing TWRP worked!
Hi,
I'm stuck in a boot loop of my OnePlus 5 (A5000, product name msm8998 - msm UFS) with stock rom. Also stock recovery and bootloader locked, secure boot: yes
Already tried:
- Button combos (Volume up/down while starting, forced restart (vol up+power))
- In Stock Recovery Mode i can sideload. Tried to sideload latest OTA from OP5 website, success, restart, still bootloop (adb devices only shows device in sideload mode)
- Fastboot mode does not list device (adb)
- Tried to wipe cache / reset system settings
The sad thing is that I can see my folders / data if "install from internal storage" is chosen, so I know it's still present.
Any hints?
Is there any possibility to get my data off the phone with OnePlus stock recovery and/or sideload? (adb pull throws "error: closed")
Thank you all for helping!
No ideas? That seems bad news for me as all data will be lost in that case.
Anybody got some hints where you could point me to find additional ways I could try?