After I flashed stock rom with this method "http://asus-zenfone.blogspot.com/2014/06/zenfone-downgrade-tutorial.html", i cant turn on my zenfone. when i connect to PC just stuck on usb logo, and then off again. i looking for solution on google for a view days, still not found how to flash a rom to zenfone 4. i use worldwide stock rom UL-ASUS_T00I-WW-4.3.2.0-user.zip, as i know my zenfone use WW stock room with lower version.
Maepong said:
After I flashed stock rom with this method "http://asus-zenfone.blogspot.com/2014/06/zenfone-downgrade-tutorial.html", i cant turn on my zenfone. when i connect to PC just stuck on usb logo, and then off again. i looking for solution on google for a view days, still not found how to flash a rom to zenfone 4. i use worldwide stock rom UL-ASUS_T00I-WW-4.3.2.0-user.zip, as i know my zenfone use WW stock room with lower version.
Click to expand...
Click to collapse
Asus uses a method of copying a zipped fw on the external flash drive, plugging it into the device, then hitting very special button combo (I think holding vol+ and power to turn on the device, but you have to google it). Thus you can flash a softbricked device with correct fw
izzylaif said:
Asus uses a method of copying a zipped fw on the external flash drive, plugging it into the device, then hitting very special button combo (I think holding vol+ and power to turn on the device, but you have to google it). Thus you can flash a softbricked device with correct fw
Click to expand...
Click to collapse
i knew about that, but before asus release firmware update my phone was bootloop :crying:. that is why googling other methods
you need to isocUSB, then just flash rom like lenovoK900
whynot4444 said:
you need to isocUSB, then just flash rom like lenovoK900
Click to expand...
Click to collapse
thanks i'll try later. i tried with MFT & xFSTK it doesnt work. i bring back zenfone 4 to asus dealer, cause still in warranty.
Hey, have you resolved this? Mine's stuck in usb mode too and identified as cloverview in device manager
hello, i can't able to flash stock rom like in lenovoK900. zenfone 4 stock rom is totally different .so please help me to recover my phone.
hemanth.kandula said:
hello, i can't able to flash stock rom like in lenovoK900. zenfone 4 stock rom is totally different .so please help me to recover my phone.
Click to expand...
Click to collapse
come to asus waranty
There are no Asus service centers in my area I'm struck in that USB logo please help me how to recover my phone. What I did is I applied a command in fastboot mode that is "fastboot reboot-bootloader" after that I have been struck in USB logo I tried to flash stock ROM as you said .and I tried to flash by Intel phone flash tool but It didn't worked
Please help me how to recover my phone
Flash with this http://forum.xda-developers.com/android/development/rom-asus-zenfone-4-stock-ww-4-3-11-t2873905
takeoutttt said:
Flash with this http://forum.xda-developers.com/android/development/rom-asus-zenfone-4-stock-ww-4-3-11-t2873905
Click to expand...
Click to collapse
please explain me how to flash that rom i cant load to droidboot mode just struck in that usb logo .or please suggest me a flash tool
---------- Post added at 08:07 PM ---------- Previous post was at 07:47 PM ----------
takeoutttt said:
Flash with this http://forum.xda-developers.com/android/development/rom-asus-zenfone-4-stock-ww-4-3-11-t2873905
Click to expand...
Click to collapse
please tell me how to flash that rom .i cant boot in droidboot mode and cant flash via fastboot. just struck in that logo so please tell me how flash that rom or tell me a flash tool to do it
the solution
hemanth.kandula said:
please explain me how to flash that rom i cant load to droidboot mode just struck in that usb logo .or please suggest me a flash tool
---------- Post added at 08:07 PM ---------- Previous post was at 07:47 PM ----------
please tell me how to flash that rom .i cant boot in droidboot mode and cant flash via fastboot. just struck in that logo so please tell me how flash that rom or tell me a flash tool to do it
Click to expand...
Click to collapse
go to my new blog i solve this problem
engashrafn.blogspot.com
watch the video and it will help you to access to droidboot
hemanth.kandula said:
please explain me how to flash that rom i cant load to droidboot mode just struck in that usb logo .or please suggest me a flash tool
---------- Post added at 08:07 PM ---------- Previous post was at 07:47 PM ----------
please tell me how to flash that rom .i cant boot in droidboot mode and cant flash via fastboot. just struck in that logo so please tell me how flash that rom or tell me a flash tool to do it
Click to expand...
Click to collapse
try this sol at my blog
engashrafn.blogspot.com/2014/10/asus-zenfone-unbrick-stuck-on-usb-logo.html
MFT process error
eng.naim said:
try this sol at my blog
engashrafn.blogspot.com/2014/10/asus-zenfone-unbrick-stuck-on-usb-logo.html
Click to expand...
Click to collapse
Hi eng.naim, thanks for help.
I allready follow all instruction from your blog but it can't fix the usb stuck, process got error at 15% (ABD enum failure).
I think the most problem is windows usb driver. I used asus k40ie with windows7 32 bit.
here's the process :
10/27/14 13:02:28.828 INFO : Port 0/0/4 #0: XFSTK-STATUS SN: 2A39A788BD36F9BC Errors encounter during download. Aborting...
10/27/14 13:02:28.828 DEBUG : Port 0/0/4 #0: XFSTK-LOG SN: 2A39A788BD36F9BC CloverviewPlusDownloader::GetStatus
10/27/14 13:02:28.828 DEBUG : XFSTK SN: 2A39A788BD36F9B C -- Success: Transfer Completed Successfully
10/27/14 13:02:28.828 INFO : Port 0/0/4 #0: IFW flash success - SN : 2A39A788BD36F9BC
10/27/14 13:02:28.828 DEBUG : Port 0/0/4 #0: IFW flash success on device 2A39A788BD36F9BC with state IFWI successfully flashed... REBOOT
10/27/14 13:04:50.765 DEBUG : Port 0/0/4 #0: SOC Device is disconnected - state:2 - status - IFWI successfully flashed... REBOOT
10/27/14 13:04:50.765 DEBUG : SOC device lost on port 4
10/27/14 13:04:53.968 DEBUG : New SOC device -> serial: 2A39A788BD36F9BC port: 4
10/27/14 13:04:58.218 ERROR : Port 0/0/4 #0: Device on port 0/0/4 #0 timeout to enum adb (TIMEOUT = 180)
10/27/14 13:05:48.875 DEBUG : Port 0/0/4 #0: SOC Device is disconnected - state:7 - status - [FAILURE] OS flash failure
10/27/14 13:05:48.875 DEBUG : Port:4 do_soc_device_lost - Pointer is cleared
10/27/14 13:05:48.875 DEBUG : SOC device lost on port 4
eng.naim said:
try this sol at my blog
engashrafn.blogspot.com/2014/10/asus-zenfone-unbrick-stuck-on-usb-logo.html
Click to expand...
Click to collapse
stuck in 15% how to fix this ???????????
---------- Post added at 03:35 AM ---------- Previous post was at 03:22 AM ----------
zabaleta10 said:
stuck in 15% how to fix this ???????????
Click to expand...
Click to collapse
11/08/14 10:31:58.130 INFO : Port 0/0/2 #0: IFW flash started - SN : 38A547125772E6FB
11/08/14 10:31:58.130 INFO : Disabling xFSTK wipe out ifwi option
11/08/14 10:31:58.130 INFO : Disabling xFSTK Misc DnX
11/08/14 10:32:33.670 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 38A547125772E6FB Unknown Ack code:baadf00d, aborting ...
11/08/14 10:32:33.670 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 38A547125772E6FB FAIL
11/08/14 10:32:33.670 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 38A547125772E6FB Errors encounter during download. Aborting...
11/08/14 10:32:33.670 INFO : Port 0/0/2 #0: IFW flash success - SN : 38A547125772E6FB
eng.naim said:
try this sol at my blog
engashrafn.blogspot.com/2014/10/asus-zenfone-unbrick-stuck-on-usb-logo.html
Click to expand...
Click to collapse
its not rebooting into bootloader struck in 15%
12/05/14 20:32:27.929 INFO : Port 0/0/2 #0: IFW flash started - SN : 5D924545D460F06D
12/05/14 20:32:27.929 INFO : Disabling xFSTK wipe out ifwi option
12/05/14 20:32:27.929 INFO : Disabling xFSTK Misc DnX
12/05/14 20:33:03.721 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 5D924545D460F06D Unknown Ack code:baadf00d, aborting ...
12/05/14 20:33:03.721 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 5D924545D460F06D FAIL
12/05/14 20:33:03.721 INFO : Port 0/0/2 #0: XFSTK-STATUS SN: 5D924545D460F06D Errors encounter during download. Aborting...
12/05/14 20:33:03.721 INFO : Port 0/0/2 #0: IFW flash success - SN : 5D924545D460F06D
plzzzz solve this
help me to recover my phone ......
solution
woyzer said:
Hi eng.naim, thanks for help.
I allready follow all instruction from your blog but it can't fix the usb stuck, process got error at 15% (ABD enum failure).
I think the most problem is windows usb driver. I used asus k40ie with windows7 32 bit.
here's the process :
10/27/14 13:02:28.828 INFO : Port 0/0/4 #0: XFSTK-STATUS SN: 2A39A788BD36F9BC Errors encounter during download. Aborting...
10/27/14 13:02:28.828 DEBUG : Port 0/0/4 #0: XFSTK-LOG SN: 2A39A788BD36F9BC CloverviewPlusDownloader::GetStatus
10/27/14 13:02:28.828 DEBUG : XFSTK SN: 2A39A788BD36F9B C -- Success: Transfer Completed Successfully
10/27/14 13:02:28.828 INFO : Port 0/0/4 #0: IFW flash success - SN : 2A39A788BD36F9BC
10/27/14 13:02:28.828 DEBUG : Port 0/0/4 #0: IFW flash success on device 2A39A788BD36F9BC with state IFWI successfully flashed... REBOOT
10/27/14 13:04:50.765 DEBUG : Port 0/0/4 #0: SOC Device is disconnected - state:2 - status - IFWI successfully flashed... REBOOT
10/27/14 13:04:50.765 DEBUG : SOC device lost on port 4
10/27/14 13:04:53.968 DEBUG : New SOC device -> serial: 2A39A788BD36F9BC port: 4
10/27/14 13:04:58.218 ERROR : Port 0/0/4 #0: Device on port 0/0/4 #0 timeout to enum adb (TIMEOUT = 180)
10/27/14 13:05:48.875 DEBUG : Port 0/0/4 #0: SOC Device is disconnected - state:7 - status - [FAILURE] OS flash failure
10/27/14 13:05:48.875 DEBUG : Port:4 do_soc_device_lost - Pointer is cleared
10/27/14 13:05:48.875 DEBUG : SOC device lost on port 4
Click to expand...
Click to collapse
i solved in this way check it out in my bloghttp://hemanthkandula.blogspot.in/2014/12/how-to-unbrick-asus-zenfone-4-struck-in.html
hemanth.kandula said:
i solved in this way check it out in my blog
Click to expand...
Click to collapse
Hey facing the same problem with zenfone 5 and gonna try your methods. i will report later. thanks for sharing.
hemanth.kandula said:
There are no Asus service centers in my area I'm struck in that USB logo please help me how to recover my phone. What I did is I applied a command in fastboot mode that is "fastboot reboot-bootloader" after that I have been struck in USB logo I tried to flash stock ROM as you said .and I tried to flash by Intel phone flash tool but It didn't worked
Please help me how to recover my phone
Click to expand...
Click to collapse
First Download Asus Zenfone 4 firmware .raw
Link:https://mega.co.nz/#!mVBzCJwT!tZbf3l...Hu_H5ygupssukM
Copy the File to Sd card
Go to fastboot mode using volume up+power button
Choose Sd Download and choose the firmware
It it doesn't work,try this http://www.asus.com/zentalk/forum.ph...hread&tid=1374
sol
press power button and volume up button for a while, while your phone is off, then use vol - button to navigate to reboot, select reboot using power button
Related
Hey,
Since multiple flashing operation (fastboot), the phone was turned into 'brick' and seems now looping on Asus logo at start..
After pressing power button + vol up the phone is well entering into droidboot but with this log message : 'E:Unable to open debricking'.
The phone stills open with USB cable (fastboot/adb) but I've already experienced some 'signature mismatching' during flash?
Any idea to recover ?
Thanks!
Product : TW_ZENFON (not WW)
Droidboot ver : 4.3.10.0
[Bricked][Asus Zenfone/Zenforce 4] fastboot flash fastboot fastboot.img
W4sh said:
Hey,
Since multiple flashing operation (fastboot), the phone was turned into 'brick' and seems now looping on Asus logo at start..
After pressing power button + vol up the phone is well entering into droidboot but with this log message : 'E:Unable to open debricking'.
The phone stills open with USB cable (fastboot/adb) but I've already experienced some 'signature mismatching' during flash?
Any idea to recover ?
Thanks!
Product : TW_ZENFON (not WW)
Droidboot ver : 4.3.10.0
Click to expand...
Click to collapse
After flashing the device with fastboot flash fastboot fastboot.img the output log are now : E:flash_fastboot_kernel : check_sign_key fail no allow to update kernel
Well, it seems that a specific firmware is needed and droidboot is checking for a key signature? If no match, it cannot allow an overwritting or something.
hi
Please forgive me English is not very good. You determine your own model, the Asus machine has some need to correct the file name, for example, k012, the file name is k012_sdupdate.zip. Then look at your card is correct brush pack
The device has been flashed once again with fastboot -> fastboot flash fastboot fastboot.img
The fastboot.img file was included from the official firmware zip archive UL_ASUS_T00Q_TW_4_3_2.zip
The operation was done succesfully without any error... meanwhile the boot is now going to blank (Android robot is fading to blank) and loop continuously...
If I restart the phone, the boot stuck as well on the Asus logo... So no more droidboot menu available..
@Chinaxiao4 : do you mean to rename the firmware (ie : UL_ASUS_T00Q_TW_4_3_2.zip) with the device model number ? Afterwards do we need to play with adb/fastboot ?
hi
You try, some machines need to change the name ASUS, please forgive me English is very bad, can not help you get more information
Chinaxiao4 said:
You try, some machines need to change the name ASUS, please forgive me English is very bad, can not help you get more information
Click to expand...
Click to collapse
No worries for your English, well.. my machine/device is an 'Asus T00i'
W4sh said:
No worries for your English, well.. my machine/device is an 'Asus T00i'
Click to expand...
Click to collapse
..so far it might be a firmware like this UL_ASUS_T00I_TW_4_X_X.zip
To resume, the Asus Zenforce/Zenfone 4 (T00I) TW model has been bricked since some flashing operation with firmware.
- used firmware : UL_ASUS_T00Q_TW_4_3_2.zip
- command line : fastboot flash fastboot fastboot.img
- result : No more boot menu... the droidboot is fading to blank, boot loop on model logo (bricked)
- Looking for (maybe) : UL_ASUS_T00I_TW_4_x_x.zip and droidboot with recovering mode
Linux to help by mounting the device and doing some repartionning job? Let's go further!!
When plug on USB the device is now unrecognized due of his previous flashing... (no matched Drivers)
Any help so far?
Boot Loop and no more driver to recognize the phone
https://www.youtube.com/watch?v=eUOTnIkXMvY&feature=youtu.be
RE
W4sh said:
https://www.youtube.com/watch?v=eUOTnIkXMvY&feature=youtu.be
Click to expand...
Click to collapse
As said from the vid, "better to replace the initial droidboot by another recovery mod before doing anything "
A bit darky but the idea seems ok, hoping for a next further release of Clockworkmod recovery
https://www.youtube.com/watch?v=OQ1gE9TpZ60
Meanwhile no idea to get outta my bootLoop locking screen...
Hi,
Is there any update solution, hint? My zenfone 4 also in brick bootloop intel logo status, can't enter to fastboot mode using key combination Power and Volume. It also cannot be detected using USB in PC.
coffeelover said:
Hi,
Is there any update solution, hint? My zenfone 4 also in brick bootloop intel logo status, can't enter to fastboot mode using key combination Power and Volume. It also cannot be detected using USB in PC.
Click to expand...
Click to collapse
me 2 same prblm dude got any solution
pls reply us
Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))
I get this error message while flashing using AFT
hi everyone
i have a xperia sp c5303 and this information you need to know:
1) unlocked bootloader
2) i had Mahdi Rom ver 2.7
3) williams kernel v42
now my problem
my phone suddenly restart and stop on boot loop
then i try to flash with flash tools and i notice it's not work for the first time because i flash sevral time my phone and others
then try fast boot and not work again
then start search and realize my phone had hard break or soft break ( i cant realize diff between two )
now that's interesting because my battery level is so low and i need to wall charge for hours to get the green ( when connect to charger sony arm show and red led on and 3 sec later black screen and red led off . 2 hours later red les startin on and 30min laters turn to green and on my phone show battery level of full )
but when i want to flash for 10 sec battery die and flash give me nothing
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
and then nothing happen and my phone led on the flash mode goes off and battery die and i try to start again of begining
any suggestion for you guys can help me please ?
if i try oppen the phone by myself ( because i repair laptop ) and change the battery . do you think i can flash again and the error in flash mode because of battery level .
thx
more information about fastboot
when I want to flash kernel (boot.img) with fastboot phone very easily goes to fastboot mode and blue led start and when i want to start flash here goes nothing ( waiting for my phone ) that's weird because program said the phone connected.
although i try to flash kernel with QuikIMG too and the same happens.
need your suggest ...
rayanafshan said:
hi everyone
i have a xperia sp c5303 and this information you need to know:
1) unlocked bootloader
2) i had Mahdi Rom ver 2.7
3) williams kernel v42
now my problem
my phone suddenly restart and stop on boot loop
then i try to flash with flash tools and i notice it's not work for the first time because i flash sevral time my phone and others
then try fast boot and not work again
then start search and realize my phone had hard break or soft break ( i cant realize diff between two )
now that's interesting because my battery level is so low and i need to wall charge for hours to get the green ( when connect to charger sony arm show and red led on and 3 sec later black screen and red led off . 2 hours later red les startin on and 30min laters turn to green and on my phone show battery level of full )
but when i want to flash for 10 sec battery die and flash give me nothing
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
and then nothing happen and my phone led on the flash mode goes off and battery die and i try to start again of begining
any suggestion for you guys can help me please ?
if i try oppen the phone by myself ( because i repair laptop ) and change the battery . do you think i can flash again and the error in flash mode because of battery level .
more information about fastboot
when I want to flash kernel (boot.img) with fastboot phone very easily goes to fastboot mode and blue led start and when i want to start flash here goes nothing ( waiting for my phone ) that's weird because program said the phone connected.
although i try to flash kernel with QuikIMG too and the same happens.
need your suggest ...
thx
Click to expand...
Click to collapse
anyone please...
hey guys . im still waiting ...
Try using a different usb port on your laptop or a different usb cable. Sometimes flashing may fail due to damaged usb port or cable. Also try using the usb cable that sony bundled with your phone (I used LG cable and didnt work for me). If that doesnt work, it seems that your battery is dead.
tj_droid said:
Try using a different usb port on your laptop or a different usb cable. Sometimes flashing may fail due to damaged usb port or cable. Also try using the usb cable that sony bundled with your phone (I used LG cable and didnt work for me). If that doesnt work, it seems that your battery is dead.
Click to expand...
Click to collapse
1) i use my pc and my sony laptop and 3 diffrent cable sony nokia sony
2) i try diffrent usb port such az usb2 and usb3
3) when i try to flash in flashmod with flashtool after
24/051/2014 12:51:15 - INFO - Selected Bundle for Xperia SP(C5303). FW release : 12.0.A.2.266. Customization : Middle East
24/051/2014 12:51:15 - INFO - Preparing files for flashing
24/051/2014 12:51:28 - INFO - Please connect your device into flashmode.
24/051/2014 12:51:30 - INFO - Device connected in flash mode
24/051/2014 12:51:30 - INFO - Opening device for R/W
24/051/2014 12:51:30 - INFO - Reading device information
24/051/2014 12:51:31 - INFO - Phone ready for flashmode operations.
24/051/2014 12:51:31 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
24/051/2014 12:51:31 - INFO - Start Flashing
24/051/2014 12:51:31 - INFO - Processing loader.sin
24/051/2014 12:51:31 - INFO - Checking header
24/051/2014 12:51:31 - INFO - Flashing data
24/051/2014 12:51:31 - INFO - Processing of loader.sin finished.
24/051/2014 12:51:32 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
24/053/2014 12:53:48 - INFO - Ending flash session
this log green led for flash mod turn off ( when i try to flash and connect usb until green led off take 5 sec not more)
4) if my battery dead if replace with new one ... can flash it again?
thx for respond
if my battery dead if replace with new one ... can flash it again?
Hello.
It could help others more if you could describe what happened when you tried to turn on the phone, after the flashmode LED turned off? Thanks.
rayanafshan said:
if my battery dead if replace with new one ... can flash it again?
Click to expand...
Click to collapse
Try locking your bootloader first (If it possible through fastboot). Looking at the errors the flashtool is giving, it seems like the flashing stops because bootloader is unlocked. Even if you read flashtool thread, it says bootloader should be locked (as far as I remember, havent visited the thread since a long time)
TechnoSparks said:
Hello.
It could help others more if you could describe what happened when you tried to turn on the phone, after the flashmode LED turned off? Thanks.
Click to expand...
Click to collapse
battery dead and need recycle again for more hours.
tj_droid said:
Try locking your bootloader first (If it possible through fastboot). Looking at the errors the flashtool is giving, it seems like the flashing stops because bootloader is unlocked. Even if you read flashtool thread, it says bootloader should be locked (as far as I remember, havent visited the thread since a long time)
Click to expand...
Click to collapse
that is actually good idea thx . i'll gonna working on that and let you know for 5-6 hours.
thank you both for respond.
rayanafshan said:
battery dead and need recycle again for more hours.
that is actually good idea thx . i'll gonna working on that and let you know for 5-6 hours.
thank you both for respond.
Click to expand...
Click to collapse
i try and that's result
when i want to relock my phone with flashtool ( because my phone sp 2013 for sony and they said we must do it this way for relock) here it is my log
27/004/2014 21:04:34 - INFO - Device connected in flash mode
27/004/2014 21:04:35 - INFO - Opening device for R/W
27/004/2014 21:04:35 - INFO - Reading device information
27/004/2014 21:04:35 - INFO - Phone ready for flashmode operations.
27/004/2014 21:04:35 - INFO - Current device : Unknown: Jan 19 2014/22:13:32 - YT91095X1H - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32 - Unknown: Jan 19 2014/22:13:32
27/004/2014 21:04:38 - INFO - Processing loader.sin
27/004/2014 21:04:38 - INFO - Checking header
27/004/2014 21:04:38 - INFO - Flashing data
27/004/2014 21:04:38 - INFO - Processing of loader.sin finished.
27/004/2014 21:04:39 - INFO - Loader : S1_Root_7054 - Version : R5G006 / Boot version : R11B022 / Bootloader status : ROOTED
27/004/2014 21:04:39 - INFO - Start Reading unit 000008B2
27/004/2014 21:04:39 - INFO - Reading TA finished.
and stop and 5 min later when i disconnect the phone this log
27/031/2014 23:31:55 - ERROR - Read error :31 : A device attached to the system is not functioning.
27/031/2014 23:31:55 - INFO - Your phone bootloader cannot be officially unlocked
27/031/2014 23:31:55 - INFO - You can now unplug and restart your phone
and when ii see this i try to use rubber band trick and see this in the morning
28/035/2014 06:35:09 - INFO - Device connected with USB debugging off
28/035/2014 06:35:09 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/035/2014 06:35:10 - INFO - Device disconnected
28/045/2014 06:45:01 - INFO - Device connected in flash mode
28/045/2014 06:45:43 - INFO - Device disconnected
28/049/2014 06:49:14 - INFO - Device connected with USB debugging off
28/049/2014 06:49:14 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/049/2014 06:49:18 - INFO - Device disconnected
28/058/2014 06:58:45 - INFO - Device connected in flash mode
28/059/2014 06:59:28 - INFO - Device disconnected
28/002/2014 07:02:55 - INFO - Device connected with USB debugging off
28/002/2014 07:02:55 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/002/2014 07:02:59 - INFO - Device disconnected
28/012/2014 07:12:26 - INFO - Device connected in flash mode
28/013/2014 07:13:09 - INFO - Device disconnected
28/016/2014 07:16:32 - INFO - Device connected with USB debugging off
28/016/2014 07:16:32 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/016/2014 07:16:36 - INFO - Device disconnected
28/026/2014 07:26:02 - INFO - Device connected in flash mode
28/026/2014 07:26:45 - INFO - Device disconnected
28/030/2014 07:30:08 - INFO - Device connected with USB debugging off
28/030/2014 07:30:08 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/030/2014 07:30:12 - INFO - Device disconnected
28/039/2014 07:39:39 - INFO - Device connected in flash mode
28/040/2014 07:40:21 - INFO - Device disconnected
28/043/2014 07:43:41 - INFO - Device connected with USB debugging off
and this repeat again and again . interesting was i am always active usb debugging mode and now log said is off. i confused here
now my usb debugging off how flash what can i do now .
for unlocked bootloader for flash
i want my phone back
help
Okay the problem is getting worse. Have you tried to unlock your bootloader again? If not, please try so. I have a final option for you to decide.
TechnoSparks said:
Okay the problem is getting worse. Have you tried to unlock your bootloader again? If not, please try so. I have a final option for you to decide.
Click to expand...
Click to collapse
i try several time .
this morning
there is another way to relock bootloader other than flashtool for sp?
if there are other way please.. or if any way to back my phone .
rayanafshan said:
i try several time .
this morning
there is another way to relock bootloader other than flashtool for sp?
if there are other way please.. or if any way to back my phone .
Click to expand...
Click to collapse
Please understand my posts correctly. Are you currently on an unlocked bootloader? Or if you can confirm it is locked, do you manage to be able to unlock the bootloader through the Flashtool?
TechnoSparks said:
Please understand my posts correctly. Are you currently on an unlocked bootloader? Or if you can confirm it is locked, do you manage to be able to unlock the bootloader through the Flashtool?
Click to expand...
Click to collapse
ohhh ok i get wrong . now i found you mean i unlocked bootloader however it is unlocked. ok i try and ley your know
rayanafshan said:
ohhh ok i get wrong . now i found you mean i unlocked bootloader however it is unlocked. ok i try and ley your know
Click to expand...
Click to collapse
hi again
now result
in 2days i try evrything
1- i try to unlocked again with fastboot but fastboot said you unlocked bootloader before and then finished
2- try to unlocked bootloader with flashtool with the final version and when said connect your phone with flashmode and i did it then said pick your model phone and i select xperia sp and green led turn off ang didnt enything
i unlocked bootloader before many time and now i'm stuck
if there is another way please let me know?
rayanafshan said:
hi again
now result
in 2days i try evrything
1- i try to unlocked again with fastboot but fastboot said you unlocked bootloader before and then finished
2- try to unlocked bootloader with flashtool with the final version and when said connect your phone with flashmode and i did it then said pick your model phone and i select xperia sp and green led turn off ang didnt enything
i unlocked bootloader before many time and now i'm stuck
if there is another way please let me know?
Click to expand...
Click to collapse
I can't really help if I don't know the current state of your bootloader
Your last option here is to retry flashing a stock ROM FTF onto your phone. I hope it will work. [Choose your desired stock ROM based on your XSP model here]
TechnoSparks said:
I can't really help if I don't know the current state of your bootloader
Your last option here is to retry flashing a stock ROM FTF onto your phone. I hope it will work. [Choose your desired stock ROM based on your XSP model here]
Click to expand...
Click to collapse
I really do not understand what you asking from me
if you want to know about my bootloader : is 100% unlocked and when i try to unlocked again it's said you bootloader unloacked if you need i posted log from fastboot here
also i try more than 100 times to flash with stock ftf of my phone and also flash kernel stock and flash recovery for unlocked and locked bootloader . i try everything in this froum and others
i dont know why when i want to flash kernel ( stock and cm) is stuck on
flashing...
and blue led is on untill battery dead and myphone not respond to program
i posted logs before
here situation of my phone
xperia sp xx03
bootloader unlocked
android 4.4.4 mahdi version 2.8
recovery cm11_williams_kernel_v4
evrything start of here 3 weeks ago
((my phone restart and when i far from my phone , it stucked on boot logo animation for 3 or 4 hours and when i found my phone situation shutdown my phone via the OFF botton of the back of my phone.))
and then i try to flash FTF stock or CM from MahdiRom or any rom , did not let me. and you know others untill now ?
I research and i Think the only way is from Fastboot mode and fstboot program with terminal function .
can you undrestand my problem know please?
rayanafshan said:
I really do not understand what you asking from me
if you want to know about my bootloader : is 100% unlocked and when i try to unlocked again it's said you bootloader unloacked if you need i posted log from fastboot here
also i try more than 100 times to flash with stock ftf of my phone and also flash kernel stock and flash recovery for unlocked and locked bootloader . i try everything in this froum and others
i dont know why when i want to flash kernel ( stock and cm) is stuck on
flashing...
and blue led is on untill battery dead and myphone not respond to program
i posted logs before
here situation of my phone
xperia sp xx03
bootloader unlocked
android 4.4.4 mahdi version 2.8
recovery cm11_williams_kernel_v4
evrything start of here 3 weeks ago
((my phone restart and when i far from my phone , it stucked on boot logo animation for 3 or 4 hours and when i found my phone situation shutdown my phone via the OFF botton of the back of my phone.))
and then i try to flash FTF stock or CM from MahdiRom or any rom , did not let me. and you know others untill now ?
I research and i Think the only way is from Fastboot mode and fstboot program with terminal function .
can you undrestand my problem know please?
Click to expand...
Click to collapse
My intention or objective right now is to have you successfully boot up your phone and restore it without relying on flashtool so much.
Since you said your bootloader is unlocked, you'll now left to flash DoomLord's advanced kernel that will give you recovery access.
Because my understanding is limited, based on your posts earlier, it seemed you indeed tried to flash a kernel via fastboot but your phone died. Based on multiple logs, there are also multiple errors that seemed to be involving hardware. And due to that kind of advanced log error I must apologise and tell you that I am now unable to help you.
Your log listed so many errors, it even unable to detect the model number of your phone, nor the current state of your bootloader (on newer posts).
If you wish to try my last suggestion, do said so. Otherwise, I have to back myself out of this since it is not my expertise.
I am very sorry
TechnoSparks said:
My intention or objective right now is to have you successfully boot up your phone and restore it without relying on flashtool so much.
Since you said your bootloader is unlocked, you'll now left to flash DoomLord's advanced kernel that will give you recovery access.
Because my understanding is limited, based on your posts earlier, it seemed you indeed tried to flash a kernel via fastboot but your phone died. Based on multiple logs, there are also multiple errors that seemed to be involving hardware. And due to that kind of advanced log error I must apologise and tell you that I am now unable to help you.
Your log listed so many errors, it even unable to detect the model number of your phone, nor the current state of your bootloader (on newer posts).
If you wish to try my last suggestion, do said so. Otherwise, I have to back myself out of this since it is not my expertise.
I am very sorry
Click to expand...
Click to collapse
i know that situation is sucks i know and thank you for helping me to this step and i'm so much own you.
but last question i found a post for fastboot unbricked my type of phone but i dont undrestand small part of it and maybe it's help others
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Quote
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partions using the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Quote
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
...If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Quote
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Quote
C:\.android>adb push update.zip /data/sdcard
(Let the process complete. It will take damm much more time !!!)
Once you get 'Successful' message..your update.zip is on your SDCARD. If this is tidious then get a Card reader and copy Update.zip to SD Card directly and replace in Device.
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Quote
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
1. Reboot device
2. Apply Update.Zip from SDCARD
3. Wipe userdata on device/Factory Update
4. Wipe Cache on Device
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)' ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!!
Click to expand...
Click to collapse
i want to know where i found update.zip or recovery.img sytem.img userdata.img splash.img cache.img because in stock rom sp they are .sin
if i wipe my all partition maybe i have chance to restore my phone
thank you
Good day. Please assist me in solving bleeding problem.
I have unlocked bootloader unbranded device C6903.
Some time ago, I used EMMA(sony flashtool) to update it to 14.6.A.1.236
(Service Name: C6903 14.6.A.1.236 Customized_NCB 1276-9897 R2D User-Live COM)
Today, I try to downgrade to 14.6.A.0.368 using same sony flashtool.
After this, l a got booting animation forever.
I restarted few times. Tries to flash cyanogen, tries services from EMMA.
Now I have boot loop, no animation, no nothing, only vibrates once when press power.
fasboot and flash mode a working, but reflashind don't do anything.
When connected to dockstation - screen blinking with sony logo, shutdown, blink, shutdown.
Is issue can caused by some invalid drm keys that gotten by mistake to my phone?
Will be grateful for any help.
Thanks.
Use Flashtool of Androxyde. Never Use EMMA for such things. EMMA just sucks rly bad and is only useful for very specific things. Everything else towards flashing, belongs to Flashtool.
Flashing different firmwares with flashtool don't make any difference.
A even try to relock bootloader and use sony companion to restore device - no luck.
Update, I flashed boot.img from custom rom and now I have 3 times red light blinking when power on.
Update.
I was trying to use this guide https://forum.xda-developers.com/showthread.php?t=2646405
When flashing s1tool give me the message
Code:
MINOR ERROR [ Open_TA_failed, err: 001D ]
After this all the same.
When connect phone to dockstation it just blinking the screen. Is it possible to be battery issue?
full log
Code:
Welcome to S1 tool.
That is small and crippled subset of SETOOL2 service tool.
SELECT FIRMWARE PACKAGES
YOU CAN SELECT SEVERAL PACKAGES WITH CTRL BUTTON
CHECKING PACKAGES ...
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
will use Sahara protocol ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
PROCESSING ...
SERIAL NUMBER : 48CC8901
HARDWARE ID : 04000100E1007B00
HASH :49109A8016C239CD8F76540FE4D5138C87B2297E49C6B30EC31852330BDDB177
Emergency loader uploaded ...
RUNNING S1_PRELOADER VER "LOADER_RELEASE_MSM8974_23_4_AID_4"
LOADER AID: 0004
DEVICE ID: 0189CC48
FLASH ID: "0011/01000010"
LOADER VERSION: "LOADER_RELEASE_MSM8974_23_4_AID_4"
WRITING PACKAGES ...
Processing package
C:\Home\Downloads\C6903\14_2_A_0_290.APP_SW_Honami_GENERIC_1272_6084_S1_SW_LIVE_6732_PID1_0005_MMC.SIN_FILE_SET
WILL UPDATE BOOT TO : 1270-3115 S1_BOOT_MSM8974_LA1.04_15
PARSING: "DEVELOPMENT"
value OTP_LOCK_STATUS_1 : UNLOCKED, not match LOCKED
PARSING: "TEST_OEM0_007B00E1"
value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
value OTP_DATA_1 : 00000100, not match 01000400
value IDCODE_1 : 007B00E1, match 007B00E1
PARSING: "PRECOMMERCIAL_007B00E1"
value OTP_LOCK_STATUS_1 : LOCKED, match LOCKED
value OTP_DATA_1 : 01000400, match 01000400
value IDCODE_1 : 007B00E1, match 007B00E1
PROCESSING : dbi_S1_Boot_MSM8974_LA1_04_15_AID_4_S1-SDI2-6732-PID1-0004-SDI_S1-BOOT-6732-0004-MMC.sin
PROCESSING : emmc_appsboot_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : s1sbl_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID65-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : sbl1_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : tz_S1_Boot_MSM8974_LA1_04_15_AID_4_PLATFORM-MSM8974-LIVE-HWID007B00E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-6732-0004-MMC.sin
PROCESSING : Honami_S1BootConfig_MiscTA_130115_1430.ta
MINOR ERROR [ Open_TA_failed, err: 001D ]
BOOT UPDATED
Processing ACPU files
PROCESSING: cache_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: apps_log_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: kernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
PROCESSING: fotakernel_S1-SW-LIVE-6732-PID1-0005-MMC.sin
SKIP: partition-image_S1-SW-LIVE-6732-PID1-0005-MBR.sin
PROCESSING: rpm_S1-RPMFW-LIVE-6732-PID1-0005-MMC.sin
no update files in package
FINISHED
Elapsed:128 secs.
Problem solved by flashing C6903_14.1.G.2.257_Global LTE.ftf
Thanks.
Nyakov said:
Problem solved by flashing C6903_14.1.G.2.257_Global LTE.ftf
Thanks.
Click to expand...
Click to collapse
Device began to charge, but still not boot.
When I try to flash AOSP
I cannot write recovery, get:
Code:
fastboot -S 256M flash recovery recovery.img
sending 'recovery' (14152 KB)...
OKAY [ 0.460s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.463s
Have you solved the issue. My phone C6903 is struck in bootloop in 4.2.2
I have unknown baseband issue.
Hello Everyone!
I create tft from xperiafirm,install and error,then my phone not work anymore,only connect to flashtool in fastboot mode(blue led),can not connect in flashmode
28/006/2017 14:06:30 - INFO - Device disconnected
28/006/2017 14:06:46 - INFO - Device connected with USB debugging off
28/006/2017 14:06:46 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/006/2017 14:06:58 - INFO - Flash canceled
28/007/2017 14:07:04 - INFO - Device disconnected
28/007/2017 14:07:19 - INFO - Device connected in fastboot mode
28/007/2017 14:07:34 - INFO - List of connected devices (Device Id) :
28/007/2017 14:07:34 - INFO - - USB\VID_0FCE&PID_0DDE\CB512A43HC Driver installed : true
28/007/2017 14:07:34 - INFO - List of ADB devices :
28/007/2017 14:07:34 - INFO - - none
28/007/2017 14:07:34 - INFO - List of fastboot devices :
28/007/2017 14:07:34 - INFO - - CB512A43HC
What can I do now!Thanks you everyone!!!! :crying:
Did you use the latest version of Flashtool? (0.9.23.2)
f870103 said:
Did you use the latest version of Flashtool? (0.9.23.2)
Click to expand...
Click to collapse
Yes!Latest version
28/015/2017 16:15:36 - INFO - Flashtool Version 0.9.23.2 built on 19-01-2017 21:50:00
28/015/2017 16:15:36 - INFO - Executing search strategies to find proxy selector
:crying::crying::crying::crying::crying::crying:
What do you mean "can not connect in flashmode"? No green light or...?
f870103 said:
What do you mean "can not connect in flashmode"? No green light or...?
Click to expand...
Click to collapse
Yes!When I holding volume down and plug cable,green light will blink in only one second then this message popup.
28/006/2017 14:06:46 - INFO - Device connected with USB debugging off
28/006/2017 14:06:46 - INFO - For 2011 devices line, be sure you are not in MTP mode
nghia3d said:
Yes!When I holding volume down and plug cable,green light will blink in only one second then this message popup.
28/006/2017 14:06:46 - INFO - Device connected with USB debugging off
28/006/2017 14:06:46 - INFO - For 2011 devices line, be sure you are not in MTP mode
Click to expand...
Click to collapse
What OS are you using?
f870103 said:
What OS are you using?
Click to expand...
Click to collapse
I'm using windows 10,my phone is sov33 au kddi,I try to flash 8.0 EU on Xperia Firm
nghia3d said:
I'm using windows 10,my phone is sov33 au kddi,I try to flash 8.0 EU on Xperia Firm
Click to expand...
Click to collapse
AFAIK, Japan model can't flash to a international ROM.
f870103 said:
AFAIK, Japan model can't flash to a international ROM.
Click to expand...
Click to collapse
What can I do now? :crying:
nghia3d said:
What can I do now? :crying:
Click to expand...
Click to collapse
Maybe take your phone to Sony and get it repaired.
nghia3d said:
What can I do now? :crying:
Click to expand...
Click to collapse
flash it back on ur Japan version, and dont try to convert ur smart phone, like Sony Ericsson K530 @ W660... it is impossible for now. try flash system and others via fastboot.
G-UN1T said:
flash it back on ur Japan version, and dont try to convert ur smart phone, like Sony Ericsson K530 @ W660... it is impossible for now. try flash system and others via fastboot.
Click to expand...
Click to collapse
Thank you!But I don't know how to flash system via fastboot!Can you explain more details?:crying:
follow the instructions I made.. always works for me.
nickcaper said:
follow the instructions I made.. always works for me.
Click to expand...
Click to collapse
how the instructions ??
flash again
whats firmware u are flashed on ur device? stock xp or from xz?
saiz0313 said:
flash again
Click to expand...
Click to collapse
how to flash again, if cant enter to flashmode??
try
1.fastboot mode to flash twrp recovery
2.reboot to twrp
3.try to flash someROM?or reboot to flash mode ?
saiz0313 said:
try
1.fastboot mode to flash twrp recovery
2.reboot to twrp
3.try to flash someROM?or reboot to flash mode ?
Click to expand...
Click to collapse
i try flash boot.img via fastboot : failed verification, and log in flashtool said command not allowed
---------- Post added at 04:26 AM ---------- Previous post was at 04:23 AM ----------
I try flash boot.img via fastboot but not work, failed verification ; and on log flashtool "command not allowed"
gungsye said:
i try flash boot.img via fastboot : failed verification, and log in flashtool said command not allowed
---------- Post added at 04:26 AM ---------- Previous post was at 04:23 AM ----------
I try flash boot.img via fastboot but not work, failed verification ; and on log flashtool "command not allowed"
Click to expand...
Click to collapse
just flash recovery twrp.img,and reboot to recovery.
It's OK?
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
gungsye said:
i try flash boot.img via fastboot : failed verification, and log in flashtool said command not allowed
---------- Post added at 04:26 AM ---------- Previous post was at 04:23 AM ----------
I try flash boot.img via fastboot but not work, failed verification ; and on log flashtool "command not allowed"
Click to expand...
Click to collapse
unlocked ?
just flash recovery to twrp ,it's OK?
reboot to twrp ,it's OK?
Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?
C0dR said:
Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?
Click to expand...
Click to collapse
would you please add some details, as to what steps you had to take to recover.
you know the only way this "developer" community works is if the people here using it share their knowledge. And you learned something in this experience that could very well help someone down the road.
C0dR said:
Hello,
i tried to root my Maze Alpha 6G and accidentally flashed the wrong Recovery from here https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575 using the fastboot method. So my phone was stuck in a orange state bootloop. I tried to flash the correct recovery then using SPFTool but after connecting the phone to the PC I got an error: "BROOM ERROR : STATUS_PRELOADER_INVALID". After that the phone is dead. I cant turn it on, nor can I connect it to PC or anything. PC only says error getting device info. SPFTools also isnt able to connect to it anymore....is there any way to unbrick it? Obviously I was so smart to not create a backup of my device....
//EDIT: OK I managed to reflash the correct stock preloader and recovery and I was able to boot into my device again! Sadly all my user data is whiped...Is there any way of getting my user data back?
Click to expand...
Click to collapse
Where have you found the correct preloader for Maze Alpha X ? Thanks, CVLo
Have you tried this?
https://forum.xda-developers.com/maze-alpha/development/unbrick-maze-alpha-x-6-64gb-t3817716
Maze Alpha 4GB. Not booting. Black screen after rooting.
Hello everyone,
I have done the same thing as the first post, and my phone is at the black screen, not booting. My Maze is the 4GB version, not the 6GB. Can someone help me unbrick it?
When I put it into usb, I got two usb devices cycling:
Bus 002 Device 047: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
Click to expand...
Click to collapse
and
Bus 002 Device 048: ID 0e8d:0003 MediaTek Inc. MT6227 phone
Click to expand...
Click to collapse
When I try to Format the device, i got:
BROM Exception! ( ERROR : STATUS_SEC_WRITE_DATA_NOT_ALLOWED (-1073610740) , MSP ERROE CODE : 0x00.
[HINT]:
)((exec,../../../flashtool/Cmd/FormatCommand.cpp,78))
Click to expand...
Click to collapse
When I try to download a partition, for example preloader, I got:
executing DADownloadAll...
Stage:
[0] WRITE TO PARTITION [ preloader ]
Download failed.
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_DL_FORBIDDEN (-1073610748) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
or for recovery:
executing DADownloadAll...
Stage:
[3] WRITE TO PARTITION [ recovery ]
Download failed.
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_DL_FORBIDDEN (-1073610748) , MSP ERROE CODE : 0x00.
Click to expand...
Click to collapse
This goes for any partitions the other partitions as well.
I have tried these ROMs:
MAZE_Alpha_4G_V09_SPFT
MAZE_Alpha_V03_20170808
MAZE_Alpha_V04_B_20171018
MAZE_Alpha_V05_20170816
Click to expand...
Click to collapse
The Smart Phone Flash Tool is showing my Chip Info correctly. Maybe i am missing something. A permission maybe? Or the correct ROM. I have no backup too. I didn`t think that the situation will get so ugly.
Any help will be much appreciated.
Thank you in advance.