Bricked? target reported max download size of 536870912 bytes - Nexus 5X Q&A, Help & Troubleshooting

[Solved]Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
[emoji736] Solution:
Use flashall.bat which comes with the stock recovery and give it a good deal of time to parse system.img and transfer it to the phone.

You have to wait longer.

sure thet you have flashed img files one by one? i've had the same problem flashing factory image by flashall.bat...flashing img file one by one, no prob.
but if you have this problem with manual flash, try to flash twrp and install a rom zip by twrp

hamedunix said:
Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
Click to expand...
Click to collapse
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.

ikyeye said:
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.
Click to expand...
Click to collapse
I am on stock recovery.
I managed to solve the problem by using "flash all" command instead of flashing each file separately.
Thanks for the reply though.

There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.

hamedunix said:
There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.
Click to expand...
Click to collapse
Glad that you figured it out. Make sure to update your fastboot of course. For me, flashing system.img took quite awhile longer than I recall it taking on Marshmallow but it did eventually flash for me.
Sent from my Nexus 5X using Tapatalk

It's confirmed, need updating fastboot to latest version to get it work.

Wuzimu said:
You have to wait longer.
Click to expand...
Click to collapse
Thanks. I figured it out accidentally by leaving the phone connected for a while and saw it booted up and all done with flashing.
Sent from my Nexus 5X using Tapatalk

Related

[Q] How to update to 4.4.3 with root

Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.

[Q] How to install WW firmware in a CN recovery?

I bought Zenfone 2 that initially had a WW firmware but a CN recovery. When I tried updating the firmware to UL-Z00A-WW-2.15.40.10-user, it threw an assertion failure because the device image SKU is CN while the OTA image SKU is WW. I wanted to update the firmware because of the persistent permission bug that was claimed to be solved by just updating the firmware. Since there is an assertion failure, I tried installing UL-Z00A-CN-2.14.40.22-user and it installed successfully. Unfortunately, google play store is now gone.. And I wanted to install WW OTA but it continually fails.
How do I fix this? Help.
Xegara said:
I bought Zenfone 2 that initially had a WW firmware but a CN recovery. When I tried updating the firmware to UL-Z00A-WW-2.15.40.10-user, it threw an assertion failure because the device image SKU is CN while the OTA image SKU is WW. I wanted to update the firmware because of the persistent permission bug that was claimed to be solved by just updating the firmware. Since there is an assertion failure, I tried installing UL-Z00A-CN-2.14.40.22-user and it installed successfully. Unfortunately, google play store is now gone.. And I wanted to install WW OTA but it continually fails.
How do I fix this? Help.
Click to expand...
Click to collapse
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file (http://www.mediafire.com/download/xf...oot_system.zip)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
I followed your procedure from a previous thread and it worked perfectly! Thank you.
Broken link
Link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
smartbuddy said:
1) Download recovery image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Xegara said:
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Click to expand...
Click to collapse
Will upload tommorrow. Sorry for the delay.
Same Problem. Now with CN Version and no google play etc
rootcron said:
I followed your procedure from a previous thread and it worked perfectly! Thank you.
Click to expand...
Click to collapse
Hi.. it seem that you were able to fix it.. to me its the first time trying to root or flash a phone.. what can i do in order to fix this? do you have like a step by step way .
I already download all the files and IMG files.. also i have the firmware downloads from asus support page.. i hope you can help me... thanks
Xegara said:
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Click to expand...
Click to collapse
Here you go for system.img :
http://www.mediafire.com/download/1nwpoqo8rpi1kur/Z00A_2.13.40.13_preroot_system.zip
smartbuddy said:
Here you go for system.img :
HTTP WWW mediafire DOT com download/1nwpoqo8rpi1kur/Z00A_2.13.40.13_preroot_system.zip
Click to expand...
Click to collapse
Thanks a lot! It worked! You just saved my zenfone 2! By the way, I was wondering why I needed to flash the pre-root system image if I already flashed the firmware? What is their difference aside from the pre-root system image being pre-rooted?
I installed the firmware which is UL-Z00A-WW-2.15.40.10-user. But now, the version was 2.13.40.13, same as the system.img.
So either of the images (firmware or pre-rooted system) is sufficient enough after installing the recovery image?
Xegara said:
Thanks a lot! It worked! You just saved my zenfone 2! By the way, I was wondering why I needed to flash the pre-root system image if I already flashed the firmware? What is their difference aside from the pre-root system image being pre-rooted?
I installed the firmware which is UL-Z00A-WW-2.15.40.10-user. But now, the version was 2.13.40.13, same as the system.img.
So either of the images (firmware or pre-rooted system) is sufficient enough after installing the recovery image?
Click to expand...
Click to collapse
Yes either of them should be ok. Some people are unable to update to latest ww firmware even after installing ww recovery hence need to flash pre root system.img.
Once u have installed ww recovery and ww system you have converted to ww phone and can update to any ww firmware in future.
smartbuddy said:
Yes either of them should be ok. Some people are unable to update to latest ww firmware even after installing ww recovery hence need to flash pre root system.img.
Once u have installed ww recovery and ww system you have converted to ww phone and can update to any ww firmware in future.
Click to expand...
Click to collapse
I see. I was wondering where did you find the recovery.img? The recovery.img cannot be found on asus official website. Is there a tool to extract the recovery.img of an existing android phone?
smartbuddy said:
1) Download recovery image file ...
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file ...
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
I get error, when try to flash system.img
C:\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery system.img
target reported max download size of 536870912 bytes
sending sparse 'recovery' (524257 KB)...
OKAY [ 18.063s]
writing 'recovery'...
FAILED (remote: flash_cmds error!)
finished. total time: 19.015s
there is any clue ?
sonic2epix said:
I get error, when try to flash system.img
C:\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery system.img
target reported max download size of 536870912 bytes
sending sparse 'recovery' (524257 KB)...
OKAY [ 18.063s]
writing 'recovery'...
FAILED (remote: flash_cmds error!)
finished. total time: 19.015s
there is any clue ?
Click to expand...
Click to collapse
Your command is wrong, fastboot flash recovery system.img (You are giving command to flash recovery and giving system.img )
Use the command fastboot flash system system.img
If you still get the error, try after restarting the PC.
smartbuddy said:
Your command is wrong, fastboot flash recovery system.img (You are giving command to flash recovery and giving system.img )
Use the command fastboot flash system system.img
If you still get the error, try after restarting the PC.
Click to expand...
Click to collapse
Oops, sorry .. my command is wrong, thanks ..
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
help with zenfone 2
I ordered a zenfone 2 from Taiwan but its the ww version. My question is....I ordered it because it says that it supports 1700mhz/2100mhz and aws band 4...I am with Mobilicity in Canada...For the life of me I cannot get this stupid phone to recognize my sim card. Ive messed around with the settings, changed sim card slots...tried everything I can think of, and its still not working. Will this method (or any you know of) get it working?
Are 2nd Set of Steps Necessary?
smartbuddy said:
1) Download recovery image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
First of all, thanks so much smartbuddy for taking the time to write up these steps and provide the necessary files. I've been working on this issue for 12+ hours and am now finally resolving with your information. I just have a couple of questions.
I completed the first set of steps without issue and ended up right where I wanted to be - with the most recent firmware version and the ability to check for software upgrades OTA (finally had the button now!). I then went through the second set of steps without issue until I booted my phone after clearing the cache - it hung while booting. I waited for like 15-20 min. and then rebooted, but it hung again. No errors or anything, just booting. So when this happened, I went back through the first set of steps and am now again right where I want to be - with the firmware I want and the ability to check for upgrades OTA.
So do I have to attempt to go through the second set of steps again? And if so, do you have any idea why my phone hung while doing so the first time? Also, with my phone in it's current state, if I were to do a factory reset in the future, would it take me all the way back to square one without any of these updates? Sorry if this is a nube question, I'm still learning.
Thanks again for all your help. You da man! :good:
tapierce said:
First of all, thanks so much smartbuddy for taking the time to write up these steps and provide the necessary files. I've been working on this issue for 12+ hours and am now finally resolving with your information. I just have a couple of questions.
I completed the first set of steps without issue and ended up right where I wanted to be - with the most recent firmware version and the ability to check for software upgrades OTA (finally had the button now!). I then went through the second set of steps without issue until I booted my phone after clearing the cache - it hung while booting. I waited for like 15-20 min. and then rebooted, but it hung again. No errors or anything, just booting. So when this happened, I went back through the first set of steps and am now again right where I want to be - with the firmware I want and the ability to check for upgrades OTA.
So do I have to attempt to go through the second set of steps again? And if so, do you have any idea why my phone hung while doing so the first time? Also, with my phone in it's current state, if I were to do a factory reset in the future, would it take me all the way back to square one without any of these updates? Sorry if this is a nube question, I'm still learning.
Thanks again for all your help. You da man! :good:
Click to expand...
Click to collapse
No you can skip that if you wish. I have moved to Oneplus 2 so dont have a zenfone 2 anymore.

Stuck on installing ROM

So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?
TheOnlyPaulV said:
So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?
Click to expand...
Click to collapse
First of all, I'm not sure whether flashing the official Huawei partition images will work if they are flashed from TWRP (I've never tried it). However, I do know that it works without problems when flashed in fastboot mode. Secondly, if TWRP was flashed as the recovery and you chose the TWRP inbuilt root option, it would have replaced your BOOT partition as well. So to repair this, you'd have to flash the official Huawei BOOT partition as well. BTW, I was in a similar state (bootloop/no boot) a couple of times (see my post here) and both times was able to recover by flashing the official Huawei BOOT.img and RECOVERY.img partitions to my device.
So, to get your device back into a decent shape, try flashing the BOOT.img as well as the RECOVERY.img from the official Huawei ROM for your device, performing the flashing in fastboot mode. I have written a guide which details extracting and flashing official Huawei partitions. Best of luck
It is obvious that I am missing something very simle here and I'm very interested in finding out what it is I'm doing wrong
So I have a TWRP booting tablet.
I downloaded the latest image from the roms thread on this forum which gives me a zip file called "M2-801LC100B205.zip".
I extract this and open it in Huawei extracter tool.
I extract the BOOT, RECOVERY, SYSTEM and CUST to separate .img files.
I flash all 4, one after the other using the commands listed in your guide:
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
They all flash okay (it seems), an exmaple of the flash is:
C:\platform-tools>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (454239 KB)...
OKAY [ 17.471s]
writing 'system' 1/6...
OKAY [ 5.909s]
sending sparse 'system' 2/6 (449072 KB)...
OKAY [ 16.927s]
writing 'system' 2/6...
OKAY [ 5.788s]
sending sparse 'system' 3/6 (459356 KB)...
OKAY [ 17.035s]
writing 'system' 3/6...
OKAY [ 5.894s]
sending sparse 'system' 4/6 (442527 KB)...
OKAY [ 17.781s]
writing 'system' 4/6...
OKAY [ 5.713s]
sending sparse 'system' 5/6 (447342 KB)...
OKAY [ 20.828s]
writing 'system' 5/6...
OKAY [ 5.736s]
sending sparse 'system' 6/6 (67700 KB)...
OKAY [ 2.524s]
writing 'system' 6/6...
OKAY [ 0.864s]
finished. total time: 122.498s
C:\platform-tools>
But still I have a tablet that is stuck on the boot screen. I can still get back to the fastboot recovery so I can still flash but I seem to be missing WHAT to flash?
Surely there must be a complete .img file some where I can flash in flash boot which will just get the thing back and working?
It seems like I'm flashing lots of small simple things when I just want a complete image from some where to flash?
I cant flash the downloaded zip files via fast boot it seems?
Does one exist of have I missed some thing?
Update:
I downloaded a ZIP file of a full rom as detailed above, installed TWRP and tried to flash the zip: it fails stating it could not mount the system partition and radio firmware does not exist. I assume this is because the file downloaded is an update and not a complete rom?
I used TWRP to format and resize the system partition and it reports 0mb in size and fails.
I really think I just need a plain original simple complete rom to flash, in a ZIP format for TWRP: the updates all seem to assume its being flashed onto a working system as an update and I don't have a full base install.
Surely this base simple rom must exist some where?
Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?
TheOnlyPaulV said:
Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?
Click to expand...
Click to collapse
Hmmm... I expected you to only flash the boot and recovery images as mentioned in my previous reply (and not other partition images, the example text in my guide was just that - an example) from your original ROM version, not from a downloaded ROM version. If your original ROM was a lollipop ROM and not marshmallow, B205 is a mm ROM and would require a full ROM flash, and in this case a bits-and-pieces flash would not work, and cause a non-booting device. A bits-and-pieces flash especially of any device partition other than BOOT and RECOVERY should ideally be done only with the ROM version which is currently installed and (previously known to be) working.
If you can connect the phone to your computer long enough to transfer over the full ROM image to the device, you should be able to flash that using the original Huawei recovery. The instructions are present on the forum thread where you found the ROM. Alternatively, if you know what version the original ROM was on your device, you can flash its SYSTEM and CUST over.
Yes, that's what I would like to do and I can do that, fast boot still works, but it's where do I get a FULL ROM from? Everything on this forum I have found is an update and relies on another working ROM to be present.
Where do I get the full ROM from, do we know the name of one which is not an upgrade ROM?
It's this full ROM I've been looking for to no avail
Please confirm your device model and I'll try to find a full ROM image download (Marshmallow) for you.
EDIT: by full I mean a ROM which is a complete image (about 2-3GB) instead of a partial OTA update. Also, I'm not certain that you can flash a full Huawei official ROM image from fastboot; it requires booting into the recovery. AFAIK Booting into the recovery does not need a working ROM system partition.
Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l
Sorry to bug but have you, or any one else, had any luck in finding a full rom?
Any one have a twrp backup of a basic fulll booting rom I could try?
I do appreciate all the help!
TheOnlyPaulV said:
Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Click to expand...
Click to collapse
Sorry for the delayed reply, I've been pretty ill for the last few days.
Here are links to what I'm pretty certain are the OEM Lollipop full ROMs for the 801L. All those links are 1.4GB zipped, which means that they should unzip to about 2.5-3GB, which indicates that it is a full ROM:
801L B006 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=57706&version=181649&siteCode=my
801L B007 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=71503&version=254039&siteCode=my
801L B003 on Huawei Russian support site (): http://download-c.huawei.com/download/downloadCenter?downloadId=71523&version=254048&siteCode=ru
You'll need to get the unzipped ROM folder onto your external SD card somehow, to be able to flash it with the Huawei recovery.
Here are some steps you can follow:
Part 1: Download ROM, extract it and then copy extracted ROM directory to sdcard on phone
In this part, we will download the ROM, extract it, and transfer the extracted ROM to your M2 using TWRP and ADB. Make sure that you have the Mediapad drivers installed, and adb and fastboot installed and available.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.
On Linux, just install the Android Command Line tools from Google.
For the phone drivers, just install HiSuite from Huawei - this will install the Mediapad device drivers. You can then uninstall HiSuite - the drivers will still continue to remain installed even if HiSuite is uninstalled, and this way you won't clutter up your computer with the useless HiSuite.
Now download one of the ROMs listed above (I suggest starting with B007. If that doesn't work, try B003 and then B006).
Unzip the downloaded ROM onto some location on your computer's hard drive. Let's say that on Windows, you unzip it to D:\MYROM
In D:\MYROM, you should find a directory called dload
Make sure that you have TWRP as the recovery on the phone. Flash TWRP onto the phone if you need to (since you already know how to do this, I won't go into more detail).
Boot into the TWRP recovery on the phone (since you already know how to do this, I won't go into more detail).
In TWRP, make sure that MTP mode is off. To do this, in the TWRP main menu, press "Mount". In the "Mount" screen, check whether the second (right-hand-side) button on the bottom reads "Enable MTP". If it says "Enable MTP", then you do not need to do anything else here, go back to the main TWRP screen. If the button says "Disable MTP", press it so that the button now reads as "Enable MTP". Setting MTP mode off will ensure that you can connect via ADB to your phone.
Now open a terminal/command-prompt window on your computer (Run->"cmd" or search for "cmd" on Windows).
In the terminal window, navigate to the directory where the unzipped ROM is present. On Windows, using the above example ROM unzip location, you would type
Code:
d:
cd D:\MYROM
Type the following ADB command to make sure that your phone is recognized by ADB:
Code:
adb devices
If it works, you should see something like
Code:
List of devices attached
ABCD1234567890 recovery
where "ABCD1234567890" will actually be your device ID string, and not literally "ABCD1234567890"
If you see a string like the above, good news, it means that your phone is recognized by ADB, and we can now transfer the unzipped ROM to your SD card. If you do not see anything after the "List of devices attached" string, make sure that you have turned off MTP mode in TWRP as detailed above. If you still don't get anything, you will have to transfer the unzipped ROM to your sdcard by some other means - perhaps by putting the SD card in another phone. Skip the rest of the steps here and see Part 1.5 below.
Now type the following command in your computer's terminal window (command below is for Windows; on Linux, replace "D:\dload" with the appropriate path to the dload directory):
Code:
adb push D:\MYROM\dload /sdcard
This will copy the extracted ROM's "dload" directory to the root of your internal SD card. To copy it to the root of your external SD card, replace "/sdcard" in the above command with "/external_sd".
If all went well with the above command, then at this point your extracted ROM's "dload" directory should have been copied over from your computer to your phone (either on the root of the internal SD if you used "/sdcard" in the "adb push" command, or on the root of the external SD if you used "/external_sd" in the "adb push" command. Go to Part 2 below.
Part 1.5: Copy extracted ROM directory to external sdcard on phone using another phone.
SKIP THIS PART IF YOU SUCCESSFULLY COMPLETED ALL STEPS IN PART 1 ABOVE, AND GO TO PART 2 BELOW!
Remove the external SD card from your M2.
Insert the external SD from the M2 into some other phone/device.
Connect that phone to your computer via USB.
Transfer the unzipped ROM's "dload" folder to the root of the SD card.
Remove the SD card from the other phone and put it back into your M2.
Part 2: Flash official Huawei BOOT.img and RECOVERY.img and installed extracted ROM using official Huawei Recovery
In this part, we will replace TWRP with the official Huawei recovery and boot partitions, and use the official Huawei recovery to flash the ROM on the phone.
From the ROM you downloaded in Part 1 above, extract BOOT.img and RECOVERY.img using the Huawei Update Extractor. Since you already know how to do this, no further details will be given.
Flash the official Huawei BOOT.img and RECOVERY.img partitions (for safety, do not flash any other partitions) onto your M2. to refresh your memory on how to do this, see my guide.
After successfully flashing the official Huawei BOOT.img and RECOVERY.img partitions to your M2, you can flash the downloaded ROM as an update by booting into the Huawei recovery which you just flashed onto your M2. After booting into the Huawei recovery, it should automatically detect and start installing the downloaded ROM.
Hope this helps. Good luck!
TheOnlyPaulV said:
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l
Click to expand...
Click to collapse
That won't be necessary, but thanks for the offer I'm just trying to help out people wherever I can; I don't want anything in return
Hello, "different customer" here
I came into the same situation, a while ago I wiped a lot of things (through TWRP) making my tablet unbootable, I was trying to recover from a bootloop.
I followed this well written guide but the stock recovery won't detect the new ROM (I have a dload folder with META-INF directory inside and UPDATE.APP).
I flashed the BOOT.img and the SYSTEM.img while at fastboot mode. At the sdcard there is a folder dload with the rest.
Booting up with pressed + and - is starting to "Installing update" but hangs at 5%
What should I do
Well finally I managed to fix it, twice! here is the story.
After I left it for half an hour saying "Installing update 5%" I decided to reboot.
Tablet booted ok but there was problem with WiFi, couldn't switch to On.
I decided to reflash http://update.hicloud.com:8180/TDS/d...1LC100B206.zip once again but still nothing, I tried B002, B005 but no success with the WiFi (this wifi problem is something I did when I was fing around at the bootloader with fastboot).
Then I decided to flash the SimplyGoogle, that got me in a bootloop.
Ok I said now I will fix it once and for all.
Then I entered TWRP, wiped EVERYTHING and I got this http://update.hicloud.com:8180/TDS/d...1LC100B206.zip uploaded to the /sdcard/dload.
Next step was fastboot mode, flashed BOOT.img, System.img and recovery.img from the extracted UPDATE.APP of the M2-802L once again (keep in mind I have the M2-801L).
Now it was time to poweron with + and - pressed so the recovery to understand I need a system update/flash.
Again it was stuck at 5% but now I knew just left it hanging for an hour and rebooted.
And it worked.
At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.
lepidas said:
At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.
Click to expand...
Click to collapse
You're welcome, glad I could be of assistance
Your posting of your experiences may help someone else who runs into a similar issue, so thank you for taking the trouble to post in detail :good:
Im afraid I am not quite as advanced as your self, I dont know what a 'META-INF directory inside and UPDATE.APP' is so please bear with me, especially if im preaching to the converted.
My problem was that I had a, basically, blank device.
The only thing that remained was the boot and recovery.
The first thing I got wrong is that the device is partitioned into multiple parts, its not one rom image for it all thus flashing a update rom wont write over all the partitions to recover the device, it will only flash the ones its updating thus you need an image that has alll the partitions to recover from a wiped device.
Second problem I has was that the TWRP recovery will not allow flashing of complete roms and I didnt have a backup of a complete rom.
Third problem I had was getting a hold of a 'complete image'.
So the link above allow you to download a complete image. part1 done.
then extract the boot partition from the complete image as the complete rom will only install/boot from its own boot partition: you cant install a complte from from a TWRP partition.
flash the bootimage from the complete rom.
copy it to the SD card, install it from there.
Then, once you have your system up and running, install your updates ot get the unit back.
Hope that makes sense and ive not just repeated things you already know, but thats as far as my knowledge goes

Fastboot issues with G3

Hi,
I've got a G3 (D855) which I rooted about 6 months ago but was never able to install TWRP on. I flashed the image but when I tried to boot into recovery I got a black screen with a tiny error message (and I mean tiny, could barely read it) saying 780(?) fastboot error.
Now I get the same message when I try to do a factory reset.
Tried to flash back to stock with LG flash tool but had an error with a milky way connection!??
The phone works fine but I want to be able to do nandroid backups and maybe install a custom ROM. Can anyone help?
Thanks
Munky99: take the latest TWRP-version, check md5, try simple adb/fastboot commands to test connection
rp158 said:
Munky99: take the latest TWRP-version, check md5, try simple adb/fastboot commands to test connection
Click to expand...
Click to collapse
Thanks rp158. I don't know what all of that means.
I've got the latest .img file for my device. There was also a .asc file which I ignored.
I don't know how to check the md5.
In powershell on my pc, I get device null not found.
@Munky99
TWRP: you're right, here is no md5 to control. But to be safe, download again and check file-size.
FASTBOOT: if you cannot see your device, reinstall LG-drivers and ADB/FASTBOOT-mini-package.

unbrick Nokia 3.2

Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.

Categories

Resources