I have Moto g4 plus and I have Indian variant but some questions are I can't even understand.
1) what is hard brick and soft brick of moto g4 plus? What is the difference?
2) in both brick of moto g4 plus there is any pc required?
1) In simple words, Soft brick is messing a little with your Android from which you can recover easily.
Hard Brick is like screwing up your device completely, yes, you can recover, but it needs lots of technical process.
Symptoms:
SoftBrick: When you turn on your phone, it is either stucked on your boot logo or you get Android Logo with an exclamation mark.
You device keep restarting from the boot logo.
Hard Brick: All your device does is showing you a black or grey screen and keeps vibrating without any display.
Sometimes all you see is the RED charging light, and nothing else on the screen.
Reason:
Soft-brick generally happens when you install a custom ROM that is either not compatible with your device, or it is corrupted. There is also a possibility you might have deleted a system file or application after rooting your phone.
Hard-brick usually happens when you mess around with system partition. Another reason can be Custom ROM making changes to your system partition while you are flashing it.
2) Yes, you must required PC for hardbrick.
I stuck into motorola logo on sky blue screen when I restore my twrp backup and then my screen is black gray ,so this is hard brick or softbrick? Because unfortunately I flash Oreo rom on 32 bit twrp and so,my phone won't turn on ,so I restore my twrp backup.
Related
When returning to stock from custom rom(cloudy g3) I accidentally bricked my g2(d802).
Every time I only get the start of the bootanimation(the lg logo) and then the screen turns black(with backlight, with sometimes there flashes a bit of the other part of the bootanimation, almost thougt it was haunted or so) and the status led flashing as usual.
I tried to restore via download mode with the lg mobile support tool and with the lg flash tool, but strangely the progress on my phone and pc didn't match (it ends with my pc still on 80% and the phone already rebooting into the same state).
Even strange is, my pc recognises the phone most of the time and thinks it has the latest software. I also can't power of the phone or perform a hard reset/reboot to recovery.
What can I do to recover my phone if still posible(I only have it for maybe a week or 2 )
[Q] D802 hard bricked after wiping & flashing TWRP, no recovery, stuck in boot loop
TL;DR: Wanted to install CM12.1, wiped everything except Internal Storage from TWRP, flashed new version of TWRP (3.0.0-0), hard bricked my D802 (stuck in LG logo, can't get into recovery mode)
ISSUE: My LG G2 is stuck in a boot loop. Only the LG logo is displayed and when I try to turn off the phone by holding down the power button, it will blank out for a few seconds and then display the LG logo again. I tried accessing recovery mode via the hardware buttons and it takes me to the factory reset screen, and after I do press the power button twice it just takes me to a blank screen. I can get the phone into download mode, although my Windows machine doesn't recognize the phone even though its drivers are installed.
I am currently trying this guide. Although I'm not sure what KDZ/TOT to download for my phone :/
All the important files on my phone like photos and contacts are stored in the cloud so I can basically reset the phone to its factory state, if it comes to that.
If someone could help me with a guide or anything that can lead me into the right steps for fixing the phone, I would be really thankful.
Purrado said:
TL;DR: Wanted to install CM12.1, wiped everything except Internal Storage from TWRP, flashed new version of TWRP (3.0.0-0), hard bricked my D802 (stuck in LG logo, can't get into recovery mode)
ISSUE: My LG G2 is stuck in a boot loop. Only the LG logo is displayed and when I try to turn off the phone by holding down the power button, it will blank out for a few seconds and then display the LG logo again. I tried accessing recovery mode via the hardware buttons and it takes me to the factory reset screen, and after I do press the power button twice it just takes me to a blank screen. I can get the phone into download mode, although my Windows machine doesn't recognize the phone even though its drivers are installed.
I am currently trying this guide. Although I'm not sure what KDZ/TOT to download for my phone :/
All the important files on my phone like photos and contacts are stored in the cloud so I can basically reset the phone to its factory state, if it comes to that.
If someone could help me with a guide or anything that can lead me into the right steps for fixing the phone, I would be really thankful.
Click to expand...
Click to collapse
Then I don't think what just happened with me is a coincidence, hmmmmmm
Does't anybody have an idea for a solution other than using KDZ? something like flashing the bootstack or recovery through PC?
---------- Post added at 06:34 PM ---------- Previous post was at 05:40 PM ----------
HHHHHHHHHHHHHHHHEY
I just got something:
So after using this tool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
I got my phone to boot to recovery, I used Unbrick to get my phone working again, now the only thing left is to get phone to actually boot to ROM
Anybody got a solution? Should I just reflash the ROM?
Update 2: I re-flashed the ROM, wiped cache and fixed permissions, still waiting for it to boot, I don't know, I think you're better off just backing up the ROM, clean install and then restore apps using TB from the nandroid backup
Final update: yup, clean flash it is
I hope this has helped
Purrado said:
TL;DR: Wanted to install CM12.1, wiped everything except Internal Storage from TWRP, flashed new version of TWRP (3.0.0-0), hard bricked my D802 (stuck in LG logo, can't get into recovery mode)
ISSUE: My LG G2 is stuck in a boot loop. Only the LG logo is displayed and when I try to turn off the phone by holding down the power button, it will blank out for a few seconds and then display the LG logo again. I tried accessing recovery mode via the hardware buttons and it takes me to the factory reset screen, and after I do press the power button twice it just takes me to a blank screen. I can get the phone into download mode, although my Windows machine doesn't recognize the phone even though its drivers are installed.
I am currently trying this guide. Although I'm not sure what KDZ/TOT to download for my phone :/
All the important files on my phone like photos and contacts are stored in the cloud so I can basically reset the phone to its factory state, if it comes to that.
If someone could help me with a guide or anything that can lead me into the right steps for fixing the phone, I would be really thankful.
Click to expand...
Click to collapse
You are goinf good mate ! follow the guide.
Hi,
I picked up a second hand XT1622 super cheap the other day. It didn't seem to want to boot at first, and stuck around on the blue Motorola logo for a while, but eventually after leaving it alone for an hour or so it sprang into action.
Trouble was I then made the mistake of downloading the December OTA update, and since rebooting from that installation it's been stuck on the blue screen again.
I thought maybe something went wrong with the OTA, and flashed the December firmware through Fastboot hoping that would resurrect it, but I'm still getting the same result.
The bootloader is locked unfortunately, and I can't boot into recovery mode either - same issue.
Does anybody have suggestions other than me breaking the phone in half (which is probably going to happen today anyway)?
Phone suddenly sprang to life, but for some reason wouldn’t let me press return after entering my PIN after prompting for it in setup - maybe it’s a hardware issue and the phone’s on its way to the great G4 graveyard in the sky?
The original G destroys this nonsense of a phone.
For and download the stock firmware, and then flash it through fastboot. After that, see if it boots. If it does, unlock the bootloader so you will have b easier time if this happens again.
Hi boys, i've done some mess on my cellphone! I flashed a preloader to root without have unlocked bootloader, now my cellphone hangs on asus screen with the following message:
Red State
Your device has failed verification and may not work properly
Your device will boot in 5s
After that, it reboots and goes to the same screen. I've tried turning it off but it won't, nor it goes to recovery screen, it keeps on booting loop on that screen.
Its a zenfone 3 max, ZC520TL.
nanhuto said:
Hi boys, i've done some mess on my cellphone! I flashed a preloader to root without have unlocked bootloader, now my cellphone hangs on asus screen with the following message:
Red State
Your device has failed verification and may not work properly
Your device will boot in 5s
After that, it reboots and goes to the same screen. I've tried turning it off but it won't, nor it goes to recovery screen, it keeps on booting loop on that screen.
Its a zenfone 3 max, ZC520TL.
Click to expand...
Click to collapse
Good day good sir,
I know the following may not be of much help, but I'm afraid you will need to return it to Asus for repairs, because:
1. Bootloader is locked (that means no flashing)
2. You can't boot into recovery (no install via adb or micro sd)
I'm sorry I wasn't able to help much, but that's all I can say after experimenting with Asus's software for a while.
Greetings,
Kevin
Hi,
I have the same issue but instead of a bootloop, I can still boot android up with my zenfone max 3 zc520tl phone but I noticed that I can't turn on my Wifi. I this issue related to Red state? How can I fix the red state error? Please, I'm in dire need of help.
I have a 2015 shield pro that was stuck in a boot loop (not sure what happened exactly, it was my dads), so I was reflashing it according to the dev guidelines after unlocking the bootloader. When i rebooted after flashing boot.img, now the green light comes on for a few seconds and goes off for a while, then comes on again after a while and off quickly. I cant get it into the bootloader by the hardware method. any other ideas or is it trash?