WAS-LX2 stock image needed - Huawei P10 Lite Questions & Answers

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

Related

[STOCK ROM BACKUP] 2.1 Éclair (V20E Baltic)

Stock Android 2.1 Éclair Recovery Backup! V20E Baltic
This is a Recovery Backup of Android 2.1 V20E Baltic ROM. All files in this rom are freshly extracted from the V20E_00.kdz update file, converted from .mbn to .img, ready to be flashed using Clockwork Recovery. No mods, just untouched stock ROM ^_^ Also, Remember to Wipe/Data factory reset before flashing to AVOID BOOTLOOPS!
NOTE: THIS IS NOT COMPATIBLE WITH MODIFIED PARTITION SIZES
(If you flashed Mur4ik's 250MB Data KDZ, YOU CANNOT USE THIS BACKUP! You will need to flash a regular Fastboot ROM using KDZ Updater to reverse the partition size change.)
FAQ:
Q: I get stuck at the Android boot logo after I flashed this. Is my device bricked?
A: No, you ignored the above and forgot to factory reset. Go into recovery, factory reset and reboot. Your phone will now fully boot.
NOOB: THIS BACKUP BRICKED MY DEVICE! (Believe me, people say this-.-)
A: Not possible. I cannot brick your device with this. Go away.
Q: Are there any mods to this ROM?
A: No. It is 100% stock.
Q: Why don't I just downgrade using KDZ?
A: Because if your PC dies during flashing, congrats on your new brick (I know the chances are slim, but hey, better to be safe, right?)
Download:
Download from MegaUpload
Size: Roughly 110.39MB (Compressed .zip)
Roughly 222MB (Uncompressed)
MD5: b17bf5ee2ef91f58ab78d07ce6a59945
Any questions? Just ask below.
Jack
thanks flashed that before rma - accepted good to use as development soruce - good work,bro ! love that !
mikegapinski said:
thanks flashed that before rma - accepted good to use as development soruce - good work,bro ! love that !
Click to expand...
Click to collapse
No problems, thanks!
Also added information on how to get original partition sizes back.
Jack
JackG256 said:
Stock Android 2.1 Éclair Recovery Backup! V20E Baltic
This is a Recovery Backup of Android 2.1 V20E Baltic ROM. All files in this rom are freshly extracted from the V20E_00.kdz update file, converted from .mbn to .img, ready to be flashed using Clockwork Recovery. The only modification to this ROM is that I have added Cyanogen's APN list, which allows this ROM to be compatible, out of the box, with your Mobile Data and saves you having to your settings again. (Some carrier's settings may not be included, Check Cyanogen's APN list) Also, Remember to Wipe/Data factory reset before flashing to AVOID BOOTLOOPS!
NOTE: THIS IS NOT COMPATIBLE WITH MODIFIED PARTITION SIZES
(If you flashed Mur4ik's 250MB Data KDZ, YOU CANNOT USE THIS BACKUP! You will need to flash an original Fastboot ROM using KDZ Updater to reverse the partition size change.)
Download:
Download from MegaUpload
Size: 110.75MB (.zip)
Roughly 222MB (Uncompressed)
MD5: 8305e31a1bdb571fd59a7db787acb6c1
Any questions? Just ask below.
Jack
Click to expand...
Click to collapse
I know this is newer but why is it special? How is it different compared to other stock ROMs?
nibras_reeza said:
I know this is newer but why is it special? How is it different compared to other stock ROMs?
Click to expand...
Click to collapse
It's not special, It just includes bugfixes or other. It's just better to have the newer software I guess. Meh, I only made the recovery backup for people to get back to 2.1 if they want, Because using KDZ could brick your phone. (The chances are slim, but it happens.)
Jack
Slightly OT:
JackG256 said:
It's not special, It just includes bugfixes or other. It's just better to have the newer software I guess. Meh, I only made the recovery backup for people to get back to 2.1 if they want, Because using KDZ could brick your phone. (The chances are slim, but it happens.)
Jack
Click to expand...
Click to collapse
Do you know what I've never understood? What is a Baltic rom? And what is the difference ? LOL
Jamielawther said:
Slightly OT:
Do you know what I've never understood? What is a Baltic rom? And what is the difference ? LOL
Click to expand...
Click to collapse
The Baltic ROM was designed for the countries in the Baltic areas (Estonia, Latvia and Lithuania) but it can be used for all over the world. I used Baltic instead of CIS as Baltic doesn't come with the CIS apps (like Yandex or other crapware) also I don't know the real differences but I think that it is just bugfixes and such.
KDZ updater is a tool used by LG customer care, right? In that case, it would be safer than recovery.
I guess they updated the Kernel as well. In any case, am using Swiftdroid. Thanks for the recovery images though. xD
JackG256 said:
The Baltic ROM was designed for the countries in the Baltic areas (Estonia, Latvia and Lithuania) but it can be used for all over the world. I used Baltic instead of CIS as Baltic doesn't come with the CIS apps (like Yandex or other crapware) also I don't know the real differences but I think that it is just bugfixes and such.
Click to expand...
Click to collapse
Ah , Going back to Baltic now then
Also , Do you know how I could install a theme for 2.1? All the ones I have from 4.pda use Metamorph , which reboots my phone whilst replacing framework-res , is there any way I can stop this or not use metamorph? I think it's the enoch theme , but no theme has ever worked
nibras_reeza said:
KDZ updater is a tool used by LG customer care, right? In that case, it would be safer than recovery.
I guess they updated the Kernel as well. In any case, am using Swiftdroid. Thanks for the recovery images though. xD
Click to expand...
Click to collapse
No, LG use R&D Test tool (I think) but Test Tool/KDZ reflashes the bootloader whenever you use it. Whereas recovery doesn't, which makes it safer because if the phone dies when flashing an image in recovery, you can just reflash it as the bootloader goes un-touched, but if your phone or computer dies during a test tool or KDZ flash, you now have a brick with a screen and buttons. Recovery is much, much, much safer, but LG don't use it as it is un-official software. LG also use it because if they upgrade your phone from 1.6 to 2.1, the bootloader needs to be reflashed and updated.
Also, these images are useful if you want to create 2.1 roms or go back to 2.1, say if your phone's screen broke etc.
Jack
JackG256 said:
No, LG use R&D Test tool (I think) but Test Tool/KDZ reflashes the bootloader whenever you use it. Whereas recovery doesn't, which makes it safer because if the phone dies when flashing an image in recovery, you can just reflash it as the bootloader goes un-touched, but if your phone or computer dies during a test tool or KDZ flash, you now have a brick with a screen and buttons. Recovery is much, much, much safer, but LG don't use it as it is un-official software. LG also use it because if they upgrade your phone from 1.6 to 2.1, the bootloader needs to be reflashed and updated.
Also, these images are useful if you want to create 2.1 roms or go back to 2.1, say if your phone's screen broke etc.
Jack
Click to expand...
Click to collapse
True about dying during boot-loader flashing but boot loader is small and it usually gets flashed within a minute or so. As per recovery, there is a higher chance of errors when flashing. I agree about your point. As long as recovery and bootloader are working, no matter what happens to system or boot, you could fix it.
I tried to flash this, also wiped cache, data and dalvik, but I'm getting boot loops.. I made a backup before so I reverted the changes... here's what I did:
copied into clockwork's backup folder, rebooted into clockwork mode, flashed and wiped cache, data and dalvik.. result: boot loops
any help?
thanks
denzig said:
I tried to flash this, also wiped cache, data and dalvik, but I'm getting boot loops.. I made a backup before so I reverted the changes... here's what I did:
copied into clockwork's backup folder, rebooted into clockwork mode, flashed and wiped cache, data and dalvik.. result: boot loops
any help?
thanks
Click to expand...
Click to collapse
I know, I was going to fix it but forgot, i'll do it now. Just give me 20 mins to upload and that.
Jack
Fixed version now uploaded, turns out it was a problem with the boot.img, all is resolved.
Jack
Thank you for the backup!
Maybe I will flash it. CM7 is slow for me.
Thank you so much, will try it later and post the results..
I have the same problems than denzig, my phone restarts after the LG's logo. Does a solution exist ?
Mat11
Uploaded another fixed version-.- If this doesn't work I will cry myself to sleep (/facepalm). (Joking about the crying myself to sleep bit by the way.)
Enjoy!
Jack
I flashed this but I immediately flashed infernal kernel so didn't get any boot loops... I've now realised why I stopped using Baltic ROMs - Google Navigation insists on using the US TTS. It's a roundabout NOT a circle
Still nice to have in my "ROM museum" though - thanks Jack!

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

[NANDROID] Motorola Marshmallow Soak test v5 - Dec 13 - makes other phones jelleh!!

This is considered a beta rom. Things may break, things may change, and your phone may brick or turn into a portable toaster. I'm not responsible.
You are flashing this at your own risk!!!
This is a nandroid backed up from a US 2gb/16gb xt1540. It may or may not work on all models...that is to be determined.
Confirmed compatible variants:
XT1540 (US 1/8GB and 2/16GB) (Canada)
XT1541 (UK) (France)
(if your variant is not here it only means it's either not tested or not reported working. please test and report back!)
If you are unable to boot or obtain any signals after flashing this, it is highly recommended you flash a full factory image intended for your specific model and wait for another solution.
This is only meant to be a temporary fix while we wait for the big guys to build us a standard rom.
PLEASE READ THE GUIDE BELOW!!! Some things have changed with v3
How to install:
Extract the .tar.gz archive like any zip
copy the folder to the directory where your other TWRP nandroids are on your internal storage or sd card (TWRP/BACKUPS/ZZY222____/) in here you will see folders with dates, times, rom names and info, etc in the folder names...copy the folder you extracted to this directory.
boot to TWRP
restore this backup
if coming from anything but a previous soak test, wipe userdata
wipe cache and dalvik cache
flash systemless root zip SuperSU v2.61 (optional) DO NOT flash any lower SuperSU version!!
reboot (Please be patient...it's a VERY long wait. If you pass 10 minutes waiting and it hasn't booted, force a reboot by holding the power button)
profit!
***It is HIGHLY recommended US xt1540 users update their radio. It is not required to run this soak test, though. THIS IS ONLY FOR US USERS!!!!! DO NOT FLASH THIS IF YOU ARE NOT IN THE UNITED STATES!!!!***
See this post for the updated soak test modem.img files (just flash to the modem partition with fastboot and reboot the device)
http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643
For anyone who is not in the contiguous USA (48 states) but still has xt1540 and would like to test the modem above, you can use the app linked below to back up your modem partition directly from your device before you try the new modem. This way you don't have to download a factory rom to get the right modem.img if you don't already have one backed up on your computer. You have to be rooted to use it.
Wanam Backup & Restore app (free)
How to root:
Please see this thread for the download:
http://www.xda-developers.com/update-to-snapprefs-xposed-module-includes-17-instagram-like-filters
The newest root method provided by chainfire does not touch the system partition. To the end-user, the only change is that when you flash a new kernel you must re-flash superSU....not your rom!!! What this means to us in this case is we can use the stock kernel provided with the soak test, flash the superSU zip, and have root, just like a Nexus device without having to wait for a permissive kernel!
*****After flashing the new systemless root zip you will be prompted to install superSU before the device reboots. DO NOT ALLOW IT TO INSTALL!!!!!! If you allow it to install with this option you will get a bootloop*****
**To view your device storage from your computer, open your notification shade, click the "USB for _____" notification, and select "transfer files (MTP)". It won't stick through a reboot, so you'll have to do this each time you boot.....the same thing goes if you unplug the cable.
Download:
https://drive.google.com/file/d/0ByE999IDa0JnaEpnX0FCRjNxX28
Gonna try it on my xt1540. Just one question about the procedure. I just restore backup directly? Without wiping anything? Or should i wipe system at least?
feligoni said:
Gonna try it on my xt1540. Just one question about the procedure. I just restore backup directly? Without wiping anything? Or should i wipe system at least?
Click to expand...
Click to collapse
TWRP wipes for you automatically in the restore process. You don't have to wipe system manually. Just restore wipe userdata and reboot!
hp420 said:
TWRP wipes for you automatically in the restore process. You don't have to wipe manually. Just restore and reboot!
Click to expand...
Click to collapse
Awsome. Im downloading the file right now, gonna report back when i try it
feligoni said:
Awsome. Im downloading the file right now, gonna report back when i try it
Click to expand...
Click to collapse
I'm reuploading a new nandroid...please wait to install the new version
hp420 said:
I'm reuploading a new nandroid...please wait to install the new version
Click to expand...
Click to collapse
Haha, ok. I was about to restore te backup, but i'll wait.
I'm very sorry for any inconvenience guys. I know it was a very large download. This next one is about half the size.
hp420 said:
I'm very sorry for any inconvenience guys. I know it was a very large download. This next one is about half the size.
Click to expand...
Click to collapse
Dont worry, i've got pretty good download speed at work hehe
All done! new link in the OP guys...go nuts
610mb??
Sarath280 said:
610mb??
Click to expand...
Click to collapse
it's system and boot only, and compressed.
it's all there, trust me
hp420 said:
All done! new link in the OP guys...go nuts
Click to expand...
Click to collapse
Things look good, right now it's in the eternal process of optimizing apps Just wondering, by upgrading like this, i will get updates via ota? or only if u keep updating it?
feligoni said:
Things look good, right now it's in the eternal process of optimizing apps Just wondering, by upgrading like this, i will get updates via ota? or only if u keep updating it?
Click to expand...
Click to collapse
We will only get an update if our friend who is an official tester shares it with us.
Okay, it worked. I booted up perfectly, but as i needed my phone completely stable for today i reverted back to LP. But it worked well I think ill wait for a stable version though, it kind of lagged compared to LP.
feligoni said:
Okay, it worked. I booted up perfectly, but as i needed my phone completely stable for today i reverted back to LP. But it worked well I think ill wait for a stable version though, it kind of lagged compared to LP.
Click to expand...
Click to collapse
Glad it worked!! Thanks for reporting back
it booted on xt1550 ril not working
Sarath280 said:
it booted on xt1550 ril not working
Click to expand...
Click to collapse
have you tried manually entering your carrier's APN information?
I'm having issues extracting the System folder from the backup.
Any ideas? Trying to cook up a flashable ROM for easier testing.
l3ones said:
I'm having issues extracting the System folder from the backup.
Any ideas? Trying to cook up a flashable ROM for easier testing.
Click to expand...
Click to collapse
you can extract with any of the popular file managers for android right on your phone if you'd like. It may take a little longer, but it will work.
hp420 said:
you can extract with any of the popular file managers for android right on your phone if you'd like. It may take a little longer, but it will work.
Click to expand...
Click to collapse
Apparently it was just an issue with 7-zip, WinRAR handled it perfectly.
This is my first time making a flashable ROM but it should be up later today.

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.

Question about custom recoveries and bootloader relocking

Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Tsun_Pooka said:
So my question is, can you lock the bootloader with TWRP installed and still access the system?
Click to expand...
Click to collapse
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Tsun_Pooka said:
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Click to expand...
Click to collapse
How you unlock the bootloader?
bozka1 said:
Unfortunately, it's impossible... If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
Thanks for the tips! By the way, what is dload? If it's a website, I cant find it (the fact that dload is short of "download" doesn't really help). I am now in need of that full-stock ROM.
Tsun_Pooka said:
By the way, what is dload?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/help/formatting-dload-method-t3815949/page2
Whew. I got the bootloader AND FRP locked on me, and now I don't have a usable system. So now, I have to rely on eRecovery to download a 3GBs package and hope all things go well...the problem is, I'd need to find a place that offers fast WiFi...my internet is terrible.
EDIT: Got the system back up thanks to eRecovery. I'm not sure if I want to root or install a custom recovery on the Lite. I've realized even more that I should cherish my older phone, my Samsung Galaxy Win. At least this one isn't complicated or protected by Fort KNOX.
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
usman400 said:
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
Click to expand...
Click to collapse
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Tsun_Pooka said:
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Click to expand...
Click to collapse
I am certainly not up to what u r indicating so cant suggest a solution, earlier in my reply, I was only
indicating my experience with custom ROMs. I havent yet come across a single custom ROM for mate 10
lite that has no problems. Earlier Galaxy S4 Mini, there was custom ROM which was awsome, not a single issue
But for mate 10 lite camera problem is most common. Stock camera app often doesnt work or partially
works, restart of the app etc. You can install open camera, but it does not give u best shots, and filters.
Other issues are already discussed in every custom ROM thread, so I had to come back to Stock ROM
with magisk to remove any system apps that I dont need plus other goodies that magisk offers u (modules)
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Tsun_Pooka said:
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Click to expand...
Click to collapse
Flash the stock erecovery whenever i root my phone i always stick with stock recovery not custom recovery(TWRP)
Theres another method to flash the stock recovery but... This is my method on how to flash stock recovery(erecovery)
PC ONLY!!! and MAKE SURE TO HAVE UNLOCKED BOOTLOADER AND FRP!!!
1.Download MultiTool from https://pro-teammt.ru/en/multi-tool-huawei-honor/
2.Make sure to install Huawei driver from the MultiTool
3.Download This File i provided Here https://mega.nz/#!nZxl2AwZ!6qRIIRbLK4Ub80dPMae4HQQ7e-O49_f2BZ8PhbuZTYM
4.Go to MultiTool and go to recovey Section an select file that you download earlier
5.Make sure to CONNECT USB CABLE TO YOR PC now Reboot your device into Bootloader mode by PRESSING VOLUME DOWN BUTTON and CONNECT THE CABLE TO YOUR PHONE
6.Now on the MultiTool click on Flash Recovery_Ramdisk andlet it flash...,
7.Now You Have The Stock Recovery Installed Now You Can Install Offical Firmware Update On Your Phone
8.All Done
I Hope I Help You
I will follow your guide later today or tomorrow! Thank you for the help!
Tsun_Pooka said:
I will follow your guide later today or tomorrow! Thank you for the help!
Click to expand...
Click to collapse
Np
LoneWolfz said:
Np
Click to expand...
Click to collapse
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
Code:
Software install failed!
Failed to check the update files
Please download the package again
> Reboot system now
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Tsun_Pooka said:
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Click to expand...
Click to collapse
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
bozka1 said:
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Deathecho said:
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Click to expand...
Click to collapse
Yes you can use the same unlock code again.
LoneWolfz said:
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
Click to expand...
Click to collapse
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Tsun_Pooka said:
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Click to expand...
Click to collapse
Np

Categories

Resources