Develop Bugs

SM-T705 EFS Problem, How to restore?

Hi, Yes you're probably right I shouldn't have messed around without knowing exactly what I'm doing, but any help would be greatly appreciated, I have tried to search for answers on here, but the forum is running so slowly for me at the moment that searches just time out for me.
Anyway, heres what I did - I rooted via ODIN, (CF-Root) and installed CM12.1 - First though, having read about the EFS risks I thought I was covering my ass by downloading EFS Backup from the Play Store - I then backed up my EFS Partition, there were three options, and I assumed the safest option was to leave as default (tar.gz)
So when I saw I'd lost my IMEI after flashing CM, I reinstalled the app, tried to restore - which directed me to an app "Partition back up", which turned its nose up at my tar.gz files! (thanks for that EFS Back up!)
Can anyone tell me what I need to do with the tar.gz files? and do I need all of them?
Thanks in advance.

Partition backup?
Just use the restore options in EFS PRO. What's inside the archive, images or files?

I've just got a file of tar.gz's Radio, CDMA Radio, EFS, and three named M9kefs1 ,2, & 3
I copied them onto my Mac and managed to open them, which gave me .img files too, Which I've tried restoring on the tablet (using Partitions backup app) It reported success but didn't work.
I'll try this EFS Pro, I had seen it mentioned wasn't sure if thats the way to go, thanks!

I've got to ask, why through all of this you didn't use the one tool that would have solved your problem in minutes. TWRP?

ashyx said:
I've got to ask, why through all of this you didn't use the one tool that would have solved your problem in minutes. TWRP?
Click to expand...
Click to collapse
To back up EFS you mean? Quite simply I didn't think I needed to, I thought I'd done it with the EFS Back up app

zoidster said:
To back up EFS you mean? Quite simply I didn't think I needed to, I thought I'd done it with the EFS Back up app
Click to expand...
Click to collapse
There's nothing better than making a full backup in recovery.
It's your one and all get out clause if your device ever doesn't boot or something goes wrong.
Backup apps rely on a Bootable system.
In fact I would suggest you do it before going any further.

I suppose I wasn't too bothered, as coming from an "empty" tablet with no data loss to worry about, I had in my mind that if all went tits up I could simply flash the stock firmware with Odin. (Which I've now done anyway as EFS Pro wouldn't play ball)
Thanks for you help! Lesson learned on Backups.

zoidster said:
I suppose I wasn't too bothered, as coming from an "empty" tablet with no data loss to worry about, I had in my mind that if all went tits up I could simply flash the stock firmware with Odin. (Which I've now done anyway as EFS Pro wouldn't play ball)
Thanks for you help! Lesson learned on Backups.
Click to expand...
Click to collapse
Stock Firmware does not flash the EFS partition.
If it gets wiped or corrupted it's gone and not recoverable.
You have been lucky.

Well flashing the stock firmware back cured the problem, Must be a CM12.1 issue. That would explain why restoring the EFS .imgs didn't work either then.

Hi, I have a similiar issue with my SM-T705. I have the stock rom installed. My IMEI number seems to be broken. It's a generic imei 00499 number. However, I still have my box laying around which it came in. Is there any way to restore it from that?

haimann95 said:
Hi, I have a similiar issue with my SM-T705. I have the stock rom installed. My IMEI number seems to be broken. It's a generic imei 00499 number. However, I still have my box laying around which it came in. Is there any way to restore it from that?
Click to expand...
Click to collapse
Have you been able to resolve it? I am in the same boat as you

einsteino said:
Have you been able to resolve it? I am in the same boat as you
Click to expand...
Click to collapse
There are dozens of us, DOZENS! Seriously though, if you get a method please share.

Sprint galaxy s3 e:failed to mount /es (invalid argument)

Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help

timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here

issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...

timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?

Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input

timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?

Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again

update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..

Would this procedure work? (install magisk and twrp on 10.0.3.0)

First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
Code:
tar -xzf ********.tgz
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.

i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.

12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.

viking777 said:
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
Click to expand...
Click to collapse
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little

12:121390 said:
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
Click to expand...
Click to collapse
Anti roll back is disabled and not an issue if bootloader is unlocked

Nice thread. Tried it as well but no chance 10.0.3.00 + twrp + magisk. And you are right the problem is twrp.
Sent from my Phh-Treble vanilla using Tapatalk

12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/

12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
brother i also want to install RR PIE Rom can you please give me the guide link?

hossman said:
Anti roll back is disabled and not an issue if bootloader is unlocked
Click to expand...
Click to collapse
correct it is not. what happened was.. lol. i thought i was crafty and did some file swapping and made miflash setups that would flash so the stock files as usual , but with gsi's like RR and/or bootleggers for the system image. and it works, up until i flashed from RR to bootleggers with those setups described previously . there is where my genius was flawed. lol. lesson learned
---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------
marstonpear said:
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
Click to expand...
Click to collapse
for me, i have not come across anything caused by the GSI. any issues I've faced are purely self inflicted.

I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!

Voodoojonny said:
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Click to expand...
Click to collapse
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).

viking777 said:
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
Click to expand...
Click to collapse
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.

Voodoojonny said:
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Click to expand...
Click to collapse
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.

viking777 said:
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
Click to expand...
Click to collapse
There seems to be some bugs restoring system and vendor... Some users talked about... I usually only save and restore the data and boot partition and I never had any problems with that. For all other partitions you can use miflash or fastboot...

Yeah all my twrp full backups don't work after a fresh stock installment either, that's very annoying.
The twrp version for daisy is bugged. Backups are not working, the wifi with GSI Roms on pie stock is not working anymore as soon as twrp is installed as well.
Sent from my Phh-Treble vanilla using Tapatalk

Thanks for the replies above. @voodoojohnny
In my case it was the data partition that caused the restore to fail, vendor and system and boot all seemed to go through normally. @cd492
Based on what you say along with my own experiences and those of voovoojohnny, it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.

viking777 said:
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
Click to expand...
Click to collapse
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.

InfinityXDA said:
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
Click to expand...
Click to collapse
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
Click to expand...
Click to collapse
I meant it, at least for now, but maybe your post will help somebody else.

viking777 said:
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
I meant it, at least for now, but maybe your post will help somebody else.
Click to expand...
Click to collapse
Yes I didn't see that post but understand I didn't give you links to the official TWRP, I gave you the unofficial fixed TWRP which actually features SD Card Support and trust me it works completely fine I haven't had a problem yet. This took me hours upon hours to figure out what I was doing wrong.
The only specific reason you are not successfully getting TWRP is because you didn't flash the aboot.img after installing the zip.
I hope this helps you in the future!

thanks InfinityXDA for the tutorial, you should create a post just for it~

Well, I completely wiped my system. Help appreciated!

Hey! First of all thank you all for making this place as awesome as it is! It has helped me incountable times and saved me more than once!
Last night I was trying to root my Redmi Note 8 (ginkgo). Everything was fine. TWRP was working, and I was backing up boot.img to then use it with Magisk when I had the brilliant idea to back everything up in case I messed something up. Before backing up I decided to factory reset the phone so then I could post the stock ROM for people that DID mess it up.
Everything worked out well... Despite the fact that instead of doing a factory reset I completely wiped EVERY SINGLE PARTITION on it, even recovery, modem, everything.
Anyways, the only thing I have access to now is fastboot, which I think should be enough to recover it. I'm right now downloading the last Global Stable ROM I could find to see if I can recover it.
I can't post the URL but the version I found is "V11.0.8.0.PCOMIXM" (MIUI 11, Android 9.0).
My questions are:
Is there any newer stock ROM? Or someone that has posted it in XDADevs?
Does that ROM contain the whole system image? (I literally wiped EVERY partition)
I know I need to make sure that I keep the bootloader unlocked... Right?
Should I go with fastboot straight? Or better stick with Mi Flash Tool?
Is there anything else I should make sure I DO/DON'T?
Anyways, thank you all again for making this such a great place.
Regards!
-fermino-
PS: Xiaomi should really think again about the "the system is destroyed message". It DOES make it look a lot worse than it is hahaha

Happened to me as well... Downloaded stable fastboot, and used mi tool for install. I am now on official tomorrow and unlocked MIUI.

Since you wiped every single partition doesn't that mean you lost imei, wifi Mac adress etc. ?

I suggest you to flash full fastboot ROM. This devices uses SAR and don't wipe system next time.

[Help]Meizu Note 8 Softbrick after GSI Treble flash

Hello everyone! I need some help because i'm out of ideas how to resolve the softbrick on my old phone. First i'll explain how i got it in this state:
So i have 2 meizu note 8 i don't use anymore (one with broken touch and lcd, and the other was perfectly fine), and because of boredom and covid restrictions i had the "brilliant ideea" to mess with them and update to android 10 with GSI treble roms. The original android was flyme os 7.1.6.1 EU. First i unlock the bootloader on both and installed twrp recovery. No problems so far , everything worked fine with flyme os. Then i tried to install gsi android 10 with twrp on one of the phone (the one that does not have the screen broken). I had an error with system partition not mounting , so i did a full format in twrp (cache, data, system,internal storage, boot,vendor) and then i managed to flash it. Android 10 GSI (Havoc Os) booted up but with problems : First i got a message right after boot "There's an internal problem with your device. Contact your manufacturer for details" then the config wizard crashed constantly, but i managed to finish the process and android is working (sort of ).The problem wich i called it soft brick is the fact that wifi, data sim,bluetooth, gps, sound are not working (not detected, nada....).Both IMEI are correctly recognized, but the basic functions of the phone don't work.
Having another identical phone with original firmware, i made a full twrp backup (21 partitions..with system,data,cache, modem,kernel,vendor ....everything) and restored it on the culprit. Flyme os booted up but with the exact same symtoms as with GSI 10. It seems i messed up somewhere so i reverted back to stock flyme os recovery and flashed the original software (update zip form their website). Still the same symtoms. So I went further and got the flyme os files for QPST / QFIL flash tool. Flashed it successfully with QFIL but no improvements. I suspected the modem firmware being corrupt and flashed it separately, but i just can't get it to work.
So any ideas? I have the msm partion table and trying to pull everything with adb root and adb shell from the other phone, and restore it back to the other, but got stuck somewhere....(i'm doing more research).

A short update. Apparently the persist and persistbak partitions got corrupted or formated by me (tho twrp does not have option to format persist). This partition is responsible for calibration data for all sensors and baseband. So that's why i had all these problems.
Right now i'm trying to pull those partition images form the other phone and flash them on the bricked one.

Got it resolved. Flashing persist.img partition resolved all my problems but the IMEI and baseband got deleted .So it was necessary to pull *.qcn backup file from the working phone with QFIL program, manually edit both IMEI within qcn file with HEX editor , adding the right ones, and then restore it in the bricked phone.
Now it's working as it should.
I'm writing this in case someone gets their phone soft-bricked like mine. Hope it helps. It got me 2 full days, researching and testing things out!

Hi, I got the same exact problem after doing the flashing using orangefox, all sensors and camera not working even after flashing the original global rom via Qfil. I have been looking for that persist.img file to help me fix the issue. could you please share the Persist.img file here? you will really help a brother

hi there! i have also the same problem... accidentally formatted all partitions in orangefox recovery, been going through all night in recovering my Meizu note 8 here.. i bricked it and been looking for a firmware everywhere, and now i found a flashable firmware through qspt, im getting the same problem here, i've been looking everywhere to where i can get persist image and qcn, im not sure if my emei is messed up though.. i really need ur help also... i need this phone for my game development progress

Hi! I need the flashable firmware of the Meizu Note 8 7.1.6.1G please. I can't find it anywhere.

X-NeRo-X said:
Got it resolved. Flashing persist.img partition resolved all my problems but the IMEI and baseband got deleted .So it was necessary to pull *.qcn backup file from the working phone with QFIL program, manually edit both IMEI within qcn file with HEX editor , adding the right ones, and then restore it in the bricked phone.
Now it's working as it should.
I'm writing this in case someone gets their phone soft-bricked like mine. Hope it helps. It got me 2 full days, researching and testing things out!
Click to expand...
Click to collapse
can you share file with us?