Related
Hi
I've upgraded to 2.3.3 and my camera doesnt work anymore. The screen comes black for a few seconds and then the message "Camera error. Cannot connect to camera" appears. The flashlight is also doesnt work. I have some MoDaCo firmware HTC Sense before, as I remember...
Help me to fix it, please.
Thanks
Flash newer radio.
Jack_R1 said:
Flash newer radio.
Click to expand...
Click to collapse
Could you tell me how to do it, pls? What is the last version of radio? How to check it?
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Jack_R1 said:
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Click to expand...
Click to collapse
The Baseband Version is 32.41.00.32U_5.08.00.04
What I'm thinking is could it be the problem because my Nexus had non original firmware before the GB update, and maybe I didnt make some important thing which blocking my camera now? Maybe I need to re-flash the radio with some original image? I'm totally NOOB in all these things...
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Jack_R1 said:
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Click to expand...
Click to collapse
Thanks for your advices. Just upgraded the radio to 5.12 via fastboot. The camera still not work Will try to flash to original state...
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
P0MkA said:
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
Click to expand...
Click to collapse
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
k_myk said:
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
Click to expand...
Click to collapse
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
P0MkA said:
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
Click to expand...
Click to collapse
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
k_myk said:
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
Click to expand...
Click to collapse
Yeah... backuping is a cool thing.... It is just my first experience with the Android phone... Maybe will find some kind of solution for this...
Well... Problem stays... However I've found few interesting things. As I've mentioned above, after the 2.3.3 update the camera and flashlight doesnt work enymore. But I've installed Z-DeviceTest and found that after the reboot this app (which provides the hardware test) sees the camera and flashlight! But, unfirtunately, doesnt able to test it. Moreover, if to start some torchlight widget directly after the reboot, the flashlight works!!! But it is not after the camera start... So, maybe someone will find this information useful.
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
sevensaints said:
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
Click to expand...
Click to collapse
Stupid actually. Its stay the same, not working....
found the solution!
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
You have go go back to stock ROM.....then camera Happy Trigger Finger!
yeah...
1. Go back to stock through HBOOT
2. Flash back ur fav ROM - mine-MIUI AU
pls click thanks
Hello pls where i can get P990 stock rom zip ( czech version ) in zip format... for me is better instalation.
Please answer fast
I have backup stock rom but if i flash it .... in boot screen freeze and after 5 sec restart phone
You'll first need to convert your file system to EXT3 first. CM is EXT4 and stock is EXT3. Flash this zip in recovery: http://android.modaco.com/topic/336...3-for-converting-your-device-er-back-to-ext3/
So you'll need to do this in recovery:
1. Wipe everything
2. Flash the BackToExt3 zip
3. Restore stock rom backup.
This should work.
Nice big thx this is easy and very fast
62.53 nicaoin
any idea, where to get stock rom for baltic states? Can't find my stock rom anymore..
janezzx said:
any idea, where to get stock rom for baltic states? Can't find my stock rom anymore..
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=3 has made an index for lg kdz updates.
You can flash it with UpTestEX.exe or extract with LGExtract.exe then flash img with CWM recovery.
i made one:
http://forum.xda-developers.com/showthread.php?t=1617458
trapacska said:
i made one:
http://forum.xda-developers.com/showthread.php?t=1617458
Click to expand...
Click to collapse
trapacska, you are a legend! For months I have been troubled with my CM9 flashed phone, wishing I still had video etc, and couldn't get my phone recognised by any pc i attached it to. Your zip file has fixed all my problems in about 3 minutes! Thanks a million!
erm, i'm from Malaysia, which Rom should i use?
trapacska said:
i made one:
http://forum.xda-developers.com/showthread.php?t=1617458
Click to expand...
Click to collapse
I read this post above and cant go anywhere further because the silly rules do not allow noobsters to ask noobster questions ????
heres my problem,
I have P990 that came with froyo
the thing was working perfectly apart from front camera in Skype and silly old me, not being able to ask novice questions here (because you are not allowed) somehow managed to install the cryogen 9 naively thinking that this will fix the only problem I ever had. And then the world of unstability, locked and frozen screens, freezing, restarting, random uninstaling of apps, cameras not working, video freezing, music (what music??) not available and not even starting etc started to be my daily dose of my randomly properly working p990 phone.
Is there anyone kind enough to explain how to do stock rom as per above post install on top of my big mistake .
I have an unstable, unreliable (rooted ) P990 that is currently (very randomly) running cryogen 9 , I downloaded the 2 part files from trapacska's post (thanks for thinking of us mortals), I have 2 laptops , one with windows XP , one with windows 7 64 bit, a usb cable to connect laptop to the phone and I will to do anything to return my phone to some normality .
Please take me step by step or show me links how to do it and what other programs do I need in order to make my phone work as it is supposed to work.
Please understand that I do not understand what all this bellow means, and would really appreciate if anyone could explain or point to places where these things are explained ( please omit the first point, I found how to root elsewhere):
THIS IS 100% FACTORIAL STOCK:
-you have to root
-wipe data and cache NOW NOT NEEDED(built in format /system /data /cache)
-100% factorial stock kernel included
-baseband and recovery will not be changed
-if you have bootloop, try to flash backtoext3 first
Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!
elsaphnite said:
Hello folks, I post this thread after months of research and 2 kernel flashing:
I'm having an issue with the S-pen of my galaxy note n7000: it doesn't work, but I noticed the following :
- It works perfectly after a reboot for a moment, but when I turn the screen off and then when I turn it on a moment after : no response.
- the bug started after I updated my phone from GB to ICS. Now I flashed it to JB 4.2.2 and the problem still continue.
Here's the specs (as it's written on my phone) :
Band Version : n7000XXLT3
Core Version : 3.0.31 [email protected] #1
CM Version : 10.1-20130508-Asylum-n7000
Build Number : cm_n7000-userdebug 4.2.2 JDQ39E
eng.chasmodo.20130508.06 5158 test-keys
Could somebody could give a tip on how to fix it ? I found numerous threads about "hovering spen" not working but that's not my problem. Neither a screen detection issue (well, I don't think so.)
I would really apreciate if somebody could help me with Gnote who is not a Gnote anymore
Thanks a lot for the responses !!!
Click to expand...
Click to collapse
have you tried the official stock 4.1.2 rom?
I would say even before answering above question, have you done a factory reset? (Be on a safe kernel of course)
Sent from my GT-N7000 using Tapatalk 2
yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?
elsaphnite said:
yes, when Jellybean went out, I updated my phone hoping it would ok but no amelioration
and when I installed the last rom, I changed also the kernel and following the installation instructions, I did a full wipe and a dalvik cache. It is comparable to a factory reset ?
The only tips I figured out is that it could be a process or an application running on startup that would block the spen, but I'm a noob at it. Could somebody confirm or not ?
Click to expand...
Click to collapse
i suggest you download latest firmware from sammobile.com and flash using pc odin...
Mayank Chandwani said:
i suggest you download latest firmware from sammobile.com and flash using pc odin...
Click to expand...
Click to collapse
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.
asf58967 said:
This advise is not going to help as it wont wipe the proper partitions. Dont follow that advise.
-----
Here is what you should Do. If this doesn't work, you 100% have damaged hardware and it is not a software problem.
1. Download latest philz kernel and latest prerooted and deodexed jellybean LT5 ROM in flashable zip format. Any ROM of your choice will do. Just make sure its a flashable zip or you will be stuck with no ROM and forced to flash a tar via PC Odin.
2. Flash philz from your external SD card if you don't have a stock recovery or using Mobile odin.
3. Reboot to philz touch recovery
4. Do a nandroid backup just in case
5. Wipe data system dalvik cache preload and .androidsecure
6. Flash the LT5 zip
7. Reboot to system and test spen
If it doesn't work after that it IS your hardware or the pen itself.
Click to expand...
Click to collapse
You really seem to be sure of you, cowboy!! OK I will try it as soon as I finished this message an d I'll tell you about it.
Thanks !
The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3
asf58967 said:
The theory is pretty simple... If you wipe out all traces of the past firmware, and the problem persists with new firmware, it is the hardware causing the issue.
Sent from my Samsung Galaxy SV using Tapatalk 3
Click to expand...
Click to collapse
I agree to the principle : putting the cleanest installation, it's ok for me.:good:
now, I found those data:
http://forum.xda-developers.com/showthread.php?t=2274152&highlight=lt5
http://d-h.st/users/philz_touch/?fld_id=16061#files (PhilZ-cwm6-v5.03.0)
Could somebody tell me if they're effectively compatible and if it's OK to flash those without risk ?
I can't wait to see my Spen running again !
Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?
georgekg said:
Hi!
I have exactly the same problem. I'm on a CM 12.1 and when I install it, after the first boot, Spen is working for a couple of seconds (10-20) and then suddenly stops (I presume there is something in the software that disable it). Then I reinstall CM 12.1 and same story again - it works for 10-20 seconds and then stops. Spen is working ONLY on the first run (not after every reboot).
Can it be the problem related to the kernel version?
Click to expand...
Click to collapse
When you say it stops working, does it mean it will give not response at all? I have tried spen on cm12. 1 and cm13 night owl and works on both.
Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.
georgekg said:
Unfortunately yes - no response at all. It works fine for just about 10 or 20 seconds and then stops. I thought that it may be a hardware problem (maybe capacitors were empty), but in that case Spen will not work at all. And it works only when I do a factory reset or reinstall ROM. Weird...
Yes I red many posts where users said that Spen is working with night owl ROMs but I have this problem. And still didn't found any solution.
Click to expand...
Click to collapse
Did you ever find out was happened with your spen?
Yesterday I noticed this problem on my note. I thought it could be the latest kernel i've had flashed, so I flashed another one. I rebooted, tested my spen and everything was good, so I forget about it. But today my spen is not working at all. I wiped my phone and reinstalled the same rom and it worked at first, but then stopped working forever (I flashed a kitkat rom, then a touchwiz, and it never worked again). I don't know anyone else with this phone so I cannot test if it is the spen :/
Unfotunately not. I stopped thinking about it. I tought to buy new Spen from AliExpress (not expencive solution) and try it...
Hi, guys:
I really need some help to make my LG G4 H811 work.
I flashed latest lineage-14.1-20170404-nightly-h811-signed.zip but my camera app "Keeps Stop Working". I tried other camera apps, none of them work.
I also flashed cm-13.0-20161010-NIGHTLY-h811.zip, same problem
I even flashed stock (but rooted) ROM, LG-G4-H811-20R-Stock-Debloated-Rooted, still the same problem.
I am using twrp-3.0.3-0-h811.img (the latest version for H811) and flash my phonh using ROMs from SD card.
Before I flash anything, the camera worked fine out of box.
Should I bring back stock ROM with LGUP/KDZ? However, I really need some 3rd party ROM working because I need multiple-user feature which is disabled in Stock ROM.
Any suggestion is very much appreciated.
eruisi said:
Hi, guys:
I really need some help to make my LG G4 H811 work.
I flashed latest lineage-14.1-20170404-nightly-h811-signed.zip but my camera app "Keeps Stop Working". I tried other camera apps, none of them work.
I also flashed cm-13.0-20161010-NIGHTLY-h811.zip, same problem
I even flashed stock (but rooted) ROM, LG-G4-H811-20R-Stock-Debloated-Rooted, still the same problem.
I am using twrp-3.0.3-0-h811.img (the latest version for H811) and flash my phonh using ROMs from SD card.
Before I flash anything, the camera worked fine out of box.
Should I bring back stock ROM with LGUP/KDZ? However, I really need some 3rd party ROM working because I need multiple-user feature which is disabled in Stock ROM.
Any suggestion is very much appreciated.
Click to expand...
Click to collapse
mmmm maybe its twrp.. not sure wich one i used that whenever i flash a rom it gave me errors non stope of camera.. and other stuff... you should use steadyfastx twrp not official.. its a beta..
twrp-3.1.0-0_BETA-h811_h815-steadfasterX-build1.img
only thing is missing that i know is reboot to recovery from recovery...
link here..
try installing twrp.. then flash rom and see i f you get error..if you do KDZ then install this.. and then flash rom good luck
http://forum.xda-developers.com/devdb/project/?id=16696#downloads
raptorddd said:
mmmm maybe its twrp.. not sure wich one i used that whenever i flash a rom it gave me errors non stope of camera.. and other stuff... you should use steadyfastx twrp not official.. its a beta..
twrp-3.1.0-0_BETA-h811_h815-steadfasterX-build1.img
only thing is missing that i know is reboot to recovery from recovery...
link here..
try installing twrp.. then flash rom and see i f you get error..if you do KDZ then install this.. and then flash rom good luck
http://forum.xda-developers.com/devdb/project/?id=16696#downloads
Click to expand...
Click to collapse
thank you for the kindly reply. The issue has been solved by flash Stock 20p KDZ first in download mode then flash the same LineageOS through TWRP. Not sure which step really fixed the issue though.
I do have issues of video recording for 4K and 1080p, which is OK to me for now.
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK https://www.youtube.com/watch?v=KBsWNrKNZzA
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
yeah, you are missing a step.
you have to format data partition.
check my guide on how to install roms: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, may I suggest EU/masik instead of stock, its a lot better
in #3 you can see that in the video data is also formated: https://youtu.be/KBsWNrKNZzA?t=190
of course i did this too....was also not working.
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
motorh3ad said:
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
Click to expand...
Click to collapse
Don't flash vendor, theirs no need, eu.miui has everything in the one zip file. Just to clarify have you formatted in twrp? The option where it requires you to type 'yes'? Everything gets wiped from your photos and apps all to the rom itself. Then just flash eu.miui and reboot. Works everytime for me without fail.
no i never formatted in TWRP wipe, only used the factory reset and swiped to wipe.
just did a format and flashed xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM _v11-10.zip
ITS BOOTING!!
first please let me thank you very much for this help, i was already quite desperate about nothing working except LINEAGE.
fingerprint in MIUI rom is working great, unbelievable!
can you please explain me why this FORMAT in WIPE is needed and what its used for? i was not aware and i can not find it in any of the howtos..
haha, glad it's working. Knew the problem was that you didn't format.
however since you posted on xda, I just assumed you knew format data is not the same as wiping data.
(literally, the most common beginners mistake for this phone)
it's cause of the encryption keys, when moving from MIUI to AOSP (and vice-versa) a format data partition is required.
I stated this in How To Change My ROM? I wanna Try them all!
section in the first post.
under there, FOR MIUI ROMS (since that is what you were trying to do)
you missed the 7th bullet point. (you can also text me on telegram)
(also, in the same guide, I inform people to flash their vendor first -4th bullet point- then in the 5th bullet point you wipe it.)
(this is cause often miui customs and some people are usually on a vendor that isnt there's. you have to be on your region vendor, then wipe it, then allow the miui custom's vendor to take over, else you will face fingerprint problems)
This is just another point most just don't follow.
Umm, if my guide needed anything to be included, or like... needed to be more easy to read and follow... I can edit that if you like.
(use can text me on telegram as well)
edit: just read the xiaomi.eu one, I'll edit it to make it more informative
motorh3ad said:
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
Click to expand...
Click to collapse
You're not installing stock ROMs. You are installing custom ROMs based on stock.
If you want to return to true stock grab a fastboot ROM from here and flash it with the Mi Flash Tool. After fully extracting the ROM delete the flash_all_lock.bat file before flashing. That way you cannot accidentally lock the bootloader.
Then choose the 'clean all' option in the Mi Flash Tool before you hit the flash button.
thank you.
my mistake, i didnt write clear. i just wanted to test a miui rom to see how the fingerprint is working there. im happy now with the custom rom based on stock.
but i also went for this solution you mentioned and noticed that on the https://www.xiaomiflash.com/ site only older xiaomi devices are mentioned as beeing compatible.
looks like this is not the point, so im happy to have this option too.