Database Users

Failed TWRP causing phone glitches?!?!?

I need help!
I tried to put TWRP on my Galaxy S4 using Flashify. I just followed the instructions and it downloaded the .img file. I then pressed flash and it flashed fine. Then it said reboot so i rebooted it. It came up with the "Samsung Custom" with the unlocked padlock like it normally does, but then it changed to a screen that said there was an error with the kernel and that i needed to connect the phone to my computer and run some Android recovery. I took the battery out and then rebooted into the page where you go to flash a custom OS. (Tried to go to recovery mode, wrong button combo). I then hit cancel and suprisingly, it booted up just fine. Kinda. After i unlocked the lock screen, I noticed that most of the apps are gone, system and downloaded. I also was bombarded with "Unfortunately, ________ has stopped." Messages. Most of the apps that are left work, except for messaging for some reason. I am writing this thread from the phone, actually. The Internet works fine, except that some apps i reinstalled via APK don't want to connect to the internet. Phone, contacts, internet, and camera still work. I know i am a noob and i shouldnt have tried to do this without help or more research. I will encolse screen shots of my phones specs if needed. If anyone reading this could just point me in the right direction, i would be extremely grateful. I can post any extra information and answer any questions you may have. Sorry for being a noob but i dont know where else to ask and i cant find any similar threads. Thank you in advance!

I assume you might have one of the models with a locked bootloader?

GDReaper said:
I assume you might have one of the models with a locked bootloader?
Click to expand...
Click to collapse
I belive i do but how do i find that out?

shannyholtz67 said:
I belive i do but how do i find that out?
Click to expand...
Click to collapse
Verizon and AT&T are the only ones as far as I know.

GDReaper said:
Verizon and AT&T are the only ones as far as I know.
Click to expand...
Click to collapse
I have Verizon :crying: . Is there anything i can do to fix my problem?

shannyholtz67 said:
I have Verizon :crying: . Is there anything i can do to fix my problem?
Click to expand...
Click to collapse
At this point you can only flash a stock rom.
Or somehow get recovery to work and then flash a custom rom. Safetrap recovery might work.

GDReaper said:
At this point you can only flash a stock rom.
Or somehow get recovery to work and then flash a custom rom. Safetrap recovery might work.
Click to expand...
Click to collapse
Ok thank you for your help. I am due for an upgrade anyway so i will just go to the S7.

[HELP] HTC One M9+ Update Android M Stuck On 25%

i need help for my htc one m9+ it seem that i can't update the latest firmware for my device, when ever i finish download the update through OTA and click install it reboot and start to install the new firmware but it stuck after it reach 25% then there's a red mark with a tringle showing on the screen, after a few minutes it freezes it reboot it self back to normal/old firmware. i've done it so many times but nothing changed. i even delete some of my data and there's 12gb left available space. still not work
what should i do to fix this problem? can somebody help me please. i've done some research but i can't find the solution yet.
P/S: sorry for my bad english

handasan10 said:
i need help for my htc one m9+ it seem that i can't update the latest firmware for my device, when ever i finish download the update through OTA and click install it reboot and start to install the new firmware but it stuck after it reach 25% then there's a red mark with a tringle showing on the screen, after a few minutes it freezes it reboot it self back to normal/old firmware. i've done it so many times but nothing changed. i even delete some of my data and there's 12gb left available space. still not work
what should i do to fix this problem? can somebody help me please. i've done some research but i can't find the solution yet.
P/S: sorry for my bad english
Click to expand...
Click to collapse
Friend, say please:
1. You phone ROOTed?
2. Recovery you phone stock or custom?
3. You phone S-ON or S-OFF ?
4. Bootloader you phone LOCKED?
Unroot your phone, flash back to stock recovery, relock it, change CID if possible, reflash stock android rom.
Follow this thread: http://forum.xda-developers.com/one-...allow-t3480444
p.s.
Please forgive my English, too, but that's not the point, is not it?

cowax said:
Friend, say please:
1. You phone ROOTed?
2. Recovery you phone stock or custom?
3. You phone S-ON or S-OFF ?
4. Bootloader you phone LOCKED?
Unroot your phone, flash back to stock recovery, relock it, change CID if possible, reflash stock android rom.
Follow this thread: http://forum.xda-developers.com/one-...allow-t3480444
p.s.
Please forgive my English, too, but that's not the point, is not it?
Click to expand...
Click to collapse
hi thanks for your response
1. not ROOTED
2. Stock Recovery
3. S-On
4. Locked
can you tell me whats is the problem?

handasan10 said:
hi thanks for your response
1. not ROOTED
2. Stock Recovery
3. S-On
4. Locked
can you tell me whats is the problem?
Click to expand...
Click to collapse
1. Recovery version matches the version of the firmware?
2. The phone was be rooted before?
3. You can show printscreen from fastboot mode?

I have the same problem whole updating the bug fix ota update.Check your root integrity in recovery mode..its failing for me..showing that file modified and removed...its unrooted and i didnt made any modification..somebody pls advise

Find the screeshot

I have the same problem =/
I downloaded that update 2.30.401.1 from my htc one m9 plus, but when it started the instalation, after the progress 25% appeared a red triangle with exclamation, then restarted after some time without to finish the update. Someone does knows whats hapening?

We have the same problem i've never modified this phone.I try to update 3 times but no luck.
After 25% freeze then automatically reboot itself.

Htc m9+
Facing the same issue.....tried factory reset but error after 25%...

Anyone know a solution to this problem,Just post it here we need it badly.:crying:
Thanks

Bricked My HTC One M9+ Chinese model
Hey guy can anyone help out. Maybe a custom rom or RUU. I cant find anything online for the HTC One M9 plus. I was on this site with custom roms that were said to be for the HTC One M9 Plus but turned out to be for the HTC One M9 now my phone is bricked. Any help would be great!!!

Same issue (m9+)
OTA update freezes at 25% even after factory reset. can't find an official rom online. phone is messed up now with stock phone app (dial pad and people)not working and quick setting are no longer customizable; just large toggle icons. also extreme battery saving mode is gone along with other features. phone is stock, never been modified.
Not rooted
stock recovery
locked
S-ON
can anyone help? please?

Hi did updated my phone to marshmallow bit after that I'm getting a new update that improve camera and security whenever I try to install it gets stuck at 25% then reboot
My m9+ camera sucks no good stabilization and colors are inaccurate
Sent from my HTC_M9pw using XDA-Developers mobile app
---------- Post added at 08:59 AM ---------- Previous post was at 08:58 AM ----------
Sent from my HTC_M9pw using XDA-Developers mobile app

I think it is something to do with mobicore.
New update has some New additional security.
Somewhere in system/app/mcregistry.
But sorry I don't have the solution.
If you guys can find out.

I think there is something wrong with the HTC update file itself. I took my mobile to the local authorized workshop and they tried several times but also without any luck. One of their brilliant staff said it might be the board!!.

That is also what i think. Htc update file itself have an issues or broken that need to be checked and re-compile.
Any update???

Maged.ali said:
OTA update freezes at 25% even after factory reset. can't find an official rom online. phone is messed up now with stock phone app (dial pad and people)not working and quick setting are no longer customizable; just large toggle icons. also extreme battery saving mode is gone along with other features. phone is stock, never been modified.
Not rooted
stock recovery
locked
S-ON
can anyone help? please?
Click to expand...
Click to collapse
I have the same problem, after trying to update, i lost dialer and people app both close unexpectantly. After that i factory restarted, but still have the problem.
Did you ever find a fix?

Is there any solution for that issue please guys we need help here ... Its been long time and theres no update

Any update for this issue?

Encryption unsuccessful

Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.

laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...

Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse

laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...

I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse

laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.

dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.

v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.

5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....

Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.

v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)

just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.

laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...

5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)

laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...

Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!

fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks

wifi not working on android p

I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work

TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk

Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...

Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.

crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.

jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue

Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).

tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!

rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked

Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.

Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?

1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since

jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference

Edited. We are all just trying to help others. Lets keep it that way.

so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips

jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...

rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.

jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob

note 3 not booting - pls help

[email protected]
thx for taking a look on my Problem
3month old note 3 no root, stock Rom, 3months no Problems,
was last week outside and i guess i was low on battery it was off as i had it in Hand
was loading all the evening and the battery is fully green
it starts, i can see mi logo, it changes to Android with loading dots at the Bottom and then it goes off
tried several times
fastboot is available
and main menu with reboot/wipe data/connect with mi assistant
i already tried:
wipe data - finished with ok (all my data gone) but still same issue
connect with mi assistant - no connecttion to Software
someone any ideas - thanks for any help
greetz

Since you already lost your data, try to flash the ROM again. I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked), if you can at least dirty install it as an update it may work too (google it). Unfortunately, providing more information over unlocking the phone is inappropriate.

GreatApo said:
try to flash the ROM again.
Click to expand...
Click to collapse
How?
GreatApo said:
I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked)
Click to expand...
Click to collapse
yes it locked
GreatApo said:
Unfortunately, providing more information over unlocking the phone is inappropriate.
Click to expand...
Click to collapse
can u pm me please?
u are the onle one who relied to my post
thanks in advance

Since your bootloader is locked, your options are limited.
To expand a little what i mentioned, your best try it may be to try and update the current from from the stock recovery. That may fix a potential corrupted partition. To do so, you can follow the steps of method 2 in this article. However, I am not aware if you can transfer the update.zip in the phone... I suppose that the stock recovery doesn't mount the phone to the PC. Thus, you probably need to try and transfer if through fastboot but that may not be possible too (could check if adb push works or if you can boot a twrp recovery, not flash just boot, but you probably wont be able)...
If you can't do the above steps, you are in a half-brick mode right now with a locked bootloader. Generally, there is no official way to get around this.