Database Users

TWRP Backup Lollipop [22.39-5 OTA] EDIT 11/27/2014 latest [22.39-6 OTA]

I was able to create a TWRP backup of the ota after I installed it on my Moto X XT1095. I was able to flash this using TWRP from kitkat.
After flashing this, you will have the new ota, however it will not have the new baseband (you will retain the original baseband from your previous installation, in other words this does not include the modem). I believe that you should be able to flash this to any one of the XT variants as long as you are able to flash a custom recovery (in this case TWRP, I used 2.8.1.0 if that matters)
I had to create new folders on the internal storage due to the fact that I was unable to create a backup of kitkat. All I did was create a new folder on the internal storage called TWRP, inside that folder I created a folder called BACKUPS within that folder I created a folder that has the unique alpha-numeric name to each device, and finally in that folder I placed this backup file. TWRP/BACKUPS/unique alpha-numeric name/2014-11-09--11-34-04 LXE22.39-5. Then I booted to my TWRP recovery performed a factory data reset along with wiping cache and dalvik, then performed the restore.
If you don't know what your unique alpha-numeric folder name is, you can find this by booting to twrp and try to perform a backup (this is how I found out what my folders name was). I got an error, within that error was the path (it is verbatim and case sensitive).
If anyone wants to try this, here is the link.
Unzip and place in the folder I described.
22.39-5 OTA
https://mega.co.nz/#!3QNmBJZD!6wRby9lwl2gWI0Lxtwq1sKZ7DGGYAs7vtP44GmZZwBQ
MD5-63a4a2eb969c1d37b543f17dec3a64e1
22.39-6 OTA
https://mega.co.nz/#!rdEVmKIR!9wt03nACOf_Gbwt1FzXwnmKkg9lcrCcQqBtlqBZMCTI
MD5-1288b96e0b90d02273ed4f2f4235273d
Let me know how it goes. I won't be able to offer much help other than what is provided here, if I have the time I will try. I hope I didn't make this to confusing. If it works for you, hit the "thanks".
Moderators, If this is not in the correct category please feel free to move it. Thanks

i appreciate you sharing this... question for u (or to make sure i understand how you tested the 5.0 Nandroid): after flashing the OTA, did you restore your 4.4.4 Nandroid (confirm it works: calls, data, etc.), factory reset and wipe and then restore your Lollipop 5.0 Nandroid (boot and confirm it works: calls, data, etc.)? thanks in advance for your reply.

cortez.i said:
i appreciate you sharing this... question for u (or to make sure i understand how you tested the 5.0 Nandroid): after flashing the OTA, did you restore your 4.4.4 Nandroid (confirm it works: calls, data, etc.), factory reset and wipe and then restore your Lollipop 5.0 Nandroid (boot and confirm it works: calls, data, etc.)? thanks in advance for your reply.
Click to expand...
Click to collapse
After the inital OTA, I wanted to see if I could get back to 4.4.4 stock unrooted. I accomplished this by running the tool created by bhp090808. After that, I unrooted through supersu, I flashed the att modem found on graffixnyc site. I then flashed "MotoX(2014)_stock_install-recovery_sh" (with twrp) that 0.0 provided in post number 124 from the "[OTA ZIP] Pure Edition Lollipop 5.0" thread. Finally I flashed stock recovery to achieve a stock 4.4.4 system. Everything worked. After I confirmed that everything worked I did the ota again just to see if it would flash. It did, from there I was able to flash twrp, but after you reboot from twrp on the new ota you lose the twrp recovery....there is a new feature in the latest twrp recovery that allows you to move a file from pc to phone internal storage, that is how I was able to create the nand.
Funny thing is, you cannot create a backup from twrp with 4.4.4 but you can from the new 5.0 ota.
Hope this answered your question.
BTW, this nand is of the 5.0 just to clarify, like I said I was unable to make a nand of the 4.4.4

That's funny. I can do a TWRP backup just fine in 4.4.4.
Did you advanced->fix pemissions in TWRP?

not working
rsa 329 said:
After the inital OTA, I wanted to see if I could get back to 4.4.4 stock unrooted. I accomplished this by running the tool created by bhp090808. After that, I unrooted through supersu, I flashed the att modem found on graffixnyc site. I then flashed "MotoX(2014)_stock_install-recovery_sh" (with twrp) that 0.0 provided in post number 124 from the "[OTA ZIP] Pure Edition Lollipop 5.0" thread. Finally I flashed stock recovery to achieve a stock 4.4.4 system. Everything worked. After I confirmed that everything worked I did the ota again just to see if it would flash. It did, from there I was able to flash twrp, but after you reboot from twrp on the new ota you lose the twrp recovery....there is a new feature in the latest twrp recovery that allows you to move a file from pc to phone internal storage, that is how I was able to create the nand.
Funny thing is, you cannot create a backup from twrp with 4.4.4 but you can from the new 5.0 ota.
Hope this answered your question.
BTW, this nand is of the 5.0 just to clarify, like I said I was unable to make a nand of the 4.4.4
Click to expand...
Click to collapse
I am having some issues with my phone so I tried to flash this.
When I attempt to copy this over MTP it tells me one of the files is too large for the system
Edit: got it ! Adb pushed it.

holtenc said:
That's funny. I can do a TWRP backup just fine in 4.4.4.
Did you advanced->fix pemissions in TWRP?
Click to expand...
Click to collapse
No, i did not. I will try that next time i downgrade. That would make things a lot easier for a person to put this in their backups.
Were you able to make a backup of your stock unrooted 4.4.4?

nineismine said:
I am having some issues with my phone so I tried to flash this.
When I attempt to copy this over MTP it tells me one of the files is too large for the system
Click to expand...
Click to collapse
follow along with the way i accomplished unrooting. i can confirm this works, I have done it several times now with consistent success.
BTW, this is not to be flashed, rather done through the "restore" feature of the twrp recovery. By placing this folder in the backups you will be able to access it through restore.

rsa 329 said:
No, i did not. I will try that next time i downgrade. That would make things a lot easier for a person to put this in their backups.
Were you able to make a backup of your stock unrooted 4.4.4?
Click to expand...
Click to collapse
I wish... I didn't even try. I rooted and then put on custom recovery.. didn't think things through very well I suppose.

holtenc said:
I wish... I didn't even try. I rooted and then put on custom recovery.. didn't think things through very well I suppose.
Click to expand...
Click to collapse
follow along with how I unrooted, it works!
You will be able to take the ota, modem and all. I'm just guessing you have the XT1095.

rsa 329 said:
I was able to create a TWRP backup of the ota after I installed it on my Moto X XT1095. I was able to flash this using TWRP from kitkat.
After flashing this, you will have the new ota, however it will not have the new baseband (you will retain the original baseband from your previous installation, in other words this does not include the modem). I believe that you should be able to flash this to any one of the XT variants as long as you are able to flash a custom recovery (in this case TWRP, I used 2.8.1.0 if that matters)
I had to create new folders on the internal storage due to the fact that I was unable to create a backup of kitkat. All I did was create a new folder on the internal storage called TWRP, inside that folder I created a folder called BACKUPS within that folder I created a folder that has the unique alpha-numeric name to each device, and finally in that folder I placed this backup file. TWRP/BACKUP/unique alpha-numeric name/2014-11-09--11-34-04 LXE22.39-5. Then I booted to my TWRP recovery performed a factory data reset along with wiping cache and dalvik, then performed the restore.
If you don't know what your unique alpha-numeric folder name is, you can find this by booting to twrp and try to perform a backup (this is how I found out what my folders name was). I got an error, within that error was the path (it is verbatim and case sensitive).
If anyone wants to try this, here is the link.
Unzip and place in the folder I described.
https://mega.co.nz/#!3QNmBJZD!6wRby9lwl2gWI0Lxtwq1sKZ7DGGYAs7vtP44GmZZwBQ
MD5-63a4a2eb969c1d37b543f17dec3a64e1
Let me know how it goes. I won't be able to offer much help other than what is provided here, if I have the time I will try. I hope I didn't make this to confusing. If it works for you, hit the "thanks".
Moderators, If this is not in the correct category please feel free to move it. Thanks
Click to expand...
Click to collapse
You're my MF'N hero! You have no idea how much BS I was having trying to flash that OTA:
Flash OTA? Nope, some BS about unexpected this and that in modem.
Flash modem? Nope, permission denied.
Restore from Custom Recovery?? YES. Thanks man. If i could spank your thanks button 100000 times i would.

holtenc said:
You're my MF'N hero! You have no idea how much BS I was having trying to flash that OTA:
Flash OTA? Nope, some BS about unexpected this and that in modem.
Flash modem? Nope, permission denied.
Restore from Custom Recovery?? YES. Thanks man. If i could spank your thanks button 100000 times i would.
Click to expand...
Click to collapse
LOL. This message brought a smile on my Monday morning face.

I can't copy the folder to my phone. It says it's too large. How can I do it?

Make room by deleting stuff? If that's not the problem then I don't know.
Maybe try pushing the folder with adb.

Did anyone try this on the XT1092?
Thanks in advance.
MY DEVICES: Moto x 2014 (XT1092), Nexus 7 2013 (razor), HTC Desire X (proto)

Unfortunately, I keep getting "invalid crc file for system.ext4.win000" when trying to copy the backup to the final destination folder. Been using Solid Explorer. I'll try another just in case.
Edit: ES File Manager worked. Also, for me, TWRP 2.8.1.0 will not backup, but 2.8.0.1 will. For what's it's worth.

holtenc said:
Make room by deleting stuff? If that's not the problem then I don't know.
Maybe try pushing the folder with adb.
Click to expand...
Click to collapse
There is plenty of space left on the SD card to copy this but it still says the file is too large. What command do I use on adb? Can you help me? Thank you.
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
nineismine said:
I am having some issues with my phone so I tried to flash this.
When I attempt to copy this over MTP it tells me one of the files is too large for the system
Edit: got it ! Adb pushed it.
Click to expand...
Click to collapse
I am having the same problem, can you help me? What adb command do I use for this?

@MaKTaiL which model of the moto x do you have?
MY DEVICES: Moto x 2014 (XT1092), Nexus 7 2013 (razor), HTC Desire X (proto)

Vineet Upadhyaya said:
@MaKTaiL which model of the moto x do you have?
MY DEVICES: Moto x 2014 (XT1092), Nexus 7 2013 (razor), HTC Desire X (proto)
Click to expand...
Click to collapse
XT1097, but it doesn't really matter for the problem I'm having.

adb push <file> /storage/emulated/0/
Try that.

I have found it to be a problem with twrp try copying it to a different folder and then use twrp file explorer to move it to the backup folder. That worked for

[GUIDE][6045]How to Restore Android MM TWRP BACKUP

Hello Everyone
This is A Guide how to restore the TWRP BACKUP OF ANDROID 6.0 Marshallow for Idol 3 5.5
They are TWO Backups of MM 6045i update
1.Here's Marionette Backup (System Img,Boot img,Data)
2.Here's Masterdex Backup(System Img,Boot img)
1. First of all you must install TWRP on your Idol 3 5.5", Link for TWRP
2.Download and unpack archive in a separate folder
3.Boot in TWRP and make backup of your current firmware
4.. Make Wipe through TWRP menu
5.After you make your backup on external microSD or USB-OTG
TWRP -> Backups -> xxxxyyyy,
(xxxxyyyy is a "number", It's unique for each device.)
6.Copy this folder 2016-06-17--13-51-57_MMB29M_release-keys from archive to xxxxyyyy folder on microSD or USB-OTG and choose Restore in TWRP.
After finished Restoring you need new partitions to work System (if you don't flash the system will not boot )..so they are two zips flash it !
Here's ZIP by me
It takes 15-20 minutes to Boot
Thats all,Enjoy
Credits:
Thanks to @Famewolf @The Marionette and @masterdex for TWRP BACKUP​

Thanks Alex, now we have fully functional android 6.0.1 on our devices.
WIFI and BT works, android 6.0.1 is very fast, almost no lag os.

Well, So @Alek Dev I have a question
If we flash the new partition zip to make the system boot, we won't be able to restore any 5.0.2 backup, since the partitions layout will have changed?
Why do we flash this zip after having restored? I seems illogical to me. Since the system will have been restored, don't the zip risk to cause the system being erased? I just need explanation for that

frankee207 said:
Well, So @Alek Dev I have a question
If we flash the new partition zip to make the system boot, we won't be able to restore any 5.0.2 backup, since the partitions layout will have changed?
Why do we flash this zip after having restored? I seems illogical to me. Since the system will have been restored, don't the zip risk to cause the system being erased? I just need explanation for that
Click to expand...
Click to collapse
If you flash the Zip system will Boot and work....You can restore Twrp backup of 5.0.2 If you don't flash the System will not boot.The zip has included new partitions..There's no RISK about installing...

Alek Dev said:
If you flash the Zip system will Boot and work....You can restore Twrp backup of 5.0.2 If you don't flash the System will not boot.The zip has included new partitions..There's no RISK about installing...
Click to expand...
Click to collapse
Yes, I have understood that well. I was just wondering that if the partition layout has changed, which seems to be the case, I don't understand how we can go back to 5.0.2, wich doesn't use the same partitions. And as far as I know, the partitions layout are not backed up when backing up.
And be reassured, I DO believe you when you say it works it's just the point above I am wondering about. If could explain to me...

frankee207 said:
Yes, I have understood that well. I was just wondering that if the partition layout has changed, which seems to be the case, I don't understand how we can go back to 5.0.2, wich doesn't use the same partitions. And as far as I know, the partitions layout are not backed up when backing up.
And be reassured, I DO believe you when you say it works it's just the point above I am wondering about. If could explain to me...
Click to expand...
Click to collapse
Twrp works so if you have Twrp backup you can restore or Mobile upgrade q or Panasonic Firmware Tool can restore you back....if you restore Twrp backup .of 5.0.2 the system will work good with newer partitions... So you will can't have any problems ??

Will this work on the 60450 Cricket phones.

Jimhackthorn said:
Will this work on the 60450 Cricket phones.
Click to expand...
Click to collapse
Yes works with every model

Root?

MoRRLiNsS said:
Root?
Click to expand...
Click to collapse
https://download.chainfire.eu/751/SuperSU/
Just flash it with Twrp !

Dosent work anyway dude gonna wait for a real dev to release MM

MoRRLiNsS said:
Dosent work anyway dude gonna wait for a real dev to release MM
Click to expand...
Click to collapse
You must do something wrong ..even Masterdex solved the problem with MM...

Alek Dev said:
You must do something wrong ..even Masterdex solved the problem with MM...
Click to expand...
Click to collapse
I think its because it cant mount system for some reason it mounts it when it wants

MoRRLiNsS said:
I think its because it cant mount system for some reason it mounts it when it wants
Click to expand...
Click to collapse
Go to twrp go to WIpe then Advanced Wipe then select system and then Repair or change system and then Repair file system
and then read again the thread and try again!

WIFI Not Working
My WiFi is not working I have Cricket 60450 model I just flashed and it works great fast smooth and stable only problem is my WiFi does not work it could be the baseband. is there a flashable baseband for this or please let me know if there is a fix for it. This is the 6045i model and could be the problem different baseband the the 60450 cricket model please help alek dev and thanks for your support.

Jimhackthorn said:
My WiFi is not working I have Cricket 60450 model I just flashed and it works great fast smooth and stable only problem is my WiFi does not work it could be the baseband. is there a flashable baseband for this or please let me know if there is a fix for it. This is the 6045i model and could be the problem different baseband the the 60450 cricket model please help alek dev and thanks for your support.
Click to expand...
Click to collapse
I had the same issues with wifi but try again with this thread ..for me helped and i'm having WIFI AND BT ON MY IDOL 3 with MM
Here's instructions
1.,WIPE EVERYTHING
2.Download and Flash this
3.Restore one of the Backups
4.And Reboot

wifi and BT still not working
I still don't have wifi working i flashed the partitions but it want mount them it seems like the baseband may be incompatible becouse this is for the international version the rom works great but there needs be flashable partition for the baseband that is comparable with the 60450 cricket model the rom works great if i could get the right flashable partitions becouse the one that you told me to try alek dev does not mount. I have picture but i am not able to add a picture in the post or attachment here below is the error it is generating if you have way for me to send the picture to you i will send it so you are able to see the problem. thanks and i hope this can be solved for all cricket models.
unmount of /persist failed; no such volume
unmount of /system failed; no such volume​

Jimhackthorn said:
I still don't have wifi working i flashed the partitions but it want mount them it seems like the baseband may be incompatible becouse this is for the international version the rom works great but there needs be flashable partition for the baseband that is comparable with the 60450 cricket model the rom works great if i could get the right flashable partitions becouse the one that you told me to try alek dev does not mount. I have picture but i am not able to add a picture in the post or attachment here below is the error it is generating if you have way for me to send the picture to you i will send it so you are able to see the problem. thanks and i hope this can be solved for all cricket models.
unmount of /persist failed; no such volume
unmount of /system failed; no such volume​
Click to expand...
Click to collapse
Send me PM i will try to help you

wifi and BT still not working
Here is the picture of it failing to mount.

Jimhackthorn said:
Here is the picture of it failing to mount.
Click to expand...
Click to collapse
Before installing unmount system and try again?

ZE500KL (Z00ED) Soft-bricked... (bootlooping on Asus logo, doesnt even show ROM logo)

Hello...
So, me, a dumbass, decided to try to encrypt the phone while it was rooted... Everything went wrong, and on the first reboot it started rebooting non-stop(on the Asus logo)... I left it for some time but nothing changed.
I tried restoring a backup(system, data and boot), stays the same, tried restoring stock boot and reflashing the rom(ResurrectionRemix) but nothing changed. How do I solve this?
(Note that I have a backup of all stock ROM partitons, except the recovery)

DarkAlpha.Sete said:
Hello...
So, me, a dumbass, decided to try to encrypt the phone while it was rooted... Everything went wrong, and on the first reboot it started rebooting non-stop(on the Asus logo)... I left it for some time but nothing changed.
I tried restoring a backup(system, data and boot), stays the same, tried restoring stock boot and reflashing the rom(ResurrectionRemix) but nothing changed. How do I solve this?
(Note that I have a backup of all stock ROM partitons, except the recovery)
Click to expand...
Click to collapse
wipe everything
Format internal storage
And then restore ur backup

addy692 said:
wipe everything
Format internal storage
And then restore ur backup
Click to expand...
Click to collapse
Already tried that, but anyways, I had to flash stock ROM using AFT... Now my problem is unlocking the bootloader because the dam application that ASUS gives doesn't want to work now... lol

Solve the problem? How? Same problems 4 me.

Genuis Loci said:
Solve the problem? How? Same problems 4 me.
Click to expand...
Click to collapse
Flash stock ROM
You can find stock rom (firmware) on ASUS website support page
Make sure you have your stock recovery installed too, and restore your rom

Genuis Loci said:
Solve the problem? How? Same problems 4 me.
Click to expand...
Click to collapse
I solved by flashing stock ROM with Asus Flash Tool:
ASUS Drivers: https://www.asus.com/Phone/ZenFone-2-Laser-ZE500KL/HelpDesk_Download/ - Select Android OS, then go to "USB" and download the drivers
Website (tutorial on how to use it is linked there): http://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html
RAW firmware files: https://forum.xda-developers.com/ze...0a-z00d-z00x-raw-fw-collection-t3448966/page3
In case you don't want to check both RAW files, I posted here the versions of each firmware:
First link: WW_ZE500KL_V12.8.5.222_M3.6.42_Phone-user (Lollipop)
Second link: WW_ZE500KL_13.10.10.44_M3.6.51_Phone-user (Marshmallow)
If you get confused when you need to select the RAW file, go to the extracted folder and there will be it. (I got confused because the folder by itself was named .raw lol)... Also, don't delete any file, as you probably will need them one time later

DarkAlpha.Sete said:
I solved by flashing stock ROM with Asus Flash Tool:
ASUS Drivers: https://www.asus.com/Phone/ZenFone-2-Laser-ZE500KL/HelpDesk_Download/ - Select Android OS, then go to "USB" and download the drivers
Website (tutorial on how to use it is linked there): http://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html
RAW firmware files: https://forum.xda-developers.com/ze...0a-z00d-z00x-raw-fw-collection-t3448966/page3
In case you don't want to check both RAW files, I posted here the versions of each firmware:
First link: WW_ZE500KL_V12.8.5.222_M3.6.42_Phone-user (Lollipop)
Second link: WW_ZE500KL_13.10.10.44_M3.6.51_Phone-user (Marshmallow)
If you get confused when you need to select the RAW file, go to the extracted folder and there will be it. (I got confused because the folder by itself was named .raw lol)... Also, don't delete any file, as you probably will need them one time later
Click to expand...
Click to collapse
Hello,
I am on lineageos with twrp installed. And i want comme back on stock, does this how to restore stock recovery?
Thanks

pabonf said:
Hello,
I am on lineageos with twrp installed. And i want comme back on stock, does this how to restore stock recovery?
Thanks
Click to expand...
Click to collapse
By using that method you get everything back to stock. Simple answer: You get back stock ROM and recovery.

Need (clean) Nandroid backup Mediadpad M3 (W09) to unbrick my device. Please help

Dear all,
I think I bricked my device (no OS installed, adb / fastboot mode can be entered, but flashing the extracted files one after the other does not work, dload routine cannot be entered). My last best hope is that somebody here can provide or rather share a clean Nandroid backup of her/his Mediapad M3 (W09) with me. On my device I can still enter TWRP and could then restore the backup. If somebody could generate such a clean backup and upload it to some cloud storage I would be very grateful.
Please help me out.

This is a clean backup. I hope you can solve your problem.
https://drive.google.com/open?id=1vK61UrY6qZbOh9xYhSmmanXhXJuDsnS1

Dear ajnexus5,
thank you for sharing a backup with me. I restored it with TWRP but my device is still not booting.
One question about your backup: Did you check all the available boxes (3rdmodem, Boot, Recovery, Cache, ...) in TWRP when you generated the backup? Because in my TWRP restore function it only offered me to check the system box.
If you haven't checked all the boxes, I would kindly ask you to repeat generating the back up and share it with me once more (please take care that the backup is for the W09 type of device, which means the WiFi version). I think my device is so messed up that I need a complete backup in order to save it. Thank you very much for your help so far. Highliest appreciated!!

Which boxes do you need to be marked? There are really many that I did not know that existed jaja

Possibly all, sorry I don't know. You can also contact me in private if you don't want to share it publicly. I would be so grateful, right now my device is only a USB mass storage

I recommend you try this first. Put the files in the sd the first one after you remove that one and put the other one and the same thing. That is a complete rom 4.1 I think that will be better for you.
https://forum.xda-developers.com/showpost.php?p=74973897&postcount=11

Thank you for your recommendation, but unfortunately I tried this before I asked here for the backup. In the internal update routine with dload it is stuck at 5% and then crashes. I tried it also with Huawei Extractor and flashed the files with fastboot individually. But there is always a error message (see attached image). I think the only way to resolve this (if at all possible) is to restore a complete backup with TWRP.

I think that does not work for you because it's done for the original recovery.

I tried it also with the original recovery but it does not work out for unknown reason. One of my last best hopes is the complete backup with TWRP. I think if this does not work out either the device is completely unusable. And in TWRP when I try to wipe then there are some messages like
Failed to mount '/3rdmodem' (Invalid argument)
Failed to mount '/system' (Invalid argument)
which is why I think I need a clean backup with all the boxes checked in order to restore the functionality. I am begging you to provide me with such a backup

I'm trying but if I check an empty box it tells me that I do not backup the folders that have something and then I upload it to diver and we'll see if it works.

ajnexus5 said:
I'm trying but if I check an empty box it tells me that I do not backup the folders that have something and then I upload it to diver and we'll see if it works.
Click to expand...
Click to collapse
Just try to check as many boxes as possible, I think more you simply cannot do. Thank you so much for your effort, it would be great if it would bring my device back to the living ones.

It is already going up to drive the complete rom.Let me ask you when you tried to flash the files of 4.1 did you do with the TWRP?
I think those files work only with the original recovery.

Great thank you so much!
You are right, as far as I know you cannot flash the Update.app with TWRP so far. I used the internal update routine (dload method) which failed for both the full stock ROM and the rollback. Then I used Huawei extractor and tried to flash all the files of the official ROM from the Huawei website one after the other via Fastboot (which failed too, see my screenshot).
I think this is what you mean by original recovery, right? Anyway, I reflashed the original recovery (with Huawei extractor + fastboot) several times, then tried it with dload, then used TWRP again. Nothing resolved my problem.

It seems that as you said you have deleted all the prticiones of the tablet. In other devices that fixes that is to flash a rom of factori and recover all the partitions. In any case if there is something of that must be in the Russian citium they have many things about this tablet.Nose if you have seen it is here: https://w3bsit3-dns.com/forum/index.php?showtopic=780572
---------- Post added at 05:20 PM ---------- Previous post was at 05:03 PM ----------
Try to see if it works.
https://drive.google.com/open?id=1AaphCQEbMfEPUl3MyVRvR8p-8vJAXUVD

Thank you, it will take some time to download. I will give you feedback whether it works or not.

Are you sure you gave me the correct link? https://drive.google.com/open?id=1Aa...RvR8p-8vJAXUVD
Because the file has the same size as the first backup.
[Edit]
It is still only the system check box that is available.
@ajnexus5: Are you sure that you uploaded the new backup? Maybe you mixed it up with the old files.
[Edit2]
And maybe it's also important that I was on Android 7 EMUI 5.0.1 before i crashed it. What version is your device on?

This ROM if I'm sure it's the backup of all the ROM.
https://drive.google.com/open?id=1trH1xKB6u3ulTXpA5hUi9g8DLj226jns

Dear ajnexus5,
I managed to bring my device back to life. I finally managed to flash the files of a firmware with Fastboot. Thank you so much for your effort and sharing those backups with me. I appreciate your help very much! All the best to you!

Borkse said:
Dear ajnexus5,
I managed to bring my device back to life. I finally managed to flash the files of a firmware with Fastboot. Thank you so much for your effort and sharing those backups with me. I appreciate your help very much! All the best to you!
Click to expand...
Click to collapse
Hi Borkse,
I ran into the same problem, on my device I can still enter TWRP and could then restore the backup. Did you manage to find a full backup? let me know know how you fix yours. Thanks in advance.
Josyskunk

Sorry for the late answer. Backup wasn't the solution in my case. I used the Huawei extractor and Fastboot to flash all the pieces of the firmware manually one after the other. Take care that you use a suitable version for your device (I first downloaded the wrong one). Hope you have already solved your problem or my post helps you.

Expert advice on restoring someone's efs?

hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?

No help here?

??????????????????????????????/

i don't think so people are helpful here or either not expert as nobody is replying lol

No idea. Sorry

taran181 said:
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
Click to expand...
Click to collapse
4-6 months back there was thread why we should not restore efs of someone & proper tutorial for people who messed up their mac address with some kernel.
Now this tutorial on downgrading pie to oreo. I have no idea. Someone's efs would mess your IMEI, wifi mac, Bluetooth mac, thats what i think. But there are tutorial how to edit imei using some Qualcomm tool.
Ask @CosmicDan. He's the expert.

Just flash Oreo on fastboot, with full wipe. Why doesn't that work?

I was having an issue since using custom rom with december fw btw.
and I was mistaken flashing november fw back to solve some calling issue, so I ended up with no signal which should be came from I didn't restore dev's efs backup.
So I start from flashing full clean stock november and ended with bootloop on it, which is something I still curious what cause it.
At that times, I'm on locked bootloader and can't even enter edl to reflash the rom and can't unlock bootloader since the rom still not booting to enable oem unlocking option.
I don't remember what I have done to it, but at times my phone can boot with no signal, 0 imei on sim1 and null on sim2.
So I start to rewrite the imei then everything is back to normal.

Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.

CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624

fhsd22 said:
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
Click to expand...
Click to collapse
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..

taran181 said:
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
Well you can try it I guess, just backup the EFS partition and other stuff with my backup tool and you can always go back if worse comes to worst.

CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
Xiaomi put out a message on their forum that after the Pie update, the phone should not be rolled back. Its for all Android one models. When users flash an older roms, bootloops occur.
https://www.fonearena.com/blog/271177/xiaomi-pie-oreo-downgrading-disabled-android-one-devices.html

taran181 said:
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
Click to expand...
Click to collapse
But what he is saying is that he did downgrade EFS, but IMEI didn't change. This suggests that EFS isn't the original source of IMEI after all. Or maybe the bootloader can re-write IMEI and stuff on boot, who knows... Surely others have actually confirmed that EFS cross-flash = IMEI change, right? Not just assumed?
...point is, you can backup your EFS via EDL mode so there should be no risk. If you made a full EDL backup of your own device when you were still on Oreo then you would be golden, as EDL has full access to all partitions.