Database Users

[Q] Bricked droid razr m XT907

hello
When i push the power button I got masasage on the screen "WARNING BOOTLOADER UNLOCKED - your device...." and the phone dosent start. I can not power it off - i must waiting to battery goes off . When the phone is unchraged and i plug the charger i got the same screen. Can you please help me ?

Can you provide a tad more details please? What happened to cause this? Did you try to flash anything or modify any system apps? What system version are you on? If you have a custom recovery and made a NANDroid just boot to recovery and restore your back up... Any who in most cases you can just boot to fast boot and flash the stock firm ware all that you need is here
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Can you provide a tad more details please? What happened to cause this? Did you try to flash anything or modify any system apps? What system version are you on? If you have a custom recovery and made a NANDroid just boot to recovery and restore your back up... Any who in most cases you can just boot to fast boot and flash the stock firm ware all that you need is here
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
The phone is rooted and have custom boot. I dont know the phone history waths hapens before - i think there is kit kat android with root and there was try to instal an online update. The problem is when the phone i power up its show the screen WARNING BOOTLOADER UNLOCKED and the power of button doesnt power off the phone (i must wait to unchraging the phone and when i plug the charger on, after 3 min the warning screen show automatically) thats why i can not get into recovery mode because the combination power+sound up+sound down doesnt work. Is any option to connect the phone to pc when ist shows te warning screen - does the computer recognised the phone ?

Hold power and volume down for 10 seconds when you see the screen the screen flicker and shut off immediately hold the volume up and down that should take you to the boot menu from there you can go into fast boot and flash stock... Read through the thread I linked it has pretty much everything you need to know and the files to do it with...
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Hold power and volume down for 10 seconds when you see the screen the screen flicker and shut off immediately hold the volume up and down that should take you to the boot menu from there you can go into fast boot and flash stock... Read through the thread I linked it has pretty much everything you need to know and the files to do it with...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Thank you for quick answer. Now i am able to go in ap fastboot flash mode (device is unlocked code:3 fasboot reason: sticky bit factory_fastboot). bout when i connect the phone to poc and try to flash in rds lite i got FAIL:Failed flash process 1/17 flash partition "gpt.bin" -> Phone returned FAIL.i was try 3 difrent roms:
offical VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip
official VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip
unnoficial VRZ_XT907_9.8.1Q-94-1_CFC.xml.zip
an have the same FAIL
now after this try to flash. the phone starts ony in ap fast boot mode
Did you know what can i do next ?
i have also instaled adb on my pc

tomigunn said:
Thank you for quick answer. Now i am able to go in ap fastboot flash mode (device is unlocked code:3 fasboot reason: sticky bit factory_fastboot). bout when i connect the phone to poc and try to flash in rds lite i got FAIL:Failed flash process 1/17 flash partition "gpt.bin" -> Phone returned FAIL.i was try 3 difrent roms:
offical VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip
official VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip
unnoficial VRZ_XT907_9.8.1Q-94-1_CFC.xml.zip
an have the same FAIL
now after this try to flash. the phone starts ony in ap fast boot mode
Did you know what can i do next ?
i have also instaled adb on my pc
Click to expand...
Click to collapse
Its ok - i just to load officiall 4.41 software. But when i restart the phone its start in ap fast boot mode - i must hold volume up+volume down and chose normal boot- then start the os. Can i change it ?

Try to flash a boot logo or something simple...Here are some boot logos a successful flash of something may stop you from booting up to fast boot mode
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Try to flash a boot logo or something simple...Here are some boot logos a successful flash of something may stop you from booting up to fast boot mode
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
I have allready copy 2 files to sd card:
_FIXED__Bin_Flashable_Zip.zip (with logo file inside)
SuperSU_V0.93_-efghi-signed_Stable_Update.zip - to root the OS
when i go in recovery (TWRP2710-RAZR-HD_M-KITKAT) and try to instal from zip i got error
"found Error flashing zip '/external_sd/_FIXED__Bin_Flashable_Zip.zip'
Updating partition details..."
can i install this 2 files from rsd lite ? Or is any other method ?
in atachment full log

tomigunn said:
I have allready copy 2 files to sd card:
_FIXED__Bin_Flashable_Zip.zip (with logo file inside)
SuperSU_V0.93_-efghi-signed_Stable_Update.zip - to root the OS
when i go in recovery (TWRP2710-RAZR-HD_M-KITKAT) and try to instal from zip i got error
"found Error flashing zip '/external_sd/_FIXED__Bin_Flashable_Zip.zip'
Updating partition details..."
can i install this 2 files from rsd lite ? Or is any other method ?
in atachment full log
Click to expand...
Click to collapse
You're using the wrong recovery. Go here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432 and download the correct verison.

ATTACK said:
You're using the wrong recovery. Go here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432 and download the correct verison.
Click to expand...
Click to collapse
I was able to root the phone with file "UPDATE-SuperSU-v2.02.zip" Its work fine. But the phone stil starts in ap fast boot mode - i must go to recovery and start normal boot. Can anybody help me ???

tomigunn said:
I was able to root the phone with file "UPDATE-SuperSU-v2.02.zip" Its work fine. But the phone stil starts in ap fast boot mode - i must go to recovery and start normal boot. Can anybody help me ???
Click to expand...
Click to collapse
While in AP fastboot, connect your device to your PC
Open mfastboot then TYPE
Code:
fastboot oem fb_mode_clear
Tap ENTER
When finished TYPE
Code:
mfastboot reboot
Tap ENTER

ATTACK said:
While in AP fastboot, connect your device to your PC
Open mfastboot then TYPE
Code:
fastboot oem fb_mode_clear
Tap ENTER
When finished TYPE
Code:
mfastboot reboot
Tap ENTER
Click to expand...
Click to collapse
Now the phone boots ok. But i have antoher two probelms:
first - when i go settings->Memory after 2-3 sceconds i got message "application Settings has stopped". I see this message from begin when I install new os ". Is the phone damaged or must reinstall the os ?
second - when I install big apps or games i must putt the obb files to folder "android" but on phone storage. When i put this files on sd card (flder android->obb) the app or game doesent see this files.

All problems will be solved
tomigunn said:
Now the phone boots ok. But i have antoher two probelms:
first - when i go settings->Memory after 2-3 sceconds i got message "application Settings has stopped". I see this message from begin when I install new os ". Is the phone damaged or must reinstall the os ?
second - when I install big apps or games i must putt the obb files to folder "android" but on phone storage. When i put this files on sd card (flder android->obb) the app or game doesent see this files.
Click to expand...
Click to collapse
Just extract firmware zip ..edit *.xml file remove getvar line and flash with rsdlite.
choose VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml
just pind me on [email protected] for any help.

May Factory Image now available MXC89F

For those in custom recovery land just flash the system and vendor img to upgrade
now in May flavor!
https://developers.google.com/android/nexus/images#instructions

Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine

redukt said:
Well it should be great IF our TWRP could mount vendor / system correctly
Only boot / recovery partitions are selectable for .img files :/
Edit: I´ve flashed the files via ADB - all went fine
Click to expand...
Click to collapse
The value of this posting would increase exponentially if you took it upon yourself to share what and how you flashed the files with ADB.

Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
No chance of losing root either, is that correct?

Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP

redukt said:
Well I assume that you have TWRP? Reboot into recovery and flash supersu again. That´s all If not you can sideload it via ADB.
In my case I have reflash supersu & xposed framework in TWRP
Click to expand...
Click to collapse
Yes, I will need to reflash both, too (I have TWRP).
Thanks!

Than you´re device is rooted again. With this method you lose no data or wipe anything (ok.... some cache *g)
And... we have a thanks button in XDA So you don´t have to thank mate

Change log ? Or its just a security update

Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.

After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...

rambobo said:
After playing around in TWRP and using the fix fastboot option I am finally able to flash system and vendor in fastboot.
I don't know if the fix fastboot was really the solution, maybe just some sort of placebo, but nevertheless I am able to flash. Problem with the bootloop remains:
Google logo, reboot recovery.
My data partition is alright. What do I need to flash to get it going?
Going in circles here...
Click to expand...
Click to collapse
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk

houtx2 said:
Just asking, did you verify your download to make sure not corrupted?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?

rambobo said:
Yes, it is verified. I am using all kinds of ways to restore the pixel.
I am positive: fastboot won't write or format partitions unless it is fixed by twrp.
I am trying out to flash the newest factory image with the skipsoft android toolkit. I could have done it manually, but spent already too much of my free Saturday on flashing. I'll report back if and what works out.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
:/ After 'successful' flashing of the stock firmware, now there is the laying android with the red exclamation sign... help...
---------- Post added at 04:54 PM ---------- Previous post was at 04:19 PM ----------
I redownloaded the official factory image grom google servers.
Then I followed the instruction, means i started the flash-all.bat.
The Tablet boot into the android on the back with the red exclamation mark symbol.
The flashing process went without warnings.
Is it bricked now? Do I have to relock the bootloader to boot it?
Click to expand...
Click to collapse
Pleas try to reinstall right drivers, change the cable / USB ports. I think your main problem is your system configuration. Good luck

m8... so glad I wasn't too tired to listen to your tip. Awesome! Redid all the steps on my freshly installed laptop, and voila!
Seems either my main PCs USB-connection is flunky or I am damned to reinstall my Windows soon. Scary...
I used the following software to revive the Pixel:
official Google USB Drivers
You have to unzip the file and right-click and install it
then you have to go to your device manager in windows and after connecting the tablet with the PC and getting into fastboot
Find the Android device on the top, select to change driver and go straight to manual selection of the driver, select android and bootloader driver
unpack the official Factory Image with 7Zip until you get to the folder with the flash-all.bat
get the minimal adb fastboot and unpack it in the same folder as the flash-all file
wait until you see the sweet booting animation
I think I didn't forget anything important. My Pixel is alive and ready for prime time.
Big thanks redukt, may the warp speed not pass you!

rambobo said:
Big thanks redukt, may the warp speed not pass you!
Click to expand...
Click to collapse
Enjoy your device
Next time simply hit the thanks button

redukt said:
Sorry for my ignorance
Extract the ryu-m5c14j-factory-b714e9bd.tgz with i.e. 7-zip. In image-ryu-m5c14j.zip you find both files system.img and vendor.img.
So... I´ll hope you have some practices using ADB / fastboot. Put both files in your ADB / fastboot folder. Activate USB debugging on your device and restart it in fastboot mode. Connect your device with your USB-C cable.
Go into your ADB / fastboot folder and press shift / rightclick your mouse at twice and open the command prompt.
Bye typing "fastboot devices" or "adb devices" you can check if your device is correctly connect with your PC.
If you´re connected type "fastboot flash system system.img" and wait for end of process. After that type "fastboot flash vendor vendor.img". Now you can reboot your device by typing "fastboot reboot"
Those are my oldschool steps without losing data or settings.
Click to expand...
Click to collapse
rambobo said:
Hello there,
so I am in a little conundrum here.
I flashed the system.img and vendor.img following the instructions, but the pixel was just stuck at the plain Google logo.
After giving it something like 30 minutes, I had to power it off.
I am using TWRP and dragon-boot-encryptable-rooted-MXB48T-02102016-1.img stock kernel.
Another boot went without success.
my next thought was to downgrade to MXC14G but trying to do so resulted in:
Code:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
FAILED (remote: unsupported command)
finished. total time: 0.004s
So far TWRP is working and I can operate within it.
Any ideas what went wrong? Should I format system and vendor in TWRP? I don't think this is a good idea... (Last time I tried to do so in this experimental version of TWRP I had to fight a long fight to revive it, because the formatting tool in TWRP was stuck. But that's another story.) Any way to flash the system.img and vendor.img from within TWRP?
Any help would be much appreciated, m8s.
Click to expand...
Click to collapse
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!

hugehead83 said:
Following redukt's instructions, I got the same error that rambobo saw. I rebooted into TWRP and executed the "Fix fastboot" option, then rebooted back to the bootloader. System & Vendor image flashing via ADB worked fine
I am now running M5C14J without loss of data, root, or recovery.
The OTA update reminder disappeared on it's own after 5-10 minutes.
Thanks yall!
Click to expand...
Click to collapse
You didn't have to apply root again via ADB or TWRP?

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Mates, the may-factory-image is available. Same procedure as ever
https://developers.google.com/android/nexus/images#instructions
Happy flashing

dmnhnterz said:
You didn't have to apply root again via ADB or TWRP?
Click to expand...
Click to collapse
Correct
But judging from others' experiences here, YMMV. I tried the latest FlashFire build too, but that got me nowhere.

P 8 lite bootloop on stock firmware

Hello all,
I have Huawei P8 lite bought from Romania. I install the android 6 and I wanted to go back to 5, so I go trough the steps on the official huawei website :
1) download an install rollback package - all went fine, the B500 firmware was shown
2)download an install B132 - on this step the problem appear; after the installation the phone is in a continuous bootloop, it can;t even shut down for good. I hear the start up sound, then if I press the volume keys it's beeping, so somehow is booting but without showing nothing(strange random colors ). The PC is recognizing the phone, but ADB won't .
The phone isn't going in to the recovery mode or update mode.
I search the forum and found methods to unbrick the phone, but only using fastboot. Since my phone isn't rooted , I can't use this method. What can I do?

Moshu646 said:
Hello all,
I have Huawei P8 lite bought from Romania. I install the android 6 and I wanted to go back to 5, so I go trough the steps on the official huawei website :
1) download an install rollback package - all went fine, the B500 firmware was shown
2)download an install B132 - on this step the problem appear; after the installation the phone is in a continuous bootloop, it can;t even shut down for good. I hear the start up sound, then if I press the volume keys it's beeping, so somehow is booting but without showing nothing(strange random colors ). The PC is recognizing the phone, but ADB won't .
The phone isn't going in to the recovery mode or update mode.
I search the forum and found methods to unbrick the phone, but only using fastboot. Since my phone isn't rooted , I can't use this method. What can I do?
Click to expand...
Click to collapse
You don't need to be rooted to use fastboot. However you need to unlock the bootloader in order to use it and don't tell me that your bootloader is locked otherwise it's a bad news.

Yes, it is locked

Moshu646 said:
Yes, it is locked
Click to expand...
Click to collapse
Use Huawei restore mode from hi suite.

I manage to enter in recovery mode(thus nothing is shown on the screen) , the HI Suite tells me that I successfully entered in recovery mode, but when I press Recover I get: Your device is not supported for system recovery

Moshu646 said:
I manage to enter in recovery mode(thus nothing is shown on the screen) , the HI Suite tells me that I successfully entered in recovery mode, but when I press Recover I get: Your device is not supported for system recovery
Click to expand...
Click to collapse
Is there an option for flashing rom? If then select that option and then select official firmware and then continue.

Suleiman01 said:
Is there an option for flashing rom? If then select that option and then select official firmware and then continue.
Click to expand...
Click to collapse
I don't see nothing on screen.
Now I discovered that if I enter in recovery mode ( Volume down + Power ; still nothing showing on the screen), fastboot is recognizing my device but when I want to write something I get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash BOOT boot.img
target didn't report max-download-size
sending 'BOOT' (21708 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s

Moshu646 said:
I don't see nothing on screen.
Now I discovered that if I enter in recovery mode ( Volume down + Power ; still nothing showing on the screen), fastboot is recognizing my device but when I want to write something I get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash BOOT boot.img
target didn't report max-download-size
sending 'BOOT' (21708 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
You can't because your phone is locked. Did you find that rom flashing option on Hisuite?

Suleiman01 said:
You can't because your phone is locked. Did you find that rom flashing option on Hisuite?
Click to expand...
Click to collapse
It has an Update option but HI is not connecting to my device because I have to tap something on my phone in order to connect.

Moshu646 said:
Yes, it is locked
Click to expand...
Click to collapse
Hello ,
I have an update : I manage to unlock fastboot
I also manage to write successfully the boot, cust, recovery an system img's , but the phone is still not working: it starts up, the screen is lightening, I hear the Huawei sound, but no logo, and then the phone shut's down

Moshu646 said:
Hello ,
I have an update : I manage to unlock fastboot
I also manage to write successfully the boot, cust, recovery an system img's , but the phone is still not working: it starts up, the screen is lightening, I hear the Huawei sound, but no logo, and then the phone shut's down
Click to expand...
Click to collapse
Can you go to recovery?

Moshu646 said:
I have an update : I manage to unlock fastboot
Click to expand...
Click to collapse
How did you do that? My phone is also in bootloop and I am not sure how to unlock the bootloader...

cunami said:
How did you do that? My phone is also in bootloop and I am not sure how to unlock the bootloader...
Click to expand...
Click to collapse
There is a program called Huawei product ID generator. You need Imei,Serial no.(both are on the box) and Product ID (via Huawei product ID generator). Through this you can obtain unlocking code
In Fastboot and rescue mode type this in minimal adb and fastboot
fastboot oem unlock XXXXXXXXXXXXXXXXX
Where XXXXXXXXXXXXXXXXX is the unlocking code.

Moshu646 said:
It has an Update option but HI is not connecting to my device because I have to tap something on my phone in order to connect.
Click to expand...
Click to collapse
I was talking about this (see the picture below).

Suleiman01 said:
There is a program called Huawei product ID generator. You need Imei,Serial no.(both are on the box) and Product ID (via Huawei product ID generator). Through this you can obtain unlocking code
In Fastboot and rescue mode type this in minimal adb and fastboot
fastboot oem unlock XXXXXXXXXXXXXXXXX
Where XXXXXXXXXXXXXXXXX is the unlocking code.
Click to expand...
Click to collapse
Thanks! Will try definitely.
Last question - does the bootloader unlock wipe the user data on the phone? I want somehow to extract it before flashing any ROM over. So my idea was to unlock it, flash some better recovery and make a backup of data partition.

I don't have that option
Maybe it appear when the devices is connected.

Moshu646 said:
I don't have that option
Maybe it appear when the devices is connected.
Click to expand...
Click to collapse
It appears on 64 bit version of Windows I tried it on 32 bit it wasn't there.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
cunami said:
Thanks! Will try definitely.
Last question - does the bootloader unlock wipe the user data on the phone? I want somehow to extract it before flashing any ROM over. So my idea was to unlock it, flash some better recovery and make a backup of data partition.
Click to expand...
Click to collapse
No. At least when I unlock my phone bootloader didn't wipe my data.
Just press thanks button if you don't mind

Suleiman01 said:
It appears on 64 bit version of Windows I tried it on 32 bit it wasn't there.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
No. At least when I unlock my phone bootloader didn't wipe my data.
Just press thanks button if you don't mind
Click to expand...
Click to collapse
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?

Moshu646 said:
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?
Click to expand...
Click to collapse
I have 4.0.6.301 version of Hisuite. Download it from this link(use chrome to translate it's Chinese).
http://consumer.huawei.com/minisite/HiSuite_cn/index.html
---------- Post added at 11:25 AM ---------- Previous post was at 11:05 AM ----------
Moshu646 said:
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?
Click to expand...
Click to collapse
Try this multi tool by sokoban.
http://huaweip8lite.blogspot.com/2016/04/mod-p8-lite-multi-tool-by-sokoban.html?m=1

The ROM flashing option is not active- I think because the device is not connected.
Tried with the multi tool, same result

Soft-bricked P9 Lite (VNS-L21)

Good day everyone!
My fellow housemate managed to soft-brick his device and now im trying to think of a fix.
The device used to have Android 7.0 installed (EMUI 5.0). Then he installed TWRP + some custom 6.0 based rom, which resulted in a soft brick.
What i've tried so far:
1. Tried multiple update.app packages (C432B170 and C432B130 SHOULD be the ones i need, since the device is european). Update always fails with message "Incompatibility with current version. Please download the correct package".
2. Extracted BOOT.img, RECOVERY.img, SYSTEM.img and CUST.img and tried flashing them with fastboot. SYSTEM.img fails with message FAILED (remote: sparse flash write failure), CUST.img fails with some error connected with partitions.
3. Tried the downgrade package from Nougat to Marshmallow. Update.app still doesnt work with the same error as mentioned earlier, however, SYSTEM.img flashed via fastboot this time, but with no success, system still only boots in eRecovery and fastboot modes.
4. Tried installing multiple TWRP recoveries, none of them seem to work. Device just wont boot in recovery mode.
Any ideas?
Best regards,
Vlad

shxtov said:
Good day everyone!
My fellow housemate managed to soft-brick his device and now im trying to think of a fix.
The device used to have Android 7.0 installed (EMUI 5.0). Then he installed TWRP + some custom 6.0 based rom, which resulted in a soft brick.
What i've tried so far:
1. Tried multiple update.app packages (C432B170 and C432B130 SHOULD be the ones i need, since the device is european). Update always fails with message "Incompatibility with current version. Please download the correct package".
2. Extracted BOOT.img, RECOVERY.img, SYSTEM.img and CUST.img and tried flashing them with fastboot. SYSTEM.img fails with message FAILED (remote: sparse flash write failure), CUST.img fails with some error connected with partitions.
3. Tried the downgrade package from Nougat to Marshmallow. Update.app still doesnt work with the same error as mentioned earlier, however, SYSTEM.img flashed via fastboot this time, but with no success, system still only boots in eRecovery and fastboot modes.
4. Tried installing multiple TWRP recoveries, none of them seem to work. Device just wont boot in recovery mode.
Any ideas?
Best regards,
Vlad
Click to expand...
Click to collapse
I had the exact same problem! And I found a fix. Boot into the dload method of updating ( make sure it will give you an error, so don't have an SD card in ) then when it fails reboot. And as soon as it starts rebooting hold volume up, then it should take you to the stock recovery, then just wipe and it should be working! All the best

vdp1nnab said:
I had the exact same problem! And I found a fix. Boot into the dload method of updating ( make sure it will give you an error, so don't have an SD card in ) then when it fails reboot. And as soon as it starts rebooting hold volume up, then it should take you to the stock recovery, then just wipe and it should be working! All the best
Click to expand...
Click to collapse
Booted into Huawei eRecovery and it doesnt give me an option to wipe anything, just "download latest version and recovery" via Wi-Fi, which, unfortunately, fails.

shxtov said:
Booted into Huawei eRecovery and it doesnt give me an option to wipe anything, just "download latest version and recovery" via Wi-Fi, which, unfortunately, fails.
Click to expand...
Click to collapse
Okay. Try again. This time go into e recovery, then reboot and the second you touch that reboot button you hold volume up. Also one question. Can u boot into fastboot and ADB recognises your device ?

vdp1nnab said:
Okay. Try again. This time go into e recovery, then reboot and the second you touch that reboot button you hold volume up. Also one question. Can u boot into fastboot and ADB recognises your device ?
Click to expand...
Click to collapse
Nope, can't get into recovery, at all. Just keeps rebooting.
Yes, i can get into fastboot mode and fastboot recognizes the device.

shxtov said:
Nope, can't get into recovery, at all. Just keeps rebooting.
Yes, i can get into fastboot mode and fastboot recognizes the device.
Click to expand...
Click to collapse
Okay that helps a huge load. What you need to do is flash the nougat ROM again. You need to put the rom files into the root of ADB install location (program files/ Minimal ADB and Fastboot) in zip format. If I'm not mistaken you have update.zip and vnsXXX_Full_data (or something similar).
Then flash the firmware using this command once your connected in fastboot. I'm not sure the command. But I did some googling and can't find a solid answer. I remember doing it but I don't remember the command line.

Stuck in fastboot. Can't access eRecovery.

Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?

yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best

Gamkutopolowk said:
yes i have same because battery is not dead still wait battery remain if dead then plug against work fastboot need firmware rollback version only C432B185 try HWOTA this is the best
Click to expand...
Click to collapse
So you're saying that I wait until my battery drains, then go into fastboot and roll back to C432B185? Maybe you could help me by outlining the steps to flash via fastboot?

flash via fastboot by HWOTA follow this link https://romprovider.com/2018/01/download-install-b185-nougat-update-huawei-p10-plus/
only method 1

Gamkutopolowk said:
flash via fastboot by HWOTA follow this link
only method 1
Click to expand...
Click to collapse
So i tried this method, but it didn't work. It flashes TWRP, and instructs me to disconnect the USB cable and boot into TWRP, but i can't boot into TWRP. It goes directly to the error message even when holding the buttons down.

because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............

Gamkutopolowk said:
because stuck in fastboot is freeze or corrupted still wait battery drains when dead battery hold vol down + plug USB then run in HWOTA...............
Click to expand...
Click to collapse
So after waiting for the battery to drain, holding vol down, and plugging the USB, I'm back where I was before with being in fastboot. Running HWOTA results in the same problem for when it tells me to reboot to TWRP after install, the phone goes to error mode.
I'm pretty sure the bl31 image corruption is preventing me from booting into recovery.

try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it

Gamkutopolowk said:
try other methode if work or not run fastboot need files from huawei firmware extractor open Update.app save files boot.img + recovery.img + system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Test it
Click to expand...
Click to collapse
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'

Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds

Gamkutopolowk said:
Try HWOTA flash TWRP then hold power + vol up stay hold vol up long 15 seconds
Click to expand...
Click to collapse
Still goes straight to the error screen.

blahblah31415 said:
Still goes straight to the error screen.
Click to expand...
Click to collapse
Please show me your mobile

blahblah31415 said:
Ok so i flashed boot.img, recovery.img, system.img all OKAY.
Reboot and i get the same error..
The problem is with the bl31 image, which is in ARM Trusted Firmware.
Maybe if i could figure out how to flash TRUSTFIRMWARE.img that would work. I tried this, but it doesn't work. I don't know the partition name.
fastboot flash trustfirmware
unknown partition 'trustfirmware'
Click to expand...
Click to collapse
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode

Junaid Shafi said:
thank you sir u saved my phone from drowning just flashed this trustedfirmware and hurray my phone got out of error mode
Click to expand...
Click to collapse
How you did that?

blahblah31415 said:
Hi all,
Please help me!
I think i messed up pretty badly here. I tried downgrading from Oreo to Nougat but I think I tried to install a wrong image. Now when i boot i get:
ERROR MODE
Attention! Please update system again
Error!
Fun NO : 15 (bl31 image)
Error NO : 1 (security verify failed)
I've tried the dload method but it doesn't even start. I boot it up holding power, vol+, vol-, and it gets stuck at "your device is booting now."
I can't access twrp, even after flashing it again.
I can get into fastboot and I've tried manually flashing images from an update.app, but after that, the same problem still persists. Trying to relock the boot loader gives an error "command not allowed"
Does anybody have any ideas?
Click to expand...
Click to collapse
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!

gonzalomorenorovetto said:
Hi
I have the exact same problem
After trying all of the methods I found (dload, HWOTA, TWRP, etc), I finally took the phone to the service center.
They told me it was an easy fix, then they called me and told me that probably they were going to replace the motherboard
I'm still waiting for them to call me for confirmation.
If you got any news on this, please keep posting
Thanks!
Click to expand...
Click to collapse
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.

blahblah31415 said:
I actually ended up using dc pheonix to fix it. It worked perfectly. I had to pay about 15 dollars for credits. It used some sort of backdoor and flashed a new ROM from scratch.
Click to expand...
Click to collapse
I tried DC Phoenix and It did not work. They returned me my money.
At the service center they finally replaced my motherboard, in warranty, even though the phone was unlocked and I bricked it completely