Stuck on t mobile screen - T-Mobile LG G6 Questions & Answers

I used custom rom and root. Later, due to low battery backup, I gave stock ROM flash with LGUP. But after that, the phone got stuck on the T mobile screen.
device model h872

Related

Andriod One Spice uno is not booting, only balck screen and screen blinking.

Dear friends,
yesterday i have charge mobile, after few charge mobile is LCD display blinking only, not able to boot the kitkat, only giving option for fast boot, recovery and normal boot,
i have installed CWM recovery but not able to boot in recovery mode also.
my phone is Andriod One Spice uno, now its not booting only blinking while charging.
help me for this issue, thanks
+pravin
If you have a smartphone stuck with bootloop, IMEI wiped, engineering mod not working, SP flash tools not working at any cost and many terrifying stuff. Just download the official firmware and copy all the image files in the adb/fastboot folder and flash them one by one. secro.img may not flash. You will have your phone up and running but IMEI may be invalid. So there is a thread which tells you to make "mp0b_001" file which carries IMEI and just copy-paste and restarting will do the job.

tried installing rom but now bootlooped

Hi guys,
So I had a stock T-Mobile LG G4 H811 that I had unlocked and booted into twrp version 3.1.1-1-g4. I wasn't able to actually flash recovery of this .img becuase of a write failure. So I booted into it instead and then installed it from within twrp into the recovery partition. The actual stock software was the ORIGINAL original, which I think was android 5.1.1
From there, I cleared the cache and delvik cache and installed the G4-H811-10N-xTreme-2.0 Rom. Now, I can't boot into recovery mode anymore, and all I get is the bootloop.. but it's not dead yet because it's a software issue on my part and not a hardware failure.
Any advice on how to get it to recovery mode or at least so I can boot into twrp somehow to try and get this fixed? I tried Power+Volume Down and then let go a sec and Power+Vol Down again and it won't work at all. Just goes straight to bootloop.
Thanks in advance.. I know I screwed up somewhere.. just so many loopholes, it's easy to miss.
Best,
Johnnie
Got somewhere, still broke
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
jtlefebvre said:
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
Click to expand...
Click to collapse
try using LGUP

Yu yureka black bricked

Hi... I was using custom ROM and decided to revert to stock rom. Downloaded a package from one of the forums and tried flashing it. After that mobile stuck at Yu yureka screen. It falls into bootloop. Am unable to to get into recovery mode or bootloader. Seems bootloader locked while flashing stock rom.
Only red notification light blinking while charging. While pressing volume down + power button, it shows boot into ffbm and restarts again. :crying:
Any help is appreciated.
same here. I got bricked flashing stock rom
https://youtu.be/e0N3iby0qH0?list=PL-8v_xzE8r_IedHQytxHxVRCZgY_T-p3u.
now, rebooting in logo,, can't boot in recovery.
was running aosp custom rom, previously, then i flashed lineage which corrupted IMEI. Though flashing stock rom would fix.
Now, unable to boot in recovery. So, can't fastboot or anything. Help!!!!!!!!
same issue happend to me to my 4 day old phone now crying and waiting for next day
to use qfil i think it may work
otherwise Mobile Care centre
or u may try this https://drive.google.com/uc?export=download&confirm=1R5_&id=1LTeTB69fsUYTT3MO8R5bjMihs7soFCGn
i hope it may work

Only Sony Boot Screen Flashes

while using phone yesterday it went automatically switched off and afterwards while powering on only sony logo screen comes then repate only that. tried flashing firmware with flashtool it flashes successfully but problem still here.
my bootloader locked unrooted stock rom
any way to turn it back to life.
waiting for experts suggestions.

Bricked A715F, Can't boot even after clean stock rom flash

my phone suddenly started this problem with the mic and was frozen too
last week my phone was out of battery but when i charged it up and wanted to boot it, it went on bootloop (couldn't access recovery either)
So i kinda wanted to install TWRP (which I did) and tried a new custom rom.
but now even after a clean stock rom flash using Odin, phone wont boot at all. its stuck on samsung logo to Galaxy A71 logo back and forth. any solutions? please.
Thank you
If flashing full stock isn't working, then it could be a dead motherboard

Categories

Resources