Database Users

lg g2 bricked

hello, i just tried to flash cloudyg2 3.3 and i have bricked my d802 16gb. i had stock lp and had rooted and installed twrp did the wipes (no internal), got the right lp bootstack and used the right settings, so i really dont know what went wrong.
the symptom is that lg logo show for a fraction of a second and then a washed out gray on top of screen that fades away slowly. also while connected in pc it reads like many many drives.
on the bright side i can enter recovery/download modes. in my original attempt i used the bumbed sign, on my tries to fix it i also used the loki one, same deal.
seems like i have no recovery file, i thought i did it with one of the programs i installed, but since i am newbie seems like i misunderstood. so no recovery file
any help?

solution found:
1.Download the latest TWRP from blastagator here.
2.Flash it with your current recovery, reboot into that new recovery.
3.Download SRKG2 rom (by somboons) here.
4.This rom is a full stock rom with some debloat and custom camera. Wipe /system/ /cache/ /dalvik-cache/ /data/ and flash it (choose any options, it's not important since you'll be only installing this rom because it also upgrades other partitions to a lollipop supported version.
5.Boot into the rom and reboot into recovery again. (If you are unable to boot or the boot is taking too long like 10 minutes, shut down, go to recovery again and perform a factory reset, the one that makes you type 'yes' in the keyboard and you should be fine).
6.Download CloudyG2 3.1 and wipe /system/ /cache/ /dalvik-cache/ /data/ again.
7.Flash the rom choosing the correct version of your phone (among other preferences) in the aroma installer.
8.Boot and enjoy!
i cant post link of the solution cause i am new, but many thanks to him. i still dont understand what went wrong, but my hypothesis is that i shouldnt install the lp bootloader since i was in lp anyway.
i hope it helps anyone with similar problem.
cheers

you are in qhsusb bulk 9006 souse srktool to unbrick
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
that becuase wrong bootleader u must use bump kk bootleader then reboot recovery and flash rom

Can not change lte to 3g can someone please...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-D800 using Tapatalk

[RECOVERY][TWRP]TeamWin Recovery Project for Samsung Galaxy J2 3G/SM-J200H

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
BEFORE INSTALLING THIS RECOVERY, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE​
About TWRP
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery
Current TWRP version- 3.1.1-0
Bug
Display output color.
How To Install
Via Custom Recovery
Download twrp.img from download section.
Boot into a old twrp then goto install and press on install images.
Find and select your downloaded twrp.img then click on recovery and swipe.
Now reboot recovery & enjoy
Via Rashr {Need Root for this method}
Download and install Rashr app From Play Store Or Download Rashr From Here
Download twrp.img file from download section and Put It In your Sdcard
Now Open Rashr And Grant For Root permission
Click on Recovery from storage and Select twrp.img file
then click Yes To Flash Recovery.
If You Get Sucsess then Hit Yes on the popup To Go in Recovery.
Downloads
TWRP-3.1.1-0
Thanks to
ashxy
Samankh
lzzy12
Md Naimur [email protected]Facebook
Hadi_K.t(t_t)t
[email protected]4pda.ru
[email protected]github
Device Tree- https://github.com/Parthib24/android_device_samsung_j23g

Its nice and functioning well
But it shows recovery is not seandroid enforcing
And I'm having yellow color theme instead of blue

WORKS
Thanks It works 100%

it shows recovery is not seandroid enforcing and I can't even reach twrp menu, reboots as normal.

Work!!!

Hi, I have a pre-rooted firmware J200HXXU0AIOB, but no TWRP installed. The last time I tried flashing TWRP (on a stock ROM) I bricked my device. It was stuck on the Samsung boot where the Logo is, with the message SEANDROID ENFORCING. So I flashed this pre-rooted ROM instead (J200HXXU0AIOB).
I understand there are risks that come with flashing custom roms and recoveries. But I would like to know if I flash my device, what are the steps I have to folllow in order to flash the custom recovery successfully with minimum risks of bricking the device again.
Any feedback would be much appreciated, thank you.

Download link not working

[Discussion] OTAs on Rooted Huawei/Honor phones- Confirmed

Saw many post from new users and senior members as well and most of the time there are lot of confusion on the OTA part, especially for the rooted phone. Few says it gets (I am one of them) and few says it doesn’t as rooting capabilities modifies the system boot.img and also we have unlocked bootloader so device wont get the OTAs. I have been using the Huawei/Honor phones for 2 years now and have been getting all the OTAs on rooted phone and confirmed the same many time but still there are lot of confusion and users thinks they wont get OTA on rooted phone.
Just confirming here that you will receive OTAs on rooted phone without any issues. This is 2nd update on my phone since rooted in past 2 months.
To show root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To show the update received
Note- I am not using any firmware finder or other things for this as I dont trust on FF as it messed my Honor 5C in February and I given up on it.
Instructions-
If you are rooted but then rolled back to stock recovery, just download the OTA and update.
If you are rooted with TWRP recovery, flash the stock recovery first and then download the OTA to update. (TWRP wont be able to update OTA)

That’s a good claim and for others/your satisfaction, I have checked it out. My honor 6x was already on B371 but it was having problem of themes and FM Radio, so I decided to root it and flash twrp, after which I flashed the B360 recovery and than again twrp and installed Flashfire. I also flashed the second zip file of B360 and it gave me the solution of FM radio and themes problem.
When I checked for updates there was the same B371 but after successful download it didn’t install due to the TWRP recovery.
Now the problem is what to do with the OTA update if you can’t flash it, I have also tried the Flashfire way of flashing because Flashfire automatically detects the OTA but it gives a warning that modified partitions may cause failed installation. Therefore I haven’t tried to flash the OTA.
So the question again here is what’s good in a OTA if you can’t flash it, yah that’s an other thing that you would know you have an OTA and you can’t flash until you go back to stock recovery.
Sent from my iPhone using Tapatalk

[ROM][LINEAGE-OS][11][UNOFFICIAL][KUNTAO]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THANKS @Astridxx
THANKS MIKE
Download:-
LINEAGE_OS_KUNTAO
Known issues:-
• CAST
Kernel_source
Changelogs :-
• initial build

my phone was stuck in bootloader mode in November and later updates. I installed 18.1 with twrp 3.4. "twrp3.4" recovery became "lineage recovery". I am writing this message with 18.1. I could not find fingerprint gestures. I did not experience video playback, mp3 playback problems.
I installed "Gapps-Android-11-sagar-12-09-2020". I like "nano gapps".

kocapomak said:
my phone was stuck in bootloader mode in November and later updates. I installed 18.1 with twrp 3.4. "twrp3.4" recovery became "lineage recovery". I am writing this message with 18.1. I could not find fingerprint gestures. I did not experience video playback, mp3 playback problems.
I installed "Gapps-Android-11-sagar-12-09-2020". I like "nano gapps".
Click to expand...
Click to collapse
Try nikgapps

kocapomak said:
my phone was stuck in bootloader mode in November and later updates. I installed 18.1 with twrp 3.4. "twrp3.4" recovery became "lineage recovery". I am writing this message with 18.1. I could not find fingerprint gestures. I did not experience video playback, mp3 playback problems.
I installed "Gapps-Android-11-sagar-12-09-2020". I like "nano gapps".
Click to expand...
Click to collapse
Settings > Kuntao Resurrected> Fp gestures

I found it now.
Settings-Kuntao Resurrected-Gestures-Fingerprint Gestures -- active
But it works sometimes, it doesn't works sometimes.

How is battery? Is it better than android 10?

What's is the new in new version of https://sourceforge.net/projects/roms5/files/lineage-18.1-20201229-UNOFFICIAL-kuntao.zip/download

I installed that rom. During the instalation I confirmed to update some los recovery. Then twrp was gone. I flashed twrp again, but every time I want to go to twrp, this los recovery comes up. I aslo couldnt flash gapps. Nickgapps are flashing, but system doesnt ask me to log into my Google account and I cant restore backup from Google cloud. Other version of gapps doesnt install as twrp says couldnt mount vendor.
The real issue for me now is dissapearing twrp.

@amdyss Uncheck the "Update Lineage Recovery" box when doing the setup. This fixes the issues of TWRP being replaced by the LOS
Recovery.
As for the gapps issue: For NikGApps you also need to flash the SetupWizard zip after the gapps one in order to get the account prompt.

I did a fresh install with uncheck - nothing happend, then I installed TWRP via adb again and installed some Pie rom. Then after setting up the rom I wanted to go to TWRP and install Magisk - and this LOS recovery still messes up normal TWRP.

Dont trust this build

simbanono said:
Dont trust this build
View attachment 5174713
Click to expand...
Click to collapse
then u make build

Look at the attachment (size of the rom) before you judge someone for making a joke.

simbanono said:
Look at the attachment (size of the rom) before you judge someone for making a joke.
Click to expand...
Click to collapse
So what?? I haven't manually put the size of ROM to be that, you will not have to trust lineageOS.

Stuck on boot animation plz help

bubka160195 said:
Stuck on boot animation plz help
Click to expand...
Click to collapse
Try the official version. It's much more up to date.
[ROM][11][OFFICIAL] LineageOS 18.1 for Lenovo P2
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com

3volution3 said:
Try the official version. It's much more up to date.
[ROM][11][OFFICIAL] LineageOS 18.1 for Lenovo P2
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
Click to expand...
Click to collapse
I agree with You.
Furthermore the update are weekly as it was the case with LineageOS 17.1 Official.
Have a look at the changelog and You will also seen that the updates are more accurate and numerous

Flashing Guide for new Poco M3 buyers in 2021

I have 2 poco m3 phones. The first 1 was bought in 2020 and there was no problems with flashing to another firmware.
The second one I bought in november 2021 and I faced many issues trying to flash. Xiaomi also use different touchscreen so custom firmware may not work.
This is what you should do if you have the newer problematic poco
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) INSTALLING RECOVERY
Use this Pitch Black Recovery. TWRP and Orange Fox doesnt work on this newer poco m3 hardware manufactured in 2021. The other recovery will just be a black screen. Extract the .img and flash using fastboot
[RECOVERY][UNOFFICIAL[joyeuse][v3.0.0] Pitch Black Recovery [07/08/2020]
/* *Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about...
forum.xda-developers.com
UPGRADING TO ANDROID 11
If you dont upgrade to Android 11, you will face issue trying to flash, such as
"Failed to mount system_root"
"Failed to mount product. No such file or directory"
Normally TWRP can mount SYSTEM without issue but TWRP / OrangeFox is not supported with this new POCO hardware
This rom works fine with Pitch Black Recovery
xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11.zip
drive.google.com
FLASHING CUSTOM FIRMWARE
After you flash, no need to reboot, just flash your custom firmware. If you reboot to the MIUI above, it will just be stuck at MIUI logo.
Don't reboot to SYSTEM yet because touchscreen doesn't work
INSTALLING TOUCHSCREEN DRIVERS
The custom firmware doesn't support the newer touchscreen model used in POCO M3. So you need to install drivers. This can be done simply by flashing kernel in recovery which has newer touchscreen driver.
Use this kernel for POCO M3 2021: https://github.com/GZR-Kernels/Optimus_Drunk_Citrus/releases
Now, everything should work fine!

Hi man, I'm new to this device, I think that I have the problematic version of poco. I successfully managed to update to miui 12 eu and then install a custom but every time I make a clean install of any rom won't let me until I flash eu first. Is there a way to not to install eu first only flash directly any custom rom? Thanks in advance