Related
Hello XDA,
Since I update to CM12.1 from CM11 (I didn't realised when I applied update, I would croos to CM12.1, so I did it the dirty way ^^)
So since I upadte to CM12.1, my phone started to freeze for anything I'm doing, even unlock it... I decided to clean all the mess I had in the phone, and do a clean installation of CM12.1.
My problem is simple : since I didn't formatted /system, I can't reinstall Gapps.
The recovery installed is now the cyanogen recovery and I don't know how to format /system with this recovery.
Have you any advice to do this ?
Thanks, see you on the thread !
Flash other kernel like tangerine kernel or kernel that already has custom TWRP or CWM recovery or use this kernel to wipe system and flash the kernel (Format -> Advanced format -> check cache, dalvik, system and what you want more). twrp_2.8.6.0-huashan.img
OK ! Thanks ! I'm trying it right after I right it.
I was reading about fastboot to do this. Could this command work too ?
Code:
fastboot flash system system.img
I tried to find a compatible recovery, but this is not simple since I don't know enough things about recoveries.
xdadogs said:
OK ! Thanks ! I'm trying it right after I right it.
I was reading about fastboot to do this. Could this command work too ?
Code:
fastboot flash system system.img
I tried to find a compatible recovery, but this is not simple since I don't know enough things about recoveries.
Click to expand...
Click to collapse
no need to ...install rashr app on your phone and then from it flash the twrp.img that the user above gave it to you
RASHR !!!
Thank you ! This app should be in every "Swiss army knife folder" of android user !
It ask me to flash Philz recovery. What is the best to do ? Philz recovery from Rashr, or the linked TWRP above ?
I really don't know the difference :-/
Hi !
I tried a lot of time to flash the recovery using rashr. I can't get rid of cyanogen recovery.
I installed clockworkmod's ROM manager and it tells me I have two recoveries installed. Cyanogen and TWRP. It was before I try to flash. But now it is the same.
Any advice ?
Sent from my Xperia SP using XDA Free mobile app
The finish touch
I started a new thread to terminate with rashr issues !
You can check it here : I can't flash any recovery on my phone
Phoenix854 told me to use an older version of rashr, and everything worked fine !
Good bye guys, and thank you for the help...
I am on stock rom, rooted with magisk, and I cannot seem to get this phone decrypted. Every time I try to format data in twrp, I get an error, and I get stuck in a bootloop to recovery. Is there a step(s) I am missing here? I've tried looking through the forum but all I've seen are the same instructions on formatting data.
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
jdesignz said:
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
UPDATE:
I tried to redo the process again, just to verify the process, and I am still having the same network issues. I have 3g every once in a while, but its iffy and I no longer have LTE.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Well, as long as you have done backup with twrp you have nothing to worry about.
Sent from my XT1805 using Tapatalk
L4ndon said:
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Click to expand...
Click to collapse
Doing things the right way always works! Trouble is finding that right way (heed my warning about bad info in these threads - there is a lot of it - as you found out). Just so happens I also know how to splain things to users, I've done it for something like 25+ years (yeah, I am old - make that experienced). Tethering - used to be ya add a build.prop entry to allow it, but that was many years ago and most of not all enable it by default now.
Anyways, enjoy the ride. It may be a little bumpy, but it's the bumps that keep ya awake!
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
THX for that, got stuck in recovery process (loop).
I followed your instructions, but need of stock recovery.
My Path :
Backup DATA (w/o /media/)
Manually Backup Media with TWRP to Ext.SD
FORMAT /Data (use the DATA Button in TWRP), in my case it showed Errors, i ignored it and did it once again - this time it worked.
flashed Magisk
ended up in Recovery Loop - flashed stock recov. via FASTBOOT, reboot
a rainbow lightning circle turned up, said " DELETING", device rebooted by itself.
Now the Phone boots to Android, shut it down, restart with PWR BUTOON + VOL DOWN pressed to access bootloader and flash twrp again with FASTBOOT ( fastboot flash recovery nameoftheimage.img ENTER).
Now u can restore /DATA TWRP Backup and then the manually part - in my case that worked.
THX!
//EDIT
After first boot, i noticed missing write permissions for most Apps - so i decided to Reset SELinux via TWRP, worked !
te amo hice format data con r15 y al parecer se soluciono todo son lo maximo cauros
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
still sim not showing on my device which is xt1804
Never had the problem so can't help.
T-Mobile G6 H872 11G Stock Collection
Based on OEM 11g KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
SysBoot ROMs were test flashed over 11g and 20a bootloaders. 11h has not been tested.
11G Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you Flashed SysBoot with Patched Kernel and Root, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:43dcc7f82c501147da6500efdd594d5c
SysBoot ROM - md5:2ac20008794eb74523a442da7b8bafdc
SysBoot Deodexed - md5:b92fcb7649bddf934ff9be0246c9fab6
SysBoot w/Patched Kernel + Magisk Root - md5:ae4bab194a69b2044f3aee69ba495464
FullStock ROM - md5:e919fe16852b5f0b830a48cda914003a
StockLAF - md5:ce70b36e4d293e183544a18409a526de
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
These files are long overdue. I hope you all find them helpful. Please let me know if you run into any problems with them. Thanks!
Other H872 Projects
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
H872 20D Stock Collection
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h87211g, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 11g KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-09-30
Current Beta Version: 0.9
Beta Release Date: 2018-09-30
Created 2018-09-29
Last Updated 2018-10-19
Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?
DmytroPitenko said:
Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?
Click to expand...
Click to collapse
very welcome. if you flash the bootloader only it will leave whatever laf you have untouched, and yes fingerprint scanner will work with custom ROMs like AOSP Extended.
However, I have not tested running stock 20a with the 11g bootloader. But it doesn't sound like that's what you are wanting to do
*edit*
if you have already flashed a custom Rom and FP doesn't work, simply flashing the 11g bootloader zip will fix it. it is not necessary to reflash the rom
also, not sure why anybody would want to, but 11g bootloader with stock 20a rom will not work. it will hang on the boot logo indefinitely which can be dangerous for your phone. so please make sure you are using a custom Rom or stock 11g with this bootloader
Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Sent from my XT1575 using Tapatalk
Ken C said:
Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Click to expand...
Click to collapse
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file on your sdcard and rename it to laf.bin, and run these
adb shell
su
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/laf
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf
weakNPCdotCom said:
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file in the folder with adb.exe, rename it to laf.bin, and run these
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/laf
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf
Click to expand...
Click to collapse
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk
Ken C said:
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak
weakNPCdotCom said:
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak
Click to expand...
Click to collapse
Ok. Figured it was something like that. Always meant to ask somebody, just never did
Sent from my XT1575 using Tapatalk
weakNPCdotCom said:
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
[/CENTER]
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
Click to expand...
Click to collapse
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).
ryanrod said:
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).
Click to expand...
Click to collapse
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
Awesome. Yeah, I am going to give it a flash tomorrow morning. I do not think I will need the stock recovery at this time, but thanks for offering! I have been stuck with the whole twrp on LAF issue, not being able to use LGUP, and this just a godsend to get back to 11g. Thanks again! :good:
weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.
ryanrod said:
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.
Click to expand...
Click to collapse
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.
If I were to downgrade if able to, would that have a chance? I still am getting stuck in fastboot mode unless I'm hooked up to the pic and let lgup do it's thing.
It detects the device, does it's thing, reboots it and gives me a factory reset phone back just no dl mode.
It's not bricked yet lol.
Sent from my XT1575 using Tapatalk
weakNPCdotCom said:
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.
Click to expand...
Click to collapse
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:
ryanrod said:
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:
Click to expand...
Click to collapse
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.
weakNPCdotCom said:
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.
Click to expand...
Click to collapse
Ahh yes this makes sense. Maybe it was a stock recovery repair due to magisk failure as you mentioned? I still don't understand why with these LG phones (ever since the G3 I think), when you boot into recovery using the hardware buttons, it asks if you want to factory reset the device. Then if you say yes, it doesn't reset/format anything, and it boots right into twrp recovery after that. So weird. I can boot directly into recovery just fine from a reboot app or adb from a running system without getting that factory reset screen...
I'm sure your laf zip with twrp works for the reasons you mention. Luckily I don't have to find out since my laf partition is fine and still has twrp!
Regarding bluetooth, I will give the sysboot flash a try and update you with the results. First I want to wait until my backup phone is running again. I bent the sim pins on the backup phone due to those ****ty plastic adapters that catch the pins (an old E980 w/ the larger sim size) so I ordered another sim reader to fix that. I also read in some forums that wiping cache and dalvik cache resolved others bluetooth issues with the G6. I will try that too.
Either way, I will update soon. I am happy to share my notes as I really appreciate the help!
@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk
Ken C said:
@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
Yes that's the message I get. So your saying not to worry about it for the moment? I only see it regularly on a stock rom when going into recovery not aex.
I just wanted to make sure. With the mess I been going through.
So, I can flash this stock build you have and if I wanted normal download back flash the laf zip and I'll have DL mode on laf, twrp on recovery and everything should Mount correctly and all that?
And if I go to flash something custom FP will work? I know I'm a pain I just want to "know" my setup isn't weird somehow. Probably over thinking it, but I think I'm good, except that when I rooted I was getting that message off & on, on the stock build of 20a. I'm hoping that running this build I can get that worked out. Maybe that deal is a 20a thing? Reading through the root thread it seemed to happen less to people on a lower numbered build and it would stop after the format.
I can make backups Burt I've yet to try to restore one.
Sent from my LG-H872 using Tapatalk
Hi, sorry for bad English.
I'm having trouble installing Custom ROMs on my Mi 8 Global. Any custom rom I install, after reboot on TWRP, the mobile does not start, it only stays on the fastboot screen or returns to the TWRP.
I already unlocked the bootloader, ADB ON, drivers installed on PC, TWRP OK, all neededs WIPEs ...
I can only install the STOCKs ROMs. I think the problem is when doing FLASH in the ROMs. It may be that I can only install ROM by Fastboot, but by Recovery not.
In the TWRP LOG, there is not a single error after installing the ROMs, always success.
I follow all the tutorials, but never start the system after installing by recovery.
Another thing I noticed is that when I install the custom rom, if I go in the TWRP file browser and go there in the SDCard folder, the files do not appear as it usually gets, such as the "Android" folder for example.
I've had several Androids since the Galaxy Y time and I've never had this problem.
Any idea?
format data "yes" then flash dm variety fix re oot recovery then flash any rom
Sent from my MI 8 using Tapatalk
altvolt74 said:
format data "yes" then flash dm variety fix re oot recovery then flash any rom
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I followed all the tutorials, including the WIPEs
try another dm variety or recovery ........make sure is format data and not just wipe it and last ensure ur in pie firmware and not oreo
Sent from my MI 8 using Tapatalk
altvolt74 said:
try another dm variety or recovery ........make sure is format data and not just wipe it
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
Ill try this. Thanks!
null
I have the same problem as you, and my rom is only 10gb. Other roms can't recognize it. How do you solve this problem?
not
altvolt74 said:
try another dm variety or recovery ........make sure is format data and not just wipe it and last ensure ur in pie firmware and not oreo
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
i tried ,very bad,my phone still into fastboot.
Bruno Wagner said:
Hi, sorry for bad English.
I'm having trouble installing Custom ROMs on my Mi 8 Global. Any custom rom I install, after reboot on TWRP, the mobile does not start, it only stays on the fastboot screen or returns to the TWRP.
I already unlocked the bootloader, ADB ON, drivers installed on PC, TWRP OK, all neededs WIPEs ...
I can only install the STOCKs ROMs. I think the problem is when doing FLASH in the ROMs. It may be that I can only install ROM by Fastboot, but by Recovery not.
In the TWRP LOG, there is not a single error after installing the ROMs, always success.
I follow all the tutorials, but never start the system after installing by recovery.
Another thing I noticed is that when I install the custom rom, if I go in the TWRP file browser and go there in the SDCard folder, the files do not appear as it usually gets, such as the "Android" folder for example.
I've had several Androids since the Galaxy Y time and I've never had this problem.
Any idea?
Click to expand...
Click to collapse
1. wrong section
2. which twrp do you use, which firmware do you use...., what a rom do wanna flash
unlock bootloader , flash this Twrp
reboot to trwp, factory rest with "yes" reboot again to trwp flash the rom that u want
Bruno Wagner said:
I followed all the tutorials, including the WIPEs
Click to expand...
Click to collapse
Follow this step
1. Copy Miui rom 9.0.zip and which rom you want to sdcard.
2. Boot into twrp, then wipe data, cache.
3. Install Miui rom 9.0.zip (dont reboot after done)
4. In twrp, choose reboot twrp again, then then wipe data, cache
5. Install any custom rom you want. And flash disable dm-variety
6. Done and reboot
romano19 said:
Follow this step
1. Copy Miui rom 9.0.zip and which rom you want to sdcard.
2. Boot into twrp, then wipe data, cache.
3. Install Miui rom 9.0.zip (dont reboot after done)
4. In twrp, choose reboot twrp again, then then wipe data, cache
5. Install any custom rom you want. And flash disable dm-variety
6. Done and reboot
Click to expand...
Click to collapse
I ll try this. Thank u
You have to format data via typing "yes", it is not wiping data, it is button in twrp. After that everything gonna be ok.
maybe you should flash a miui based on android pie （globe developer version）
then use the latest twrp recovery （both wzsx and black pitch is ok）
Murik01 said:
You have to format data via typing "yes", it is not wiping data, it is button in twrp. After that everything gonna be ok.
Click to expand...
Click to collapse
Yes, I do. Dont work
Bruno Wagner said:
I ll try this. Thank u
Click to expand...
Click to collapse
Did you do something or you fix your problem?
NewbyCmUser said:
Did you do something or you fix your problem?
Click to expand...
Click to collapse
No, not a tip has solved the problem. Yesterday I spent all day trying different things, searching in several sites but nothing works. I'll have to settle for the ROM stock.
I had the same problem installing pixel experience you need to flash stock fastboot rom via miflash be careful, do not select the relock option, then install twrp, wipe system, caches and data and install your custom rom It worked for me.
Murik01 said:
You have to format data via typing "yes", it is not wiping data, it is button in twrp. After that everything gonna be ok.
Click to expand...
Click to collapse
i had same problem. and this format data has worked with "miui_MI8Global_8.12.20_c7a9af8587_9.0" i can flash it. phone working now but i will change rom tomorrow again.. i guess it will be brick in a couple days
Problem solved!
Sorry bad english, translated by Google Translate ...
Now I've been able to install custom ROMs. :laugh:
I tested Havok and Pixel Experience.
I'll speak the steps I did:
1 - Install the Stock Pie: MIUI Global Stable 10.1.2.0 (dipper_global_images_V10.1.2.0.PEAMIFI_20181211.0000.00_9.0_global_0099f5af5f)
Install with XiaomiMiFlash, at the bottom, check the option "Clean All".
NO INSTALL ON TWRP MODE.
2 - Start the system normal and make ADB ON
3 - Make Root
4 - Start the system normal again
5 - Install TWRP: recovery-TWRP-3.2.2-0711-XIAOMI8-CN-wzsx150 (use this version)
6 - WIPE > Advanced> System, Data, Cache
7 - Flash ROM: PixelExperience_dipper-9.0-20190111-2226-OFFICIAL
8 - Reboot System
9 - Ready!
10 - Optional Step (*recommended*) - Go again in TWRP and Wipe > System, Data, Cache, Internal Storage > Flash ROM > Reboot.
After this procedure I was able to install custom roms without problems.
Hi,
I bought a new phone and thought I would get in to custom ROMs again. Mostly to get rid of bloatware. However, after following multiple guides I'm still no where closer to achieving my goals. The phone is a MI 9.
I found there's a lot of different steps depending on guide but most of the once I've tried does the following:
* Unlock bootloader, working
* Installing twrp via fastboot, working
* Deleting data in twrp, working
* Transfering a rom.zip file (depending on rom), working via usb cable
* Some guides recommends to install disable force Encryption via another zip file transferred from the computer, however, that seems to not be necessary, tried i few times
* Installing rom via twrp, seems to work
* In some guides you then need to remove cache, working
* Rebooting from twrp, working
After these steps I find myself in one of three different cases,
1. Phone is stuck in fastboot, have to reflash it with MIflash and global MIUI rom to get phone to work again
2. Phone in boot loop, logo shows up, phone waits for awhile, phone reboots, logo shows up
3. Phone boots up, logo is shown, phone reboots into twrp
I've also tried both XiaoMiTool and XiaoMiTool V2,
XiaoMiTool seems to write the global ROM to the phone whatever I choose (Have tried Xiaomi.eu and LineageOS 17)
XiaoMiTool V2, fails in second to last step, it wants to remove some cache before the installation in twrp is done.
Things I've not tried:
* Moving file to twrp with adb instead, should not make a difference
* Installing magisk
Now, I'm a bit afraid my phone will get hard bricked, have reinstalled the OS 20 times the last day to test different approaches and steps. Nothing seem to work. Does anyone have a proven method working in 2020?
Another way to go might be to just get rid of the commercials, run a different launcher to get app list and get rid of the bloatware. This is not really what I want but I can live with it.
As you can hear I'm about to just throw in the towel and give up. But I've heard a lot good about the xda forums so I thought it might be worth a try even though I do understand if no one has time or energy to help out a newbie.
Help please!
Edit: I do realize I've accidentally put this under Guides and not Q&A. I find no way of moving it nor deleting the thread so I guess some moderator will have to come help. Sorry for this.
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
mxxt01 said:
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
sangbuana said:
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
Click to expand...
Click to collapse
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Step 6 is to type adb push rom.zip /tmp/
I renamed the zip file to rom.zip so that I don't typo when typing.
Sent from my MI 9 using Tapatalk
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
From personal experience of using xiaomi.eu's ROM, I never did install vbmeta.img or dmverity, since that particular rom is based on the official beta Chinese MIUI ROMs, and the latest TWRP from Mauronofrio supports decryption. Not sure about other ROMs though.
Just to be safe, just download the stock fastboot ROM as a backup just in case anything goes wrong. Always remember to NOT lock your bootloader when flashing back to stock, in case your persist partition gets corrupted, you can flash it to recover.
ZevSwe said:
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Click to expand...
Click to collapse
Like written by toscha42 you should flash the latest fastboot stock rom (tgz) for your phone first, as after all the attempts you have made your phone is probably kind of ****ed up... Do not lock bootloader.
What I do and it works for me, starting from stock ROM.
1. Unlock bootloader (you already done that)
2. Flash in fastboot latest TWRP for your device (I use Mauronofrio)
3. After flashing disconnect the phone and push VOLUME UP + POWER to enter from fastboot directly to TWRP recovery
4. Format data with yes
5. Reboot to recovery
6. Flash xiaomi.eu custom rom for your device with USB OTG (usb otg is the easiest way I guess as you don't need to move the rom to internal storage)
7. Reboot to recovery
8. Wipe cache and dalvik cache
8. Reboot to system
And that's all.
Poslano z mojega MI 9 z uporabo Tapatalk
toscha42 said:
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
Click to expand...
Click to collapse
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
ZevSwe said:
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
Click to expand...
Click to collapse
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
mxxt01 said:
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
sangbuana said:
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
Click to expand...
Click to collapse
Right, well I wish to switch to another ROM so installing MIUI Global ROm will not help.
I'm able to install TWRP without touching verfiedboot at all and get it to work even after reboot so that is not a problem. If that is what verifiedboot does I believe I can skip that?
ZevSwe said:
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
Click to expand...
Click to collapse
than try once again by following my steps in post #8
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
sangbuana said:
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
That seems to have made the trick! Thanks so much!
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
thecdn said:
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
Click to expand...
Click to collapse
Since you noted that you have been doing a backup to a USB stick, it could be the USB stick is failing.
Honestly, all the installation guides for custom Roms i came across on XDA in the recent years are complete garbage. It fills like copy pasted from a guide that has been copypasted from a copypasted thread which has been copypasted and never worked.
For me, this guide works just fine. I just had to find the files for my Mi 9 instead of the k20 Pro. I would upload them for you but my upload speed is garbage.
https://www.youtube.com/watch?v=w_u_w6SrTDY&t=249s
I have flashed a lot of ROMs custom and official, fastboot and recovery. Never had any problems, the steps is here in thread.
Just remember 2 thing:
1. If you have ROM which using encryption, you must format data, because wipe will not remove encryption and you will see gibberish names
2. If you wipe system (which is mean less, because every ROM flash will do that, when you flash it, but many people insist in wiping it) then you must flash a ROM without reboot or you will stuck in fastboot and only option to repair is to flash official fastboot ROM (Non official fastboot ROMs, don't exist).