Hi All,
I have made an custom ROM for Huawei U8818 device.I flashed my device with the fastboot protocol and I received following messages during flash of device.
Code:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot' (2806 KB)...
OKAY [ 0.713s]
writing 'boot'...
OKAY [ 0.778s]
sending 'recovery' (3124 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 0.602s]
sending 'system' (156310 KB)...
OKAY [ 39.081s]
writing 'system'...
OKAY [ 36.423s]
erasing 'userdata'...
OKAY [ 0.004s]
erasing 'cache'...
OKAY [ 0.007s]
rebooting...
finished. total time: 78.403s
From above it seems that device is flashed properly but when device is rebooting.
It does not proceed after boot screen.It simply stucks at boot screen.
How do I debug it.
Any suggestions.......
Related
Hello,
I've been using the leaked ICS version for GSM for about one week and this morning I tried to run some optimization script (motomize, I think). Since then it got stuck in a boot loop, remaining with the flashing M logo. Last operation I remember was running clean dalvik cache from the above application.
Got into recovery mode, cleaned dalvik cache -> same
Factory reset from recovery -> same
Used EPRJ_FlashITRZR_Windows.tar with the same image (SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip) and phone is now showing the dual core logo, screen going black, and after one minute the cycle repeats.
Tried several times to flash with the eternity tool and same result.
At first boot after flashing it shows the android on its back with the blue triangle. Pressing both vol keys shows the last log entries like:
Code:
E: can't mount /cache/recovery/....
...
E: can't open /cache/recovery/....
Output from eternity tool:
Code:
ECHO is off.
Flashing BootLogo....
sending 'logo' (854 KB)... OKAY [ 0.078s]
writing 'logo'... INFOno such partition
FAILED (remote: )
Flashing EBR....
sending 'ebr' (16 KB)... OKAY [ 0.249s]
writing 'ebr'... OKAY [ 0.483s]
Flashing MBR....
sending 'mbr' (16 KB)... OKAY [ 0.265s]
writing 'mbr'... OKAY [ 0.436s]
Flashing DevTree....
sending 'devtree' (512 KB)... OKAY [ 0.281s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android System....
sending 'system' (262144 KB)... OKAY [ 25.187s]
writing 'system'... OKAY [ 11.518s]
sending 'system' (262144 KB)... OKAY [ 27.961s]
writing 'system'... OKAY [ 10.583s]
sending 'system' (262144 KB)... OKAY [ 27.338s]
writing 'system'... OKAY [ 10.552s]
sending 'system' (6912 KB)... OKAY [ 0.733s]
writing 'system'... OKAY [ 0.343s]
Flashing Kernel....
sending 'boot' (8192 KB)... OKAY [ 0.810s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android Recovery....
sending 'recovery' (9216 KB)... OKAY [ 1.964s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Flashing CDR....
sending 'cdrom' (216832 KB)... OKAY [ 22.023s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Flashing Radio (BP)....
sending 'radio' (14404 KB)... OKAY [ 1.559s]
writing 'radio'... OKAY [ 1.761s]
Flashing WebTop....
sending 'webtop' (262144 KB)... OKAY [ 29.052s]
writing 'webtop'... OKAY [ 11.409s]
sending 'webtop' (262144 KB)... OKAY [ 29.941s]
writing 'webtop'... OKAY [ 10.598s]
sending 'webtop' (262144 KB)... OKAY [ 28.288s]
writing 'webtop'... OKAY [ 10.598s]
sending 'webtop' (262144 KB)... OKAY [ 28.818s]
writing 'webtop'... OKAY [ 10.614s]
sending 'webtop' (262144 KB)... OKAY [ 27.665s]
writing 'webtop'... OKAY [ 10.614s]
sending 'webtop' (54016 KB)... OKAY [ 5.284s]
writing 'webtop'... OKAY [ 2.416s]
Erasing Cache....
erasing 'cache'... OKAY [ 0.888s]
Rebooting....
rebooting...
ECHO is off.
ECHO is off.
Greets from the EternityProject!
Any more ideas?
brainwash123 said:
Hello,
I've been using the leaked ICS version for GSM for about one week and this morning I tried to run some optimization script (motomize, I think). Since then it got stuck in a boot loop, remaining with the flashing M logo. Last operation I remember was running clean dalvik cache from the above application.
Got into recovery mode, cleaned dalvik cache -> same
Factory reset from recovery -> same
Used EPRJ_FlashITRZR_Windows.tar with the same image (SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip) and phone is now showing the dual core logo, screen going black, and after one minute the cycle repeats.
Tried several times to flash with the eternity tool and same result.
At first boot after flashing it shows the android on its back with the blue triangle. Pressing both vol keys shows the last log entries like:
Code:
E: can't mount /cache/recovery/....
...
E: can't open /cache/recovery/....
Output from eternity tool:
Code:
ECHO is off.
Flashing BootLogo....
sending 'logo' (854 KB)... OKAY [ 0.078s]
writing 'logo'... INFOno such partition
FAILED (remote: )
Flashing EBR....
sending 'ebr' (16 KB)... OKAY [ 0.249s]
writing 'ebr'... OKAY [ 0.483s]
Flashing MBR....
sending 'mbr' (16 KB)... OKAY [ 0.265s]
writing 'mbr'... OKAY [ 0.436s]
Flashing DevTree....
sending 'devtree' (512 KB)... OKAY [ 0.281s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android System....
sending 'system' (262144 KB)... OKAY [ 25.187s]
writing 'system'... OKAY [ 11.518s]
sending 'system' (262144 KB)... OKAY [ 27.961s]
writing 'system'... OKAY [ 10.583s]
sending 'system' (262144 KB)... OKAY [ 27.338s]
writing 'system'... OKAY [ 10.552s]
sending 'system' (6912 KB)... OKAY [ 0.733s]
writing 'system'... OKAY [ 0.343s]
Flashing Kernel....
sending 'boot' (8192 KB)... OKAY [ 0.810s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Flashing Android Recovery....
sending 'recovery' (9216 KB)... OKAY [ 1.964s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Flashing CDR....
sending 'cdrom' (216832 KB)... OKAY [ 22.023s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Flashing Radio (BP)....
sending 'radio' (14404 KB)... OKAY [ 1.559s]
writing 'radio'... OKAY [ 1.761s]
Flashing WebTop....
sending 'webtop' (262144 KB)... OKAY [ 29.052s]
writing 'webtop'... OKAY [ 11.409s]
sending 'webtop' (262144 KB)... OKAY [ 29.941s]
writing 'webtop'... OKAY [ 10.598s]
sending 'webtop' (262144 KB)... OKAY [ 28.288s]
writing 'webtop'... OKAY [ 10.598s]
sending 'webtop' (262144 KB)... OKAY [ 28.818s]
writing 'webtop'... OKAY [ 10.614s]
sending 'webtop' (262144 KB)... OKAY [ 27.665s]
writing 'webtop'... OKAY [ 10.614s]
sending 'webtop' (54016 KB)... OKAY [ 5.284s]
writing 'webtop'... OKAY [ 2.416s]
Erasing Cache....
erasing 'cache'... OKAY [ 0.888s]
Rebooting....
rebooting...
ECHO is off.
ECHO is off.
Greets from the EternityProject!
Any more ideas?
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showpost.php?p=26915046&postcount=6
http://forum.xda-developers.com/showthread.php?p=26915046
Post Nr. 6 is the usual way to unbrick the EU Leak.
Gesendet von meinem XT910 mit Tapatalk 2
All right, toooo slow.
Gesendet von meinem XT910 mit Tapatalk 2
Many thanks, I was able to recover it!
This should be sticky somewhere, this seems to be the only way to recover after some bad settings on the GSM ICS.
Fortunately the data/sdcard partition was not wiped, since that is where I keep my titanium backups and only sync them with the NAS once per week. Lesson learned.
Thanks again, that was fast.
brainwash123 said:
Many thanks, I was able to recover it!
This should be sticky somewhere, this seems to be the only way to recover after some bad settings on the GSM ICS.
Fortunately the data/sdcard partition was not wiped, since that is where I keep my titanium backups and only sync them with the NAS once per week. Lesson learned.
Thanks again, that was fast.
Click to expand...
Click to collapse
No problem, just remember to thanks the original poster of the guide ^^
Just as a follow-up, you don't need to do a factory reset. I messed up again today and by flashing boot_new, system_signed and Blur*zip I was back to the configuration I had before.
You're losing root though and any /system modifications you did, but everything else is there.
Hi All,
i have created my own factory cable and i can now boot the phone up in to the recovery menu, but when i try to flash anything including the Utility i keep getting this error =
< waiting for device >
sending 'boot' (8192 KB)... OKAY [ 0.796s]
writing 'boot'... OKAY [ 0.830s]
sending 'recovery' (9216 KB)... OKAY [ 0.948s]
writing 'recovery'... FAILED (status read failed (Too many links))
Is there something i can do to correct this?
i also tried to do it manually and get the same,im on a UK razr if that helps
flash system system.img
< waiting for device >
sending 'system' (793344 KB)... OKAY [ 82.924s]
writing 'system'... INFOPreflash validation failure
FAILED (remote: )
finished. total time: 83.136s
flash radio radio.img
sending 'radio' (14404 KB)... OKAY [ 1.468s]
writing 'radio'... FAILED (status read failed (Too many links))
finished. total time: 2.124s
Hi, I´m trying to recovery my Huawei G740, and I have from the other Huawei G740 all files to recovery my phone (boot.img/recovery.img/system.img/userdata.img/cache.img and custom.img, but when I put all together with fastboot the phone don´t work, It try to start after that restart itself and come inside recovery mode, any suggestion or advice to make this work guys.Thank you.
I:\Android\sdk\platform-tools>fastboot devices
96ee49a fastboot
I:\Android\sdk\platform-tools>fastboot flash cache cache.img
sending 'cache' (196608 KB)...
OKAY [ 12.415s]
writing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 12.421s
I:\Android\sdk\platform-tools>fastboot flash cust cust.img
sending 'cust' (262144 KB)...
OKAY [ 16.512s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 16.517s
I:\Android\sdk\platform-tools> fastboot flash boot boot.img
sending 'boot' (12288 KB)...
OKAY [ 0.773s]
writing 'boot'...
OKAY [ 0.608s]
finished. total time: 1.382s
I:\Android\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.029s]
writing 'recovery'...
OKAY [ 1.023s]
finished. total time: 2.053s
I:\Android\sdk\platform-tools>fastboot flash userdata userdata.img
sending 'userdata' (460449 KB)...
OKAY [ 28.798s]
writing 'userdata'...
OKAY [ 22.669s]
finished. total time: 51.469s
I:\Android\sdk\platform-tools>fastboot flash system system.img
sending 'system' (445101 KB)...
OKAY [ 27.826s]
writing 'system'...
OKAY [ 21.810s]
finished. total time: 49.636s
I:\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.005s
Long time Droid Pro user who now has got a hold of a Droid RAZR XT912. I am trying to get it completely back to stock in order to flash it over to Pageplus. It IS a VZW XT912 was rooted and had safestrap 3.11 installed and I was running CM10.2 Spyder (very slick ROM). Anyhow I want to zero the phone back to stock and I don't have access to a windows machine that can RSD Lite back to stock so I am trying to use the Matt L Groff Batarang Droid RAZR script which is an amazing piece of work. So I put the XT912 into AP Fastboot and run the program in Linux and it does all the flash magic but it will not write the preinstall img or recovery img files...everything else works fine and the phone reboots into the radio programming screen and then reboots to a fresh install WITH superuser ROOT still intact. I did not install OTA Voodoo rootkeeper or any other root retention apk. Any ideas using the Linux script to flash the phone back to completely non rooted stock?
I tried to search all the message boards and threads but I can't find a specific solution....thank you for you time if anyone has any ideas? I downloaded the script twice and checked the MD5sums.
thanks in advance.
here is the script string
sending 'mbm' (512 KB)...
OKAY [ 0.039s]
writing 'mbm'...
OKAY [ 0.526s]
finished. total time: 0.565s
rebooting into bootloader...
OKAY [ 0.147s]
finished. total time: 0.147s
Press any key when the screen flashes back on.
sending 'mbmloader' (42 KB)...
OKAY [ 0.011s]
writing 'mbmloader'...
OKAY [ 0.292s]
finished. total time: 0.303s
sending 'mbm' (512 KB)...
OKAY [ 0.162s]
writing 'mbm'...
OKAY [ 0.582s]
finished. total time: 0.744s
rebooting into bootloader...
OKAY [ 0.154s]
finished. total time: 0.154s
Press any key when the screen flashes back on.
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s
sending 'logo.bin' (854 KB)...
OKAY [ 0.060s]
writing 'logo.bin'...
OKAY [ 0.286s]
finished. total time: 0.345s
sending 'devtree' (512 KB)...
OKAY [ 0.170s]
writing 'devtree'...
OKAY [ 0.514s]
finished. total time: 0.684s
error: cannot load 'system.img'
sending 'boot' (8192 KB)...
OKAY [ 0.512s]
writing 'boot'...
OKAY [ 0.885s]
finished. total time: 1.397s
sending 'recovery' (9216 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 1.421s]
finished. total time: 1.993s
error: cannot load 'preinstall.img'
sending 'radio' (21936 KB)...
OKAY [ 1.364s]
writing 'radio'...
OKAY [ 2.788s]
finished. total time: 4.153s
rebooting...
finished. total time: 0.150s
Your device will now reboot and install radio files, then fully boot normally.
Hi guys,
Recently after a
fastboot boot twrp-3.3.1-test43-hotdog-unified-mauronofrio.img
Click to expand...
Click to collapse
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Do you want to wipe all the data ( Reccomended )[Y/N]?n
Sending 'boot_b' (98304 KB) OKAY [ 2.785s]
Writing 'boot_b' OKAY [ 0.468s]
Finished. Total time: 3.700s
Sending 'dtbo' (16384 KB) OKAY [ 0.473s]
Writing 'dtbo' OKAY [ 0.043s]
Finished. Total time: 0.621s
Sending 'modem_b' (166356 KB) OKAY [ 4.741s]
Writing 'modem_b' OKAY [ 0.686s]
Finished. Total time: 6.146s
Sending 'reserve' (250136 KB) OKAY [ 7.109s]
Writing 'reserve' FAILED (remote: '(reserve_b)
No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 2.794s]
Writing 'recovery' OKAY [ 0.353s]
Finished. Total time: 3.314s
Sending 'vbmeta' (8 KB) OKAY [ 0.013s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.039s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.034s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.956s
Sending 'abl_b' (1164 KB) OKAY [ 0.036s]
Writing 'abl_b' OKAY [ 0.013s]
Finished. Total time: 0.071s
Sending 'aop_b' (200 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'bluetooth_b' (828 KB) OKAY [ 0.025s]
Writing 'bluetooth_b' OKAY [ 0.011s]
Finished. Total time: 0.057s
Sending 'cmnlib_b' (384 KB) OKAY [ 0.012s]
Writing 'cmnlib_b' OKAY [ 0.008s]
Finished. Total time: 0.036s
Sending 'cmnlib64_b' (500 KB) OKAY [ 0.015s]
Writing 'cmnlib64_b' OKAY [ 0.009s]
Finished. Total time: 0.042s
Sending 'devcfg_b' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'dsp_b' (65536 KB) OKAY [ 1.919s]
Writing 'dsp_b' OKAY [ 0.335s]
Finished. Total time: 2.553s
Sending 'hyp_b' (480 KB) OKAY [ 0.015s]
Writing 'hyp_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'imagefv_b' (20 KB) OKAY [ 0.001s]
Writing 'imagefv_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'keymaster_b' (248 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.007s]
Finished. Total time: 0.034s
Sending 'LOGO_b' (6540 KB) OKAY [ 0.195s]
Writing 'LOGO_b' OKAY [ 0.046s]
Finished. Total time: 0.284s
Sending 'multiimgoem_b' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_b' OKAY [ 0.006s]
Finished. Total time: 0.030s
Resizing 'odm_b' OKAY [ 0.006s]
Sending 'odm_b' (912 KB) OKAY [ 0.028s]
Writing 'odm_b' FAILED (Status read failed (T
oo many links))
fastboot: error: Command failed
Sending 'oem_stanvbk' (876 KB) FAILED (Write to device faile
d (No such file or directory))
fastboot: error: Command failed
Sending 'opproduct' (612316 KB) FAILED (Write to device faile
d (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'qupfw' (72 KB) OKAY [ 0.012s]
Writing 'qupfw' OKAY [ 0.003s]
Finished. Total time: 0.042s
Sending 'storsec' (24 KB) OKAY [ 0.007s]
Writing 'storsec' OKAY [ 0.003s]
Finished. Total time: 0.032s
Sending 'tz' (3092 KB) OKAY [ 0.096s]
Writing 'tz' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.011s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.037s
Sending 'xbl' (3120 KB) OKAY [ 0.094s]
Writing 'xbl' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.014s]
Writing 'xbl_config' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 23.363s]
Writing 'system' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 23.425s]
Writing 'vendor' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785428 KB) OKAY [ 23.379s]
Writing 'product' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Premere un tasto per continuare . . .
Click to expand...
Click to collapse
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Gorthan said:
Hi guys,
Recently after a
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Click to expand...
Click to collapse
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
thanks so much for your reply.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. Now I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in the Partition B and works properly.
mauronofrio said:
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
Click to expand...
Click to collapse
thanks so much for your reply. I followed your advice and actually helps.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in Partition B and works properly.
Update 2: I finally spend a bit of time on the phone and I already rooted. Thanks to @mauronofrio for help.