Related
So, I looked a lot, but I couldn't find nothing useful.
I flashed Ubuntu Phone, tried and than flashed the stock ROM again. But after that, the phone didn't make any call, send/receive SMS or use GPS.
1 .I tried a lot of custom ROMS, SIM cards, back to the original ROM (download from google) and the radio from stock ROm, a lot of tutorials and nothing worked.
2. I read something about the EFS folder, but I couldn't find this using the app Root Explorer (I bought it!). Than I read the Nexus has no EFS floder.
Here are some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone can help me?
Thanks a lot!
Flash the radio from stock ROM
Sent from my Nexus 7 using Tapatalk 4
cmason37 said:
Flash the radio from stock ROM
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks, but I forgot to write that. I tried this too! :/
Backup /data and flash stock ROM
Sent from my Nexus 7 using Tapatalk 4
cmason37 said:
Backup /data and flash stock ROM
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I tried this, several times. I downloaded from developers.google.com
Did you check to see if your APNs were right or if your SIM card was corrupt? If that doesn't work, try to fastboot format all your partitions before installing stock ROM.
Sent from my Nexus 7 using Tapatalk 4
cmason37 said:
Did you check to see if your APNs were right or if your SIM card was corrupt? If that doesn't work, try to fastboot format all your partitions before installing stock ROM.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I'm using my SIM card in another android and it´s working. I also tried others SIM card's in my phone.
I format using the recovery mode. Do you mean format using fastboot in ubuntu terminal? If yes, could you help with the commands?
ps: I flashed all ROMS using fastboot in ubuntu 12.04 terminal.
No, fastboot format <partition> in a terminal. Also formatting the bootloader is not reccomended but if you do format bootloader DO NOT reboot until you flash it again. May seem obvious but a lot of people brick their Nexus that way...
Sent from my Nexus 7 using Tapatalk 4
cmason37 said:
No, fastboot format <partition> in a terminal. Also formatting the bootloader is not reccomended but if you do format bootloader DO NOT reboot until you flash it again. May seem obvious but a lot of people brick their Nexus that way...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Well, I did it but now it is in bootloop. Than I flashed the last cyanogem stable, but still in bootloop.
Now I gonna try Nexus Root Toolkit v1.7.1, but I have no Windows here, so I'll wait until monday to try and when get the results I'll post them here!
wwwbruno said:
Well, I did it but now it is in bootloop. Than I flashed the last cyanogem stable, but still in bootloop.
Now I gonna try Nexus Root Toolkit v1.7.1, but I have no Windows here, so I'll wait until monday to try and when get the results I'll post them here!
Click to expand...
Click to collapse
Okay, assuming you formatted, you shouldn't need cyanogenmod. Do:
fastboot format boot
fastboot format system
fastboot format recovery
fastboot format data
....................................
Then, download the 4.3 factory image from Google and run the flash-all.bat. You should be golden after that
Sent from my Nexus 4 using xda premium
Tanmaynarang said:
Okay, assuming you formatted, you shouldn't need cyanogenmod. Do:
fastboot format boot
fastboot format system
fastboot format recovery
fastboot format data
....................................
Then, download the 4.3 factory image from Google and run the flash-all.bat. You should be golden after that
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So, I followed a tutorial and did this commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot update –w image-occam-jwr66v.zip
And after this, my phone got in bootloop. I tried the Nexus Root Toolkit v1.7.1 but it seems do the same commands above and the same results.
I'll try to do what you've told me and post here later.
Thanks a lot!
I am not familiar with Ubuntu phone; however, if it has modified the partitions on the Nexus, you will need to use Gigadroid's unbrick method at http://forum.xda-developers.com/showthread.php?t=2347060 in order to rewrite the proper partitions and allow you to flash a ROM successfully.
Tanmaynarang said:
Okay, assuming you formatted, you shouldn't need cyanogenmod. Do:
fastboot format boot
fastboot format system
fastboot format recovery
fastboot format data
....................................
Then, download the 4.3 factory image from Google and run the flash-all.bat. You should be golden after that
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I tried this but I got some errors, any way I keep downloading the stock and ran the ./flash-all.sh (I use linux) but it is still in bootloop
# fastboot format boot
formatting 'boot' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.002s
# fastboot format system
erasing 'system'...
OKAY [ 0.048s]
formatting 'system' partition...
Creating filesystem with parameters:
Size: 880803840
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 3360
Label:
Blocks: 215040
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/53760 inodes and 6965/215040 blocks
sending 'system' (15680 KB)...
writing 'system'...
OKAY [ 1.457s]
finished. total time: 1.505s
# fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.002s
# fastboot format data
formatting 'data' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.002s
Now I gonna try the link that BobWalker send.
Thanks a lot!
BobWalker said:
I am not familiar with Ubuntu phone; however, if it has modified the partitions on the Nexus, you will need to use Gigadroid's unbrick method at http://forum.xda-developers.com/showthread.php?t=2347060 in order to rewrite the proper partitions and allow you to flash a ROM successfully.
Click to expand...
Click to collapse
Thanks a lot, my phone get out from bootloop and now it is working, but is still without IMEI and BaseBand. Any sugestions?
wwwbruno said:
Thanks a lot, my phone get out from bootloop and now it is working, but is still without IMEI and BaseBand. Any sugestions?
Click to expand...
Click to collapse
Download the latest radio (.84) from efrant's page at http://forum.xda-developers.com/showthread.php?t=2087227 and install it in recovery. I can't help you with the IMEI though With a little luck the IMEI may reappear spontaneously after flashing the radio.
BobWalker said:
Download the latest radio (.84) from efrant's page at http://forum.xda-developers.com/showthread.php?t=2087227 and install it in recovery. I can't help you with the IMEI though With a little luck the IMEI may reappear spontaneously after flashing the radio.
Click to expand...
Click to collapse
Well, I tried, but still no radio.
I notice that in fastboot, the baseband version is showing "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.84", but in "Settings > About phone" is showing "Unknown". Is this right?
wwwbruno said:
Well, I tried, but still no radio.
I notice that in fastboot, the baseband version is showing "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.84", but in "Settings > About phone" is showing "Unknown". Is this right?
Click to expand...
Click to collapse
The correct radio is registering in fastboot. I do not know why the phone settings continue to show baseband "Unknown".
same problem
I have the exact same problem and out of ideas. I hope someone could enlighten us. Thank you
coolau said:
I have the exact same problem and out of ideas. I hope someone could enlighten us. Thank you
Click to expand...
Click to collapse
having same problem, tried everything everyone suggested with no luck
any updates?
GuyZapPa said:
having same problem, tried everything everyone suggested with no luck
any updates?
Click to expand...
Click to collapse
I had the exact same issue - Android 4.3, 0.84 radio, showing no baseband, no imei - and when I turn on the phone, there is no service at all. Try flashing the 0.54 or earlier radio. Your IMEI, baseband will reappear on your phone, but now you will not have any audio in call. I am not sure what's the next step, someone please help, do you have any suggestions ?
So as far as I know, I am one of the first people to have the bootloader unlocked on the Chinese Mate 9.
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
We can flash small files, can flash recovery, etc. So we need someone to make TWRP in order to do anything with the unlocked BL. Since there's no source out for the Mate 9, I'm worried about that, but hopefully @raimondomartire can get it done!
Update: I've built a preliminary TWRP, but I don't understand TWRP well, and the mount points are incorrect. However, I believe we will have a working TWRP very soon.
Solid info. Thanks. Once more developers start hopping on, I'm sure we'll get to this faster especially after the fact that you managed to already get the bootloader unlock.
Ahh, progress. Almost there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good job !!!!
Congrats
أرسلت من HUAWEI NXT-L29 بإستخدام تاباتلك
duraaraa said:
I have some unfortunate findings. Mainly, you cannot flash large files over fastboot. Here's what happens:
target reported max download size of 471859200 bytes
sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 10.869s
Click to expand...
Click to collapse
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797
Job well done!
5[Strogino] said:
I don't think, that it can stop xda community
http://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
Thank you for the idea. Unfortunately, when I tried this tool, it required that the image size is a multiple of 4096 bytes. So I appended null bytes to the end until it was a multiple, split, and flashed all the files, but it doesn't boot.
An update. I hate TWRP mounting /system, /data, /cache, and so on. The only one that doesn't mount is 3rdmodem (I can't even find it in the filesystem.) The data partition and /sdcard partition seem to be encrypted. USB doesn't work (yet)
When I try to flash supersu, the phone crashes and reboots just after the message that it's trying to do a systemless install and creating space...
I tried flashing the zip from Huawei's google services download. That flash worked.
I can't flash any regular huawei updates without a lot of work, so I haven't made an honest effort at unpacking the update.app's partitions and making them into flashable zip files.
So we're kind of stuck unfortunately, with not very much we can do, despite the bootloader being unlocked.
That's all I've got for you all for now.
How do you do to unlock the bootloader once you got the code
playa77176 said:
How do you do to unlock the bootloader once you got the code
Click to expand...
Click to collapse
If you don't know how to do it you might be better off not doing it because there is some risk involved with it at this point.
If you want to try anyway turn off the phone and plug in a USB cable while holding volume down key.
Then run the command on your computer
fastboot oem unlock CODE
Replace code with your code.
Update. I just figured out how to flash a rom via fastboot. Going to try flashing European newest rom on Chinese mate momentarily.
Update: The error I mentioned in my previous post (sending sparse 'system' (433085 KB)...
OKAY [ 10.825s]
writing 'system'...
FAILED (remote: sparse flash write failure)
)
This error doesn't occur if I'm flashing the Chinese firmware. Only if I flash the European firmware.
Something is not quite right. I'm download other version of Euro firmware to check.
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
Maybe you need an updated fastboot files?
It's possible to unlock With srktool ?
playa77176 said:
It's possible to unlock With srktool ?
Click to expand...
Click to collapse
I think it's best you stick to the regular fastboot commands. SRKTool is for the older Mate, so it might want to flash an incompatible TWRP or something like that.
gm007 said:
Maybe you need an updated fastboot files?
Click to expand...
Click to collapse
I've tried every version of fastboot I can find, on every platform. That's not the issue. I'm going to try and find a way though!
duraaraa said:
Update: The results of which firmwares I can and can't flash via fastboot are pretty much the same as the ones that I could and couldn't flash through eRecovery/HiSuite, without unlocking the bootloader. We need to find a way to flash the system partition from TWRP, with original Huawei images, if we hope to get European builds on the Chinese Mate. Looking pretty bad right now unfortunately. Much more difficult than the Mate 8 / Android 6.
Click to expand...
Click to collapse
The problem is that fastboot does not allow flash very big files.
Solution is to divide file on chunks.
Unfortunately, i don'y have Mate 9.
Try this:
Code:
fastboot -S 256M system path_to_system.img
p.s. You should use actual fastboot version (SDK version)
Good evening everyone,
Hope to find the answer here.
I have a p9 lite vns-l33 I wanted to install Android 7 on and it has, of course, bricked!!
Since I am stuck on the screen that warns that the device is unlock and the message "your device is booting now ...."
http://www.hostingpics.net/viewer.php?id=862217IMG20161217001029.jpg
Nothing happens is the screen stays on I can not even turn off such.
I have access to fastboot, my phone is unlock. So I tried to put twrp nothing to do, to restart boot, recovery, system and believed from an official image in b100. But nothing to do comes back to the same screen.
I tried to boost fastboot on twrp but nothing to do
The I'm blocked would you have an idea?
This stuck should cause by trying trying to boot mm twrt in nougat.
Don't have dload in scard,just press volume+,volume-,and power, boot into eRecovery flash process then restart is okey
Otherwise, you can also flash stock nougat recovery , put update .app on sd card and have a dload flashing. like:
Code:
fastboot flash recovery recovery.img
If flash recovery failed/ command not allowed, unlock first
Code:
fastboot oem unlock your former_unlock_code
thank you for your reply
I do not have the update.app on the sd card because my erecovery does not allow me to install it. It just allows me to reinstall by wifi but it crashes.
For Fastboot is what I need to extract from recovery.img update.app or it does it all by itself?
Thank you for your help
You'll have to go the hard route. You'll find all the required files in the ROM section.
Download any Nougat.zip (329 worked for me, 336 did not). Unzip. You'll get the update.app.
Download the second file with all the missing apps. Do not unzip. Maybe rename to something shorter like data.zip.
Download Revolution Recovery for Nougat. Unzip. You get the recovery.img. RENAME to something like revolution.img.
Open update.app in Huawei Update Extracor. Extract recovery.img, boot.img and system.img to wherever your fastboot.exe is. It's practical to put it all in one directory so you don't have to type long paths.
Now, careful...
Go into Fastboot. If Vol- + Power doesn't work, let it boot into eRecovery, press Vol- and tap Reboot. There you are.
Open a command window in the dir with fastboot.exe and the .img files (right click, Open Command Window)
fastboot flash boot boot.img
.... OK
fastboot flash system system.img
.... sparse 1/5 or something, this takes a bit of time.
fastboot flash revolution.img
.... OK
Now DO NOT REBOOT into System. Hold Vol+ + Power while still in Fastboot. It'll boot into Revolution eventually. Tap Advanced, ADB Sideload. Swipe.
Back in your command window, type:
adb sideload second_file.zip
... working... this'll take a bit. There might be an error message like 'could not mount /data'. Doesn't matter at this point.
When done, type
fastboot flash recovery recovery.img (this is the stock recovery you extracted from update.app)
... OK
Reboot to recovery from Revolution.
Do factory reset. Note: If you don't do this last step, there will be a bootloop.
Reboot. The system should now boot up normally. At least it did for me... good luck.
THX !!!! i can boot !!!
But :
dancress said:
fastboot flash revolution.img
.... OK
.
Click to expand...
Click to collapse
when i try this , it's not work. Fastboot say :
unknown partition 'revolution.img'
error: cannot determine image filename for 'revolution.img'
I'm try : fastboot flash recovery revolution.img and after i reboot my phone with Hold Vol+/- + Power and only after my phone boot into Revolution eventually.
After this work :
dancress said:
Back in your command window, type:
adb sideload second_file.zip
... working... this'll take a bit. There might be an error message like 'could not mount /data'. Doesn't matter at this point.
.
Click to expand...
Click to collapse
But
dancress said:
When done, type
fastboot flash recovery recovery.img (this is the stock recovery you extracted from update.app)
... OK
.
Click to expand...
Click to collapse
don't work.
Finally
dancress said:
Reboot to recovery from Revolution.
Do factory reset
.
Click to expand...
Click to collapse
I don't find factory reset in Revolution ....
I'm one question why, in parametes, my android model is ?????
Ok after want to format phone with Revolution now when i'm a black screen???? why?
BenouLM said:
THX !!!! i can boot !!!
But :
when i try this , it's not work. Fastboot say :
unknown partition 'revolution.img'
error: cannot determine image filename for 'revolution.img'
I'm try : fastboot flash recovery revolution.img and after i reboot my phone with Hold Vol+/- + Power and only after my phone boot into Revolution eventually.
After this work :
But
don't work.
Finally
I don't find factory reset in Revolution ....
I'm one question why, in parametes, my android model is ?????
Click to expand...
Click to collapse
1. fastboot flash recovery revolution.img in Fastboot - sorry, mistyped. Was in a hurry.
2. Fu**ed up there too. You need to reboot directly into Fastboot from Revolution, then flash the stock recovery. Then boot into it (Vol+ + Power) before anything else and do the factory reset.
SORRY. One should not type such relatively sensitive things while already late for something
dancress said:
Then boot into it (Vol+ + Power) before anything else and do the factory reset.
Click to expand...
Click to collapse
Thx but now i can open eRecovery ....
I managed to do everything you said but now I have nothing more ....
I have at all erased and my such does not boot anymore.
I can not reinstall android with Revolution ....
I do not know what to do
Then I succeeded to have eRecovery but it does not install anything and I can not do a reset
I would like to go back to the original configuration with android 6 .0
Ok I summarize:
- I made a data format I have nothing on my phone
- I just have recovery Revolution and fastboot that works
- I can not install anything by eRecovery and Revolution crash
- I would like to reinstall original when I installed N.
Thank you for your help
plz help
Current version: VNS-L31C900B058
Extracting partitions
Cannot create extract directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\tmp\20161217_221104_UPDATE\
Extract files to directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM_FW OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CUST.img
CUST partition UPDATE ...OK
Software written
17/12/2016 22:18:50 Writing device finished OK
AND :
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing VENDOR partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\VENDOR.img
VENDOR partition UPDATE ...FAILED
Writing PRODUCT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\PRODUCT.img
PRODUCT partition UPDATE ...FAILED
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Software written
17/12/2016 22:42:08 Writing device finished - INCOMPLETE
BenouLM said:
plz help
Current version: VNS-L31C900B058
Extracting partitions
Cannot create extract directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\tmp\20161217_221104_UPDATE\
Extract files to directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM_FW OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CUST.img
CUST partition UPDATE ...OK
Software written
17/12/2016 22:18:50 Writing device finished OK
AND :
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing VENDOR partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\VENDOR.img
VENDOR partition UPDATE ...FAILED
Writing PRODUCT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\PRODUCT.img
PRODUCT partition UPDATE ...FAILED
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Software written
17/12/2016 22:42:08 Writing device finished - INCOMPLETE
Click to expand...
Click to collapse
Why did you use dc-phoenix ?!
Dc Phoenix may break your phone !
After that you have done your phone booted up right ? But he falls on a bootllop
So download b336 version, with your computer using huawei update extractor , extract recovery
After in fastboot command type :
fastboot flash recovery RECOVERY.img
After boot to recovery, do a Factory reset and wipe cache
simo255 said:
Why did you use dc-phoenix ?!
Dc Phoenix may break your phone !
After that you have done your phone booted up right ? But he falls on a bootllop
So download b336 version, with your computer using huawei update extractor , extract recovery
After in fastboot command type :
fastboot flash recovery RECOVERY.img
After boot to recovery, do a Factory reset and wipe cache
Click to expand...
Click to collapse
I use Dc_Phenix because I read in another post that it had worked for some people.
I take the B336 http://www.gizrom.com/b336-huawei-p9-lite-android-6-0-ota/ or http://forum.xda-developers.com/huawei-p9lite/development/android-7-emui-5-0-vns-l31-l21-l23-t3513816 but I do not get anything. Either the wipe does not work as it does not give me the ability to do it ...
I'm really stuck ...
simo255 said:
After boot to recovery, do a Factory reset and wipe cache
Click to expand...
Click to collapse
After boot to Recovery the phone stay to installing update 5% :
http://hpics.li/63a6275
A few minutes after the phone restarts and nothing has changed.
If youre Still on MM because the Nougat Update failed, even the Revolution Recovery wont work, in this case you need Meticulus Recovery. it even may get flashed by revolution rec, but i dont know if it uses the exactly same partition paths.
It even May help to Root your phone if your bootloader is open and you got a working recovery. The SuperSU patches the boot.img with the required ramdisk etc and reflashes it.
Your Stucking between the Unlocked message and the Logo ( Which would be shown next ) is a signal for an incompatible boot.img, otherwise ( if it is the right but broken it would get stuck in after the Huawei Logo. )
even regard that you have unplugged the phone from your Computer when you try to flash the update.app via Vol Up+ Down + Power, otherwise it aborts at around 5% or shows an error that its not possible. I Worked on the Same problem for 16 Hours till i got it fixed.
For me the following Chain worked : Installed the nougat recovery for file manager Access, created the dload folder on the external sd, and putted the b150 Update.app to it, flashed the Recovery from "vovler de nougat a MM p9 lite.zip" and flashed the oeminfo "C432OemInfo-DUALSIM-P9LITE.zip" ( relocks the bootloader ). After this the Stock Hardflashing worked, rebooted to erecovery and wiped data and cache. Unlocked the Bootloader again, flashed meticulus twrp and rooted the phone ( Systemless, to path the boot.img ) Then i flashed the flashable Firmware ( For me it was CM13 but it should work with MEDROM too )
Just think about if you flashed CM13 anytime your dataencrypten will get lost ( Then The recovery tells you its unable to Mount /data ) then the whole intern storage needs a wipe.
Some of this May work for you, but some may not. But i guess a Softbrick cant even get much worser and i dont know a hardbricked huawei, so its up to you to give it a try or not, otherwise the Huawei Support May Help you for a little Donation ( at least i think they do, ive never spoken to one of them )
WieserZ1C said:
If youre Still on MM because the Nougat Update failed, even the Revolution Recovery wont work, in this case you need Meticulus Recovery. it even may get flashed by revolution rec, but i dont know if it uses the exactly same partition paths.
It even May help to Root your phone if your bootloader is open and you got a working recovery. The SuperSU patches the boot.img with the required ramdisk etc and reflashes it.
Your Stucking between the Unlocked message and the Logo ( Which would be shown next ) is a signal for an incompatible boot.img, otherwise ( if it is the right but broken it would get stuck in after the Huawei Logo. )
even regard that you have unplugged the phone from your Computer when you try to flash the update.app via Vol Up+ Down + Power, otherwise it aborts at around 5% or shows an error that its not possible. I Worked on the Same problem for 16 Hours till i got it fixed.
For me the following Chain worked : Installed the nougat recovery for file manager Access, created the dload folder on the external sd, and putted the b150 Update.app to it, flashed the Recovery from "vovler de nougat a MM p9 lite.zip" and flashed the oeminfo "C432OemInfo-DUALSIM-P9LITE.zip" ( relocks the bootloader ). After this the Stock Hardflashing worked, rebooted to erecovery and wiped data and cache. Unlocked the Bootloader again, flashed meticulus twrp and rooted the phone ( Systemless, to path the boot.img ) Then i flashed the flashable Firmware ( For me it was CM13 but it should work with MEDROM too )
Just think about if you flashed CM13 anytime your dataencrypten will get lost ( Then The recovery tells you its unable to Mount /data ) then the whole intern storage needs a wipe.
Some of this May work for you, but some may not. But i guess a Softbrick cant even get much worser and i dont know a hardbricked huawei, so its up to you to give it a try or not, otherwise the Huawei Support May Help you for a little Donation ( at least i think they do, ive never spoken to one of them )
Click to expand...
Click to collapse
I LOVE YOU
i get stuck the last night trying to put nougat, but i downgrade to mm and get stuck in huawei logo and no led,
only flash supersu and all worked good again :$
spadyrus said:
I LOVE YOU
i get stuck the last night trying to put nougat, but i downgrade to mm and get stuck in huawei logo and no led,
only flash supersu and all worked good again :$
Click to expand...
Click to collapse
I have the same issue..but the problem with my device it's worse..when I connect my phone to PC it says: Fastboot2.0, and it's stucked on a blackscreen 4ever.. any ideas what can I do? Thanks!
I'm also on the sh** with my phone. Stuck on your device is booting now...
Can't get erecovery or fast boot or anything. Can't even turn off the phone.
Sent from my ONEPLUS A3003 using Tapatalk
I am in the same situation, bootloop, and i was able to enter bootloader and unlock it, but now can't enter anymore. Phone wasn't turning off then i managed to drain battery, but I still can't enter bootloader. when i press volume - and power the yellow menu appears and if i press volume up to enter eRecovery it freezes. If try to boot normal the yellow screen with the unlock message appears and then the mobile hangs. How were you able to solve this?
thanks
Hello,
When you pressed Vol- you plugged your phone on the computer or not?
Because to access fastboot it is compulsory to do the manipulation Vol- with the telephone connected to the PC
Well, I have a nice paperweight now from my P9Lite.
Here are the facts :
1. phone was on Vodafone firmware (VNS-L31C02B120)
2. flased C432B130 which was ok, despite changing to C900.
3. I think I flashed oem_info_eu or something like that.
4 Since then the phone booting into CRAPPY Huawei eRecovery only(it does absolutelly nothing!)
5 I can boot it to Fastboot/recovery mode, can flash UPDATE.APP (flashed few in the past days), but the result is the same - booting into Huawei eRecovery
6 whatever trying to flash it won't pass 5%!
7 the current status is : USB debugging & OEM Unlocking not allowed and can't access them anyway
Flashed ROM with this result
Extracting partitions
Cannot create extract directory: C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\tmp\20 161220_003545_UPDATE\
Extract files to directory: C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM_FW OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Device found: xxxxxx
IMEI: xxxxxxxx
Build number: :VNS-L31C900B130
Product model: HUAWEI VNS-L31
Writing XLOADER partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\XLOADE R.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\XLOADE R.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\FW_LPM 3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\FASTBO OT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\MODEMN VM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\TEEOS. img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\TRUSTF IRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\SENSOR HUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\FW_HIF I.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\BOOT.i mg
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\RECOVE RY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\RECOVE RY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\DTS.im g
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\MODEM_ FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\CACHE. img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\SYSTEM .img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\CUST.i mg
CUST partition UPDATE ...OK
Software written
20/12/2016 00:52:39 Writing device finished OK
So if everything is OK, nothing failed, why the hell this phone not start up properly???
It s a xmas present for missis, but wanna throw it to the bin!!!!
Any help appreciated.
aspot72 said:
Well, I have a nice paperweight now from my P9Lite.
Here are the facts :
1. phone was on Vodafone firmware (VNS-L31C02B120)
2. flased C432B130 which was ok, despite changing to C900.
3. I think I flashed oem_info_eu or something like that.
4 Since then the phone booting into CRAPPY Huawei eRecovery only(it does absolutelly nothing!)
5 I can boot it to Fastboot/recovery mode, can flash UPDATE.APP (flashed few in the past days), but the result is the same - booting into Huawei eRecovery
6 whatever trying to flash it won't pass 5%!
7 the current status is : USB debugging & OEM Unlocking not allowed and can't access them anyway
Flashed ROM with this result
Extracting partitions
Cannot create extract directory: C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\tmp\20 161220_003545_UPDATE\
Extract files to directory: C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM_FW OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Device found: xxxxxx
IMEI: xxxxxxxx
Build number: :VNS-L31C900B130
Product model: HUAWEI VNS-L31
Writing XLOADER partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\XLOADE R.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\XLOADE R.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\FW_LPM 3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\FASTBO OT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\MODEMN VM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\TEEOS. img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\TRUSTF IRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\SENSOR HUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\FW_HIF I.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\BOOT.i mg
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\RECOVE RY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\RECOVE RY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\DTS.im g
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\MODEM_ FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\CACHE. img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\SYSTEM .img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\Acer\Desktop\DC_Phoenix\DC_Phoenix\CUST.i mg
CUST partition UPDATE ...OK
Software written
20/12/2016 00:52:39 Writing device finished OK
So if everything is OK, nothing failed, why the hell this phone not start up properly???
It s a xmas present for missis, but wanna throw it to the bin!!!!
Any help appreciated.
Click to expand...
Click to collapse
This works I have done same thing more than I can remember. Get the toolkit from Rom section flash the twrp onto it if you connect to comp and go to restore phone ir will tell you how to fastboot.
Downliad stock firmware for your phone than flash it through twrp your still going to be in bootloop so turn phone off hold power and vol up till logo appears let go of power button and then factory reset and reboot. I have done it dozens time it works
while DC_Phoenix flashing update.app,
you can Use Sysinternals Process Explorer suspend the process, and flash a proper oeminfo.like:
fastboot flash oeminfo oeminfo_vns-l31.img
Then you can use dload method flash update.app
stevegtrlmk said:
This works I have done same thing more than I can remember. Get the toolkit from Rom section flash the twrp onto it if you connect to comp and go to restore phone ir will tell you how to fastboot.
Downliad stock firmware for your phone than flash it through twrp your still going to be in bootloop so turn phone off hold power and vol up till logo appears let go of power button and then factory reset and reboot. I have done it dozens time it works
Click to expand...
Click to collapse
Yeah, but I don't have USB debug enabled and boot loader is locked. ?
rann77 said:
while DC_Phoenix flashing update.app,
you can Use Sysinternals Process Explorer suspend the process, and flash a proper oeminfo.like:
fastboot flash oeminfo oeminfo_vns-l31.img
Then you can use dload method flash update.app
Click to expand...
Click to collapse
Actually I was thinking about it. The DC-Phoenix temporary unlocks the boot loader and frp. But not sure if unplug and then start again will it stay unlocked?
Have you tested this
Put the phone in bootloader mode, connect to the toolkit 0.0.0.8, unlock the bootloader even if it says it is already there.
Install twrp, wipe, check all, wipe.
Install oeminfo, turn off. Restarted with dload.
aspot72 said:
Actually I was thinking about it. The DC-Phoenix temporary unlocks the boot loader and frp. But not sure if unplug and then start again will it stay unlocked?
Click to expand...
Click to collapse
It possible,I didnt try.
I got the same problem before and after flash oeminfo. Dload flashing is okey.
---------- Post added at 10:14 PM ---------- Previous post was at 10:03 PM ----------
Chisetdel31260 said:
Have you tested this
Put the phone in bootloader mode, connect to the toolkit 0.0.0.8, unlock the bootloader even if it says it is already there.
Install twrp, wipe, check all, wipe.
Install oeminfo, turn off. Restarted with dload.
Click to expand...
Click to collapse
When frp is locked, It is impossile to unlock bootloader use traditional methods but DC pheonix.
Chisetdel31260 said:
Have you tested this
Put the phone in bootloader mode, connect to the toolkit 0.0.0.8, unlock the bootloader even if it says it is already there.
Install twrp, wipe, check all, wipe.
Install oeminfo, turn off. Restarted with dload.
Click to expand...
Click to collapse
Can't unlock boot loader as can't retrieve phone's ID.
rann77 said:
It possible,I didnt try.
I got the same problem before and after flash oeminfo. Dload flashing is okey.
---------- Post added at 10:14 PM ---------- Previous post was at 10:03 PM ----------
When frp is locked, It is impossile to unlock bootloader use traditional methods but DC pheonix.
Click to expand...
Click to collapse
What's wrong with Phoenix? I found it quite good.
How did you flash oeminfo?
aspot72 said:
What's wrong with Phoenix? I found it quite good.
How did you flash oeminfo?
Click to expand...
Click to collapse
Am I expressed not clearly?
I mean dc phoenix can unlock bootloader temporarily even frp is locked.
Then,You can suspend DC Phoenix
Process and flash oeminfo use fastboot flash command. Just as I said before.
I have just seen this,
If its can help.
http://forum.xda-developers.com/mate-8/help/frp-locked-bootloader-update-to-n-t3524202
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
zkn1021 said:
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
Click to expand...
Click to collapse
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
zkn1021 said:
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
Click to expand...
Click to collapse
zkn1021 said:
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
Click to expand...
Click to collapse
Well first unroot by flashing boot and system, then install update in Lenovo recovery. Yes it's possible to do that. Then when the update installed successfully you can root again with TWRP and SuperSU.
brothers, I skipped system verifying by editing updater-script, but the OTA still failed because signature verifying failed.
Anyone knows how to skip signature verifying?
If we can skip that, we may install ota update package manually while the device is rooted.
matshias said:
the easiest way is to restore the boot and system partition .
...
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
DGolovin said:
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
Click to expand...
Click to collapse
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
matshias said:
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
Click to expand...
Click to collapse
Thanks for eхplain. I have downloaded your backups of 734th firmware for Lenovo Yoga 3 Plus F already but new knowlege will not be redundant
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
NtahX said:
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Click to expand...
Click to collapse
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
dasinflames said:
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
Click to expand...
Click to collapse
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash system system_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.626s]
sending sparse 'system' (516880 KB)...
OKAY [ 18.443s]
writing 'system'...
OKAY [ 7.726s]
sending sparse 'system' (507198 KB)...
OKAY [ 18.163s]
writing 'system'...
OKAY [ 7.812s]
sending sparse 'system' (511833 KB)...
OKAY [ 18.332s]
writing 'system'...
OKAY [ 7.876s]
sending sparse 'system' (514911 KB)...
OKAY [ 18.410s]
writing 'system'...
OKAY [ 7.345s]
sending sparse 'system' (514937 KB)...
OKAY [ 18.282s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (511997 KB)...
OKAY [ 18.328s]
writing 'system'...
OKAY [ 22.033s]
sending sparse 'system' (156572 KB)...
OKAY [ 5.703s]
writing 'system'...
OKAY [ 17.717s]
finished. total time: 194.195s
c:\adb>fastboot flash recovery recovery_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 0.829s]
finished. total time: 2.907s
Since I already flashed boot.img yesterday, continue with system & recovery. I didn't know that Download mode will only shows Lenovo logo. Normally it will shows what running on the background. Did as told and manage to recover. Sadly I've wiped cache & data in Recovery yesterday, now back to square 1. But at least better than bricked device. Thank you.
matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
the only way that my tablet can to be recognized in my computer is with sideload. I'll try with that method.
thxs!!
PS: I used at the end the Multiflashtool and now my tablet works perfectly
if someone has the parallel problem, here is the solution: http://www.mediafire.com/download/58upc51o93ux2f4/Archivo+StargetDawn.rar
just install and execute the multiflash program.
greetings
matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
zkn1021 said:
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
Click to expand...
Click to collapse
Well it seems you have to request the backup again. system.ext4 is a file based backup. This will not restore to a 100% original system image. The person who provided this for you has to run it again and select "system image" instead of "system" when creating the backup. This will then be a binary copy of the system partition.
Once you have that you should create a backup using TWRP on your own device with boot and system image selected onto an external SD card. Don't forget to boot TWRP with system left read only. Then you replace the *.win* files (also the .md5 files) on you SD card with ones you get from this person files. Then reinsert the SD card into the tablet and select restore in TWRP. Then the two partitions should be original if the person you got them from didn't modify it somehow.
I am not sure which format TWRP uses to store these partition images but if the above doesn't work we'll figure out how to extract it.
matshias said:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
hello iam on s000689 and i have a hard time trying to find that recovery image... can i just you S000725 and then not have OTA updates?