Related
Hi everybody,
First I apologizes for my poor English. Nobody is perfect I'm French..
Whell, On my new P9 lite buy on October 20.... I have made some changes. I' have rooted it and suhide it. After that I have tried to put Xposed, and.... crash... black screen on boot, no bip, no little green or red light.
First on linux with dmesg linux see it like:
[510675.849532] usb 3-2: Product: vns
[510675.849533] usb 3-2: Manufacturer: HUAWEI
[510675.849534] usb 3-2: SerialNumber: FUH7N16627059031
[511731.855900] usb 3-2: USB disconnect, device number 103
[511735.297752] usb 3-2: new high-speed USB device number 104 using xhci_hcd
[511735.426016] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[511735.426019] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[511735.426020] usb 3-2: Product: Fastboot2.0
[511735.426021] usb 3-2: Manufacturer: Fastbo
[511735.426022] usb 3-2: SerialNumber: FUH7N16627059031
[511753.734515] usb 3-2: USB disconnect, device number 104
[511763.010163] usb 3-2: new high-speed USB device number 105 using xhci_hcd
[511763.139415] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2
[511763.139418] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[511763.139419] usb 3-2: Product: vns
[511763.139420] usb 3-2: Manufacturer: HUAWEI
[511763.139421] usb 3-2: SerialNumber: FUH7N16627059031
[512470.759942] usb 3-2: USB disconnect, device number 105
[512622.440907] usb 3-2: new high-speed USB device number 106 using xhci_hcd
[512622.628306] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2
[512622.628309] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[512622.628319] usb 3-2: Product: vns
[512622.628320] usb 3-2: Manufacturer: HUAWEI
[512622.628321] usb 3-2: SerialNumber: FUH7N16627059031
[512711.648289] usb 3-2: USB disconnect, device number 106
[512858.258337] usb 3-2: new high-speed USB device number 107 using xhci_hcd
[512858.444693] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2
[512858.444696] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[512858.444697] usb 3-2: Product: vns
[512858.444698] usb 3-2: Manufacturer: HUAWEI
[512858.444699] usb 3-2: SerialNumber: FUH7N16627059031
[513073.322806] usb 3-2: USB disconnect, device number 107
[513075.949626] usb 3-2: new high-speed USB device number 108 using xhci_hcd
[513076.077907] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[513076.077910] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[513076.077911] usb 3-2: Product: Fastboot2.0
[513076.077913] usb 3-2: Manufacturer: Fastbo
[513076.077914] usb 3-2: SerialNumber: FUH7N16627059031
[513106.427014] usb 3-2: USB disconnect, device number 108
[513109.556986] usb 3-2: new high-speed USB device number 109 using xhci_hcd
[513109.685423] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[513109.685426] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[513109.685427] usb 3-2: Product: Fastboot2.0
[513109.685428] usb 3-2: Manufacturer: Fastbo
[513109.685429] usb 3-2: SerialNumber: FUH7N16627059031
[513110.427719] usb 3-2: USB disconnect, device number 109
[513210.899154] usb 3-2: new high-speed USB device number 110 using xhci_hcd
[513211.027436] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[513211.027439] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[513211.027440] usb 3-2: Product: Fastboot2.0
[513211.027441] usb 3-2: Manufacturer: Fastbo
[513211.027442] usb 3-2: SerialNumber: FUH7N16627059031
[513245.019570] usb 3-2: USB disconnect, device number 110
[513257.462374] usb 3-2: new high-speed USB device number 111 using xhci_hcd
[513257.590785] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[513257.590788] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[513257.590789] usb 3-2: Product: Fastboot2.0
[513257.590790] usb 3-2: Manufacturer: Fastbo
[513257.590791] usb 3-2: SerialNumber: FUH7N16627059031
[513749.414149] usb 3-2: USB disconnect, device number 111
[513832.330178] usb 3-2: new high-speed USB device number 112 using xhci_hcd
[513832.458459] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[513832.458462] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[513832.458463] usb 3-2: Product: Fastboot2.0
[513832.458464] usb 3-2: Manufacturer: Fastbo
[513832.458465] usb 3-2: SerialNumber: FUH7N16627059031
[514378.819119] usb 3-2: USB disconnect, device number 112
[514429.084772] usb 3-1: USB disconnect, device number 92
[514690.700924] usb 3-1: new full-speed USB device number 113 using xhci_hcd
[514690.832742] usb 3-1: New USB device found, idVendor=1ea7, idProduct=0066
[514690.832744] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Etc...
But now on dmesg I have only:
[545310.125871] usb 3-2: USB disconnect, device number 125
[545338.435131] usb 3-2: new high-speed USB device number 126 using xhci_hcd
[545338.563716] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[545338.563730] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[545338.563733] usb 3-2: Product: Fastboot2.0
[545338.563735] usb 3-2: Manufacturer: Fastbo
[545338.563737] usb 3-2: SerialNumber: FUH7N16627059031
I don' have access to m phone!
My question is how could I have access?
I have tried Vo+ an power, Vol- and power, vol+and - and power and nothing, no signs of my phone....
Anybody have solution or my phone is dead??
Thanks in advance for your help.
Richard
PD: Well, now I progress. Whith android-sdk-linux I have now this output:
fastboot devices
FUH7N16627059031 fastboot
But still black screen and others... someone have an idea or a solution??
Try to install the full stock firmware of your phone model. Copy it in /sdcard/dload folder and use 3 bottons to update.
Hi SevenSlevin
SevenSlevin said:
Try to install the full stock firmware of your phone model. Copy it in /sdcard/dload folder and use 3 bottons to update.
Click to expand...
Click to collapse
How?? I haven't access to my phone, I don't see any partitions and folders... I tried to use 3 buttons, but nothing happen.
I tried to access via linux and Windows but in windows nothing and on Linux jus visible on dmesg, can't mounting the phone or the sdcard...
That's crazy!!
fastboot reboot bootloader works?
snapdesign said:
fastboot reboot bootloader works?
Click to expand...
Click to collapse
Yes:
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.073s
And :
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-L31C432B150
finished. total time: 0.003s
And:
fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: RISK
(bootloader) change_time: 1476921460
(bootloader) Check System: PASS
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-L31C432B150
finished. total time: 0.003s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot getvar rescue_versionrescue_version: rescue0.3
finished. total time: 0.001s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model...
(bootloader) HUAWEI VNS-L31
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.003s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model...
(bootloader) HUAWEI VNS-L31
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot oem get-build-number
...
(bootloader) :VNS-L31C432B150
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.003s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model...
(bootloader) HUAWEI VNS-L31
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot oem get-psid
...
(bootloader) SN:FUH7N16627XXXXXX
(bootloader) IMEI:8694000293XXXX
(bootloader) IMEI:8694000294XXXX
OKAY [ 0.002s]
finished. total time: 0.002s
But....: Next don't work
fastboot oem backdoor info
...
FAILED (remote: Command not allowed)
finished. total time: 0.006s
fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.010s
adb shell su -v
error: device '(null)' not found
... Any idea??
RicoMotril said:
Yes:
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.073s
And :
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-L31C432B150
finished. total time: 0.003s
And:
fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: RISK
(bootloader) change_time: 1476921460
(bootloader) Check System: PASS
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-L31C432B150
finished. total time: 0.003s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot getvar rescue_versionrescue_version: rescue0.3
finished. total time: 0.001s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model...
(bootloader) HUAWEI VNS-L31
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.003s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model...
(bootloader) HUAWEI VNS-L31
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot oem get-build-number
...
(bootloader) :VNS-L31C432B150
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.003s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot oem get-product-model...
(bootloader) HUAWEI VNS-L31
OKAY [ 0.003s]
finished. total time: 0.003s
fastboot oem get-psid
...
(bootloader) SN:FUH7N16627XXXXXX
(bootloader) IMEI:8694000293XXXX
(bootloader) IMEI:8694000294XXXX
OKAY [ 0.002s]
finished. total time: 0.002s
But....: Next don't work
fastboot oem backdoor info
...
FAILED (remote: Command not allowed)
finished. total time: 0.006s
fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.010s
adb shell su -v
error: device '(null)' not found
... Any idea??
Click to expand...
Click to collapse
yeah... you have l31, download latest update.app, use huawei update extractor and get system, boot,recovery, cust... and flash them in fastboot with fastboot flash system system.img etc... you can find some tutorials on p8 lite section... or simply try to flash twrp and see if the device boots in recovery "fastboot flash recovery twrpnamehere.img"
I have flashed the last TWRP and no change, I gonna test with the last update.
the B151 is good??
snapdesign said:
yeah... you have l31, download latest update.app, use huawei update extractor and get system, boot,recovery, cust... and flash them in fastboot with fastboot flash system system.img etc... you can find some tutorials on p8 lite section... or simply try to flash twrp and see if the device boots in recovery "fastboot flash recovery twrpnamehere.img"
Click to expand...
Click to collapse
Update
Well, I used VNS-L31C432B151 (L31)
Update.zip don't work: archive does not contain 'android-info.txt'
Nest I have split to images and:
Require Maj like BOOT.img and no boot.img... I suposed..
fastboot flash boot BOOT.img
fastboot reboot
rebooting...
finished. total time: 0.072s
fastboot reboot
rebooting...
finished. total time: 0.072s
But my fone don' work... Black screen no light, and buzz...
I tried
fastboot flash system SYSTEM.img
that don't work...
I tried:
fastboot flash boot twrp-3.0.2-0-eva.img
Don't work...
I tried:
fastboot flash boot twrp-3.0.2-0-eva.img
Don't work...
Anything wrong?? why that don't work? please
Update
Well, I used VNS-L31C432B151 (L31)
Update.zip don't work: archive does not contain 'android-info.txt'
Nest I have split to images and:
Require Maj like BOOT.img and no boot.img... I suposed..
fastboot flash boot BOOT.img
fastboot reboot
rebooting...
finished. total time: 0.072s
fastboot reboot
rebooting...
finished. total time: 0.072s
But my fone don' work... Black screen no light, and buzz...
I tried
fastboot flash system SYSTEM.img
that don't work...
I tried:
fastboot flash boot twrp-3.0.2-0-eva.img
Don't work...
I tried:
fastboot flash boot twrp-3.0.2-0-eva.img
Don't work...
Anything wrong?? why that don't work? please
RicoMotril said:
Well, I used VNS-L31C432B151 (L31)
Update.zip don't work: archive does not contain 'android-info.txt'
Nest I have split to images and:
Require Maj like BOOT.img and no boot.img... I suposed..
fastboot flash boot BOOT.img
fastboot reboot
rebooting...
finished. total time: 0.072s
fastboot reboot
rebooting...
finished. total time: 0.072s
But my fone don' work... Black screen no light, and buzz...
I tried
fastboot flash system SYSTEM.img
that don't work...
I tried:
fastboot flash boot twrp-3.0.2-0-eva.img
Don't work...
I tried:
fastboot flash boot twrp-3.0.2-0-eva.img
Don't work...
Anything wrong?? why that don't work? please
Click to expand...
Click to collapse
You are using a P9 twrp probably there is something wrong.
Anyway to install update.app of b151 you need stock recovery and put that file in sdcard (dload folder) using PC (without phone).
Huawei has 2 recovery, the second is ercovery. You need to flash the first 1 and be sure that you have flashed it.
I need to flash B151?? and where i can find stock recovery?
What SDcard? the intern or the extern?? in twice I don't can access to folders or partitions...
only to fastboot commands and not all by example I can't erase userdata or cache and i can't access to the shell..
SevenSlevin said:
You are using a P9 twrp probably there is something wrong.
Anyway to install update.app of b151 you need stock recovery and put that file in sdcard (dload folder) using PC (without phone).
Huawei has 2 recovery, the second is ercovery. You need to flash the first 1 and be sure that you have flashed it.
Click to expand...
Click to collapse
RicoMotril said:
I need to flash B151?? and where i can find stock recovery?
What SDcard? the intern or the extern?? in twice I don't can access to folders or partitions...
only to fastboot commands and not all by example I can't erase userdata or cache and i can't access to the shell..
Click to expand...
Click to collapse
External Sd Card man! Put your external sd card on PC and just copy from pc to it the update.app of b151 or b150 (I think it's the same), in a folder called "dload" (just create it) . After put your external on your phone and use 3 buttons.
Don't work.
SevenSlevin said:
External Sd Card man! Put your external sd card on PC and just copy from pc to it the update.app of b151 or b150 (I think it's the same), in a folder called "dload" (just create it) . After put your external on your phone and use 3 buttons.
Click to expand...
Click to collapse
Hi SevenSlevin,
I tried your solution but that don't work that continue black screen, no buzz no red light..
have you or anybody another solution please??
More and more strange... Take a look:
usb 3-2: new high-speed USB device number 24 using xhci_hcd
[35458.945542] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[35458.945556] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35458.945558] usb 3-2: Product: Fastboot2.0
[35458.945560] usb 3-2: Manufacturer: Fastbo
[35458.945562] usb 3-2: SerialNumber: FUH7N16627059031
[38407.154339] usb 3-2: USB disconnect, device number 24
[38409.399645] usb 3-2: new high-speed USB device number 25 using xhci_hcd
[38409.528094] usb 3-2: New USB device found, idVendor=18d1, idProduct=d00d
[38409.528097] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38409.528099] usb 3-2: Product: Fastboot2.0
[38409.528100] usb 3-2: Manufacturer: Fastbo
[38409.528101] usb 3-2: SerialNumber: FUH7N16627059031
Why the manufacturer have change to Fastbo?? why the product name is now Fastboot2.0?? I dont understand
for recovery and twrp is fastboot flash recovery not boot...other than that yeah you are using twrp for p9(eva). Try with the tools on this forum to flash twrp... and you just tried with boot and system...i told you to flash more files... and we need another info about why system flash failed... also check if bootloader is unlocked... maybe it's re locked
Like snapdesign wrote before, obtain the b151 firmware (vns-l31 or vns-l21 depending on your model).
Extract the zip file. Then you will get the update.app.
Use Huawei Update Extractor to extract the firmware files from the update.app.
ONLY flash boot.img, system.img and recovery.img. DON'T flash anything else. If you really want to flash everything either flash trough the phone after it boots properly or use DC-Phoenix (paid and dangerous, it will flash anything).
Don't mess with backdoor commands. Those commands require a special packet to be enabled.
Edit: And whatever you do, DO NOT use dd to flash those images. They all seem to have some kind of header in the beginning of the file (most likely a signature for validation).
Edit 2: Since you are flashing a wrong twrp recovery (P9 instead of P9-lite) and you are flashing it to the boot partition instead of the recovery partition, it is normal that your phone doesn't boot. Flash each image to the proper partition.
Nogood news..
Well, I used the good tool now and with the SRKToolHuawei-STABLE-V1.3-20160619 I tried to connect via ADB with the drivers on Windows 7.
I can't connect on ADB.... I have a message "waiting for the device" non stop!!
I can't access to my device.
I tried with fastboot on Linux this commands:
fastboot flash recovery stockrecoveryp9mm.img
target reported max download size of 471859200 bytes
sending 'recovery' (35180 KB)...
OKAY [ 1.102s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.542s
And I tried this see on one web site booth don't work the firs have ok message but nothing on reboot and the second have error message.
~/Bureau/android-sdk-linux/tools$ fastboot flash recovery/boot stockrecoveryp9mm.img
target reported max download size of 471859200 bytes
sending 'recovery/boot' (35180 KB)...
OKAY [ 1.102s]
writing 'recovery/boot'...
FAILED (remote: partition error)
finished. total time: 1.124s
I don't know where the problem is..
Thank for helping me.
Richard
randhackr said:
Like snapdesign wrote before, obtain the b151 firmware (vns-l31 or vns-l21 depending on your model).
Extract the zip file. Then you will get the update.app.
Use Huawei Update Extractor to extract the firmware files from the update.app.
ONLY flash boot.img, system.img and recovery.img. DON'T flash anything else. If you really want to flash everything either flash trough the phone after it boots properly or use DC-Phoenix (paid and dangerous, it will flash anything).
Don't mess with backdoor commands. Those commands require a special packet to be enabled.
Edit: And whatever you do, DO NOT use dd to flash those images. They all seem to have some kind of header in the beginning of the file (most likely a signature for validation).
Edit 2: Since you are flashing a wrong twrp recovery (P9 instead of P9-lite) and you are flashing it to the boot partition instead of the recovery partition, it is normal that your phone doesn't boot. Flash each image to the proper partition.
Click to expand...
Click to collapse
Hi, I have do this now with b151 vns-l31 firmware and my phone have no change:
~/Bureau/android-sdk-linux/tools$ fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (14002 KB)...
OKAY [ 0.432s]
writing 'boot'...
OKAY [ 0.326s]
finished. total time: 0.758s
[email protected]:~/Bureau/android-sdk-linux/tools$ fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (451070 KB)...
OKAY [ 13.916s]
writing 'system'...
OKAY [ 5.886s]
sending sparse 'system' (457911 KB)...
OKAY [ 14.172s]
writing 'system'...
OKAY [ 5.639s]
sending sparse 'system' (460613 KB)...
OKAY [ 14.565s]
writing 'system'...
OKAY [ 6.551s]
sending sparse 'system' (454334 KB)...
OKAY [ 14.091s]
writing 'system'...
OKAY [ 5.747s]
sending sparse 'system' (451030 KB)...
OKAY [ 13.811s]
writing 'system'...
OKAY [ 5.571s]
sending sparse 'system' (284111 KB)...
OKAY [ 8.716s]
writing 'system'...
OKAY [ 3.559s]
finished. total time: 112.226s
fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (33120 KB)...
OKAY [ 1.009s]
writing 'recovery'...
OKAY [ 0.752s]
finished. total time: 1.761s
fastboot reboot
rebooting...
finished. total time: 0.122s
Any idea??
Odd. But now you should create a folder on the microsd card named dload and copy the update.app there.
Try to boot the recovery (power + vol up). If it works reboot the phone and do the three button combo.
Edit: You can try to do a factory reset or also try dc-phoenix to flash the phone but it costs 15€ and doesn't flash the oeminfo partition (and again it is a dangerous tool).
randhackr said:
Odd. But now you should create a folder on the microsd card named dload and copy the update.app there.
Try to boot the recovery (power + vol up). If it works reboot the phone and do the three button combo.
Edit: You can try to do a factory reset or also try dc-phoenix to flash the phone but it costs 15€ and doesn't flash the oeminfo partition (and again it is a dangerous tool).
Click to expand...
Click to collapse
Hi randhackr,
I tried all your solutions and no one work with my crazy phone..
I tried to with dc-phoenix and that is the output:
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : HUAWEI VNS-L31
Model : Huawei phone in fastboot mode
IMEI : 869400029XXXXXX
Serial NR. : FUH7N16627059031
Firmware : VNS-L31C432B150
IMEI:8694000294XXXXX
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 0 Is it normal?
AND:
Authorising phone...
Phone authorization fail!
Port unavailable
anufacturer - Huawei phones
model - Huawei P9 series
Selected Diagnostics port COM19
The soft cant contact in ADB mode or in fastboot mode i Think... I'm gonna be crazy!!
i have buy phone las week, do you think is it possible to change it by warranty?
I have successfully recovered my dead/hard brick moto g4 plus mobile using below process.
To give you background, I have hard bricked my new moto g4 plus mobile. To do that, I have unlocked boot loader which void my warranty, then I have rooted yet and got root access. Till that it was working. After that I have installed custom rom cyanogenmod 14.1 . It was still working for some days. Now As I came from blackberry z10 to moto, I was missing blackberry hub features, so I downloaded BlackBerry android OS(Blackberry Priv) and tried to flash it. that's it, it stopped working. I know it was stupid things to do . I have given mobile to service center, other few famous mobile repairing shops, but no one was able to do anything.
My mobile was dead for almost 1 month, I tried lots of option, including MI flash tool, QPST(QFIL) etc. but didn't get it thought it. For current options also I was working for couple days, after that I got the solution.
Let start work now.....
------------------------------------------------------
There are two parts for this tutorial,
Part1 - make your device bootable/softbrick/start in recovery mode. This is difficult part and most of us stuck here only. We need to make device from hard brick to soft brick. Should work for all Qualcomm devices(except hardware failure).
Part2 - Flash ROM to your device. This is easy part and there are lots tutorial/information available to flashing ROM into device. It will be dependent on individual devices.
Part1:- -
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Download QualcommDrv.zip from here , extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe (if you have 64-bit Windows) to install the Qualcomm driver
now please connect your Qualcomm Mobile to PC or laptop Your phone should now being detected as “Qualcomm HS-USB QDLoader 9008” and the driver version 2.0.8.7 (please check it through Windows’ “Device Manager”). If its not detected, then you can keep mobile connecting to computer and press power button and volume down button.( This is for motorola g4 plus and can be different for your mobile. )
Now you have your mobile connected to computer, now follow the below steps.
Please download zip " blankflash1.zip" from location here extract it your computer and goto extracted folder and click blank-flash.bat
It will start in command prompt and detect device on your computer port(eg. COM5, COM8 etc).
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile. Refer below Part2 for this.
If above didn't work and you are getting error like below..
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Or any other error, then its little tricky to solve this.
Follow the below steps.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 2.059] ReadFile() failed, GetLastError()=0
[ 2.563] ...cpu.id = 2418 (0x972)
[ 2.563] ...cpu.sn = 28194769 (0x1ae37d1)
[ 2.563] Opening singleimage
[ 2.563] Loading package
[ 2.563] ...filename = singleimage.pkg.xml
[ 2.563] Loading programmer
[ 2.563] ...filename = programmer.mbn
[ 2.563] Sending programmer
[ 2.793] Handling things over to programmer
[ 2.793] Identifying CPU version
[ 2.793] Waiting for firehose to get ready
[ 5.800] ...MSM8952 1.1
[ 5.800] Determining target secure state
[ 5.800] ...secure = yes
[ 5.816] Flashing GPT...
[ 5.816] Flashing partition:0 with gpt_main0.bin
[ 5.816] Initializing storage
[ 5.816] Configuring device...
[ 5.832] ...blksz = 512
[ 6.331] Re-initializing storage...
[ 6.331] Initializing storage
[ 6.362] Flashing bootloader...
[ 6.362] Flashing aboot with emmc_appsboot.mbn
[ 6.721] Flashing rpm with rpm.mbn
[ 6.783] Flashing tz with tz.mbn
[ 7.033] Flashing hyp with hyp.mbn
[ 7.080] Flashing cmnlib with cmnlib.mbn
[ 7.158] Flashing keymaster with keymaster.mbn
[ 7.236] Flashing sbl1 with sbl1.mbn
[ 7.392] Rebooting to fastboot
[ 7.392] Total time: 7.392s
5. once this is complete then you mobile will boot in bootloader/recovery mode, or you can go to recovery mode using volume up/down button.
After this, your mobile would be detected using adb(android driver), and you can execute fastboot commands.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
Step3 is the key for whole process. you may need to try multiple times while blank-flash.bat is running.
Once you reached here, Congratulations, your mobile is saved and back to life. next part flashing stock rom is very easy. I will try to find url for that.
you just need correct ROM for your mobile and steps to flash it.
Part 2 :
Below is url for motorola, you will get idea how to do it for your mobile by going through it.
Alternative, now you can give your mobile to service center or mobile repair shop to flash ROM.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
https://forum.xda-developers.com/showthread.php?t=2131284
https://www.xda-developers.com/how-to-install-custom-rom-android/
Let me know if you have any doubts/questions, I will try to update.
Also let me know if it helps you and you can also Donate (Optional).
Thanks for the help, it is good to know that there are people helping others but I already repaired it with the same method thanks for responding
Secure=no
vijayjadhav_143 said:
I have successfully recovered my dead/hard brick moto g4 plus mobile using below process.
To give you background, I have hard bricked my new moto g4 plus mobile. To do that, I have unlocked boot loader which void my warranty, then I have rooted yet and got root access. Till that it was working. After that I have installed custom rom cyanogenmod 14.1 . It was still working for some days. Now As I came from blackberry z10 to moto, I was missing blackberry hub features, so I downloaded BlackBerry android OS(Blackberry Priv) and tried to flash it. that's it, it stopped working. I know it was stupid things to do . I have given mobile to service center, other few famous mobile repairing shops, but no one was able to do anything.
My mobile was dead for almost 1 month, I tried lots of option, including MI flash tool, QPST(QFIL) etc. but didn't get it thought it. For current options also I was working for couple days, after that I got the solution.
Let start work now.....
------------------------------------------------------
There are two parts for this tutorial,
Part1 - make your device bootable/softbrick/start in recovery mode. This is difficult part and most of us stuck here only. We need to make device from hard brick to soft brick. Should work for all Qualcomm devices(except hardware failure).
Part2 - Flash ROM to your device. This is easy part and there are lots tutorial/information available to flashing ROM into device. It will be dependent on individual devices.
Part1:- -
Make your PC into Test Mode.
Then run “CMD” or “Windows Terminal” as administrator and type:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Download QualcommDrv.zip from here , extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe (if you have 64-bit Windows) to install the Qualcomm driver
now please connect your Qualcomm Mobile to PC or laptop Your phone should now being detected as “Qualcomm HS-USB QDLoader 9008” and the driver version 2.0.8.7 (please check it through Windows’ “Device Manager”). If its not detected, then you can keep mobile connecting to computer and press power button and volume down button.( This is for motorola g4 plus and can be different for your mobile. )
Now you have your mobile connected to computer, now follow the below steps.
Please download zip " blankflash1.zip" from location here extract it your computer and goto extracted folder and click blank-flash.bat
It will start in command prompt and detect device on your computer port(eg. COM5, COM8 etc).
If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile. Refer below Part2 for this.
If above didn't work and you are getting error like below..
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 4.072] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.072] Check qboot_log.txt for more details
[ 4.072] Total time: 4.072s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
Or any other error, then its little tricky to solve this.
Follow the below steps.
1. Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.
4. keep trying step 3 unless you dont see below logs.
Code:
C:\Users\Vijay\Desktop\blankflashathene\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ 2.059] ReadFile() failed, GetLastError()=0
[ 2.563] ...cpu.id = 2418 (0x972)
[ 2.563] ...cpu.sn = 28194769 (0x1ae37d1)
[ 2.563] Opening singleimage
[ 2.563] Loading package
[ 2.563] ...filename = singleimage.pkg.xml
[ 2.563] Loading programmer
[ 2.563] ...filename = programmer.mbn
[ 2.563] Sending programmer
[ 2.793] Handling things over to programmer
[ 2.793] Identifying CPU version
[ 2.793] Waiting for firehose to get ready
[ 5.800] ...MSM8952 1.1
[ 5.800] Determining target secure state
[ 5.800] ...secure = yes
[ 5.816] Flashing GPT...
[ 5.816] Flashing partition:0 with gpt_main0.bin
[ 5.816] Initializing storage
[ 5.816] Configuring device...
[ 5.832] ...blksz = 512
[ 6.331] Re-initializing storage...
[ 6.331] Initializing storage
[ 6.362] Flashing bootloader...
[ 6.362] Flashing aboot with emmc_appsboot.mbn
[ 6.721] Flashing rpm with rpm.mbn
[ 6.783] Flashing tz with tz.mbn
[ 7.033] Flashing hyp with hyp.mbn
[ 7.080] Flashing cmnlib with cmnlib.mbn
[ 7.158] Flashing keymaster with keymaster.mbn
[ 7.236] Flashing sbl1 with sbl1.mbn
[ 7.392] Rebooting to fastboot
[ 7.392] Total time: 7.392s
5. once this is complete then you mobile will boot in bootloader/recovery mode, or you can go to recovery mode using volume up/down button.
After this, your mobile would be detected using adb(android driver), and you can execute fastboot commands.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
Step3 is the key for whole process. you may need to try multiple times while blank-flash.bat is running.
Once you reached here, Congratulations, your mobile is saved and back to life. next part flashing stock rom is very easy. I will try to find url for that.
you just need correct ROM for your mobile and steps to flash it.
Part 2 :
Below is url for motorola, you will get idea how to do it for your mobile by going through it.
Alternative, now you can give your mobile to service center or mobile repair shop to flash ROM.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Other link for flashing ROM into any android mobile:
https://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
https://forum.xda-developers.com/showthread.php?t=2131284
https://www.xda-developers.com/how-to-install-custom-rom-android/
Let me know if you have any doubts/questions, I will try to update.
Also let me know if it helps you and you can also Donate (Optional).
Click to expand...
Click to collapse
For me it is showing secure=no and waiting for firehose to get ready is constantly popping out plz plz help me
Irvin16 said:
For me it is showing secure=no and waiting for firehose to get ready is constantly popping out plz plz help me
Click to expand...
Click to collapse
Could you please provide more details? on which steps you are getting error? error log/screenshot?
Its command prompt activity so not sure how you are getting pop up.
for moto g4 play
Colleague you have this file for moto g4 play
you can try above files, these are blankflash files meaning, after this your mobile will be reboot in recovery mode and will be available to connect it using adb/android driver and after that you can flash Moto g4 play stock ROM. you can search for moto g4 stock rom on internet.
fo moto g4 play
vijayjadhav_143 said:
you can try above files, these are blankflash files meaning, after this your mobile will be reboot in recovery mode and will be available to connect it using adb/android driver and after that you can flash Moto g4 play stock ROM. you can search for moto g4 stock rom on internet.
Click to expand...
Click to collapse
It's giving you this error.
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 1797 (0x705)
[ -0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.010] Failed identify board. Wrong package?
[ 0.010] ERROR: error loading package
[ 0.010] Check qboot_log.txt for more details
[ 0.010] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
try with other blankflash.
tecnologianet2 said:
It's giving you this error.
[ -0.000] Opening device: \\.\COM8
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 1797 (0x705)
[ -0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ 0.010] Failed identify board. Wrong package?
[ 0.010] ERROR: error loading package
[ 0.010] Check qboot_log.txt for more details
[ 0.010] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
Click to expand...
Click to collapse
Did you tried with other blankflash*.zip, Please note below lines.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
for moto g4 play
vijayjadhav_143 said:
Did you tried with other blankflash*.zip, Please note below lines.
Note: blankflash1.zip file is working for motorola moto g 4 plus, it should work for other mobiles also. If that doesn't work with your mobile then try with blankflash2.zip and blankflash3.zip files. download here
blankflash1.zip -- is for latest mobile above android lollipop,
blankflash2.zip -- for android lollipop.
blankflash3.zip -- for Kitkat devices.
please try with 1,2 and 3 in order.
Click to expand...
Click to collapse
error logs
blankflash1
[ 0.000] Opening device: \\.\COM8
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 1797 (0x705)
[ 0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] Failed identify board. Wrong package?
[ 0.000] ERROR: error loading package
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
blankflash2
opening device: \\.\COM8
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.010s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
blankflash3
opening device: \\.\COM8
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
tecnologianet2 said:
error logs
blankflash1
[ 0.000] Opening device: \\.\COM8
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 1797 (0x705)
[ 0.000] ...cpu.sn = 574581666 (0x223f6ba2)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.000] Failed identify board. Wrong package?
[ 0.000] ERROR: error loading package
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.010s
FAILED: qb_flash_singleimage()->error loading package
blankflash2
opening device: \\.\COM8
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.010s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.000s]
validating files
OKAY [ 0.000s]
switching to download mode
OKAY [ 0.010s]
greeting device for image downloading
OKAY [ 0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
blankflash3
opening device: \\.\COM8
OKAY [ -0.000s]
greeting device for command mode
OKAY [ -0.000s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.010s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ -0.000s]
validating files
OKAY [ -0.000s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)
Click to expand...
Click to collapse
please try below options to fix error (Unexpected packet: 4. Was expecting: 3)
1. Copy only singleimage.bin file from blankflash1 to blankfalsh 2 folder and run,
if not working then
2. revert above change, and only copy programmer.mbn in from blankflash1 to blankflash and run,
if not working then,
3. revert above changed and copy both programmer.mbn and singleimage.bin file from blankflash1 to blankflash2 and run.
please let me know the result.
for moto g4 play
vijayjadhav_143 said:
please try below options to fix error (Unexpected packet: 4. Was expecting: 3)
1. Copy only singleimage.bin file from blankflash1 to blankfalsh 2 folder and run,
if not working then
2. revert above change, and only copy programmer.mbn in from blankflash1 to blankflash and run,
if not working then,
3. revert above changed and copy both programmer.mbn and singleimage.bin file from blankflash1 to blankflash2 and run.
please let me know the result.
Click to expand...
Click to collapse
erro log
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
Ta giving same error i need singleimage file for moto g4 play
tecnologianet2 said:
erro log
opening device: \\.\COM8
OKAY [ 0.003s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x223F6BA2
...chip-id = 0x705
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.008s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.006s]
validating files
FAILED (blank-flash:validate-singleimage:invalid single image)
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
Ta giving same error i need singleimage file for moto g4 play
Click to expand...
Click to collapse
you are really close of it because I was also getting error "Unexpected packet: 4. Was expecting: 3" then I tried few combinations of singleimage.bin and programmer.mbn files and it worked.
did you tried other combinations?
for moto g4 play
Yes many combinations
tecnologianet2 said:
Yes many combinations
Click to expand...
Click to collapse
Ok. Sorry, Actually I tried many days and many ways. I dont remember each and every things but these are the steps which helped me to get things done. there might be few difference due to different mobile you have. I will check my system and will check if I get some more details/scripts etc.
Don't give up.
fo moto g4 play
Poblema this in the singleimage.bin that is not for the model moto g4 play I need for this model
Blankflash files are device specific
siredux said:
Blankflash files are device specific
Click to expand...
Click to collapse
No, it's not because moto g4 play has another motherboard and moto g4 plus too.
Specifications for moto g4 play
Chipset
Qualcomm Snapdragon 410 MSM8916 Cortex-A53
tecnologianet2 said:
No, it's not because moto g4 play has another motherboard and moto g4 plus too.
Click to expand...
Click to collapse
OP says any Qualcomm device can be unbricked with this blankflash which is not true. This is only for G4/G4+. If you want to unbrick G4 Play you need that specific blankflash file, otherwise it will remain as a cute paperweight, duh
Will anyone from xda be able to create a blank image for this moto g4 play
I recently got a new Moto G7 (XT1962-5) and almost instantly bricked it while trying to install LineageOS (forgot the copy_partitions step :-/)
Now I no longer get into fastboot, but I still see the phone as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" with "lsusb" (I'm on Linux).
Reading the forum I had some hope to revive it via a blankflash, but the error message I get includes
[email protected]:~/Downloads/blankflash$ sudo ./qboot blank-flash
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.003] ...cpu.id = 186 (0xba)
[ 0.003] ...cpu.sn = 675895826 (0x28495a12)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.mbn
[ 0.009] Sending programmer
[ 0.291] Handling things over to programmer
[ 0.291] Identifying CPU version
[ 0.294] Waiting for firehose to get ready
[ 3.300] Target NAK!
[ 3.300] ...This version of programmer has been revoked!
[ 3.300] ...Rebooting to blank flash mode in 30 seconds...
So it seems that the blankflash image I'm using (https://mirrors.lolinet.com/firmware/moto/river/blankflash/blankflash_from_QPUS30.52-16-2-5.zip) is too old.
Does anyone know whether there is a more recent one available? Any other hints are also greatly appreciated!
I have no idea why, but using the blankflash from https://drive.google.com/open?id=1ShVC_VUJXIKkexunWpt1qtCRB29N0BlZ worked (found in https://forum.xda-developers.com/t/blankflash-moto-g7-xt1962-5-river-reteu-9-0-ppo29-80-66.4020263/), although it is supposed to be for a different model. Now back to installing!
Larabiata said:
I have no idea why, but using the blankflash from https://drive.google.com/open?id=1ShVC_VUJXIKkexunWpt1qtCRB29N0BlZ worked (found in https://forum.xda-developers.com/t/blankflash-moto-g7-xt1962-5-river-reteu-9-0-ppo29-80-66.4020263/), although it is supposed to be for a different model. Now back to installing!
Click to expand...
Click to collapse
Do you have the blankflash still with you to share. please??
After trying everything and failing, this file saved me.
C:\blankflash_river_QPU30.52-23>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 0.007] ...cpu.id = 186 (0xba)
[ 0.007] ...cpu.sn = 4075180311 (0xf2e65117)
[ 0.008] Opening singleimage
[ 0.117] Loading package
[ 0.123] ...filename = singleimage.pkg.xml
[ 0.126] Loading programmer
[ 0.127] ...filename = programmer.mbn
[ 0.127] Sending programmer
[ 0.413] Handling things over to programmer
[ 0.414] Identifying CPU version
[ 0.418] Waiting for firehose to get ready
[ 3.444] ...MSM8953 1.0
[ 3.444] Determining target secure state
[ 3.447] ...secure = yes
[ 3.502] Configuring device...
[ 3.512] Flashing GPT...
[ 3.513] Flashing partition with gpt.bin
[ 3.524] Initializing storage
[ 3.561] ...blksz = 512
[ 3.692] Re-initializing storage...
[ 3.693] Initializing storage
[ 3.811] Flashing bootloader...
[ 3.844] Flashing aboot_a with emmc_appsboot.mbn
[ 4.107] Flashing rpm_a with rpm.mbn
[ 4.190] Flashing tz_a with tz.mbn
[ 4.493] Flashing devcfg_a with devcfg.mbn
[ 4.544] Flashing cmnlib_a with cmnlib_30.mbn
[ 4.765] Flashing cmnlib64_a with cmnlib64_30.mbn
[ 4.998] Flashing keymaster_a with keymaster64.mbn
[ 5.213] Flashing prov_a with prov.mbn
[ 5.286] Flashing sbl1_a with sbl1.mbn
[ 5.420] Rebooting to fastboot
[ 5.423] Total time: 5.425s
guy thank you very much you're a god
Welcome to this unbrick tutorial
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
fastboot devices
Click to expand...
Click to collapse
If a line appears, your phone is correctly connected.
Type the command :
fastboot flash super super.img
Click to expand...
Click to collapse
If it flashed correctly, you should see something like this :
C:\Users\Alex\Desktop\platform-tools>fastboot flash super super.img
Invalid sparse file format at header magic
Sending sparse 'super' 1/9 (786428 KB) OKAY [ 19.574s]
Writing 'super' OKAY [ 0.013s]
Sending sparse 'super' 2/9 (786428 KB) OKAY [ 19.587s]
Writing 'super' OKAY [ 0.018s]
Sending sparse 'super' 3/9 (786428 KB) OKAY [ 19.609s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 4/9 (698716 KB) OKAY [ 17.393s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 5/9 (765968 KB) OKAY [ 19.103s]
Writing 'super' OKAY [ 0.010s]
Sending sparse 'super' 6/9 (763420 KB) OKAY [ 19.074s]
Writing 'super' OKAY [ 0.017s]
Sending sparse 'super' 7/9 (786097 KB) OKAY [ 19.636s]
Writing 'super' OKAY [ 0.009s]
Sending sparse 'super' 8/9 (786089 KB) OKAY [ 19.745s]
Writing 'super' OKAY [ 0.029s]
Sending sparse 'super' 9/9 (102406 KB) OKAY [ 2.853s]
Writing 'super' OKAY [ 6.798s]
Finished. Total time: 167.087s
Click to expand...
Click to collapse
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.
Download the correct region and version of the firmware.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
fastboot reboot fastboot
Click to expand...
Click to collapse
You should reboot into fastbootd.
Then use :
fastboot getvar all
Click to expand...
Click to collapse
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
fastboot set_active b
Click to expand...
Click to collapse
If you're on a slot, or :
fastboot set_active a
Click to expand...
Click to collapse
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Update :
Here are listed all the Super Partitions available for us to fix our Nothing :
1.1.3 EEA : Link
1.1.4 Global : Link
More to come...
Remember that you have to download the Sh4ttered tool version according to the version you are trying to restore.
Again, feel free to share a backup of yours that is not listed here to help other in need
Reserved 2
i have super img latest 1.14 global
ayed78 said:
i have super img latest 1.14 global
Click to expand...
Click to collapse
Can you upload it and share the link?
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.
Code:
Erasing 'userdata' OKAY [ 0.027s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Wiping data on userspace fastboot works:
Code:
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata' OKAY [ 0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s
There were also problems with flashing to B slot.
Code:
Sending 'odm_b' (1052 KB) OKAY [ 0.024s]
Writing 'odm_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 6.057s]
Writing 'product_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB) OKAY [ 6.077s]
Writing 'system_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 6.133s]
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB) OKAY [ 0.083s]
Writing 'tz_b' OKAY [ 0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 6.079s]
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
arinc9 said:
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.
Code:
Erasing 'userdata' OKAY [ 0.027s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Wiping data on userspace fastboot works:
Code:
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata' OKAY [ 0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s
There were also problems with flashing to B slot.
Code:
Sending 'odm_b' (1052 KB) OKAY [ 0.024s]
Writing 'odm_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 6.057s]
Writing 'product_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB) OKAY [ 6.077s]
Writing 'system_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 6.133s]
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB) OKAY [ 0.083s]
Writing 'tz_b' OKAY [ 0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 6.079s]
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
Click to expand...
Click to collapse
The Persist partition contains the unique calibration settings for the sensors on your phone. It cannot be recovered. If it's really corrupted, the only way is to send the phone back for warranty for now.
On Xiaomi forum, they solved the issue by flashing the persist partition from a stock fastboot rom, can't tell if it'll work with yours but you Can Always give it a try if you can find a persist partition backup
For the B slot, I think I had errors too, but switching slots fixed mine.
AntoXik72 said:
Can you upload it and share the link?
Click to expand...
Click to collapse
2.98 GB file on MEGA
mega.nz
persist global 1.1.4
5.5 MB file on MEGA
mega.nz
ayed78 said:
persist global 1.1.4
5.5 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thank you so much, this fixed it!!! I only know how to backup partitions with TWRP, did you do this with an android app?
arinc9 said:
Thank you so much, this fixed it!!! I only know how to backup partitions with TWRP, did you do this with an android app?
Click to expand...
Click to collapse
yes...
ayed78 said:
yes...
Click to expand...
Click to collapse
What's the name of the app?
arinc9 said:
What's the name of the app?
Click to expand...
Click to collapse
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
This one for example.
ayed78 said:
2.98 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
That's perfect, thanks, i'll update the post tonight
AntoXik72 said:
That's perfect, thanks, i'll update the post tonight
Click to expand...
Click to collapse
AntoXik72 said:
Welcome to this unbrick tutorial
This tutorial is EEA only at the moment
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
Unlocked bootloader both classic and critical unlock Link
Sh4ttered Tool (the 1.1.3 update!! for now as I don't have a super partition backup for both 1.1.4 or 1.1.3 Global) Link
1.1.3 super partition (EEA Only at the moment, feel free to share a Global one in the comments) Link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
If a line appears, your phone is correctly connected.
Type the command :
If it flashed correctly, you should see something like this :
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, Run the Download.ps1 with powershell and download the 1.1.3 EEA made by Sh4ttered and downloaded earlier.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
You should reboot into fastbootd.
Then use :
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
If you're on a slot, or :
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
very good man, I'm busy rn so it's sooo good that you wrote this for everyone, thanks!
AntoXik72 said:
Welcome to this unbrick tutorial
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
If a line appears, your phone is correctly connected.
Type the command :
If it flashed correctly, you should see something like this :
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.
Download the correct region and version of the firmware.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
You should reboot into fastbootd.
Then use :
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
If you're on a slot, or :
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
pankspoo said:
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
Click to expand...
Click to collapse
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.
For the downgrade, I can't tell, try it at your own risks.
AntoXik72 said:
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.
For the downgrade, I can't tell, try it at your own risks.
Click to expand...
Click to collapse
Actullly the term you use must be revive phone from bootloop like that.
Any way thanks
mine still stuck at fastboot...nothing tool not update....it detect lower version update on mine 1.1.4 global