Related
I was curious, is there anyway to flash the firmware and modem through fastboot instead of TWRP? I accidentally downloaded the OP3 firmware instead of OP3T and then flashed it and well you know how that goes. Thankfully this phone almost impossible to brick even when doing the worst. It shows up in the computer and my bootloader is unlocked, and i was wondering, instead of losing everything and following the unbrick guide if there are actually commands or ways to flash it through fastboot so i don't have to fully wipe the phone? I have TWRP backups that are from yesterday on the phone, so if there was a way to restore that at the very least if i did have to do the full flash then thats fine too. I guess if the unbrick tool didn't wipe out internal storage or something thats fine. Any help is appreciated.
M3drvr said:
I was curious, is there anyway to flash the firmware and modem through fastboot instead of TWRP? I accidentally downloaded the OP3 firmware instead of OP3T and then flashed it and well you know how that goes. Thankfully this phone almost impossible to brick even when doing the worst. It shows up in the computer and my bootloader is unlocked, and i was wondering, instead of losing everything and following the unbrick guide if there are actually commands or ways to flash it through fastboot so i don't have to fully wipe the phone? I have TWRP backups that are from yesterday on the phone, so if there was a way to restore that at the very least if i did have to do the full flash then thats fine too. I guess if the unbrick tool didn't wipe out internal storage or something thats fine. Any help is appreciated.
Click to expand...
Click to collapse
If you're experienced, you can actually flash each individual partition image file back to each partition on your phone using fastboot flash file partition. So yes, if you know what you're doing you could just restore the firmware partitions and you should be back on track. However if you accidentally flash to the wrong partitions you could potentially brick your phone. ?
pitrus- said:
If you're experienced, you can actually flash each individual partition image file back to each partition on your phone using fastboot flash file partition. So yes, if you know what you're doing you could just restore the firmware partitions and you should be back on track. However if you accidentally flash to the wrong partitions you could potentially brick your phone.
Click to expand...
Click to collapse
I'm perfectly comfortable flashing partitions. Done it many times with old HTC's and Nexus's. I just need to know what the actual names of the files are that i'd need to extract from the zips is the other thing.
M3drvr said:
I'm perfectly comfortable flashing partitions. Done it many times with old HTC's and Nexus's. I just need to know what the actual names of the files are that i'd need to extract from the zips is the other thing.
Click to expand...
Click to collapse
Well, I've never really had to do this on the 3t. Last was on an old Huawei mediapad, but you can Google all the partition dumps in the latest full OTA zip, some are self explaining.
hey @M3drvr,
i have now the same problem as you had. i flashed accidentally the wrong firmware file for my op3t and it stucks now at the oneplus booting screen. how did you solved your issue back then? any help is appreciated.
the solution for my problem is to flash the correct firmware via pc - but i dont know how..
mcdachpappe said:
hey @M3drvr,
i have now the same problem as you had. i flashed accidentally the wrong firmware file for my op3t and it stucks now at the oneplus booting screen. how did you solved your issue back then? any help is appreciated.
the solution for my problem is to flash the correct firmware via pc - but i dont know how..
Click to expand...
Click to collapse
With the unbrick tool in the general section.
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
As stated above, I am trying to unbrick my Axon M with the firehose provided by Unjustified Dev. and firmware from deadman96385. When I tried using QFIL, even placing everything in its own directory on the root of the PC with no spaces in file names, it would get stuck when flashing. And whenever I tried to use MiFlash, I would get the error:"couldn't find flash script" when I selected the firmware folder. Any help is much appreciated.
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
ehsan96696 said:
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
Click to expand...
Click to collapse
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
boot
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
ff7cloudsnobody said:
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
Click to expand...
Click to collapse
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Drakosha said:
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
Click to expand...
Click to collapse
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
ehsan96696 said:
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Click to expand...
Click to collapse
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
Click to expand...
Click to collapse
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
Click to expand...
Click to collapse
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
ehsan96696 said:
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
Click to expand...
Click to collapse
Weird but awesome that it worked
Drakosha said:
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
Click to expand...
Click to collapse
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Root
ff7cloudsnobody said:
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Click to expand...
Click to collapse
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Drakosha said:
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Click to expand...
Click to collapse
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
ff7cloudsnobody said:
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
Click to expand...
Click to collapse
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Drakosha said:
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Click to expand...
Click to collapse
Doing the unpatched boot with security removed works, so this must be something that is in a subsection of boot.img other than build.prop. I'll have to look at what magisk changes, see what other locks ZTE has inside the image, and go from there.
edit: at this point, this conversation is not related to the post. If I make a breakthrough then I will make a new thread.
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Hi all
I need Loader please for this AT&T Z999 model
the one I found in this publication did not work for me : https : // forum.xda-developers.com/axon-m/how-to/rom-zte-axon-m-stock-firmware-firehose-t3909847
I just wish this method would work to update the AT&T Axon M from B30 to B37.
tj65 said:
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Click to expand...
Click to collapse
Are you able to provide the firehose that you used?
I tried the B37 and the firehost from this link https://forum.xda-developers.com/t/rom-zte-axon-m-stock-firmware-firehose.3909847/
along with the miflash from this link https://forum.xda-developers.com/t/edl-a2017-a2017u-emergency-dl-mode-twrp-unlock-upgrade.3553514/
But it always fails.
It will simply give an error of "Cannot receive hello packet"
then it will eventually go to the error of
"Object reference not set to an instance of an object."
I am using an AT&T Z999 that is on B30, and I am trying to get it updated to B37 (currently not looking to root or anything else, just want to update without having to have active AT&T service.
Edit: I think I found the right one. https://forum.xda-developers.com/t/...-unofficial-twrp-recovery-for-axon-m.3959314/
So far, copying that firehose file into the B37 folder seems to be allowing it to flash.
Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.
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