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.

ZUK Z2 Pro persist.img files flashable by twrp / adb

Hi mates,
here we go with the persists.img for Lenovo ZUK Z2 Pro.
So if you deleted them by accident you can try to reflash these:
new added file host for all files: https://www.androidfilehost.com/?w=files&flid=243937
persist.img ZUI 1.9.104:
https://mega.nz/#!0dxzwRrD!0DjKphWCRU-vv4yb1clTqrppVPGzbdaLEc4P7ItX6Ek
persist.img ZUI 2.3.044:
https://mega.nz/#!9QAE3J4I!wMNuXJ9430ihNKUgAmfJJqaB7a13v8qHtTGhCb-3hOE
persist.img ZUI 2.5.462:
https://mega.nz/#!MVZEnQCb!KvKYcHFdxvQEjlRC3zKsvQH316YY3iyNJEV3HE63cDU
persist.img ZUI 3.1.194:
https://mega.nz/#!oURh0ARA!JvliKwO6-bvdobG1qZoXg9CrH1u0zmtLsjFuoCIBoFk
persist.zip FLASHABLE zip ZUI 4.0.233 ST:
https://mega.nz/#!8RJ3hCpS!8cjVHyoOoa6yg9uvgTht71WB1CVCNoQi07GEZMxUR6M
All credits to @crisps
WARNING: these files are not tested. All use to your own risk.
Anyway if you accidentially deleted your persist partition it is worth a try
Flashable by fastboot or twrp. Note: Twrp 3.2.0.0 is not giving you the option to flash persist img. Use a previous Twrp version or flash by adb/fastboot.
TWRP 3.1.0.0 for Z2 Pro:
https://mega.nz/#!ABACiBKD!jPpLuguCoPU58Wq667D3H-YnsoyyXQ505ih0sapAOUY
Enjoy
_______________________________________
HowTo flash with fastboot:
- Download correct adb and fastboot drivers
(look into sticked thread "how to flash stock rom")
- put Persist.img in same folder like your adb/fastboot installation
- reboot your phone into fastboot mode
(hit volume when phone starts, select fastboot)
- open command line in the folder where your drivers / ADB-Fastboot installation is located.
- enter command:
fastboot.exe flash persist Persist.img
- you can reboot phone by select via volume buttons(not recommended) or type command:
fastboot reboot
!!! Dont / never ever / at no time ever select "reboot to ffbm"
Dont touch that!!!!
So my suggest is to enter command:
Fastboot reboot
(avoid missclick to that ffbm mode)
_____________________________________
experiences:
persist.img of 3.1.194 is not good with AEX 5.0. Produces black screen / blue led freeze.
persist.img of 2.3.044 is good with AEX 5.0
_____________________________________
experiences by crisps:
persist.img of 3.1.194 no problem with LineageOS by cosme 20171125

OP link added to 1.9.104 and 2.5.462 persist.img.
Added link to Twrp 3.1.0.0 where you can flash persist.img to persist partition.
With twrp newer than 3.1.0.0 the option to flash to persist partition is no longer available.

added new file host in post #1

What are those containing?
Is there any benefit to upgrade the image?

These are containing core drivers for sensors (correct me if im wrong).
No real benefit, flash only if you screw up your phone by formatting persist partition.

yep, use these persist partitions only if you deleted them by accident or experience problems with sensors.
Not necessary to use them if there is no problem.

Jb boin said:
What are those containing?
Is there any benefit to upgrade the image?
Click to expand...
Click to collapse
I have a problem with AEX, getting BLODs since 5.0. I've never used qpst and went straight from ZUI 2.5.462 to AEX. Tried all the basebands with no result(well I'm on the latrest 3.5.444 now for a couple hours still no BLODs). The recommended baseband doesn't allow me to unlock the phone as if UI restarts right after pattern entering and then asks me to draw it again. I wonder whether flashing 3.1 could help and aren't there newer persis images?

dimitar.petrunov said:
I have a problem with AEX, getting BLODs since 5.0. I've never used qpst and went straight from ZUI 2.5.462 to AEX. Tried all the basebands with no result(well I'm on the latrest 3.5.444 now for a couple hours still no BLODs). The recommended baseband doesn't allow me to unlock the phone as if UI restarts right after pattern entering and then asks me to draw it again. I wonder whether flashing 3.1 could help and aren't there newer persis images?
Click to expand...
Click to collapse
So between this post and the one where you asked me about not needing to do QPST/QFIL flashes any more since there's unofficial Treble support in the AEX thread, I get the feeling you're hoping someone will tell you that there's a simple answer that doesn't involve using QFIL to flash a factory ZUI QPST package.
There isn't.
What you're realizing is that you need to update more than just /system, /boot, and /persist... there's a lot of potential partitions that could've been messed up or accidentally wiped or overwritten, depending on which recovery you've been playing with and what the many various custom ROM installer scripts tell it to do... and the best way to make sure that ALL the partitions are healthy and have current, works-well-together data in them is by using QFIL to flash a current ZUI package (3.1.194 as of this writing) then use the factory recovery to install the latest ZUI Oreo OTA. With this phone, it's not an optional step; using QFIL to go back to a standard, factory image is literally step 1 in any of the upgrade or troubleshooting guides.
It's time to make sure you have it installed, USB drivers working, a good USB 3.0 type C cable that works reliably for data transfer, 7-zip installed, and at least 2 gigs of drive space available so you can decompress ZUI 3.1.194 into a folder at the root level of your drive. This isn't a phone you can work on without a computer unless you're ready to only stay on official ZUI releases with a locked bootloader & no root so that you can't accidentally mess anything up trying to get custom ROMs to work. If you want to re-lock your bootloader in that case, be sure you download the ZUI 1.9 QPST package and start from that instead of 3.1.194.
It's not that scary, and I'm happy to answer questions in PM if you need some help.

Terminator.J said:
So between this post and the one where you asked me about not needing to do QPST/QFIL flashes any more since there's unofficial Treble support in the AEX thread, I get the feeling you're hoping someone will tell you that there's a simple answer that doesn't involve using QFIL to flash a factory ZUI QPST package.
There isn't.
What you're realizing is that you need to update more than just /system, /boot, and /persist... there's a lot of potential partitions that could've been messed up or accidentally wiped or overwritten, depending on which recovery you've been playing with and what the many various custom ROM installer scripts tell it to do... and the best way to make sure that ALL the partitions are healthy and have current, works-well-together data in them is by using QFIL to flash a current ZUI package (3.1.194 as of this writing) then use the factory recovery to install the latest ZUI Oreo OTA. With this phone, it's not an optional step; using QFIL to go back to a standard, factory image is literally step 1 in any of the upgrade or troubleshooting guides.
It's time to make sure you have it installed, USB drivers working, a good USB 3.0 type C cable that works reliably for data transfer, 7-zip installed, and at least 2 gigs of drive space available so you can decompress ZUI 3.1.194 into a folder at the root level of your drive. This isn't a phone you can work on without a computer unless you're ready to only stay on official ZUI releases with a locked bootloader & no root so that you can't accidentally mess anything up trying to get custom ROMs to work. If you want to re-lock your bootloader in that case, be sure you download the ZUI 1.9 QPST package and start from that instead of 3.1.194.
It's not that scary, and I'm happy to answer questions in PM if you need some help.
Click to expand...
Click to collapse
It's been over a day without a blod now with latest baseband. I don't want to qfil anything because I'm sceptical of the outcome.

dimitar.petrunov said:
It's been over a day without a blod now with latest baseband. I don't want to qfil anything because I'm sceptical of the outcome.
Click to expand...
Click to collapse
And that's your choice, but if you've been flashing partitions piecemeal since ZUI 2.5.x and AEX 5.0 instead of a clean QFIL flash & bring-up to eliminate potential unknown causes of instability, please don't waste time submitting bug reports or asking for help with blue LED hard crashes since there's no way to know what state your phone is in.

Terminator.J said:
And that's your choice, but if you've been flashing partitions piecemeal since ZUI 2.5.x and AEX 5.0 instead of a clean QFIL flash & bring-up to eliminate potential unknown causes of instability, please don't waste time submitting bug reports or asking for help with blue LED hard crashes since there's no way to know what state your phone is in.
Click to expand...
Click to collapse
Well, I have only reflashed the firmware partition until now, which according to your own criteria makes me eligible for bug reporting. Jokes aside, here's why I believe it doesn't make sense what you recommend. It's been reported that the only way to recover from nonworking device sensors is by going back to zui 1.9 which you don't do. So your partitions have to be in a mixed state since you start from zui 3.1. Since your device works I assume you never ran into sensor problems and respectively reflashing zui 3.1 on your phone just gives you the illusion of a clean slate start( since there is nothing wrong with your phone in the first place)
Having said that, I haven't had a blod since firmware .344 which makes me think I'm right about that.

I'm not trying to attack you by the way, and I still want to help make sure you've got a working QPST/QFIL setup on your computer because I do believe it'll help make sure you have the best experience going forward. But I'm also appreciating the discussion, and I hope some other folks will chime in (and we can take it elsewhere in the forums if needed - I know it's getting a little off-topic).
dimitar.petrunov said:
Well, I have only reflashed the firmware partition until now, which according to your own criteria makes me eligible for bug reporting.
Click to expand...
Click to collapse
You've installed custom roms. Without QFIL in-between. That touches more than just /system, /data, /boot, /dalvik-cache, or /cache. It touches /persist where your device sensor configs live, it means you're modifying NVRAM areas like /modem-st1 and /modem-st2, and now, with the Treble-compatible TWRP fstab mounting /factory as /vendor, you're modifying /factory. There's probably many more. But you're not resetting them to a known-good factory state in-between, which is the entire point of this discussion.
dimitar.petrunov said:
Jokes aside, here's why I believe it doesn't make sense what you recommend.
Click to expand...
Click to collapse
What everyone recommends. Go look at troubleshooting and how-to guides throughout the Z2 Pro forums here and on zukfans.eu. It's all about starting with a QFIL flash which will reset your device's partitions to a known factory state before custom ROM installation. How much time have you spent looking at the files included in a QPST package, or digging into the XML to see what they're flashing? They've got a full GPT blank partition map included; it wipes out and re-loads whatever Lenovo thinks needs to get wiped out to factory flash a phone.
dimitar.petrunov said:
It's been reported that the only way to recover from nonworking device sensors is by going back to zui 1.9 which you don't do.
Click to expand...
Click to collapse
It's been reported that you might be able to flash just a persist.img that corresponds to your last-flashed ZUI version to recover from non-working sensors, but it's safer to just QFIL flash the whole thing. And I literally just flashed 1.9 before 3.1 three nights ago, and re-unlocked my bootloader. So I *DO* do that.
Like I have already said, what I disagree with is the generally proposed troubleshooting/clean flashing advice of starting with 1.9 and then doing OTA updates... more steps = more points of potential failure, especially when you're transferring over the internet from servers in China. I feel like it's superstition that we're passing along because it usually works; it's true that it's a slightly more complete troubleshooting option because it also restores a locked bootloader, which all later factory QPST packages don't touch. But if I have no reason to believe that my bootloader is messed up, as I have no problem getting into & out of it or using fastboot commands, then it's also a big waste of time. My advice continues to be that if you're trying to do super-super clean or need to troubleshoot, you should QFIL flash 1.9 then QFIL flash 3.1, rather than only flashing 1.9 then downloading OTA updates and risk those being corrupted in-transit or wasting the time/download bandwidth to get and apply several updates over & over again. As far as I can tell looking at the QPST installation packages, it's just as thorough (other than bootloader), with fewer opportunities for something to go wrong.
dimitar.petrunov said:
So your partitions have to be in a mixed state since you start from zui 3.1. Since your device works I assume you never ran into sensor problems and respectively reflashing zui 3.1 on your phone just gives you the illusion of a clean slate start( since there is nothing wrong with your phone in the first place)
Click to expand...
Click to collapse
I didn't start from 3.1, I just understand that since it's literally blowing a new GPT partition map over the storage and filling them with the appropriate images, it's not a mixed state and it is a clean state. But since it had been a while since I last touched my bootloader, I decided to start with 1.9 before going to 3.1 before going to 3.5.316 OTA before unlocking bootloader & going to custom ROM + 3.5.344 baseband via TWRP-flashable zip.
dimitar.petrunov said:
Having said that, I haven't had a blod since firmware .344 which makes me think I'm right about that.
Click to expand...
Click to collapse
Good, I'm glad it's working better now, but that shouldn't make you think you're right about avoiding QPST/QFIL. The BLoD could be from the bluetooth radio freaking out, could be from someone using a poorly-configured thermal-engine.conf that has an artificially low temp limit and it thinks it's overheating, could be from using a custom kernel with aggressively low voltages for given clock steppings, could be from failure to change clock states trying to come out of deep sleep at a certain time (like alarm going off, ugh, that one's awful). It's the Z2's general "I think I have a hardware failure and I'm going to hard crash to avoid potential physical damage by trying to continue", and I'm glad you're not getting it now with the latest radio firmwares.
Again, not trying to pick on you, but I think you're doing yourself a disservice AND wasting peoples' troubleshooting efforts if you're not willing to start with a QPST/QFIL flash, and I'm hoping I'm giving a good explanation as to why.

Actually I suffered from non-working sensors and full wipe (or you can say total factory reset) by QFIL of ZUI 1.9 solved it. I softbricked my phone between these two states trying to solve it without QFIL btw.

@Terminator.J thanks for the input. Still I'm coming from the fact that If I've only flashed AEX and AEX is the culprit of my partition problems then reflashing it once again won't solve them. And AEX is the only ROM I've ever flashed on this phone. I haven't understood you correctly about ZUI 1.9, my appologies. I haven't reported BLODS in the ROM's thread only asked if anyone experiences it since I'm aware of my personal setup. Btw If I remeber correctly NYE version was BLOD free on my phone too.
@Oriwen That's exactly what I wonder how is it possible to wipe your persist partition by flashing a custom rom? Since the cure is going to zui 1.9 and then flashing the same ROM how do you not loose your persist partition again? I'm trying to understand why flashing has such side effects or is just because of flashing random partition images like the ones in this thread?

dimitar.petrunov said:
@Oriwen That's exactly what I wonder how is it possible to wipe your persist partition by flashing a custom rom? Since the cure is going to zui 1.9 and then flashing the same ROM how do you not loose your persist partition again? I'm trying to understand why flashing has such side effects or is just because of flashing random partition images like the ones in this thread?
Click to expand...
Click to collapse
I probably flashed recovery partition badly, rewritten wrong partition and boom .... thats only possible culprit for me as far as I know.

dimitar.petrunov said:
@Terminator.J thanks for the input. Still I'm coming from the fact that If I've only flashed AEX and AEX is the culprit of my partition problems then reflashing it once again won't solve them. And AEX is the only ROM I've ever flashed on this phone. I haven't understood you correctly about ZUI 1.9, my appologies. I haven't reported BLODS in the ROM's thread only asked if anyone experiences it since I'm aware of my personal setup. Btw If I remeber correctly NYE version was BLOD free on my phone too.
@Oriwen That's exactly what I wonder how is it possible to wipe your persist partition by flashing a custom rom? Since the cure is going to zui 1.9 and then flashing the same ROM how do you not loose your persist partition again? I'm trying to understand why flashing has such side effects or is just because of flashing random partition images like the ones in this thread?
Click to expand...
Click to collapse
All an installer script (any of them - rom, gapps, magisk, supersu, whatever) has to do is touch something in /persist. And there's legitimate reasons to do that, like survival scrips for things that you want to persist across a system wipe/update (someone correct me if I'm wrong, but I know it's for more than just sensor configs), like google apps install info.
It seems like a number of folks either got too happy with wiping things in TWRP trying to clean their phone (rather than using QFIL to flash a factory QPST image, which does all the partitions!) or otherwise some custom ROM or systemless root or botched flashing attempt put garbage data into /persist. Some of the TWRP versions available, like the LR.Team ones, allow you to wipe a LOT more than just /system, /data, /cache, /dalvik-cache, /boot, and internal storage... the Chinese one will let you mount & wipe /persist, /efs, and a bunch of others you reeeeeally don't want to touch. Or maybe it just gets crusty with several months' worth of various installations (again, not just a ROM, but any installation script could actually touch it) doing different things to it and leaving ultimately incompatible data.
The cure doesn't cure /persist by wiping it, but by making sure that it only has good data in it (particularly the configs for the sensors), and that those config versions match the drivers that depend on those configs. So if you've got configs from an ancient (ZUI 1.9 = Android 6 marshmallow) version in /persist but drivers for that hardware from Oreo (taking the ZUI 3.5 blobs), it's likely that some things aren't going to behave correctly, wouldn't you agree? When someone's having trouble with their setup, QFIL of the latest full factory package (which includes fresh /persist partition images), followed by as few OTA updates as needed, is the fastest way to get good data back in all the places so you can start loading a custom recocovery & ROM from a known-good state.
Yeah, you're right; AEX 5.2 and earlier (including NYE beta and some other non-Treble custom ROMs worked okay with the ZUI nougat basebands (like the ZUI 2.5.462 you had), and they were even recommending coming from 3.1.194 because the early 3.5 DEV basebands were unstable. But in AEX 5.3 & up it REALLY needed an oreo (3.5.x) one in order to work... I was running into that same problem of constant BLOD crashes right after a QFIL flash of ZUI 3.1 and fresh TWRP 3.2.1 & AEX 5.3 install from there. Reflashing ZUI 3.1 via QFIL then updating with the 3.5.316 OTA package via factory recovery, then loading TWRP , wiping, & installing AEX 5.3 again took care of it and 5.3 has been basically solid for me in all the important ways since then (and with the latest 3.5.344 baseband update).
Again, please feel free to PM me if you'd like to compare more notes on things or are having issues... I really do want to be a resource for you & everyone here in making the most of these phones, and avoiding some big headaches. Setting up QPST/QFIL is a little headache, but it helps prevent much bigger ones in the long run.

weimerd said:
Hi mates,
here we go with the persists.img for Lenovo ZUK Z2 Pro.
So if you deleted them by accident you can try to reflash these:
new added file host for all files: https://www.androidfilehost.com/?w=files&flid=243937
persist.img ZUI 1.9.104:
https://mega.nz/#!0dxzwRrD!0DjKphWCRU-vv4yb1clTqrppVPGzbdaLEc4P7ItX6Ek
persist.img ZUI 2.3.044:
https://mega.nz/#!9QAE3J4I!wMNuXJ9430ihNKUgAmfJJqaB7a13v8qHtTGhCb-3hOE
persist.img ZUI 2.5.462:
https://mega.nz/#!MVZEnQCb!KvKYcHFdxvQEjlRC3zKsvQH316YY3iyNJEV3HE63cDU
persist.img ZUI 3.1.194:
https://mega.nz/#!oURh0ARA!JvliKwO6-bvdobG1qZoXg9CrH1u0zmtLsjFuoCIBoFk
All credits to @crisps
WARNING: these files are not tested. All use to your own risk.
Anyway if you accidentially deleted your persist partition it is worth a try
Flashable by fastboot or twrp. Note: Twrp 3.2.0.0 is not giving you the option to flash persist img. Use a previous Twrp version or flash by adb/fastboot.
TWRP 3.1.0.0 for Z2 Pro:
https://mega.nz/#!ABACiBKD!jPpLuguCoPU58Wq667D3H-YnsoyyXQ505ih0sapAOUY
Enjoy
_______________________________________
HowTo flash with fastboot:
- Download correct adb and fastboot drivers
(look into sticked thread "how to flash stock rom")
- put Persist.img in same folder like your adb/fastboot installation
- reboot your phone into fastboot mode
(hit volume when phone starts, select fastboot)
- open command line in the folder where your drivers / ADB-Fastboot installation is located.
- enter command:
fastboot.exe flash persist Persist.img
- you can reboot phone by select via volume buttons(not recommended) or type command:
fastboot reboot
!!! Dont / never ever / at no time ever select "reboot to ffbm"
Dont touch that!!!!
So my suggest is to enter command:
Fastboot reboot
(avoid missclick to that ffbm mode)
_____________________________________
experiences:
persist.img of 3.1.194 is not good with AEX 5.0. Produces black screen / blue led freeze.
persist.img of 2.3.044 is good with AEX 5.0
_____________________________________
experiences by crisps:
persist.img of 3.1.194 no problem with LineageOS by cosme 20171125
Click to expand...
Click to collapse
By flash Twrp:
Witch partition i select?
Boot
Recovery
Système image
Firmware

Read OP

"persist" lenovo z5
Hi everyone, I could get the file persist.img for lenovo z5. I am trying to use twrp but always the error because of the persist folder

new flashable persist sensors zip from ZUI 4.0.233 ST online, see first post.
Enjoy mates, all for Z2 Pro only.
Tested with latest twrp and RedWolf twrp. Tested with Android 8.1 and upcoming versions.
All credits to @crisps who did all the work and let me upload it

How to reset firmware

so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help

Um, i think ur in the wrong category

thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)

Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions

thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .

thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too

Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help

Question soft bricked oneplus 10 pro that worked great with lineage os

I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!

This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
yedashare said:
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
Click to expand...
Click to collapse

Savio Dantes said:
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
Click to expand...
Click to collapse
Thank you Savio, but this is my main issue, I cannot enter fastbootD.
Whether using the tool "fastboot enhance" or using the command line. I cannot reach FastboodD.
When I try to reach this using the tool, it's looping with no error log.
And when I try from CMS:
C:\Users\me\Downloads\from dumper> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

It also still sounds like your recovery.img and/r boot.img still may be corrupted.
this needs to MATCH in BOTH slots A & B
Try this:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713

Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery

yedashare said:
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Click to expand...
Click to collapse
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers

u can try to fix sms mms problem using this thread
xiaomi 12/moto edge x30(or any device with sm8450) sms＆ims error · Issue #2246 · phhusson/treble_experimentations
Now gsi is able to boot on devices with sm8450.But sms doesn't work.And ims settings shows "not supported" .I tried to install q-ims.apk or ims.apk from the stock rom.Still ,ims does work at all. A...
github.com
@yedashare
@dladz maybe we can share it groups ?

beatbreakee said:
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
Click to expand...
Click to collapse
Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
I thought that as long as I reach the recovery mode, I can still fix it.
If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
Many thanks for your efforts.

Damn. Nice to know Lineage works well on this phone with extensive tweaking. GSI's can be pretty unstable from what I've seen, missing cell reception and the like.
Yeah, flashing that image killed the phone. I've seen some people recover by flipping their boot slot to the other one and forcing the phone to boot the stock boot there. But if you've flashed to both slots, you're most likely SOL and need a MSM flash. In which case, you could try flashing the complete stock boot image for your OOS version you were on before moving to GSI to both slots as sort of a last resort, but even then I've only seen minimal success.

Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use MSM.
I understand that MSM is no longer available.
Any other direction how I can just fix the booting process?
And this is another error I received which gets closer to the source of the problem:
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer

I’m assuming Adb does not work?

why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.

Arealhooman said:
I’m assuming Adb does not work?
Click to expand...
Click to collapse
Yes right, adb doesn't work, only fastboot is still alive

TuLy2702 said:
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Click to expand...
Click to collapse
Thanks for taking time to answer.
Could you be more specific?

I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.

yedashare said:
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
Click to expand...
Click to collapse
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS

yedashare said:
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
Click to expand...
Click to collapse
you make me laugh

yedashare said:
EoS
Click to expand...
Click to collapse
Damn. I think what happened is you lost your persist.img when initially flashing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.

Prant said:
Damn. I think what happened is you lost your persist.img when initially flaahing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Click to expand...
Click to collapse
It's okay to spend a little money. It's very risky to do it yourself

Did you managed to get fingerprint working on gsi ?

Question NV data corrupted each time I install LineageOS 20 via TWRP

I have bricked several times the phone trying to install lineageOS 20. every time I manage to recover the phone using mtk and then a clean and full reset to stock images from Mi Flash.
I have tried flashing the GSI rom through fastbootD (after installing TWRP) and also via TWRP>install>image>myGSIROM
Any idea about how could be flashing the system partition causing the NV data corruption? Any other possible cause of the corruption?
Thank you!

Hello.
I was able to install it without any problems.
light version lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img
nvdata mac address is also fine.
Installing GSI is very simple.
Install without TWRP.
Please use the latest SDK Platform Tools.

newboihere said:
I have bricked several times the phone trying to install lineageOS 20. every time I manage to recover the phone using mtk and then a clean and full reset to stock images from Mi Flash.
I have tried flashing the GSI rom through fastbootD (after installing TWRP) and also via TWRP>install>image>myGSIROM
Any idea about how could be flashing the system partition causing the NV data corruption? Any other possible cause of the corruption?
Thank you!
Click to expand...
Click to collapse
I was able to boot other GSIs as well.
but I'm using the evo x custom rom published on the telegram group.
There are plenty of smarter people out there than me, so I encourage you to take a look there too.

kousuke5555 said:
Hello.
I was able to install it without any problems.
light version lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img
nvdata mac address is also fine.
Installing GSI is very simple.
Install without TWRP.
Please use the latest SDK Platform Tools.
Click to expand...
Click to collapse
Thank you!
I have been checking the issue at the lineage thread and I think the reason for losing the mac and sometimes also end up with a vndata corruption is that I changed the size of super partition but did not updated the scatter file at MiFlash, so all the flashing resets afterwards might be compromised (although MiFlash does not complain). Another reason is that when I changed the size I might have also changed some flags or something like that, I will check later.
By the way, I would really appreciate if someone could share the original gpt table (to be restored with gdisk or gparted)

newboihere said:
Thank you!
I have been checking the issue at the lineage thread and I think the reason for losing the mac and sometimes also end up with a vndata corruption is that I changed the size of super partition but did not updated the scatter file at MiFlash, so all the flashing resets afterwards might be compromised (although MiFlash does not complain). Another reason is that when I changed the size I might have also changed some flags or something like that, I will check later.
By the way, I would really appreciate if someone could share the original gpt table (to be restored with gdisk or gparted)
Click to expand...
Click to collapse
I don't know what your situation is.
It seems that it can be solved by flashing the firmware with sp flash tool using the auth bypass tool.
Isn't gpt table a scatter file in the firmware? I think you can get it by extracting the .tgz.
If you use the sp flash tool, be sure to select "Download Only Mode". Do not choose anything else.
There seems to be an error in "combo_partsize_check" when flashing with miui13rom. Please rewrite the corresponding part in the scatter file to false with Notepad etc.
There seems to be a tool that makes bypassing and flashing easier, such as "act unlock tool", so use whatever you like.
If the situation cannot be resolved with sp tool
I can't solve it with my knowledge level.