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?

[GUIDE]Restoring Honor 7x (L22) back to stock for OTA (required partitions only)

This will restore your Indian variant Honor 7x back to stock, in case you have rooted or flashed TWRP before. After this you can get OTA updates and they will flash fine. If you want to manually flash OTA updates, you can continue to next video after watching this
I suggest you to watch it carefully and do same as I did to prevent any damages.
Downloads:
https://goo.gl/8TKYoT
Password for the zip is shared in telegram group:
MOD EDIT: LINK REMOVED
Also files access will be granted in the group for now, later they will be made public.
Text guide coming soon.
Watch on YouTube (not monetized)

Sudeep Duhoon said:
This will restore your Indian variant Honor 7x back to stock, in case you have rooted or flashed TWRP before. After this you can get OTA updates and they will flash fine. If you want to manually flash OTA updates, you can continue to next video after watching this
I suggest you to watch it carefully and do same as I did to prevent any damages.
Downloads:
https://goo.gl/8TKYoT
Password for the zip is shared in telegram group:
MOD EDIT: LINK REMOVED
Also files access will be granted in the group for now, later they will be made public.
Text guide coming soon.
Click to expand...
Click to collapse
Thanks for the helpfull information.
I have the files for BND-L24 uploaded and want to share same method of restore , for US version. As the method is the same.
Would it be ok to link to your thread from a new thread with L24 files attached , or add the backup here and just change the title?

mrmazak said:
Thanks for the helpfull information.
I have the files for BND-L24 uploaded and want to share same method of restore , for US version. As the method is the same.
Would it be ok to link to your thread from a new thread with L24 files attached , or add the backup here and just change the title?
Click to expand...
Click to collapse
Do as you like, I am good with anything.

Sudeep Duhoon said:
Do as you like, I am good with anything.
Click to expand...
Click to collapse
Ok. I like to keep thing simple. And to not complicate things as much as possible.
I will put this link to the L24 backed up images here.
File host folder with ==>BND-L24C567B140<== files

mrmazak said:
Ok. I like to keep thing simple. And to not complicate things as much as possible.
I will put this link to the L24 backed up images here.
File host folder with ==>BND-L24C567B140<== files
Click to expand...
Click to collapse
Thank you so much!! I've been looking for this all day yesterday!!

Will i have to flash all this file by twrp?
mrmazak said:
Ok. I like to keep thing simple. And to not complicate things as much as possible.
I will put this link to the L24 backed up images here.
File host folder with
Click to expand...
Click to collapse
Will i have to flash all this files by twrp? Liie flashing system.zip as system and flashing other images in partition? And if yes then there is other zip file 482 Mb how to flash it? Also in system ?
Will i be able to go to Emui 6 from Emui 8? I had manually flashed oreo.
Thanks

suryaxcharel said:
Will i have to flash all this files by twrp? Liie flashing system.zip as system and flashing other images in partition? And if yes then there is other zip file 482 Mb how to flash it? Also in system ?
Will i be able to go to Emui 6 from Emui 8? I had manually flashed oreo.
Thanks
Click to expand...
Click to collapse
All the post I see about manually flashing Oreo say you CAN NOT return to emui 5. So I would believe no
**EDIT**
I see now on firmware finder there are roll-back to emui 5.1 full-ota packages.
right now only for
BND-AL00
BND-AL10
BND-TL10
but perhaps after flashing that full ota to get partition table back , then follow this method from here to get correct regional specific parts back.
All still untested at this point

Suppose if I install Other rom first like AOSP or RR?
mrmazak said:
All the post I see about manually flashing Oreo say you CAN NOT return to emui 5. So I would believe no
Click to expand...
Click to collapse
Suppose if i install other rom RR or Aosp from Emui.and then can i ftry this method?
Thanks

suryaxcharel said:
Suppose if i install other rom RR or Aosp from Emui.and then can i ftry this method?
Thanks
Click to expand...
Click to collapse
I have no first hand information. Just that for RR you need to first update to Oreo, so same as before, the information at this point is, NO , roll-back is not able.

need help please
suryaxcharel said:
Will i have to flash all this files by twrp? Liie flashing system.zip as system and flashing other images in partition? And if yes then there is other zip file 482 Mb how to flash it? Also in system ?
Will i be able to go to Emui 6 from Emui 8? I had manually flashed oreo.
Thanks
Click to expand...
Click to collapse
What if you used recovery and went to stock but you don't have system updater and when you try to update firmware it keeps failing is there anyway to fix this on my bnd-l24?
P.S no longer have twrp

Can I try it on my Honor 7X BND-AL10 variant.??Please reply

riteshnaik77 said:
Can I try it on my Honor 7X BND-AL10 variant.??Please reply
Click to expand...
Click to collapse
Your other post show you are on Oreo. This method, files linked are Android nougat.
You need to replace twrp with stock recovery, then wipe cache from there. This should fix your bootloop ,caused by wipeimg cache in twrp. Unless there is more to the story than you tell.

mrmazak said:
Your other post show you are on Oreo. This method, files linked are Android nougat.
You need to replace twrp with stock recovery, then wipe cache from there. This should fix your bootloop ,caused by wipeimg cache in twrp. Unless there is more to the story than you tell.
Click to expand...
Click to collapse
OHHHHH!!!!..Thank you!
This is what I actually did so far.
1)I am on BND AL10 Oreo.
2)Unlocked the bootloader & rooted device.
3)Tried to flash Xposed using Magisk,Then my phone went to bootloop.
4)I tried to flash RR rom using fastboot mode.Then my phone gone mad, Now I can access TWRP ,But only for 10 sec.
5)PLEASE GUIDE ME TO A COMPLETE GUIDE WHERE I CAN FRESH START.
----------------------------------------------------------------------------------------------------------------------

riteshnaik77 said:
OHHHHH!!!!..Thank you!
This is what I actually did so far.
1)I am on BND AL10 Oreo.
2)Unlocked the bootloader & rooted device.
3)Tried to flash Xposed using Magisk,Then my phone went to bootloop.
4)I tried to flash RR rom using fastboot mode.Then my phone gone mad, Now I can access TWRP ,But only for 10 sec.
5)PLEASE GUIDE ME TO A COMPLETE GUIDE WHERE I CAN FRESH START.
----------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Well it twrp is not staying on, then fastboot will have to be the method to recover
Hope this will work
fastboot format cache
fastboot format userdata
If those not work, or not allowed try
fastboot -w

mrmazak said:
Well it twrp is not staying on, then fastboot will have to be the method to recover
Hope this will work
fastboot format cache
fastboot format userdata
If those not work, or not allowed try
fastboot -w
Click to expand...
Click to collapse
Thanks alot for your quick reply.Lemme try the method you have shared.

I did the steps in post. Was successfully able to downgrade from Oreon to Naugat. But Ota failed and phone into boot loop. Any suggestion

kavena78 said:
I did the steps in post. Was successfully able to downgrade from Oreon to Naugat. But Ota failed and phone into boot loop. Any suggestion
Click to expand...
Click to collapse
the downgrade is tricky , if not done with full downgrade files. It is pretty much a half full update, then restore a backup. There are many things that could cause trouble with this.
Did you try to factory reset after failed OTA?

mrmazak said:
the downgrade is tricky , if not done with full downgrade files. It is pretty much a half full update, then restore a backup. There are many things that could cause trouble with this.
Did you try to factory reset after failed OTA?
Click to expand...
Click to collapse
Unfortunately I do not have backup (can you share it pls if you have) after factory reset also same issue.

kavena78 said:
Unfortunately I do not have backup (can you share it pls if you have) after factory reset also same issue.
Click to expand...
Click to collapse
backup files are linked in the op

mrmazak said:
backup files are linked in the op
Click to expand...
Click to collapse
Op is that 1st post? It has link to update files in rar format

WAS-LX2 stock image needed

I tried to install custom roms but I ended up bricking(?) my phone
*not exactly, some roms boot but it'll reboot itself
I've tried finding stock roms but it's either an UPDATE.app that my phone won't update into or the image is of another model like WAS LX1 or WAS L01 (and flashing other models result in a bootloop)
Hope someone can help out

CheesyBen said:
I tried to install custom roms but I ended up bricking(?) my phone
*not exactly, some roms boot but it'll reboot itself
I've tried finding stock roms but it's either an UPDATE.app that my phone won't update into or the image is of another model like WAS LX1 or WAS L01 (and flashing other models result in a bootloop)
Hope someone can help out
Click to expand...
Click to collapse
If you still have a backup, you can try to restore it and then there is firmwarefinder, so reboot to bootloader and from the PC execute "fastboot oem get-build-number". You need your exact build number, I guess. Maybe the last 3 numbers don't matter, not sure.
My build number is WAS-LX2JC719B210. (If you have custom rom installed and try to get the build-number, then you will get the build-number of the custom rom).
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Not sure how to do this though.... Always fails at 5%...

hakaishi said:
If you still have a backup, you can try to restore it and then there is firmwarefinder, so reboot to bootloader and from the PC execute "fastboot oem get-build-number". You need your exact build number, I guess. Maybe the last 3 numbers don't matter, not sure.
My build number is WAS-LX2JC719B210. (If you have custom rom installed and try to get the build-number, then you will get the build-number of the custom rom).
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Not sure how to do this though.... Always fails at 5%...
Click to expand...
Click to collapse
I'll try

Same issue
I have the same problem hey but I didn't make a back up before flashing. Any ideas on how I can move forward?

hakaishi said:
If you still have a backup, you can try to restore it and then there is firmwarefinder, so reboot to bootloader and from the PC execute "fastboot oem get-build-number". You need your exact build number, I guess. Maybe the last 3 numbers don't matter, not sure.
My build number is WAS-LX2JC719B210. (If you have custom rom installed and try to get the build-number, then you will get the build-number of the custom rom).
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
Not sure how to do this though.... Always fails at 5%...
Click to expand...
Click to collapse
I have another rom installed, so it just says "lineage-os blah blah blah" (a not working rom)

CheesyBen said:
I have another rom installed, so it just says "lineage-os blah blah blah" (a not working rom)
Click to expand...
Click to collapse
Forget about having a stock rom
I'll try to make a new post about Element V2 and my problem right now
close thank <3

CheesyBen said:
Forget about having a stock rom
I'll try to make a new post about Element V2 and my problem right now
close thank <3
Click to expand...
Click to collapse
I also just came to know that you need the original recovery partition to use the update.app method (for reinstalling stock). Well, at least for WAS-LX2J... I tried to install the recovery extracted from update.app, but still didn't succeed...
As I still have an backup (except recovery and data partitions), I was still able to get back to my stock rom.
I would prefer any other custom rom though...
Any way, good luck to you! :fingers-crossed:

hakaishi said:
I also just came to know that you need the original recovery partition to use the update.app method (for reinstalling stock). Well, at least for WAS-LX2J... I tried to install the recovery extracted from update.app, but still didn't succeed...
As I still have an backup (except recovery and data partitions), I was still able to get back to my stock rom.
I would prefer any other custom rom though...
Any way, good luck to you! :fingers-crossed:
Click to expand...
Click to collapse
Elemental V3 has just updated to support LX2

CheesyBen said:
Elemental V3 has just updated to support LX2
Click to expand...
Click to collapse
Wow, thanks for the info.
Is there any way to backup the data partition? - If not, then I would have to setup the whole system for stock again, in case that anything goes wrong...
I tried manual backup of the userdata partition using dd, but somehow the "data partition" was corrupted afterwards, showing a size of 0 and format of ext4 (didn't touch that though)...

hakaishi said:
Wow, thanks for the info.
Is there any way to backup the data partition? - If not, then I would have to setup the whole system for stock again, in case that anything goes wrong...
I tried manual backup of the userdata partition using dd, but somehow the "data partition" was corrupted afterwards, showing a size of 0 and format of ext4 (didn't touch that though)...
Click to expand...
Click to collapse
Not sure tho
I only know the basics

updating failed

So, I just rooted my Huawei P Smart, the 136 update shows up, it does all the install steps, reboots and then says it failed. Do O need to do something on the twrp boot?

Download the full firmware, we lose the option to just update via normal update and we can update with a full system update

airb05 said:
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
Click to expand...
Click to collapse
Just did that, 2 GB download, tries to install, reboots, goes to twrp, then I reboot to normal system and still says update failed.

Pretty sure you'll need stock recovery to update the "normal" way.

callmeWhiskers said:
Pretty sure you'll need stock recovery to update the "normal" way.
Click to expand...
Click to collapse
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL

siivet said:
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
Click to expand...
Click to collapse
I'm not an expert - I always use HuRUpdater to update. It just requires you to download the (exact) right files, renaming them correctly and (like rooting with Magisk) just simply flashing a single .zip in recovery. In case you try it out, remember rule#1: Always make sure you have a (nandroid)backup.
Here are the relevant lines from my "Huawei-related-findings" text file:
#update
"Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
• HUAWEI stock recovery installed
• unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install)."
Click to expand...
Click to collapse
#source XDA
 @st_voss (u=1065667)
https://forum.xda-developers.com/showpost.php?p=73011427&postcount=2
#update
“It's recommended to use a proper custom recovery (with running oeminfo_nvm_server service) like for example*my version of TWRP.
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
1. Download firmware files (for official firmware use Huawei Firmware Finder).
2. Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
◦ update.zip (use FullOTA file)
◦ update_all_hw.zip
◦ update_data_public.zip
3. Optional: Put recovery.img in same folder if you want to keep custom recovery.
4. Put HuRUpdater zip in same folder.
 5. Select*only HuRUpdater*to flash in custom recovery.
6. Follow instructions on screen. Flashing can take multiple minutes.
Problems:
• If firmware includes factory reset
◦ Factory reset is not supported by custom recovery. Therefore HuRUpdater will flash stock recovery before launching factory reset. After flashing firmware and doing factory reset, you need to flash recovery manually.”
Click to expand...
Click to collapse
#source XDA
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
#notes HuRUpdater_0.4.zip working

Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip

siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Yes, I'm im the same boat - I guess you also get the "can't have connection" error using the FF app. During the last weeks they had troubles with their service regarding hackers and moving to a new server (according to their telegram group), which have been fixed ("all services working normally now"), and many can use it again - for whatever reason some still can't connect. I tried reinstalling the app, using proxies from different countries - still doesn't let me connect.
But their web interface is working: https://pro-teammt.ru/firmware-database/ though you can't check iirc, if the firmware has been approved for your IMEI.
According to this post:
sun75 said:
It's online now! I suggest you to download the "2018.08.30" .158 "2379" release, if you have a FIG-LX1, L31 board phone.
Click to expand...
Click to collapse
You apparently can download this release (2379) if you own this device/board- though the last time I updated mine (.148) I used the 2079 (154226) one despite owning the exact same device. I'm slightly confused about this
I didn't try the above mentioned update myself.

siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Try installing an older version of the Firmware Finder app - I switched from (current) v9.0 to v8.9 and it works now
https://apkpure.com/firmware-finder...efinder/download/86-APK?from=versions/version

..