Related
Good day,
I flashed my phone to gingerbread lately (the latest build). But I didn't like it as it was taking up more RAM(174 MB where Froyo occupied just 150-160 MB) so I wanted to flash back to Froyo. I downloaded the latest Indian version S5830DDKC1. It contained a single package which was a .tar file. I was successful in flashing the firmware. But the phone didn't reboot. I got these messages:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> amss download..
<1> 1/5 Finished.
<1> boot.img download..
<1> 2/5 Finished.
<1> recovery.img download..
<1> 3/5 Finished.
<1> system.rfs download..
<1> 4/5 Finished.
<1> csc.rfs download..
<1> 5/5 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
But later I tried to flash to gingerbread and it worked. Please help. It would be appreciated.
Thank you in advance.
I got a problem, downloaded RC2 Final from broodROM post in i9001, started odin, aries and broodROMRC2.tar.md5,sonected phone in boot mode (green logo with download under it) and clicked start and after 30 min still stuck on
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> amss.mbn download..
<1> 1/7 Finished.
<1> adsp.mbn download..
<1> 2/7 Finished.
<1> boot.img download..
<1> 3/7 Finished.
<1> system.img.ext4 download..
. disconected phone and start all over again and same, then formated win7 and installed xp and still same , please help. THX
Hi everybody, yesterday I install cyanogenmod 11 unofficial in my Huawei p6, I have unlocked the bootloader, all works fine, I used for a long time, after that I started charging from the computetr USB port , I went out for 3 hours, when I back the smartphone was off, I turned on, but the Logo Huawei ascend don't change, , after I go to recovery mode, I had installed TWRP 2.8.1.0, when I try to wipe, a error ocurred, "unable to mount /data" and other folders, after that I try to restored the original recovery, I used Fastboot, but nothing happens, the flash is good, but when I reboot in recovery mode appears TWRP, please help me, this smarphone is new, I bought them one month ago.
I'll be very grateful if someone helps me:crying::crying:
When I flash boot and recovery.
"F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
erase boot
erasing 'boot'...
OKAY [ 0.002s]
finished. total time: 0.002s
F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
flash boot boot.img
target reported max download size of 838860800 bytes
sending 'boot' (5658 KB)...
OKAY [ 0.188s]
writing 'boot'...
OKAY [ 0.300s]
finished. total time: 0.489s
F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
erase recovery
erasing 'recovery'...
OKAY [ 0.005s]
finished. total time: 0.005s
F:\Programas\Ejecutables\Sdk y Eclipse para android\sdk\platform-tools>fastboot
flash recovery recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.529s]
writing 'recovery'...
OKAY [ 0.664s]
finished. total time: 1.195s"
try this
try this forum out and if that is something you have tried pm me and ill help you to fix your problem
http://forum.xda-developers.com/showthread.php?t=2534420
Didn't work
Deltax82 said:
try this forum out and if that is something you have tried pm me and ill help you to fix your problem
http://forum.xda-developers.com/showthread.php?t=2534420
Click to expand...
Click to collapse
I was watching and I can not modify any folder in the root directory, eg put a file in "/ system", I reset the smarphone and the file disappears, I probe this command from the console windows "adb shell dmesg" and showed some errors, I think they are serious
---------------------------------------------------------------------------------------------------------------------------------
<7> [104.0, recovery] [13.020177] EXT4-fs (mmcblk0p19): ext4_orphan_cleanup: deleting unreferenced inode
<2> [104.0, recovery] [14.755787] EXT4-fs error (device mmcblk0p19): ext4_readdir: 214: inode # 113127: blo
ck 460238: comm recovery: path (unknown): bad entry in directory: rec_len is smaller than minimal - offset =
0 (0), inode = 16777216, rec_len = 0, name_len = 0
<3> [104.0, recovery] [14.755814] Aborting journal on device mmcblk0p19-8.
<2> [104.0, recovery] [14.755824] EXT4-fs (mmcblk0p19): Remounting filesystem read-only
<2> [104.0, recovery] [14.823290] EXT4-fs error (device mmcblk0p19): ext4_readdir: 214: inode # 113247: blo
ck 459687: comm recovery: path /data/data/de.robv.android.xposed.installer/app_webview: bad entry in direct
ory: rec_len% 4 = 0 - offset = 0 (0), inode = 1118398749, rec_len = 55815, name_len = 0!
---------------------------------------------------------------------------------------------------------------------------------
is a part, the there are more lines of this.
Format data
Wipe
Type 'Yes'
.
.
.
.
HOW TO UNBRICK A HARD BRICKED MOTO Z XT1650-03
Note: This is only for Moto Z XT1650-03. Don't use this for any other device, i'm not responsible if anything happens to your device.
My Moto Z died in January because of flashing a wrong file and it wont power on or charge. And the service center wont help because Motorola voids your warranty the moment you get the unlock code from their website. So i kept digging for 3 months and finally my phone is back from the dead. And i'd like to help other people who are struggling with the same problem.
So, things you'll need:
-A dead Moto Z with no boot/charging at all
-Drivers
-Blankflash file
-Stock Rom/Custom Rom
How To Unbrick:
Step 1: If your PC detecta the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)
Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.
Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.
Cheers :highfive:
Thanks, dude, but it didn't work.
My phone is listed in device manager as qualcomm hs-usb qdloader 9008, but when I try to run the batch script it fails.
Here's the log, if it helps:
**** Log buffer [000001] 2017-04-15_15:21:57 ****
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 3.001] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 3.001] Check qboot_log.txt for more details
[ 3.001] Total time: 3.016s
[ 3.001]
[ 3.001] qboot version 3.37
[ 3.001]
[ 3.001] DEVICE {
[ 3.001] name = "\\.\COM4",
[ 3.001] flags = "0x64",
[ 3.001] addr = "0x61FE5C",
[ 3.001] api.bnr = "0x8E2C38",
[ 3.001] }
[ 3.001]
[ 3.001]
[ 3.001] Backup & Restore {
[ 3.001] num_entries = 0,
[ 3.001] restoring = "false",
[ 3.001] backup_error = "not started",
[ 3.001] restore_error = "not started",
[ 3.001] }
[ 3.001]
martonto said:
Thanks, dude, but it didn't work.
My phone is listed in device manager as qualcomm hs-usb qdloader 9008, but when I try to run the batch script it fails.
Here's the log, if it helps:
**** Log buffer [000001] 2017-04-15_15:21:57 ****
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 3.001] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 3.001] Check qboot_log.txt for more details
[ 3.001] Total time: 3.016s
[ 3.001]
[ 3.001] qboot version 3.37
[ 3.001]
[ 3.001] DEVICE {
[ 3.001] name = "\\.\COM4",
[ 3.001] flags = "0x64",
[ 3.001] addr = "0x61FE5C",
[ 3.001] api.bnr = "0x8E2C38",
[ 3.001] }
[ 3.001]
[ 3.001]
[ 3.001] Backup & Restore {
[ 3.001] num_entries = 0,
[ 3.001] restoring = "false",
[ 3.001] backup_error = "not started",
[ 3.001] restore_error = "not started",
[ 3.001] }
[ 3.001]
Click to expand...
Click to collapse
Try a different port. And avoid USB 3.0 ports
Still no go. I've been looking for another solution, but I'm yet to have any luck.
It seems there's a qualcomm utility to fix this called BordDiag, but I haven't found one that supports the msm8996 chipset.
Thanks, anyway!
Solved!
It finally worked! I've managed to boot into fastboot mode and flash my ROM. My moto Z is now working again!
If anyone ever happens to come across the same error I mentioned in my previous post, there's a trick to solve it that I found in another thread:
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.
source: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Thank you again, Manish54! I wouldn't have done it so soon without your help.
martonto said:
It finally worked! I've managed to boot into fastboot mode and flash my ROM. My moto Z is now working again!
If anyone ever happens to come across the same error I mentioned in my previous post, there's a trick to solve it that I found in another thread:
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.
source: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Thank you again, Manish54! I wouldn't have done it so soon without your help.
Click to expand...
Click to collapse
You're welcome
Manish54 said:
.
.
.
.
HOW TO UNBRICK A HARD BRICKED MOTO Z XT1650-03
Note: This is only for Moto Z XT1650-03. Don't use this for any other device, i'm not responsible if anything happens to your device.
My Moto Z died in January because of flashing a wrong file and it wont power on or charge. And the service center wont help because Motorola voids your warranty the moment you get the unlock code from their website. So i kept digging for 3 months and finally my phone is back from the dead. And i'd like to help other people who are struggling with the same problem.
So, things you'll need:
-Drivers
-Blankflash file
-Stock Rom/Custom Rom
How To Unbrick:
Step 1: If your PC detecta the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)
Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.
Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.
Cheers :highfive:
Click to expand...
Click to collapse
Hello. I have a Sheridan XT1650-03 that I cannot get your fix to work for. I had the Motorola drivers installed so my phone appeared as a "Motorola ADB Interface" in the device manager. When I ran your batch file it hung on "waiting for device" and no matter what USB port I plugged into, 2.0 or 3.0, it's stuck at "waiting for device". So I manually uninstalled the Motorola drivers and forced the install of the drivers you provided so that my phone appears in device manager as "Qualcomm HS-USB QDLoader 9008". Same problem no matter where is plug it in. I have tried this on two different computers with the same result. Can you help me get past "waiting for device"?
twitchfidelis said:
Hello. I have a Sheridan XT1650-03 that I cannot get your fix to work for. I had the Motorola drivers installed so my phone appeared as a "Motorola ADB Interface" in the device manager. When I ran your batch file it hung on "waiting for device" and no matter what USB port I plugged into, 2.0 or 3.0, it's stuck at "waiting for device". So I manually uninstalled the Motorola drivers and forced the install of the drivers you provided so that my phone appears in device manager as "Qualcomm HS-USB QDLoader 9008". Same problem no matter where is plug it in. I have tried this on two different computers with the same result. Can you help me get past "waiting for device"?
Click to expand...
Click to collapse
Are you getting the same "waiting for device error even are it's on Qualcomm..9008 mode?
Do you have universal adb drivers installed?
Manish54 said:
Are you getting the same "waiting for device error even are it's on Qualcomm..9008 mode?
Do you have universal adb drivers installed?
Click to expand...
Click to collapse
I am unclear on what you mean by Qualcomm..9008 mode. I have installed the drivers you provided and the phone appears as Qualcomm HS-USB QDLoader 9008 in Device Manager, but still the batch script hangs on waiting for device. The phone is in fastboot bootloader mode, is there a seperate Qaulcomm..9008 mode or is this just a misunderstanding?
I do not know if I have the universal adb drivers you are talking about. Do you have a link? I installed minimal adb and fastboot from here.
https://forum.xda-developers.com/showthread.php?t=2317790
twitchfidelis said:
I am unclear on what you mean by Qualcomm..9008 mode. I have installed the drivers you provided and the phone appears as Qualcomm HS-USB QDLoader 9008 in Device Manager, but still the batch script hangs on waiting for device. The phone is in fastboot bootloader mode, is there a seperate Qaulcomm..9008 mode or is this just a misunderstanding?
I do not know if I have the universal adb drivers you are talking about. Do you have a link? I installed minimal adb and fastboot from here.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
It's the same. I skipped the middle portion. Qualcomm HS-USB QDLoader 9008.
And you said the batch file says waiting for device and then you said the phone is in fastboot bootloader mode. Please confirm if you're phone is dead or not. If it's booting into bootloader then you should flash your rom normally.
Here is the adb driver: http://adbdriver.com/downloads/
Manish54 said:
It's the same. I skipped the middle portion. Qualcomm HS-USB QDLoader 9008.
And you said the batch file says waiting for device and then you said the phone is in fastboot bootloader mode. Please confirm if you're phone is dead or not. If it's booting into bootloader then you should flash your rom normally.
Here is the adb driver:
Click to expand...
Click to collapse
Yes the batch file says waiting for device. If I open a command prompt and type "fastboot devices" my device is listed. My phone is not dead the screen is clearly on with the icon of the Android lying on its back with a chest panel open and the first line of text says "AP Fastboot Flash Mode (Secure)".
twitchfidelis said:
Yes the batch file says waiting for device. If I open a command prompt and type "fastboot devices" my device is listed. My phone is not dead the screen is clearly on with the icon of the Android lying on its back with a chest panel open and the first line of text says "AP Fastboot Flash Mode (Secure)".
Click to expand...
Click to collapse
Well man... Then this thread is not for you. It is for a dead phone with no boot/charging at all. If you're already on the bootloader then what's stopping you from flashing a rom?
I managed to flash it with a different set of instructions. There is an issue it appears with Windows 10 and RSD Lite maybe it's related to this but who knows. Thanks for your help anyway!
hello i have a hard bricked moto z and i can't get it detected on the pc. i have tried on multiple different pc's ALOT of times but it never shows up. any advice?
MOTO Z Hardbricked
Hellow everyone,
my moto z also got hard brick.Tried manish's tutorial and I was successful till the end.But my phone even now dead.I will paste the command lines and the responses I got. Thanks
Code:
C:\Users\pterion\Desktop\blankflash\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.37
[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 2375 (0x947)
[ 0.000] ...cpu.sn = 43926045 (0x29e421d)
[ 0.000] Opening singleimage
[ 0.016] Loading package
[ 0.016] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.elf
[ 0.016] Sending programmer
[ 0.094] Handling things over to programmer
[ 0.094] Identifying storage type
[ 0.094] Waiting for firehose to get ready
[ 3.141] ...UFS
[ 3.141] Identifying CPU version
[ 3.156] ...MSM8996 3.1
[ 3.156] Determining target secure state
[ 3.156] ...secure = yes
[ 3.266] Configuring device...
[ 3.297] Skipping UFS provsioning as target is secure
[ 3.297] Configuring device...
[ 3.594] Skipping 'setbootablestoragedrive' as target is secure
[ 3.594] Flashing GPT...
[ 3.594] Flashing partition:0 with gpt_main0.bin
[ 3.594] Initializing storage
[ 3.828] ...blksz = 4096
[ 3.828] ...part = "SAMSUNG KLUBG4G1CE-B0B1 0800 "
[ 4.641] Flashing partition:1 with gpt_main1.bin
[ 4.672] Flashing partition:2 with gpt_main2.bin
[ 4.703] Flashing partition:3 with gpt_main3.bin
[ 4.750] Re-initializing storage...
[ 4.750] Initializing storage
[ 5.781] Flashing bootloader...
[ 5.797] Flashing xbl with xbl.elf
[ 5.938] Flashing cmnlib with cmnlib.mbn
[ 5.985] Flashing cmnlib64 with cmnlib64.mbn
[ 6.047] Flashing prov with prov64.mbn
[ 6.094] Flashing aboot with emmc_appsboot.mbn
[ 6.188] Flashing keymaster with keymaster.mbn
[ 6.250] Flashing rpm with rpm.mbn
[ 6.281] Flashing pmic with pmic.elf
[ 6.313] Flashing hyp with hyp.mbn
[ 6.360] Flashing tz with tz.mbn
[ 6.485] Flashing devcfg with devcfg.mbn
[ 6.512] Rebooting to fastboot
[ 6.528] Waiting for device to disconnect
[ 8.535] Total time: 8.535s
randomthots said:
Hellow everyone,
my moto z also got hard brick.Tried manish's tutorial and I was successful till the end.But my phone even now dead.I will paste the command lines and the responses I got. Thanks
Click to expand...
Click to collapse
If you had Nougat on before, your bootloader was updated to v91.05. However, the currently available unbrick files contain bootloader files of v91.03. The downgraded bootloader detects that and skips right back into the "9008"-download mode.
I've assembled a package with the current v91.05 bootloader and the most recent partition layout I had at hand, see attachment.
unbrick package with bootloader 91.05 files (timestamp: 2017-01-06 02:58:48, build id: git=MBM-NG-V91.05-0-gd081b7e)
benzinerwin said:
If you had Nougat on before, your bootloader was updated to v91.05. However, the currently available unbrick files contain bootloader files of v91.03. The downgraded bootloader detects that and skips right back into the "9008"-download mode.
I've assembled a package with the current v91.05 bootloader and the most recent partition layout I had at hand, see attachment.
unbrick package with bootloader 91.05 files (timestamp: 2017-01-06 02:58:48, build id: git=MBM-NG-V91.05-0-gd081b7e)
Click to expand...
Click to collapse
Thanks a lot.
Much appreciated
randomthots said:
Thanks a lot.
Much appreciated
Click to expand...
Click to collapse
In case anyone had a more recent stock rom OTA runnning you'd been updated to bootloader version 91.07, requiring the following unbrick files...
unbrick package with bootloader 91.07 files from 25.221.12 OTA,
GPT seq#0008 (timestamp: 2017-03-30 04:41:31, build id: git=MBM-NG-V91.07-0-gd081b7e)
The package was built from the 25.221.12 OTA update package. Not updated items were taken from when last supplied (i.e. 25.11.14). The GPT sequence counter reached #0008.
Will this work on z play? I have a XT1635-02 bricked now and I tried with v91.03, v91.05 and v91.07, they all give me output like below.
Do I need specific blankflash file on different phone models / bootloader versions?
From the cmd:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.006] Check qboot_log.txt for more details
[ 4.006] Total time: 4.008s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
In the log:
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.006] Check qboot_log.txt for more details
[ 4.006] Total time: 4.008s
[ 4.007]
[ 4.007] qboot version 3.40
[ 4.007]
[ 4.007] DEVICE {
[ 4.007] name = "\\.\COM5",
[ 4.007] flags = "0x64",
[ 4.007] addr = "0x61FE5C",
[ 4.007] api.bnr = "0xFB2920",
[ 4.007] }
[ 4.007]
[ 4.007]
[ 4.007] Backup & Restore {
[ 4.007] num_entries = 0,
[ 4.007] restoring = "false",
[ 4.007] backup_error = "not started",
[ 4.007] restore_error = "not started",
[ 4.007] }
[ 4.007]
Hard Brick Moto Z Play
Fellows, I hope you can help me with the Blankflash file for the MZP.
I left it in full brick, I was locating MM and Nougat going down with the script Downgrade and going up with adb sideload and it happened when installing Nougat again.
It should be mentioned that I was with the April patch, I downgraded to MM Brazil patch November, restart and install the apps as always and personalize, then by adb add patch December, restart and reinstalled N but when finished instead of reboot , I chose to boot bootloader and alli brickeo.
All this only with the Bootloader open, no Root or any modification, now it does not turn on anything and if I connect it to the charger or pc only the charging led flashes, when connecting the pc I recognize it as ¨Qualcomm hs-usb qdloader 9008 COM5¨ I used e Blankflash for the bike z and did not finish the process and the 1,2 and 3 dce XDA and neither.
If someone can pass me the Blankflash will thank you, please.
I arrived here:
Blur_Version.25.211.10.addison.retail.en.US - Security April 2017
NPN 25.137-24-1-9
Download here:
Blur_Version.24.221.12.addison.retail.en.US - Security November 2016
MPNS24.104-44-10
Install this:
Blur_Version.24.231.19.addison.retail.en.US - Security December 2016
MPNS24.104-44-16
Then bricke it at the end of the process:
Blur_Version.25.21.2.addison.retail.en.US - Android 7.0 Nougat January 2017
NPN25.137-15.2
By the way a colleague Ali Guzman from the face group I passed this compilation NPN25.137-24-1 with the included blankflash but in the middle of the process notifies me of package error.
I pass the link in case someone serves:
Https://mega.nz/#!nMdEFLxY!4x0BZWr45...anoX16JZv5B5-E
Http://lenovo-forums.ru/files/category/140-moto-z-play/
Here are two archives with blankflash available so far
ATT Channel Software
thank you very much.
my p2 got hard brick, no way to enter to fastboot and recovery, even with any configuration button, when connected to pc i only get red blinking led, screen show blank, and in pc device manager just show Qualcomm HS-USB QDLoader 9008, no solution how to Resurrected from death even with qfil tool or miflash tool, luckily now back to live after 3 month death, here what i did:
before all started, first recharge your p2 for 1/2 an hour to make sure enough battery more than 20%,
install lenovo p2 usb driver: https://mega.nz/#!rQgjACaJ!-ZVi7TDUgtVaUVEe7yGZ-jr4ijarO704T7x2IQdVjeU,
install qualcomm usb driver:
https://mega.nz/#!GNRWiQrJ!ASpU78MPYzh-I4EUiK_ba5YtlZUTQHP_r_P4Dd7hSZg
reboot your pc,
connect your p2 to pc,
go to pc device manager, you will see in pc device manager like in screenshot, if you didn't see like that press vol +and- togather with power button, hold all of them till appear like screenshoot
now download zip file blankflash tool https://mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8, extract it, and place it in c folder your pc,
open folder and run blank-flash.bat,
automaticly your p2 will start reboot to fastboot,
or if your rom still intack p2 will reboot to system os,
Or if no os, now you can flash rom from fastboot
congratulation now your p2 back to live.
hendibudi said:
my p2 got hard brick, no way to enter to fastboot and recovery, even with any configuration button, when connected to pc i only get red blinking led, screen show blank, and in pc device manager just show Qualcomm HS-USB QDLoader 9008, no solution how to Resurrected from death even with qfil tool or miflash tool, luckily now back to live after 3 month death, here what i did:
before all started, first recharge your p2 for 1/2 an hour to make sure enough battery more than 20%,
install lenovo p2 driver,
reboot your pc,
connect your p2 to pc,
go to pc device manager,
you will see in pc device manager like in screenshot,
now download zip file blankflash tool, extract it, and place it in c folder your pc,
open folder and run blank-flash.bat,
automaticly your p2 will start reboot to fastboot,
or if your rom still intack p2 will reboot to system os,
congratulation now your p2 back to live
Click to expand...
Click to collapse
Thanks! Please post a link to download that BlankFlash Tool.
kermex said:
Thanks! Please post a link to download that BlankFlash Tool.
Click to expand...
Click to collapse
When upload finished there is link
hendibudi said:
When upload finished there is link
Click to expand...
Click to collapse
Great! Thanks again!
hendibudi said:
my p2 got hard brick, no way to enter to fastboot and recovery, even with any configuration button, when connected to pc i only get red blinking led, screen show blank, and in pc device manager just show Qualcomm HS-USB QDLoader 9008, no solution how to Resurrected from death even with qfil tool or miflash tool, luckily now back to live after 3 month death, here what i did:
before all started, first recharge your p2 for 1/2 an hour to make sure enough battery more than 20%,
install lenovo p2 driver,
reboot your pc,
connect your p2 to pc,
go to pc device manager,
you will see in pc device manager like in screenshot,
now download zip file blankflash tool, extract it, and place it in c folder your pc,
open folder and run blank-flash.bat,
automaticly your p2 will start reboot to fastboot,
or if your rom still intack p2 will reboot to system os,
congratulation now your p2 back to live
Click to expand...
Click to collapse
Waiting for download link. Will this fix no signal issue? Does it have non-holos.bin? Also if my device is working can I use that tool?
Sent from my Lenovo P2 using Tapatalk
abhayruparel said:
Waiting for download link. Will this fix no signal issue? Does it have non-holos.bin? Also if my device is working can I use that tool?
Sent from my Lenovo P2 using Tapatalk
Click to expand...
Click to collapse
No download link. I'm waiting for it, too. Maybe he doesn't want to share this.
kermex said:
No download link. I'm waiting for it, too. Maybe he doesn't want to share this.
Click to expand...
Click to collapse
Be patients for couple of days, compare to me waiting 3 months my p2 death back to live, cause i have limited data
hendibudi said:
Be patients for couple of days, compare to me waiting 3 months my p2 death back to live, cause i have limited data
Click to expand...
Click to collapse
Why you don't use wifi?!
kermex said:
Why you don't use wifi?!
Click to expand...
Click to collapse
Where?
hendibudi said:
Where?
Click to expand...
Click to collapse
He meant that why don't you use Wi-Fi for uploading. Please reply to #5
OK, thanks! Just forgot about this.
the laptop loses the portconnection and I get
readfile() failed , getlastError()=31
anny idea how to fix this?
Datech2 said:
after identifying CPU I get
the laptop loses the portconnection and I get
readfile() failed , getlastError()=31
anny idea how to fix this?
Click to expand...
Click to collapse
How about p2
hendibudi said:
How about p2
Click to expand...
Click to collapse
no reaction , the red led keeps blinking ,
when push de power button and the volume + he reconnects
Datech2 said:
no reaction , the red led keeps blinking ,
when push de power button and the volume + he reconnects
Click to expand...
Click to collapse
Check first post step by step
Yes blankflash method works. But I must push VolDown + Power buttons in the right moment to done it properly.
So below are my instructions. I also put my log. Without pushing the buttons I have IOError.
1. Install Latest Qualcomm 9008 Driver from link below and restart PC:
androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
2. Download flashbank.zip from link below
mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8
3. Unpack archive to C:\lenovo (or other directory if you are poweruser and you will know what to change in steps below)
4. Open cmd and go to C:\lenovo\
5. Turn off the phone, and connect to USB, in Device Manager you should see Qualcomm 9008 device in Ports (LPT & COMM) section (or something like this)
6. Push VolumeDown + Power buttons together
7. In cmd run command below
qboot blank-flash
8. When in cmd text below appear, release VolumeDown + Power buttons
Waiting for firehose to get ready ......
9. Now the phone should boot into Fastboot
My log:
C:\lenovo>qboot blank-flash
Opening device: \\.\COM3
OKAY [ 0.004s]
Detecting device
...cpu.id = 70 (0x46)
...cpu.sn = 2326272297 (0x8aa81929)
OKAY [ 7.010s]
Opening singleimage
OKAY [ 0.001s]
Loading package
...filename = bootloader.qboot.xml
OKAY [ 0.011s]
Loading programmer
...filename = programmer.mbn
OKAY [ 0.007s]
Sending programmer
OKAY [ 0.247s]
Handling things over to programmer
Waiting for firehose to get ready ......
Identifying CPU
...MSM8953 1.1
Storage Information
...physical partition number: 0
...num_partition_sectors=61071360
...SECTOR_SIZE_IN_BYTES=512
...num_physical_partitions=3
...MFR_ID=144
...OEM_ID=74
...Product name=HBG4a2
...{"storage_info": {"total_blocks":61071360, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":144, "serial_num":574148832, "fw_version":"164","mem_type":"eMMC", "prod_name":"HBG4a2"}}
Flashing partition sbl1 with sbl1.mbn (375KB)
....100%
Flashing partition sbl1bak with sbl1.mbn (375KB)
....100%
Flashing partition rpm with rpm.mbn (170KB)
..100%
Flashing partition rpmbak with rpm.mbn (170KB)
..100%
Flashing partition tz with tz.mbn (1447KB)
.....100%
Flashing partition tzbak with tz.mbn (1447KB)
.....100%
Flashing partition devcfg with devcfg.mbn (36KB)
..100%
Flashing partition devcfgbak with devcfg.mbn (36KB)
..100%
Flashing partition aboot with emmc_appsboot.mbn (854KB)
....100%
Flashing partition abootbak with emmc_appsboot.mbn (854KB)
....100%
Flashing partition lksecapp with lksecapp.mbn (56KB)
....100%
Flashing partition lksecappbak with lksecapp.mbn (56KB)
....100%
Flashing partition cmnlib with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlibbak with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlib64 with cmnlib64.mbn (249KB)
..100%
Flashing partition cmnlib64bak with cmnlib64.mbn (249KB)
..100%
Flashing partition keymaster with keymaster.mbn (220KB)
..100%
Flashing partition keymasterbak with keymaster.mbn (220KB)
..100%
Flashing partition prov with prov32.mbn (64KB)
....100%
Flashing partition PrimaryGPT with gpt_main0.bin (17KB)
..100%
Flashing partition BackupGPT with gpt_backup0.bin (16KB)
....100%
Patching DISK -- Update last partition 56 'userdata' with actual size in Primary Header.
Patching DISK -- Update last partition 56 'userdata' with actual size in Backup Header.
Patching DISK -- Update Primary Header with LastUseableLBA.
Patching DISK -- Update Backup Header with LastUseableLBA.
Patching DISK -- Update Primary Header with BackupGPT Header Location.
Patching DISK -- Update Backup Header with CurrentLBA.
Patching DISK -- Update Backup Header with Partition Array Location.
Patching DISK -- Update Primary Header with CRC of Partition Array.
Patching DISK -- Update Backup Header with CRC of Partition Array.
Patching DISK -- Zero Out Header CRC in Primary Header.
Patching DISK -- Update Primary Header with CRC of Primary Header.
Patching DISK -- Zero Out Header CRC in Backup Header.
Patching DISK -- Update Backup Header with CRC of Backup Header.
OKAY [ 4.572s]
finished. total time: 11.861s
It worked like charm.[emoji106][emoji106][emoji106]
Sent from my Lenovo P2a42 using Tapatalk
I lost sim modem after flashing stock firmware
Anyway to restore it?
You'd only do this to restore fastboot or, if possible, boot into an existing OS, right? There's no way of recovering a lost signal by flashing modem?
slimok5 said:
Yes blankflash method works. But I must push VolDown + Power buttons in the right moment to done it properly.
So below are my instructions. I also put my log. Without pushing the buttons I have IOError.
1. Install Latest Qualcomm 9008 Driver from link below and restart PC:
androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
2. Download flashbank.zip from link below
mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8
3. Unpack archive to C:\lenovo (or other directory if you are poweruser and you will know what to change in steps below)
4. Open cmd and go to C:\lenovo\
5. Turn off the phone, and connect to USB, in Device Manager you should see Qualcomm 9008 device in Ports (LPT & COMM) section (or something like this)
6. Push VolumeDown + Power buttons together
7. In cmd run command below
qboot blank-flash
8. When in cmd text below appear, release VolumeDown + Power buttons
Waiting for firehose to get ready ......
9. Now the phone should boot into Fastboot
My log:
C:\lenovo>qboot blank-flash
Opening device: \.\COM3
OKAY [ 0.004s]
Detecting device
...cpu.id = 70 (0x46)
...cpu.sn = 2326272297 (0x8aa81929)
OKAY [ 7.010s]
Opening singleimage
OKAY [ 0.001s]
Loading package
...filename = bootloader.qboot.xml
OKAY [ 0.011s]
Loading programmer
...filename = programmer.mbn
OKAY [ 0.007s]
Sending programmer
OKAY [ 0.247s]
Handling things over to programmer
Waiting for firehose to get ready ......
Identifying CPU
...MSM8953 1.1
Storage Information
...physical partition number: 0
...num_partition_sectors=61071360
...SECTOR_SIZE_IN_BYTES=512
...num_physical_partitions=3
...MFR_ID=144
...OEM_ID=74
...Product name=HBG4a2
...{"storage_info": {"total_blocks":61071360, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":144, "serial_num":574148832, "fw_version":"164","mem_type":"eMMC", "prod_name":"HBG4a2"}}
Flashing partition sbl1 with sbl1.mbn (375KB)
....100%
Flashing partition sbl1bak with sbl1.mbn (375KB)
....100%
Flashing partition rpm with rpm.mbn (170KB)
..100%
Flashing partition rpmbak with rpm.mbn (170KB)
..100%
Flashing partition tz with tz.mbn (1447KB)
.....100%
Flashing partition tzbak with tz.mbn (1447KB)
.....100%
Flashing partition devcfg with devcfg.mbn (36KB)
..100%
Flashing partition devcfgbak with devcfg.mbn (36KB)
..100%
Flashing partition aboot with emmc_appsboot.mbn (854KB)
....100%
Flashing partition abootbak with emmc_appsboot.mbn (854KB)
....100%
Flashing partition lksecapp with lksecapp.mbn (56KB)
....100%
Flashing partition lksecappbak with lksecapp.mbn (56KB)
....100%
Flashing partition cmnlib with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlibbak with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlib64 with cmnlib64.mbn (249KB)
..100%
Flashing partition cmnlib64bak with cmnlib64.mbn (249KB)
..100%
Flashing partition keymaster with keymaster.mbn (220KB)
..100%
Flashing partition keymasterbak with keymaster.mbn (220KB)
..100%
Flashing partition prov with prov32.mbn (64KB)
....100%
Flashing partition PrimaryGPT with gpt_main0.bin (17KB)
..100%
Flashing partition BackupGPT with gpt_backup0.bin (16KB)
....100%
Patching DISK -- Update last partition 56 'userdata' with actual size in Primary Header.
Patching DISK -- Update last partition 56 'userdata' with actual size in Backup Header.
Patching DISK -- Update Primary Header with LastUseableLBA.
Patching DISK -- Update Backup Header with LastUseableLBA.
Patching DISK -- Update Primary Header with BackupGPT Header Location.
Patching DISK -- Update Backup Header with CurrentLBA.
Patching DISK -- Update Backup Header with Partition Array Location.
Patching DISK -- Update Primary Header with CRC of Partition Array.
Patching DISK -- Update Backup Header with CRC of Partition Array.
Patching DISK -- Zero Out Header CRC in Primary Header.
Patching DISK -- Update Primary Header with CRC of Primary Header.
Patching DISK -- Zero Out Header CRC in Backup Header.
Patching DISK -- Update Backup Header with CRC of Backup Header.
OKAY [ 4.572s]
finished. total time: 11.861s
Click to expand...
Click to collapse
Hey I am stack on identifying the cpu
---------- Post added at 01:43 PM ---------- Previous post was at 01:34 PM ----------
slimok5 said:
Yes blankflash method works. But I must push VolDown + Power buttons in the right moment to done it properly.
So below are my instructions. I also put my log. Without pushing the buttons I have IOError.
1. Install Latest Qualcomm 9008 Driver from link below and restart PC:
androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
2. Download flashbank.zip from link below
mega.nz/#!PIZ0GChJ!3RhdFN38IajIVYQT_5ppZGxcconOntG1-d75vNK1Vg8
3. Unpack archive to C:\lenovo (or other directory if you are poweruser and you will know what to change in steps below)
4. Open cmd and go to C:\lenovo\
5. Turn off the phone, and connect to USB, in Device Manager you should see Qualcomm 9008 device in Ports (LPT & COMM) section (or something like this)
6. Push VolumeDown + Power buttons together
7. In cmd run command below
qboot blank-flash
8. When in cmd text below appear, release VolumeDown + Power buttons
Waiting for firehose to get ready ......
9. Now the phone should boot into Fastboot
My log:
C:\lenovo>qboot blank-flash
Opening device: \.\COM3
OKAY [ 0.004s]
Detecting device
...cpu.id = 70 (0x46)
...cpu.sn = 2326272297 (0x8aa81929)
OKAY [ 7.010s]
Opening singleimage
OKAY [ 0.001s]
Loading package
...filename = bootloader.qboot.xml
OKAY [ 0.011s]
Loading programmer
...filename = programmer.mbn
OKAY [ 0.007s]
Sending programmer
OKAY [ 0.247s]
Handling things over to programmer
Waiting for firehose to get ready ......
Identifying CPU
...MSM8953 1.1
Storage Information
...physical partition number: 0
...num_partition_sectors=61071360
...SECTOR_SIZE_IN_BYTES=512
...num_physical_partitions=3
...MFR_ID=144
...OEM_ID=74
...Product name=HBG4a2
...{"storage_info": {"total_blocks":61071360, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":144, "serial_num":574148832, "fw_version":"164","mem_type":"eMMC", "prod_name":"HBG4a2"}}
Flashing partition sbl1 with sbl1.mbn (375KB)
....100%
Flashing partition sbl1bak with sbl1.mbn (375KB)
....100%
Flashing partition rpm with rpm.mbn (170KB)
..100%
Flashing partition rpmbak with rpm.mbn (170KB)
..100%
Flashing partition tz with tz.mbn (1447KB)
.....100%
Flashing partition tzbak with tz.mbn (1447KB)
.....100%
Flashing partition devcfg with devcfg.mbn (36KB)
..100%
Flashing partition devcfgbak with devcfg.mbn (36KB)
..100%
Flashing partition aboot with emmc_appsboot.mbn (854KB)
....100%
Flashing partition abootbak with emmc_appsboot.mbn (854KB)
....100%
Flashing partition lksecapp with lksecapp.mbn (56KB)
....100%
Flashing partition lksecappbak with lksecapp.mbn (56KB)
....100%
Flashing partition cmnlib with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlibbak with cmnlib.mbn (196KB)
..100%
Flashing partition cmnlib64 with cmnlib64.mbn (249KB)
..100%
Flashing partition cmnlib64bak with cmnlib64.mbn (249KB)
..100%
Flashing partition keymaster with keymaster.mbn (220KB)
..100%
Flashing partition keymasterbak with keymaster.mbn (220KB)
..100%
Flashing partition prov with prov32.mbn (64KB)
....100%
Flashing partition PrimaryGPT with gpt_main0.bin (17KB)
..100%
Flashing partition BackupGPT with gpt_backup0.bin (16KB)
....100%
Patching DISK -- Update last partition 56 'userdata' with actual size in Primary Header.
Patching DISK -- Update last partition 56 'userdata' with actual size in Backup Header.
Patching DISK -- Update Primary Header with LastUseableLBA.
Patching DISK -- Update Backup Header with LastUseableLBA.
Patching DISK -- Update Primary Header with BackupGPT Header Location.
Patching DISK -- Update Backup Header with CurrentLBA.
Patching DISK -- Update Backup Header with Partition Array Location.
Patching DISK -- Update Primary Header with CRC of Partition Array.
Patching DISK -- Update Backup Header with CRC of Partition Array.
Patching DISK -- Zero Out Header CRC in Primary Header.
Patching DISK -- Update Primary Header with CRC of Primary Header.
Patching DISK -- Zero Out Header CRC in Backup Header.
Patching DISK -- Update Backup Header with CRC of Backup Header.
OKAY [ 4.572s]
finished. total time: 11.861s
Click to expand...
Click to collapse
Phone boot into fastboot but no light