Database Develop

[Q] HTC Hero looping on the boot screen. How can this be fixed?

Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.

grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.

You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.

grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.

You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!

Get titanium backup FTW.
BANG! from my shooter...

[Q] only boots into recovery

ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.

If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.

drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.

I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.

I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...

drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.

Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.

http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.

Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.

drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.

actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless

Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.

drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.

Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.

oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.

Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again

Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app

I'd try another baseband.

[Q] Moving from CM11 back to Stock or Otherwise

Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.

Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.

simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.

If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.

Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse

no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app

[Q] Brick after every CM Update.

I don't know if I'm missing some vital step but I've successfully bricked my phone consistently when manually updating my CM12.1 nightly.
I try to update to the latest nightly once a week, and for the past couple weeks it ends up bricking the device, causing me to go through unbricking procedure and return to stock, then root and all that other fun ****. That being said I have the whole unbricking down to a science, but that doesn't change the fact that it is getting more and more annoying each and every time I have to do this.
It's not that the ROM I'm flashing is bad, It works perfectly fine if I do a clean flash, but when it comes down to updating it completely ****s the phone. To make it worse, thanks to my phones locked bootloader my recovery method is using safestrap, which of course gets wiped when the phone fails the update, leaving me with fastboot as my lord and savior.
I simply don't understand the issue, I'm willing to adapt to doing a clean flash every time I have to update, but I'd at the very least like to know why the hell it does this, to me it makes little to no sense.
I'm using a stock kernel, and no weird init.d scripts that could cause it to boot funny.
On another note, slightly irrelevant, but if someone could tell me how (if possible at all) I could skip the foreplay of flashing back to stock and just flash a ROM through fastboot, it'd be greatly appreciated.

Are you using some kind of built-in update mechanism in CM 12.1 or just flashing the updates through safestrap? If it is the former, maybe it is messing with the safestrap files in some way, maybe even removing them; they do reside in the /system partition, after all. If you are running it on one of the numbered slots, maybe it is mounting the actual /system partition during some part of the update process and doing something it shouldn't on this phone.

Maybe you should create a rom slot and use it for cm. That way your phone won't be bricked...only that rom slot might get messed up if at all.
I guess safestrap is getting messed up and therefore you have to go back to stock. How are you flashing cm nightly? Are you using install option in safestrap or some other way?

problems when going back to stock rom (lineage 17.1 working fine)

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.