Database Info

lgp500h screen messed up

My screen responds to touch but if you touch the top item in a menu it picks the bottom item, I can't type anything because it never gets the right letters. I updated the firmware and it did not fix it. Now I can't log onto my wifi or google account because I can't correctly type my password. Any idea how to fix this?

leah7471 said:
My screen responds to touch but if you touch the top item in a menu it picks the bottom item, I can't type anything because it never gets the right letters. I updated the firmware and it did not fix it. Now I can't log onto my wifi or google account because I can't correctly type my password. Any idea how to fix this?
Click to expand...
Click to collapse
Try doing a factory reset separately. (since you would say that updating the firmware factory resets the phone)
PRESS THANKS IF I HELPED YOU!!
PHONE : LG P500
ROM : BYTECODE'S PA 2.52
KERNEL : DJNOXD 2.5.6
RECOVERY : TWRP 2.2.2.1

[Q] Need help with FRP Lock PLEASE read me.

.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Odin Mode
Download Speed: Fast
Product name: SM-N920T
Current Binary: Custom
System Status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warrenty Void: 1
AP Swrev: B:2 K:0 S:0
=========
Custom Binary (Recovery) BLOCKED by FAP Lock
.
Click to expand...
Click to collapse
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.

Thibor69 said:
.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Click to expand...
Click to collapse
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)

.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
josezr said:
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
Click to expand...
Click to collapse

Thibor69 said:
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
Click to expand...
Click to collapse
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE

josezr said:
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
Click to expand...
Click to collapse
Thank you so much my friend. I will try it and report back.
Cheers

Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.

I just rebooted with the developer options turned off on Friday. I was on ph1 firmware. Saw joeyv (spelling?) Deodexed stock rom with an option for an Odin installation. Did the installation through Odin and was back to stock. Odin flashed the kernel and tarp combo and was back up and running with root. No information was lost. For anyone else having this problem.
Sent from my SM-G935T using Tapatalk

Thank you JohnMonsour for taking the time to write all that. I will save it for future use if needed. BUT ... thanks to Josezr I got it fixed.
I was able to boot into download mode like I stated, but I just needed the correct firm to flash. They all failed until I tried
N920TUVS4DPH2_N920TTMB4DPH2_TMB.zip ( Thank you Josezr ).
I just flashed that file and Odin completed and phone rebooted to OS. So ALL IS GOOD. My only question now is ... inside the developer
options section ( in settings ) I have turned Developer options back ON but ... all the options that can be set ON or OFF are in the OFF
position and I am not sure which should be turned on. Can anyone please give me a quick run down on how they should be set .. like this:
stay awake on
next ones set to,
on
off
off
off
on
off
ect............
=======================
Debugging
=======================
on
on
off
ect........
=======================
Networking
=======================
on
off
off
ect........
It would sure help me. Thanks again to all 3 of you guys for helping.
Cheers

This is crazy I just ran into my phone becoming locked yesterday. T mobile sent me a update and my phone of course was set to auto update and my phone would do nothing it was a FRP LOCK. All I did was download odin and used this site to walk me through it all files are provided thanks to [ROM] [STOCK] N920TUVU3DPG1 | 6.0.1 | Deodexed | KNOX Free | 7.22.2016 by jovy23. At the bottum of the page is the download and also instruction to use odin. This was a life saver. LINK/ http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270. Copy and past everything you need to do to get out of a FRP Lock situation is in this tutorial. Thanks again Jovy23.

JohnMonsour said:
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
Click to expand...
Click to collapse
its so much wrong with this write up its not funny...for one his model number is sm-n920t second if he is in frp lock then he cant turn his phone off, i tried this method it doesnt work period

you can't turn your phone off?
Yeah actually you can hard reset it and then enter download mode....
Hold volume down the home button and power for like 10 seconds then when the screen turns black you quickly hold volume down, home, and power......
You might not be able to turn it off but you can still enter recovery and download mode.
You might not be able to get into recovery depending on how screwed up your phone is.
And kies3 version was the only one that would work with the above method, now kies has checks in place that checks your knox status and if you've tripped knox it won't work. I can rewrite the guide and link the proper kies if it's really necessary. But this is from 2016 so I am sure that I don't need a proper rewrite.
And at this point I'm pretty sure it might not even matter what version of kies is used it probably does all checks server-side. So this method is obsolete for an almost obsolete phone.
Sorry I didn't help you.

J327P And J727P Reboot Only After Unlock or Update FIX 100%

J327P And J727P Reboot Only After Unlock or Update
SOLUTION FOR MODEL J327P
1- FLASH COMBINATION https://androidfilehost.com/?fid=5862345805528056035
2- OPEN KEYBOARD NUMBER (IME) Y MARK *#33725327#
3- "MAKE BACKUP"
4- IN THE 3 LITTLE POINTS PRESS "BACK"
5- PRESS "EFS CLEAR & RESTORE"
6- REBOOT
7- FLASH FULL STOCK ROM
See the VIDEO
https://www.youtube.com/watch?v=jiJPn5XEIHg&t=29s

step 2 not working not appear after insert code
as well as after some seconds still phone restart with combination as well

Worked with me 100%.Thank you!

Thanks also worked for me.
THanks Again

still getting invalid sim response from phone. any ideas?

Nothing happens after I enter *#33725327# or ##33725327# on stock firmware. Guess you need to flash combi first.

Fingerprint sensor disabled

Hi,
Around three weeks ago, my fingerprint sensor suddenly stopped working and it disappeared from the settings.
It seems to be software and not hardware since if I do a factory reset it works again.
The problem is that it has happened three times since then and every time I have to do a factory reset. It's really annoying so I'm trying to find durable solutions.
My model is a FRD-L06
I'm on EMUI 5.0.4 and Android 7.0
By the way I tried to upgrade to EMUI 8 to fix the problem but it never worked (no update found with HiSuite, bad checksum following the answer bellow and error while updating using firmware finder and dns installation)
Sorry I didn't find the thread where I got this answer (it is on this website) but here a copy/past:
If anyone has the EU FDR-L09 and is stuck in Nougat version C432B416, not getting the latest oreo b562 update,here is the easiest method to get it,unlocked bootloader not required; First install the Firmware Finder app for Huawei on your Honor 8 from Play Store.Open the app, and press on your model number,you will see a list with firmwares.Press on the fifth one,the first one you see that has 4 lines of text,its latest oreo.Now press Check Firmware Access if it says you are approved proceed.Press the In-app Proxy option.It will ask to set a Proxy so long press your Wifi network ,press edit settings,show advanced option change Proxy server to Manual and set hostname to localhost and port to 8080.Now go to the OTA updater app of your phone and search for updates,it will appear!..Now press on the three dots in the top right corner and press Download Full Package.So wait for the update to install.When its finished and your phone reboots you will notice that you are stuck in a screen where only the nav bar flashes and you cant do anything.Dont worry,power off your phone.Now press and hold Volume up and power button.I let go the buttons 1-2 secs after honor logo appears(long enough).Now you are in recovery so wipe data.When phone reboots the phone will be functioning but missing a lot of apps.Sideload any keyboard apk to your phone (you dont have one)with a pc ,locate it in the file manager and install it.Now connect to your wifi network open the OTA updater and search for updates...it detects one and you install it.When everything is finished you’ll have a fully functioning oreo with all apps
Click to expand...
Click to collapse
Anyone has an idea ?
(I'm open to install custom ROM but I'm a total noob (never did it)) and really like EMUI
Thanks !

Stock-S7 freezes on startup after Oreo-update (full wipe, different stock ROMs)

Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp

philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.

Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...

philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.

cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089

philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.

Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!