Phone bricked during rooting, or is it salvageable? - LG K8 Questions & Answers

I followed this guide to unlock my boot loader:
https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
All went well except when doing the last instruction of step 3, rebooting after installing rce.zip for the 2nd time.
According to the guide the device should reboot for a few minutes, and then start normally.
For me its the LG Screen for 2 seconds, and then jumps to "device corrupt etc.", directly reboots and looping this again and again.
My PC detects no USB connection to the phone at any point, the only thing I can access is the "Factory data reset" screen, but this doesn't do anything either.
Reseting is only possible by removing the accumulator.
Any chance I can restore the phone somehow ?

What is exact phone model that you have? Hm, well when you get to factory reset screen try connecting to PC via usb and see if phone is recognized on ADB or LG bridge?

https://forum.xda-developers.com/showpost.php?p=71349559&postcount=177

Yamchu said:
I followed this guide to unlock my boot loader:
https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
All went well except when doing the last instruction of step 3, rebooting after installing rce.zip for the 2nd time.
According to the guide the device should reboot for a few minutes, and then start normally.
For me its the LG Screen for 2 seconds, and then jumps to "device corrupt etc.", directly reboots and looping this again and again.
My PC detects no USB connection to the phone at any point, the only thing I can access is the "Factory data reset" screen, but this doesn't do anything either.
Reseting is only possible by removing the accumulator.
Any chance I can restore the phone somehow ?
Click to expand...
Click to collapse
yes it does: https://forum.xda-developers.com/cr...tion-android-one-hard-bricked-device-t3361988
that worked for my x240ar

Related

[Q] Help going back to stock?

Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
dav08094194 said:
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
Click to expand...
Click to collapse
The only way I could get it to work was the following; however there is one thing to try before you try my way because mine did this also - after the wipe and flash with flashtool etc. The only way I found to get out the bootloop was to do a factory restore after when its looping. So from the boot screen loop hold the power button until it goes off then on then off again.
Then do the process to get into the recovery so hold down and power then release power as soon as the lg logo appears (first one) then press it again immediately that SHOULD get ya to the grey factory reset screen. Press the power button 3 x and it should do a factory restore and boot up this time. First boot may take a minute it should eventually start up.
Failing that try this - Open the lg mobile support tool and connect the phone in download mode (volume up and power with plugged in usb on mine) then go to options and upgrade recovery. it will download a file usually about 2GB then install it, the phone will reboot at 100% on the phone and 80ish% on the lg tool it will then start into the setup feature,
DO NOT disconnect the phone until it gets to 100% and finishes. This way you shouldn't need to do an extra factory reset.
I understand for this the phone needs to be seen on com 4 (it shows on the phone screen) so if necessary go into device manager with the phone still plugged in in download mode and select com ports then select the phone com port then right click >properties> advanced and change the com port to 4. It may tell u its already being used but don't worry it is fine. Save and exit device manager.
please bare in mind these are just my experiences on MY LG D802 however its worked every single time for me without fail and ive done it a good few lol.
HTH:good:

[Q] Rotted my phone, messed up recovery install, tried to revert by OTA. HELP!

after rooting my verizon g2 with vs98011a firmware, I tried to push twrp recovery on the device, and it seemed to work.
Tried to boot in to the recovery by holding power+down, and saw the factory reset screen.
Pressed power twice, and so the android with a red caution on it.
Restarted, and decided to accept the OTA as I thought it would give me a fresh start. Big mistake.
Phone starts, shows Security boot messages at the LG splash screen, and then just goes to nothing on the screen.
What do I do?
Can't factory reset, and can't get in to download mode by holding up then inserting the USB cable.
Also when I plug the phone in to the PC when it gets to the black screen, the PC recognizes a bunch of partitions with one of them having a folder name 'images'. All other partitions are inaccessible.
http://forum.xda-developers.com/showthread.php?t=2432476 try this to get your phone up and running
jr313 said:
http://forum.xda-developers.com/showthread.php?t=2432476 try this to get your phone up and running
Click to expand...
Click to collapse
I can't in to the download mode. I inserted the usb cable while only holding the up button, but it still goes to a blank screen.
try this solution
http://forum.xda-developers.com/showthread.php?t=2432476

Help: G4 Plus won't start after accidentally hitting "Open" on icon pack install.

Help: G4 Plus won't start after accidentally hitting "Open" on icon pack install.
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Yodhrin said:
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Click to expand...
Click to collapse
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
strongst said:
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Hi, thanks for responding. After four or five attempts to boot into recovery it succeeded; wiping the cache did nothing so I did a factory reset, which worked and now the phone will boot to the setup stage. Unfortunately now I'm getting "The device was reset. To continue, sign in with a Google Account that was previously synced on this device.", which after googling seems to be a security feature - the problem is it doesn't accept the google account credentials, every time I enter them it just cycles back to the "This device was reset..." screen again.
I know I'm not getting the details wrong since I made the account specifically for the phone and have the details written down. Any suggestions on how to proceed?
EDIT: Actually nevermind, I managed to follow along with a tutorial on how to bypass it using MotoService & ADB. Thanks again for replying.

Recovery from bootloop (and other issues)

Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.
neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery Mode​Rebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD Card​You may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe Mode​This problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery Mode​When you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]​Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.
At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.
The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)

Samsung A52s 5G stuck in reboot-freeze loop

Hi, I have a Samsung Galaxy A52s 5G that goes into the following loop for two days:
boots up, waits for me to unlock the phone through the draw pattern, I unlock the phone, "Phone Starting" pops up, phone starts, I am able to navigate the phone and phone apps for something like 20 seconds and then it freezes.
Model Number: SM-A528B/DS
The firmware shown in recovery mode is the following: A528BXXS1CVI6
Why I am trying all this
This is my wife's phone. I thought she was backing up photos through google photos and she told me that she was doing it. Unfortunately, she was only uploading them on the local app and the backup was not working since her storage was full for several months. So, if there is a way to access her stuff from any Operating System please let me know. The problem, I think, is that I can't without unlocking the phone (of course).
Note
If I don't unlock the phone, the phone does not freeze but of course, I cannot do anything. Therefore, I suspect it is some thread that starts by default as soon as the phone is unlocked.
What I tried
I tried the following things:
Remove the SD/SIM card tray (just because it was easy)
I tried to boot my phone in Safe mode. I correctly entered in safe mode, the third-party apps were disabled but then the phone froze again.
I connected the phone to a laptop (running Ubuntu 22.04) and entered in recovery mode. Once in recovery mode, I tried basically all the options without any luck so far:
Reboot system now
Reboot to bootloader
Apply update from ADB:
I tried to download a firmware for my phone and then send it through ADB with the following command
`$ ./adb sideload ~/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip`
and I got stuck at
`serving: '/PATH_TO/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip' (~0%)" `
I don't know why
I did not try "Apply update from SD Card" yet
I did not try "Wipe data/factory reset" yet
I tried "Mount /system" but it got me the following error:"Error updating for slotselect"
I tried "Repair apps"
I tried "Run Graphics test"
I tried "Run Locale test"
I tried and then did "./adb reboot recovery" to test that I was able to reboot through adb and it did reboot the phone indeed.
Let me know if you have any ideas on what to try next.
Having a similar issue right here, please notify me what you did afterwards and if you managed to solve it
I am in the same situation and same try outs. Only one slight different. Phone does not start at all. Only "SAMSUNG" and "powered by android" logos. Then starts to bootloop again.
Did you find a solution?
@minidiable did you try to flash with Odin? You should have a try using CSC that avoid erasing data.
In any case, I'm coming back here to give my result after several try-outs and finally going to a Samsung Center.
My phone, entering in recovery mode, had from the begining a message at the bottom saying " E:[libfs_mgr]Error updating for slotselect ".
At Samsung Service Center they told me that this error may probably warn about motherboard failure. And after tearing down the phone and checked it, they changed the moterhboard. Sadly, All data lost. That's all.

Categories

Resources