Database Develop

What rom should i use? for xt1063

I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.

abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case

reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.

abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?

reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.

abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone

reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup

abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link

im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...

abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise

I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.

abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?

reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....

heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.

Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.

ANDROID 7.0 Nougat for UMI Super, Max and Plus

Hi,
Android 7.0 is coming (rumors said this Christmas) :
link
link2

Update is alive: http://community.umidigi.com/thread-5751-1-1.html
But got many problems saving files son internal SD and the bartery is draining fast. LTE is working good.

nougat on umi plus
mafury said:
Update is alive: http://community.umidigi.com/thread-5751-1-1.html
But got many problems saving files son internal SD and the bartery is draining fast. LTE is working good.
Click to expand...
Click to collapse
my experience is very good .ive rooted the phone and flashed also adblock gps is working good internet very fast lte for the price just amazing

After Update Bootloop
After the 7.0 Update, i have an issue. If my Umi Plus is connected to my WLAN AP (with other devices no such error), it is rebooting every 10 seconds. If i turn my Access Point off, it stops rebooting itself and if i turn it on again, it is restarting after 5 seconds over and over again. My mobile carrier internet works fine, without any such errors.
I dont want to use my mobile carrier with limit, but my home wlan.
Anyone has similiar issues? If anyone knows the solution please write it

Preisschild said:
After the 7.0 Update, i have an issue. If my Umi Plus is connected to my WLAN AP (with other devices no such error), it is rebooting every 10 seconds. If i turn my Access Point off, it stops rebooting itself and if i turn it on again, it is restarting after 5 seconds over and over again. My mobile carrier internet works fine, without any such errors.
I dont want to use my mobile carrier with limit, but my home wlan.
Anyone has similiar issues? If anyone knows the solution please write it
Click to expand...
Click to collapse
Use flashtool to reflash firmware.

New UMI Super Android 7.0 beta update
New UMI Super Android 7.0 beta V7.01_20170114 update
Flashing through SP Flash Tool.
Camera, flash LED and on-screen buttons fixed!
The list of known bugs:
The camera still needs some adjustments
No standby Harlequin LED (only basic notification LED settings)
Other minor bugs
ROM link(UMi_SUPER_Android_N_beta_20170114_c239v55_kw_u1.rar):
mediafire.com/file/hpzw37aca481bvc/UMi_SUPER_Android_N_beta_20170114_c239v55_kw_u1.rar
SPFT link (SP_Flash_Tool_v5.1648.rar):
mediafire.com/file/2g6qau85a7fvnjq/SP_Flash_Tool_v5.1648.rar
Original post:
community.umidigi.com/thread-6169-1-1.html
Aditional IMPORTANT update info:
community.umidigi.com/thread-5265-1-1.html
Sorry, I can't attach links
This version should be stable with the mentioned minor bugs but please, post your feedback to check the correct performance, if there is any issue found, let us know!
Dora te quierooooooooo

So far so good. Android 7 has made a big improvement to my Super.
Does anyone know if root is possible with this beta and / or whether there's a version of TWRP that will work with it?
Thanks,
Steve

steveharman said:
So far so good. Android 7 has made a big improvement to my Super.
Does anyone know if root is possible with this beta and / or whether there's a version of TWRP that will work with it?
Thanks,
Steve
Click to expand...
Click to collapse
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.

Brilliant, thanks for that @Creedo4Life.
Can you remind my poof befuddled brain please - does flashing TWRP / recovery wipe the device? I should know this but can't remember.
Thanks again.
Steve

steveharman said:
Brilliant, thanks for that @Creedo4Life.
Can you remind my poof befuddled brain please - does flashing TWRP / recovery wipe the device? I should know this but can't remember.
Thanks again.
Steve
Click to expand...
Click to collapse
No worries. There's no need to wipe anything after you flashed Supersu in TWRP. One of the best things about Nougat 7 is that it use a different file system then Lollipop and Marshmallow, so you will never again sit and wait while the OS optimize apps (sometimes hundreds if you had a lot of apps installed!!) Just reboot after flash and you good to go. The first boot might bootloop once or twice, no need to do anything it will di everything on its own. Enjoy full root mate.

Creedo4Life said:
No worries. There's no need to wipe anything after you flashed Supersu in TWRP. One of the best things about Nougat 7 is that it use a different file system then Lollipop and Marshmallow, so you will never again sit and wait while the OS optimize apps (sometimes hundreds if you had a lot of apps installed!!) Just reboot after flash and you good to go. The first boot might bootloop once or twice, no need to do anything it will di everything on its own. Enjoy full root mate.
Click to expand...
Click to collapse
Quick question - I've only flashed recoveries using adb before, how do I point SPFlashTool at the recovery .img file?
Do I replace the recovery.img file inside the UMI ROM folder, with the TWRP .img file?
And then tick 'Recovery' inside SPFlashTool per your instructions?
Thanks,
Steve

steveharman said:
Quick question - I've only flashed recoveries using adb before, how do I point SPFlashTool at the recovery .img file?
Do I replace the recovery.img file inside the UMI ROM folder, with the TWRP .img file?
And then tick 'Recovery' inside SPFlashTool per your instructions?
Thanks,
Steve
Click to expand...
Click to collapse
That's correct, you browse the img file on the ticket recovery (the only one that should be ticked.) click on "download only" while your phone is switched off and then connect it through the usb. It will then flash TWRP and let you know when its done. Now disconnect your phone and hold in power button and volume up simultaneously. When you see the umi logo let go of the power button but keep holding volume up. When you see the TWRP logo you can let go. The first time you boot into TWRP you need to swipe the bar which will allow modifications, you will only have to do that once, the system will then remember it. Good luck and happy rooting.

Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve

steveharman said:
Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve
Click to expand...
Click to collapse
That's very odd. I used the exact same supersu myself and never encountered that problem. That version is also compatible with Nougat. Try one of the other versions on https://www.chainfire.eu/
Maybe that solves your problem.

Creedo4Life said:
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.
Click to expand...
Click to collapse
I follow this procedure but I only obtain partial root. I cannot cut and paste in the system partition even though I can run some apks that require root. Is there a way I can obtain full root?

[email protected] said:
I follow this procedure but I only obtain partial root. I cannot cut and paste in the system partition even though I can run some apks that require root. Is there a way I can obtain full root?
Click to expand...
Click to collapse
You have full root, you just don't know it.
If you want to edit anything in any system folders you need to change r, rw permissions. I use file explorer for this. Look at the attached SS to understand what I mean.

TWRP Install
Hi,
I'm on 3.02-20161121 version and my phone is rooted: may I flash Nougat via TWRP, instead of using SP Flashtool?
Thanks

pollock49 said:
Hi,
I'm on 3.02-20161121 version and my phone is rooted: may I flash Nougat via TWRP, instead of using SP Flashtool?
Thanks
Click to expand...
Click to collapse
No, you need to flash beta 2 using SPFT, there is no zip file to use with TWRP for this.
http://community.umidigi.com/thread-6169-1-1.html

steveharman said:
Thanks.
Hmm, this is odd though. I managed to get TWRP flashed but whenever I flash that SuperSU and reboot, all my apps complain and keep quitting when I try to launch them. I've been careful to wipe cache after flashing, as usual.
In fact I've rried wiping everything cache, dalvik, - even started again from an entirely factory-wiped device, including data.
Flashed a fresh copy of the Nougat beta ROM, booted up fine. Flashed TWRP, booted up fine but then I reboot to recovery, flash SuperSU and bingo - on my next reboot all the apps starts complainin that they have stopped - even Launcher.
Weird...
Steve
Click to expand...
Click to collapse
I have a similar problems. However in my case many of the apk still working include play store. Just the apks that needs internet quit working.

Creedo4Life said:
Root is possible using TWRP 3.0.2 for umi.
I've attached a zip file of the TWRP version below, unzip it and flash using SPT flashtool, you need to untick all the other boxes and just tick the recovery and direct it to where you unpacked the zip file.
I've also attached the Super su i used to root the beta 2 for the umi super. Flash it in TWRP.
Click to expand...
Click to collapse
Hello,
I have the problem that SPFT shows me 100% wehn I am flashing TWRP to the UMI Super but still hangs at 100% and does nothing more.
I'm using the Android N V7.01_20170123.
I also tried an Android scatter from Android 6 before I flashed Android 7, but it also doenst work.

[Q][HELP] OP3T Soft bricked after installing TWRP Recovery

Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance

First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.

Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0

RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?

redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance

Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0

redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro

Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide

mannulko said:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine

mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.

[STOCK] Flashable Oreo ROM H872 20A (20g Update!)

H87220a Flashable ROM for the T-Mobile LG G6
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP v3.2.1-0, 11g ROM
Based On: LG Stock ROM
Click to expand...
Click to collapse
This ROM based on H87220xxxx.kdz then extracted and repacked with autoprime's zip based on this thread.
Also, thanks for runningnak3d for TWRP install method. This ROM is ARB01 which is safe if you want revert to 11g.
Installation :
Modullar Installation
You should install at least bootloader, modem, and system in order to boot properly.
Install xxxOreo.zip using TWRP don't reboot
Press back button and Install Magisk (It's mandatory if you want root and twrp retained)
DONE and Reboot
[*]In most case, you'll lost your /data due to data encryption. so backup first
[*]This build's ONLY for T-Mobile US LG G6
[*]If you decided to downgrade, make it sure that firmware is ARB01 (11g or later)
Download :
As requested by many people I've uploaded new update within 4 modules (Bootloader, Laf, Modem, and System).
You can download here: H87220g (latest)
LGH87220F
LGH87220D
LGH87220A
Recommended TWRP/Orangefox Recovery
my G6 seems broken, it has no display but it still ringing when I call it. probably LCD issue. Basically, I can't test any future update with this phone. I've planned to buy v30 soon and try to repair my g6 by myself. Any info or some suggestions will be appreciated
Have a nice day,

OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
So, to flash this, using H872 recovery/TWRP:
1) TWRP backup whatever you want to keep.
2) Wipe all normal stuff
3) Flash this and magisk, assuming you want to root anyway.
4) Using TWRP File manager, delete /system/recovery_rom_boot.p so that if something goes wrong, you don't have to reflash H872 TWRP into recovery using laf.
Boot, and you should have the stock 8.x rooted?
In my case, I also a going to try and install stock GApps to replace LG/TMobile stuff...I'll post about my success on that later...
MW

MetroWestMA said:
OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
Click to expand...
Click to collapse
You'll get download mode back after flashing this zip anyway (stock laf). in case something bad happens, you should not worry much. though, i've never use custom rom in this phone before. so, extra precaution will be good for you.:good:

immns said:
You'll get download mode back after flashing this zip anyway (stock laf). in case something bad happens, you should not worry much. though, i've never use custom rom in this phone before. so, extra precaution will be good for you.:good:
Click to expand...
Click to collapse
Which is the correct way to do it in my opinion. Once you TWRP installed in Recovery, having it stay on LAF is dangerous as far I'm concerned. In theory TWRP should be able to keep you from needing to ever restore back to stock, but it has been known to fail sometimes. Leaving with no way of using LG UP or any other flasher outside of sending it into LG (unless firehose files get leaked).

NighthawkXL said:
Which is the correct way to do it in my opinion. Once you TWRP installed in Recovery, having it stay on LAF is dangerous as far I'm concerned. In theory TWRP should be able to keep you from needing to ever restore back to stock, but it has been known to fail sometimes. Leaving with no way of using LG UP or any other flasher outside of sending it into LG (unless firehose files get leaked).
Click to expand...
Click to collapse
yep, flashing back original laf will save you in the future mistakes.

By "Stock" do you mean LG's bloatware stuffed "stock" or do you mean "Vanilla Android" stock?
MetroWestMA said:
OK -- So I am going to install that later today...but just to be clear (and hopefully this helps others)...if you have been flashing other ROM, you should have...
1) H870 TWRP in laf, accessible for emergencies via holding up button and plugging phone into computer.
2) H872 Unofficial TWRP in recovery...
So, to flash this, using H872 recovery/TWRP:
1) TWRP backup whatever you want to keep.
2) Wipe all normal stuff
3) Flash this and magisk, assuming you want to root anyway.
4) Using TWRP File manager, delete /system/recovery_rom_boot.p so that if something goes wrong, you don't have to reflash H872 TWRP into recovery using laf.
Boot, and you should have the stock 8.x rooted?
In my case, I also a going to try and install stock GApps to replace LG/TMobile stuff...I'll post about my success on that later...
MW
Click to expand...
Click to collapse

BTW -- I did this method, got laf back to what it should be, rooted the H872 Oreo, installed GApps, and have a pretty good setup with Volte/WiFI calling, Goodle Dialer and Messages (with web message support), stock camera, etc -- kinda best of all worlds.
The only issue, as noted in another thread, is that TWRP can no longer mount data -- meaning you gotta jump through some hoops to back it up...so hopefully this get fixed.
For those that are not aware, with TWRP still in recovery, you can boot to this following the factory reset options for the phone, but after answer to confirm "Yes" twice, you will boot into recover TWRP, so you can always get back there without a laptop and / or fastboot. If I recall, the key sequence is hold down button, hold power until logo appears, then turn power on and off until factory reset appears...
But TWRP needs to be fixed to access that data partition -- no idea what that is all about.

So twrp rebooted even though I clicked cancel on reboot, magisk not installed. Is there anyway back? I'm totally fine on stock btw if that's the case.

GoofyPanda said:
So twrp rebooted even though I clicked cancel on reboot, magisk not installed. Is there anyway back? I'm totally fine on stock btw if that's the case.
Click to expand...
Click to collapse
Try to combination buttons for reset, it'll brings you to TWRP again, and install magisk after that. Hope twrp still remains in recovery partition as sometimes they'll be replaced by bootloader. If it doesn't work, you should be able to use LGUP to flash 11g kdz, and try flashing twrp again.

MetroWestMA said:
The only issue, as noted in another thread, is that TWRP can no longer mount data -- meaning you gotta jump through some hoops to back it up...so hopefully this get fixed.
Click to expand...
Click to collapse
I believe that's possible, all you need's the right dm-verity disabler that works with this phone. In theory, just format (not wipe) your data partition, flash rom, flash dm-verity disabler, and then reboot. Data partition is encrypted by bootloader, I've checked twrp's fstab and all point to the right direction. But still, we've to try this before knowing what's actually possible or not. For now, I utilize LG Mobile Switch to backup my data and it's totally fine.
UPDATE: It doesn't work, dm-verity patches actually only patch boot.img while this phone has aboot, tz, and a lot elf programer

immns said:
Try to combination buttons for reset, it'll brings you to TWRP again, and install magisk after that. Hope twrp still remains in recovery partition as sometimes they'll be replaced by bootloader. If it doesn't work, you should be able to use LGUP to flash 11g kdz, and try flashing twrp again.
Click to expand...
Click to collapse
Seems that it is back to stock recovery also, I am going to try flashing the 11g kids later

GoofyPanda said:
Seems that it is back to stock recovery also, I am going to try flashing the 11g kids later
Click to expand...
Click to collapse
I doubt it is...because mine didn't and there was no /system/recovery_rom_boot.p to delete.
you can try installing a program like Titanium Backup that has the option to reboot into recovery.
Did you get it to the menu asking to factory reset -- if you got that and answered yes both times and did not get into recovery, then it is gone...

Kdz h827bk is same as h872?

AdrianNeo said:
Kdz h827bk is same as h872?
Click to expand...
Click to collapse
do you mean h872bk? The answer is yes, this is from H872BK kdz

immns said:
do you mean h872bk? The answer is yes, this is from H872BK kdz
Click to expand...
Click to collapse
mine is h872, but lg firmware only has the h872bk and h872tn, i do not know which down.

AdrianNeo said:
mine is h872, but lg firmware only has the h872bk and h872tn, i do not know which down.
Click to expand...
Click to collapse
if your phone is from T-Mobile, it's b872bk. please check ota update. if you got oreo update then you're in the right path. but if not, then it's more likely that your phone is the 872tn one.

I'm assuming the 2 letters at the end signify the color of the devices (BK = Black and TN = Titanium/Silver). Even though the devices are the same, perhaps there are minute differences in each build? I flashed the 20a zip that was provided by OP, but it changed my splash screen to say G6 ThinQ? The G6 I have is T-Mobile branded Titanium color, but I definitely had the devices before the ThinQ moniker became a thing. I'm going to download the KDZ branded for my 872TN and see what happens when I flash with LGUP.

The G6 ThinQ splash screen came with the oreo update. I think too that bk=black and tn=titanium no diff at the builds.

Your zip save my phone
Keep it up bro ..
Thanks

So I should be able to flash this through twrp like any other zip?
Y'all were talking about deleting deleting things so I wanted to make sure before I did anything.
I'm in agreement with fixing the laf after getting root, and this way looks like it would simplify matters if you got stuck with an issue and didn't want to or didn't have access to a pc.
Thanks

I think I messed up royally

Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?

Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH

Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?

newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com

Hmm, it didn't work. I get bootloops...

Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH

For Multidisabler just do a google search one for samsung devices will appear

Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.

Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH

Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!

newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.