Related
Hi,
my Nexus 4 is stuck in a boot loop since 2 days. I found it turned off and assumed it crashed (has done that once or twice before), but after turning it on it's gets stuck on the boot up screen. I've tried restarting it numerous times, left it on the boot screen for hours - nothing.
I can access the recovery mode and according to most things I've found while searching the internet for a solution a "wipe data/factory reset" would hopefully do the trick, but the thing is... I haven't backed up my device in ages. (Stupid, I know.) I'm travelling and took a lot of pictures that I would hate to loose.
Is there any way to save them? I don't care for app data or anything else.
I wouldn't mind rooting it (was thinking about doing that anyway), but I'm pretty much a n00b when it comes to Android, haven't done more with it than simply using it.
I have read up quite a bit about rooting in the last two days (here on the forum and everywhere else) but I'm still not sure how exactly to do it, since all methods seem to require unlocking the bootloader and therefore deleting my photos (or just don't give much in the way of explanation).
I'm using a mac, but if necessary I also have Windows installed. I have installed Adb and fastboot following this guide.
The phone is not rooted, I don't have developer options or USB debugging enabled and it's running on 4.4.4.
I would be really grateful for help.
If you can boot into the bootloader you can install a custom recovery, I'd recommend twrp. Then booting into the custom recovery you could use adb to pull files off your device . But your bootloader needs to be unlocked. If it isn't I'm afraid you won't be able to get your photos
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
bootloop issue
A.
Try to go into safe mode and backup your data.
Boot into Safe Mode:
1. Press/Hold Power button until power menu shows up
2. Tap/Hold Power off option
3. Choose OK to reboot in safe mode
B.
For bootloop problem:
Boot into Stock Recovery
1. Power+VolUp while booting to enter recovery
2. You can release buttons after you see Google on screen
(Note: Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power)
3. Android fallen down screen - VolUp to toggle recovery menu
Now wipe Cache & Dalvik Cache in recovery and reboot the phone.
C.
If the (Option B) does not solved then try to flash the stock rom with the below given mentioned steps.
First download any stock rom and also the related usb drivers. Install the drivers into the PC.
Boot into the bootloader.
Open (fastboot.exe) Cmd prompt as admin. Put the stock rom into that particular folder.
fastboot flash bootloader filename.img
reboot the phone and return back to the bootloader.
Then, we will flash all other partitions.
fastboot flash radio filename.img
Again reboot the phone and go back into the bootloader
fastboot flash boot filename.
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
If you want to relock the bootloader of your device after flashing the device, put the device back in fastboot mode. Then type in the following command in the Terminal or Command Window you had opened earlier -:
fastboot oem lock
This will re-lock the bootloader of your Nexus device, restoring your warranty and putting the device back to complete stock.
I hope this helps you out.
Thank you, but is there a way to boot into safe mode if the phone isn't turned on? I can not get to the power menu since I can't turn the phone on...
I can only access the recovery menu.
Data backup
Alternate method you can do is that you have to download a software by name 'DROID EXPLORER' - (try to google it) you will find this software from the internet. Then install the software on your PC or Laptop. Once you open the software it will take some time to download the sdk files from the internet then install the windows sdk files also.
Later you go into the recovery mode with the usb cable connected to your PC. Then open the Droid Explorer software you will see your phone connected picture. Now double click and open it go to sdcard and copy all your pictures and other files to your system.
Finally, Once you backed up all your files now you can reflash with the proper rom from the recovery mode. From directly inserting the rom.zip file into the sdcard and run the custom rom after you wipe the partitions properly in recovery.
Note: Before wiping the partitions always unmount the system, data, cache and then wipe it.
Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Haphim said:
Okay, to start with, I've read the other threads about this. I understand the process that *should* work:
1. Power off.
2. Then, press and hold both all Volume Down + Power buttons at the same time until the LG Logo is being displayed on your LG V20.
3. Now, release the keys and press the above combination again however, this time you should wait until recovery mode menu is displayed.
...and I've tried the version where you keep holding the Volume Down button the entire time.
So, yes, I've reached the white screen where it asks you if you want to do a factory reset. I've hit "Yes" to both questions. The problem is that it really does a factory reset then.
---
After unlocking the bootloader, I installed TWRP via fastboot:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
...everything went fine.
But I can't get into recovery. And since I'm waiting to have TWRP working so that I can flash root, I can't boot into recovery via an app.
What did I do wrong?
EDIT:
Okay, it looks like TWRP isn't working properly. I tried "adb reboot recovery" and that got me to a dead Android icon and a "No command" message. I have no idea why TWRP isn't working.
Click to expand...
Click to collapse
to confirm, have you verified you are using the correct TWRP version for your V20?
in this step "fastboot flash recovery twrp.img" is your twrp image that you saved, named twrp.img? If its not, that command won't work correctly.
usually after I flash recovery, when still in the recovery menu, i choose reboot recovery just to make sure it did stick. If it reboots back to itself, then try rebooting the device, and again confirm with manually entering recovery. Maybe overkill but it works for me LOL.
Good luck!
I am in need of big help! I made a critical error after days of trying to navigate the minefields of rooting my device. I have a LG V20 h910 and it is no one-click wonder root. It made me work for it and I finally got it. I loaded LineageOS 14.1 and all was good until the USB OTG cable from my PS4 controller did not register anymore. Damn, that was a let down, and probably led to my careless move of needing to downgrade my TWRP, saw the version I needed, forgot these are device specific, and now I'm stuck in a hard place.
Perhaps the fix is easy, but I have not found the answer after many, many searches...
I had TWRP 3.2.1-2 and needed to downgrade to 3.2.1-0 to try SuperRom (hoping it would have OTG ability). I hastily grabbed the first TWRP 3.2.1-0, threw it on the SD card, wiped everything except internal storage, and flashed the img, and did a reboot. Road block went up.
I tried getting back into recovery, did the PWR and DOWN pressing combo and got the Factory Reset screen, but after clicking "Yes" to both, instead of getting the TWRP screen, I got this error screen (attached).
I tried another idea - hooked it up USB to my PC and tried accessing it via adb/fastboot. I tried multiple drivers for my device, but no adb and no fastboot devices were ever found. The only thing that almost worked was booting phone into FASTBOOT mode by holding DOWN btn and plugging in a USB cable attached to PC. Once in FASTBOOT mode, My PC at least saw the ID for fastboot device. I tried to flash TWRP via fastboot, and it looked like it would happen, but in the end there was no phone screen response to my attempt, and the cmd window on my PC would get stuck and just hang.
Can someone please advise me on how I can fix this problem?
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.
I post this because none of the guides on the internet worked for my phone, and I had to cut my own way through the jungle. Maybe, this helps someone out there. I have found it extremely difficult to flash LineageOS on my LG G5 (H850). It seems that LG changes that device every now and then, and the installation guides on the internet do not fit any more. Flashing Cyanogen on my Samsung S2 was a cakewalk compared to this.
Here is how I - finally - managed to flash LineageOS: I will explain it as a modification to LineageOs.org‘s installation-wiki for the LG-H850 (wiki.lineageos.org/devices/h850/install) and for Linux.
Firstly, I had difficulties with fastboot. It does not work just to download adb and fastboot. You have to properly install them so that you can run them from any directory. Installation guides are all over the net. Fastboot can only be used when you are in the bootloader. That means you have to run „adb reboot bootloader“ first. Other than adb, you have to run fastboot as administrator (i.e. sudo fastboot devices). You will probably forget adding „sudo“ every now and then.
Trying to tackle my fastboot problems I installed the entire Android SDK; I do not know if that is a requirements. People discuss driver problems; fastboot seems to use other drivers than adb. However, from what I can tell the core-issue is to run fastboot as administrator.
Secondly, rebooting into recovery is also extremely tricky. Entering recovery worked for me by pressing volume down + power and releasing only power for a blink of an eye once the LG logo appears. Most instructions tell you that you will enter a fully-fledged recovery menu. My phone presented me a menu which only offered factory data reset. That you have to do although one hesitates to reset the phone.
However, this will only bring you into the TWRP recovery when you earlier have taken the correct exit after flashing TWRP. You should not have left the bootloader by entering „sudo fastboot reboot“, which will simply restart your phone and you have to shut it down again after it has rebooted. If you enter recovery and do the factory data reset then, the phone will not go into TWRP recovery but simply do a factory reset, and you can start from the scratch.
Instead of rebooting, I had to end the bootloader by disconnecting the battery. When I went into recovery by using the above button-combination and did the factory reset, that lead me into the TWRP recovery menu.
Another lesson I have learned is not to use the system update but to run updates manually through TWRP recovery. The system update does not work properly, and the phone will keep booting into recovery. Another flaw well documented all over the net. And don‘t forget that you have to become a developer and to enable debugging again before you can use adb to manually access recovery...
Several months back I encountered the error "E:[liblp]Logical partition metadata has invalid geometry magic signature." when trying to apply updates. I've been unable to apply updates since that time, which has concerned me.
Yesterday I noticed the release notes for a multiple month old release of Lineage Recovery stated the "Logical partition metadata has invalid geometry magic signature." error had been fixed. It made reference to returning to stock to upgrade.
Last evening I downloaded the stock rom for this device and installed it using ODIN. All is well.
I would like to put both LineageOS and Lineage Recovery back on the device. Unfortunately, I can't enter Fastboot. When I use either the key combinations or "adb reboot bootloader" I see the text "Entering Fastboot..." on the display of the device, but nothing more. I've let the device sit for about five minutes without any change. It's definitely not in fastboot because "fastboot devices" shows nothing. "adb devices" shows the device when it's in recovery, I just can't enter fastboot.
Has anyone seen this problem? I've tried wiping cache and system using the Samsung Recovery (which overwrote LineageOS Recovery when I installed the stock rom) without any improvement.
Thanks,
Bob
I've got the same issue. Anyone can help here.?
You are NOT supposed to ever use adb reboot fastboot. EVER! Always use ODIN mode.
If I remember correctly, do Samsung devices even have fastboot?
They don't but Samsung added a what's basically a dummy version of fastboot that does nothing.
Try using the key combowith the tablet connected to your PC. That got me in recovery mode and from there you should be able to go into fastboot.
The whole point is not to use fastboot LMAO, because fastboot on modern Sammy devices is just a dummy version.