Well, I get this error on my galaxy fit, a few days ago reinstall a fresh rom (aokp jb by erikcas), failed much and reboot, no longer able to LAUNCH and only see the logo "Samsung Galaxy Fit", try reinstalling the stock firmware with ODIN but I have always this result:
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> mibib download..
<1> 1/9 Finished.
<1> qcsbl download..
<1> 2/9 Finished.
<1> oemsbl download..
<1> 3/9 Finished.
<1> amss download..
<1> 4/9 Finished.
<1> arm11boot download..
<1> 5/9 Finished.
<1> boot.img download..
<1> 6/9 Finished.
<1> recovery.img download..
<1> 7/9 Finished.
<1> system.rfs download..
<1> 8/9 Finished.
<1> csc.rfs download..
<1> 9/9 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
now after trying to reinstall the stock firmware in recovery mode automatically starts. Anyone have any solution?, And browse the network without satisfactory result.
________________________________________________________________________________________________________________________________
I experimented and it seems it is a problem with the data partition on the device and dalvik cache, try to mount the data partition but I can not, the recovery freezes try like if I try to wipe data reset. Any idea?
Try flashing old froyo
samo_gf said:
Try flashing old froyo
Click to expand...
Click to collapse
Thanks bro!!!!! Now its working!!!!! :victory:
FxSxKx said:
Thanks bro!!!!! Now its working!!!!! :victory:
Click to expand...
Click to collapse
You're welcome
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'
hello
my phone stuck on the circles dots that spins i gave it like 30 mints and nothing, when i try to plug it in the PC i dont have the drivers and when i try to get in the recovery mode i get the no command massage
i really dont know what to do now...
ty for your help
When you boot to recovery, you don't see the dead android on his back?
when i try to get to recovery i see the dead android with no command
but i have access to boot loader (not really helping)
When you see the dead android, press and hold power button, then press volume up.
audit13 said:
When you see the dead android, press and hold power button, then press volume up.
Click to expand...
Click to collapse
together or one after another?
what i should see?
One after the other and it will take you I to stock recovery.
ok got to there
when i try to make wipe i get stuck and the the died android get flashing(same as cache)
What happens when you factory wipe? How do you get back to the android?
when i factory wipe i see the dead android flashing like every 5 sec for 1 mili sec
and if i want to get back to boot loader or something else i press power button and up\down
i think its the cache that doing the problem becuas when i do the factory rest its saying:
--Wiping data...
formatting \data...(1-2 minuts wait)
formatting \cache...
after 5 sec flashing of dead android
and if i do wipe of cache i get the flashing like 5 sec after...
Try flashing a stock rom via fastboot. Make sure to perform a factory wipe before booting the rom for the first time.
audit13 said:
Try flashing a stock rom via fastboot. Make sure to perform a factory wipe before booting the rom for the first time.
Click to expand...
Click to collapse
how can i flash a rom if i dont have any drivers and the Pc dont recognize the phone when i press on "update from ADB"...?
Did you install the drivers before connecting the phone? You can't use stock recovery to flash a stock rom, you use fastboot mode.
Have you tried different USB cables, USB ports, computers, and operating systems? Is the bootloader unlocked?
ok so this is the deal with the phone.
i didn't touch this phone for the last 3 mounts and now i am thinking to buy new one or to fix this(prefer to fix).
the pc that i am using dont have the driver and the phone wont start(stuck in loop-dots circle) so i cant really install the drivers properly.
the phone is unlock-root dont remember if it have superuser and i cant think of a way to fix it
i dont have fast boot mode
thank you for your help i realy need him alive
Not sure how the phone can't have fastboot mode. What happens when you try to boot into fastboot mode?
i got the driver on the PC and tryed to install the factory rom
after he finished the phone starts to go up but still stuck on the circle dots(waited all day)
after that tried to wipe again and nothing..
After flashing the stock ROM, boot back into fastboot mode, flash userdata.img file, immediately boot into recovery from fastboot mode, perform a factory wipe, reboot.
"flash userdata.img file, immediately boot into recovery from fast boot mode"
need more info for that please its new to me...
how i can flash it if i dont have recovery mode?
i am using nrt program to install the images, if you have any other why i would like to know
just tried Flashing the factory images using method 1 from here:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
but no success. got this error in the cmd line, GOT any suggestions?
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.284s]
writing 'bootloader'...
FAILED (remote flash write failure)
finished. total time 0.490s
rebooting into bootloader...
OKAY [ 0.106s]
finished. total time 0.109s
target reported max download size of 1073741824 bytes
sending 'radio' (42033 KB)...
OKAY [ 1.496s]
writing 'radio'...
FAILED (remote flash write failure)
finished. total time 2.725s
rebooting into bootloader...
OKAY [ 0.102s]
finished. total time 0.104s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters
Size 13725835264
Block size 4096
Blocks per group 32768
Inodes per group 8144
Inode size 256
Journal blocks 32768
Label
Blocks 3351034
Block groups 103
Reserved block group size 823
Created filesystem with 11838832 inodes and 936543351034 blocks
Creating filesystem with parameters
Size 734003200
Block size 4096
Blocks per group 32768
Inodes per group 7472
Inode size 256
Journal blocks 2800
Label
Blocks 179200
Block groups 6
Reserved block group size 47
Created filesystem with 1144832 inodes and 5813179200 blocks
--------------------------------------------
Bootloader Version... HHZ12h
Baseband Version..... M8974A-2.0.50.2.26
Serial Number........ 04b3d59122d76e25
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ12h'.
Update requires 'HHZ11d'.
finished. total time 0.547s
Press any key to exit...
Is the bootloader unlocked before the flashed process starts?
the phone is ulocked and if i try to get in bootloader i get the died android, in the prosses of the flash of the factory imege the phone stayes in the same state(in fastboot) after its finished i get all the failers and then the phone restarts and stuck on the dots spin
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