Hello Guys! . I've got an issue on my hands, and I'm not really sure how can I solve it. I installed a new ROM, through TWRP recovery. After flashing, I tried to access the recovery, but the the phone started to bootloop, and sometimes it showed a greenish welcome screen. After a few bootloops, the phone started normally, entering the system. So, no recovery on it. Right now, after I tried to access the recovery a few times, the phone is blocked on bootloop . No access to files, no access to system, and no access to recovery also. Can you please advise what can I do furthermore?
Also, very important to mention is that the computer doesn;t seem to see the phone, I tried to another PC, the same thing. It says (in both computer cases) " USB device not recognised".
Is there any way to force somehow fastboot mode on the phone? ...
I really need some helping ideas, since I'm out....
Thank you!
Related
Hi,
yesterday I got d802 phone to fix it. First the phone was stuck at LG screen with certification error which I fixed. Phone was recognized by PC and i installed twrp on phone. I tried everything (i guess) and now phone is stuck at LG screen and it doesnt move. Now i cannot go back to twrp recovery but i can get to download mode but phone isn't recognized by pc so i cannot flash kdz file to phone. I'm really stuck at this point. Is this real hard brick or is there any way to fix it? Any ideas what should i do or something i can try?
I tried to plug phone in other computers and it's the same thing. My laptop recognized that something is plugged in once but it didn't know what was it so by now. Somehow from time to time phone doesn't go to download mode but it goes in hardware key control mode.
Hope someone can help...
So far i manged to get to recovery mode but adb sideload isn't working. I tried to wipe everything and that didn't help. As we speak factory reset is in progress but I think it's stuck on formatting cache. I hope I'll be able to get the phone recognized in download mode. Any suggestions are appreciated
I have made some progress. ADB is working now and i pushed cyanogenmod and on installation it says that it cannot mount data and cache. I think that main problem is that phone isn't rooted and now I'm trying to root phone via adb. If someone knows anyway to do this that would be great
I have an issue I'm hoping someone can help me with. I'll try to keep it brief.
I rooted my phone, successfully, but in the process the phone app mysteriously disappeared, not sure why. I download the stock apk's from 'theandroidsoul.com/download-lg-v20-stock-apps/, and dropped the phone app into the system app directory, set the permissions, and rebooted. Yes, I know that was probably pretty stupid to try.
Anyway, I can't access the UI as the constant, endless crash caused by com.android.phone. Phone OS is done, so I attempted to get into recovery, re-flash, no big deal.
In previous LG phones, to access recovery via the hardware buttons, you had to go through a menu that made it appear your phone would be factory reset, but wouldn't, and bring you to TWRP after selecting 'yes'. Except with the V20, it actually does reset your phone. USB debugging, disabled now!!
So I can't find out how the hell to access recovery from the hardware, USB debugging is disabled so I can't adb push recovery files, can't access UI, and every fastboot command I run returns 'remote:unknown command', probably due to the USB debugging authorization being revoked.
I know I got myself into this mess, I tinkered too much, and I realize it was an amateur move.
My question is, how can I get out of this? Can't use LG flashtool as I don't have relevant .dll. Can't access recovery (so far; I've tried 50x). Can anyone help? Do I just need to wait for LG to release TOT / KDZ files?
One clarification - when I select the option to factory reset via the hardware button menu - TWRP actually performs the wipe. So its on there. It just resets it and reboots. I can't get into TWRP!
Im having the same problem. "encryption unsuccessful" on white screen. dont know what to do or where to go from here.
All we need is the .dll file for the V20 so we can flash the TOT with the LGUP tool. Until then I think we're out of luck.
Bricked stuck on white encryption error corruption
Messed up. Bricked lg v20 h18. Hopefully someone can help us.
HI was wondering if you could help me fix my 6P booting issue, it seems to be bricked after trying to install an android 9.0 rom
https://forum.xda-developers.com/nexus-6p/development/rom-statixos-t3832438
^ that one in particular, I think i did something wrong because right after I flashed it with TWRP it completely blacked out, and nothing comes on the screen. My computer will recognize it but can't seem to recognize its software. I have tried to put it into recovery mode with the buttons and it doesn't work, however my computer makes a noise as if I have plugged in the device. I am not quite sure what to do, could you help?
Here's what I had done, downloaded the ROM, TWRP FBE (it was supplied as a download link) and GAPPS. I went into TWRP, it required me to put in a password (I assume that this is because when my phone boots it requires a password to get into the OS and I don't know how to remove it). I put in the same password to TWRP, got in and did a complete wipe of everything, I then installed the ROM & Gapps, then rebooted the device and once I did it went black and nothing happened. I tried to reset it to the bootloader/recovery with the buttons and nothing happened... however, when I plug in and unplug the USB in my laptop its still able to tell that a device is hooked to it but doesn't recognize it. When I hold the buttons down to get into recovery my computer recognizes that its there but not that its in recovery mode while the screen is black. I can't seem to get Skipsoft toolkit or NRT to recognize it. Can someone please help me fix this? I think that this is a hard brick issue and I am trying to fix this as soon as possible. Please if its more convenient call or send me a text to communicate faster I am using hangouts 8594100253
Sounds for me like if the phone were in EDL mode. Check if its in EDL mode by reading and understanding this: https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
Hi Guys,
Today I think I bricked my phone and I would appreciate any help.
I will describe the whole situation.
So around 2019 May, I rooted my device and decided to flash a stock based,debloated custom rom. Everything work just fined including downloading mode and recovery menu. Today, I decided to try out [S7/S7 Edge][OneUI Pie][JetBlackUI] LightROM, however strangely I was not able to boot either to TWRP neither to downloading mode via key combination.
However I had install TWRP app and from there i was able to boot to recovery mode,install the new rom and try it out.
For some reason root was not enabled in the new rom, so i figured I will try to do it via TWRP however I was unable to boot, since root access is needed to boot from TWRP app + key combo still did not work.
After searching on google, I found a poprgram which can do the trick. (Recovey-Download (CMD)
With this I was able to boot to recovery mode. Now I thought, since all this mess up was started with the new roms, I decided to restore my original stock rom, which I had a back up of. It booted up first and seemed okay, but I was curious if this solved the issues with the key comb, so I tried it going downloading mode, but it only worked with the program ((Recovey-Download (CMD)), and I saw that it is probably not gonna be good, since it only had the blue screen, but no data in the upper left corner.
Then I restarted the device and now it say " Custom binary blocked by FRP lock". and turns off itself.
I saw that FRP lock could be solved easly with Odin fresh install, problem is I have no idea how to go downloading mode. ( Assuming at this point I still can).
Sorry for the long essay but i think the more detail the easier to diagnose. Also, thank you for reading.
I would greatly appreciate any help.
BR
Csaba
Managed to solve it with USB JIG.
Is your phone an Exynos/Snapdragon variant?
csesztes said:
Managed to solve it with USB JIG.
Click to expand...
Click to collapse
Hey, how did you manage to get your phone into dl mode with an USB jig? I want to try this out, but you're the only one here who's confirmed that you were able to do this on an S7 Edge.
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.