Please help me unbrick the phone if possible.
I was using TWRP to flash a backup (of stock image) but it gave me error (I don't remember the error message).
Then the phone discharged and I cant turn it on. No screen, no vibration, but the empty battery image appears if the battery is low. I can charge it and red led light up (blinks in three stages).
If I connect to pc green light appears (flash mode).
Xperia Flashtool gives error when I try to flash stock rom:
ERROR - Processing of *.sin finished with errors.
All .sin files give the same error, but the .ta files can be written to device.
In console (I use linux on pc) there are error messages too:
org.flashtool.flashsystem.X10FlashException: S1 Data CRC32 Error
at org.flashtool.flashsystem.S1Packet.validate(S1Packet.java:84)
at org.flashtool.flashsystem.io.USBFlash.readS1Reply(USBFlash.java:86)
at org.flashtool.flashsystem.io.USBFlash.writeS1(USBFlash.java:61)
at org.flashtool.flashsystem.S1Command.writeCommand(S1Command.java:77)
at org.flashtool.flashsystem.S1Command.send(S1Command.java:97)
at org.flashtool.flashsystem.S1Flasher.processHeader(S1Flasher.java:278)
at org.flashtool.flashsystem.S1Flasher.uploadImage(S1Flasher.java:289)
at org.flashtool.flashsystem.S1Flasher.runScript(S1Flasher.java:642)
at org.flashtool.flashsystem.S1Flasher.flash(S1Flasher.java:704)
at org.flashtool.gui.tools.FlashJob.run(FlashJob.java:50)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Does it mean that the phone is dead?
Thank you.
Ok. I know the problem. I flashed wrong backup with twrp. I have two of this type of phone and that wasn't the right one's backup. So I cant use it anymore because the trim area is overwritten and I don't have a backup.
Related
Hello to all XDA Family,
This is my first post here in XDA hope someone could help me reviving my Friend's HTC Desire 310. My friend asked me to repair her sister's bootloop HTC desire 310 uni sim. I searched a tutorial in XDA and downloaded the necessary files (Drivers, SP Flashtool & rom-Uni Sim). I followed the tutorial and finished flashing the stock rom. Unfortunately after flashing the rom the phone won't turn on or charge. I tried to reflashed it and got some error after the 100% yellow bar progress it gave me some errors.
*Below is the Scenario during and after flashing*
1- After flashing anything whatever it was the phone will get Hard Brick . Does it mean that Preloader or Bootloader "1st 2 data partations" is faulty.
2- Since Factory Mode is in Bootloader so you are not able to access it
3- since adb starts after bootloader phase so also u cant access it.
4- THANKFULLY i can get the phone into Preloader Mode by Removing Battery ===> connect usb ===> then hold Volume Down
5- In Preloader Mode the phone shutsdown in approxmatly 2-3 seconds getting SP Flash Tool Recognising it for 2 seconds and disconnect again after 2 seconds.
6- I can also get the phone into Preloader mode by Removing battery =====> connect USB =====> plug the battery back in. the phone will get into Preloader Mode for 2 seconds too but when i tried to flash the rom using SP Flash tool it give some error like (BROM ERROR: S_CHKSUM_ERROR) when the yellow progress bar reached 100%.
What can i do to revive the phone.? Please lend me your knowledge Thank you in advance.
Please help guys... thank you
I want to install custom ROM on my Zenfone 5.
Things you should know:
.. Phone OS completely corrupts unable to boot the device (even android logo also not appear)
.. It is not showing charging symbol also when connected to charger/usb
.. Phone never boots into recovery mode (it is just restarting(vibration)! and stay idle)
.. It has TeamWin recovery project that appear after 30 mins of charging (useful!!)
So, can anybody tells me how install custom ROM (http://forum.xda-developers.com/zenfone-5/orig-development/beta-cyanogenmod-12-1-tank0412-t3285392) please don't say boot into recovery mode and do some adb/fastboot commands it is not working (volume up+power or any combination). It is just showing one big red charging bar symbol without charging.. and some times TeamWin which may helpful because it has filemanager and I can browse but I don't know how to install with that.
If you have any ideas please share me..
Thanks
You can put rom on the external sdcard and install it after TWRP booting.
But i think that something wrong with bootloader on your phone so you should try to make unbrick.
tank0412 said:
You can put rom on the external sdcard and install it after TWRP booting.
But i think that something wrong with bootloader on your phone so you should try to make unbrick.
Click to expand...
Click to collapse
Thanks for the answer..
Hard bricked device - Just like it's name, your device is dead. It behaves like a real brick. You can have no operation on pressing the power button.
So we can make a conclusion: soft bricked device can’t be defined as "BRICKED"; the hard bricked device is the real "DEAD & BRICKED", and it can't be unbricked. Sorry for the answer to how to unbrcik hard bricked Android phone.
This is the situation of my phone and whenever I flash a zip file from TWRP I'm getting following error..
"E: Error executing updater binary in zip '/sdcard/.....zip'"
I'm googling this error but unable to get anything(trying some of the one plus one solutions to the similar problem).. Please help me..
wyephani said:
Thanks for the answer..
Hard bricked device - Just like it's name, your device is dead. It behaves like a real brick. You can have no operation on pressing the power button.
So we can make a conclusion: soft bricked device can’t be defined as "BRICKED"; the hard bricked device is the real "DEAD & BRICKED", and it can't be unbricked. Sorry for the answer to how to unbrcik hard bricked Android phone.
This is the situation of my phone and whenever I flash a zip file from TWRP I'm getting following error..
"E: Error executing updater binary in zip '/sdcard/.....zip'"
I'm googling this error but unable to get anything(trying some of the one plus one solutions to the similar problem).. Please help me..
Click to expand...
Click to collapse
It looks like you use TWRP by Knone which is broken a bit. So you should install TWRP by quanganh2627.
Try to flash this package via TWRP:
https://drive.google.com/file/d/0B-Fin8UxrD6PNm1NSDNQQ3JqUkU/view?usp=sharing
It will install a stable TWRP.
tank0412 said:
It looks like you use TWRP by Knone which is broken a bit. So you should install TWRP by quanganh2627.
Try to flash this package via TWRP:
It will install a stable TWRP.
Click to expand...
Click to collapse
Hi! Your zip file successfully installed but after that also I'm getting same error. Is there any file download problem (Checksum or like that) or do I have to restart my phone(No OS installed!)
wyephani said:
Hi! Your zip file successfully installed but after that also I'm getting same error. Is there any file download problem (Checksum or like that) or do I have to restart my phone(No OS installed!)
Click to expand...
Click to collapse
Thanks for your TWRP. I successfully installed custome ROM of this..(http://forum.xda-developers.com/zenfone-5/orig-development/rom-cyanogenmod-12-1-xhook-t3289543) but I'm getting these problems which are nowhere found in any forum
1. Charging stops at 10% never goes beyond this point
2. IMEI missing (seriously !!)
Thanks
wyephani said:
Thanks for your TWRP. I successfully installed custome ROM of this..(http://forum.xda-developers.com/zenfone-5/orig-development/rom-cyanogenmod-12-1-xhook-t3289543) but I'm getting these problems which are nowhere found in any forum
1. Charging stops at 10% never goes beyond this point
2. IMEI missing (seriously !!)
Thanks
Click to expand...
Click to collapse
Try to downgrage to stock rom:
https://drive.google.com/file/d/0BwEWY6gMvYOeelBEQ2J0ckxnRmc/view
tank0412 said:
Try to downgrage to stock rom:
https://drive.google.com/file/d/0BwEWY6gMvYOeelBEQ2J0ckxnRmc/view
Click to expand...
Click to collapse
Yes, I'm trying that but the problem here is I'm unable to flash TWRP now (Run the command prompt - wait for device - phone starts several times but only big red battery symbol without charging/usb cable showing red bar below - boot into installed OS) that's it without flashing the TWRP phone reboots and command prompt still waiting for device even device already booted.
Interestingly now the battery showing 100% directly (I don't know ! whether it is actual figure or something goes wronng!) but still my IMEI is empty and I want to install stock ROM on this device for this purpose.
Note: still power + volume up/down to goto recovery mode not working
Any help appreciated. Thanks!!
wyephani said:
Yes, I'm trying that but the problem here is I'm unable to flash TWRP now (Run the command prompt - wait for device - phone starts several times but only big red battery symbol without charging/usb cable showing red bar below - boot into installed OS) that's it without flashing the TWRP phone reboots and command prompt still waiting for device even device already booted.
Interestingly now the battery showing 100% directly (I don't know ! whether it is actual figure or something goes wronng!) but still my IMEI is empty and I want to install stock ROM on this device for this purpose.
Note: still power + volume up/down to goto recovery mode not working
Any help appreciated. Thanks!!
Click to expand...
Click to collapse
You bricked your device.
You should use unbrick method:
http://4pda.ru/forum/index.php?showtopic=584672&st=460#entry33842670
WHAT IS HARD-BRICK?
The Hard-Brick, translated means device NULL, without function neither one! This happens a lot for forced updating: AS ANDROID 4.4.4 FOR 5xx ....
Most of the time, the cell phone stays in BOOTLOOP (infinite loop), another case as hard brick gets on the black screen with LED access.
Then you ask me?
Wagner, I Brickei my device, how to recover?
YES! There is always a way to recover. More remembering that each device has a way of doing, some are easier and others more complicated. We just need to find the right files.
So let's go!
MOTOROLA DRIVER
Drivers required for device recognition on PC.
If you have already installed, you do not have to install again.
Download
HAND-BRICK.exe
It will install the drives, recover the cell phone and recover the fastboot.
Download
STEP BY STEP
1- Turn off the phone and enter the fastboot mode:
Yes, I know the phone is off!
Plus the device is in operation and we need the phone to be turned off and enter the Fastboot mode.
HOW DO I DO THAT? I discovered two ways!
- Fast and easy mode:
OPEN THE PHONE AND DISCONNES THE BATTERY, IT WILL PLACE THE FATBOOT MODE.
IF YOU MAKE ERRORS IN COMMANDS, YOU CAN GET THE FASTEST ANSWER.
- Time-consuming and need patience:
PLUG THE PHONE TO CHARGE "INTO THE SOCKET", THE LED GOES ON, WAITES THE LED OFF.
If the LED does not turn on?
SAFETY THE POWER BUTTON ON + THE DOWN VOLUME, FOR 2 SECONDS OR ACCOUNT UP TO 30!
THEN PLACE INTO THE OUTLET, AND OBSERVE THAT THE LED WILL TURN ON! And wait until the LED turns OFF.
Why did I say I had to be patient?
Well, you're going to do this straight, each made the commands go wrong.
And it will only work again if the phone restarts. Many times the LEDs do not light up among other things like not recognizing on the PC.
HOW DO I KNOW THAT IT WORKS?
When using the unbrick, it will show you a path:
EXP:
C: / USERS / NAME / DESKTOP / MOTO MAXX / PORTUGUESE [BR] / 2 - REVIVER FB / UNBRICK - 5.1> .QBOOT BLANK - FLASH
AND THEN HE SHOWS THE RECOGNIZED FILES.
When of FAILED?
(BLANK-FLASH: **********):
THE FILES WILL BE DEMANDED TO BE RECOGNIZED, THEN IN THIS CASE THE COMMANDS WILL NOT WORK! AND AI FOLLOW THE STEPS AGAIN THE LED!
OK! now that the phone is off and ready to use the unbrick.
Remember, every time you use the unbrick and appear errors, you will have to repeat the STEP to turn on the LED!
2 - Connect the device to the PC, and check that the device is being recognized as QUSB-BULK.
Search the device manager for your PC.
And look in the part (Ports (COM and LPT)) and see if you recognize the device!
3- Install the MOTOROLA + Qualcomm USB drives.
In the Device Manager will shows that the device is being recognized as QUALCOMM.
4- Choose the Unbrick option and execute the files "GO" and wait ends up to 100%
NOTE THAT: THE PHONE WILL BECOME LIFE, AND SHOW THE BOOTLOADER WITHOUT ANDROID!
If it looks like FAIL - You have to repeat STEP 1 to turn on the LED, done that, Test other files
Contains GPT.BIN files from Android 4.4.4 to the latest version 6.0.1!
CASE NOTHING WORKS USE THIS FILE "download"
1 - REMOVE THE ARCHIVE
2- EXECUTE THE FILE WITH THE NAME "GO.bat"
3- NOTHING EVEN? ENTER WITHIN THE "DATE" FOLDER AND EXECUTE THE "01 GO.bat"
4 - NOTHING EVEN? EXECUTE THE FILE "02 GO.cmd"
ONE OF THOSE FILES MUST WORK, BECAUSE THERE IS ONLY THIS FILE!
Now go to the Fastboot option and execute the files "GO"
Contains GPT.BIN files from Android 4.4.4 to the latest version 6.0.1!
THE NEW VERSION IS MARKED WITH RED!
6. Ready! the cell phone will restart with Android 5.0.2, but this one with ERROR does not connect in the WIFI!
To correct this error, turn off the phone
Enter Fastboot mode
Choose a ROM STOCK "here" and install.
If you want a customized ROM First:
Download the new version of TWRP "here"
Choose a CUSTOM ROM "here"
And the GApps according to Android Chosen "here"
READY! YOU CAN BE HAPPY AND INSTALL ANY ROM THAT YOU WANT.
REMEMBER THAT THE ROM Stock 4.4.4 CAN NOT BE UPDATED OVER.
Hope this helps!
do not forget to leave your LIKE and SHARE, leave your comment than you found.
Hi Wagner! The "HAND-BRICK.exe" download link isn't working. Could you provide a new download link, please? Thanks in advance!!!
Hey there,
after flashing a created boot.img I think my phone is bricked
Cannot start it anymore / no bootloader / no hardreset.
Evertime I connect it to my PC first the red LED flashes and get stuck at a green LED.
Flashtool shows "no Device" and no adb connection is working.
What did I wrong?
Is my phone bricked?
Kind regards,
Chris
dhchris said:
Hey there,
after flashing a created boot.img I think my phone is bricked
Cannot start it anymore / no bootloader / no hardreset.
Evertime I connect it to my PC first the red LED flashes and get stuck at a green LED.
Flashtool shows "no Device" and no adb connection is working.
What did I wrong?
Is my phone bricked?
Kind regards,
Chris
Click to expand...
Click to collapse
I don't think flashing boot img would hard brick. Have you tried connecting while pressing volume up and volume down? I have had situations with my old Xa where a bad flash zapped the battery to zero, and I wouldn't get any response plugging in the charger, etc, but I would try it with different cables and try holdings buttons while plugging, and it suddenly resurrected and started charging, (happened twice when Xposed N unofficial was first released)...
levone1 said:
I don't think flashing boot img would hard brick. Have you tried connecting while pressing volume up and volume down? I have had situations with my old Xa where a bad flash zapped the battery to zero, and I wouldn't get any response plugging in the charger, etc, but I would try it with different cables and try holdings buttons while plugging, and it suddenly resurrected and started charging, (happened twice when Xposed N unofficial was first released)...
Click to expand...
Click to collapse
hmm, I tried to connect in many ways, but nothing happens.
If I connect it to my charger, the red light flickers (red light to red dark to red light...)
or
it flickers from off to red to off to red...
Charging in this state over night takes no effect.
Under Flashtool the green light is on (device connected in falsh mode) and trying to flash a xperifirm-ftf:
28/041/2018 07:41:54 - INFO - Device connected in flash mode
28/042/2018 07:42:15 - INFO - Selected Bundle for Sony Xperia X Compact(F5321). FW release : 34.4.A.2.19. Customization : Customized DE
28/042/2018 07:42:15 - INFO - Preparing files for flashing
28/042/2018 07:42:48 - INFO - Please connect your device into flashmode.
28/042/2018 07:42:49 - INFO - Using Gordon gate drivers version 3.2.0.0
28/042/2018 07:42:49 - INFO - Opening device for R/W
28/042/2018 07:42:49 - INFO - Device ready for R/W.
28/042/2018 07:42:49 - INFO - Reading device information
28/042/2018 07:42:51 - INFO - Phone ready for flashmode operations.
28/042/2018 07:42:51 - INFO - Opening TA partition 2
28/043/2018 07:43:09 - INFO - Current device : D5803 - YT910ZASZ3 - 1289-4696_R5D - 1285-6521_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291
28/043/2018 07:43:09 - INFO - Closing TA partition
28/043/2018 07:43:11 - ERROR - The bundle does not match the connected device
28/043/2018 07:43:11 - INFO - Ending flash session
28/043/2018 07:43:16 - INFO - Device connected in flash mode
28/043/2018 07:43:16 - INFO - Device disconnected
28/043/2018 07:43:21 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
Sounds not so good :crying:
dhchris said:
hmm, I tried to connect in many ways, but nothing happens.
If I connect it to my charger, the red light flickers (red light to red dark to red light...)
or
it flickers from off to red to off to red...
Charging in this state over night takes no effect.
Under Flashtool the green light is on (device connected in falsh mode) and trying to flash a xperifirm-ftf:
Sounds not so good :crying:
Click to expand...
Click to collapse
Hey Guys,
now I found the mistake i´ve done.
I swapped the file.
Taken the wrong TA.img from my other phone.
Is there a way to get the phone back to life?
dhchris said:
Hey Guys,
now I found the mistake i´ve done.
I swapped the file.
Taken the wrong TA.img from my other phone.
Is there a way to get the phone back to life?
Click to expand...
Click to collapse
Did you try checking 'wipe' boxes in Flashtool? How did you flash the ta?
levone1 said:
Did you try checking 'wipe' boxes in Flashtool? How did you flash the ta?
Click to expand...
Click to collapse
Yes, tried this.
Flashed the TA manually by adb
dhchris said:
Yes, tried this.
Flashed the TA manually by adb
Click to expand...
Click to collapse
What, with dd command? Did you try to do it again with correct ta, or use adb to wipe?
Flashier wrong ta could be a big deal... I know with Z phones it was for sure a hard brick, but maybe there's hope.
Do you get the same error with Emma / Sony Companion?
Yes, dd-command.
I´m searching for my right Xc - TA.img file, but I cannot find it anymore.
adb-wipe didnt tried.
In worst case, I overwritten it by the old Z3 phones TA.
EMMA told me that the device could not be identified.
I think, that there´s no other way to get a new phone ;-(
Hello everyone,
I played around with my Xperia X Compact, backuped my TA partition, upgraded Android again, unlocked the bootloader and oem partition and then tried to flash a custom ROM. That ROM failed to start and it seems like I couldn't write to the oem partition. Now the real problem started. While I can still enter fastboot mode and flash partitions, I can't enter flashmode anymore. If I try, the light just flashes red, then green for a second and switches off again. It doesn't even show up on my PC in the brief period, that it's green.
I've since flashed android back via fastboot (flashed kernel, system, cache and userdata), but I'm out of ideas, how to restore flashmode or unlock the oem partition, so I can actually write to it. If I try to unlock the oem partition, it just tells me, that this is not needed, but I can't write to it.
Does anyone have any ideas? I tried to find a solution for the last few months now and I'll probably give up and just buy a new phone soon (as I don't like android and I can't even update it to 8).
Thank you in advance!
deepbluev7 said:
Hello everyone,
I played around with my Xperia X Compact, backuped my TA partition, upgraded Android again, unlocked the bootloader and oem partition and then tried to flash a custom ROM. That ROM failed to start and it seems like I couldn't write to the oem partition. Now the real problem started. While I can still enter fastboot mode and flash partitions, I can't enter flashmode anymore. If I try, the light just flashes red, then green for a second and switches off again. It doesn't even show up on my PC in the brief period, that it's green.
I've since flashed android back via fastboot (flashed kernel, system, cache and userdata), but I'm out of ideas, how to restore flashmode or unlock the oem partition, so I can actually write to it. If I try to unlock the oem partition, it just tells me, that this is not needed, but I can't write to it.
Does anyone have any ideas? I tried to find a solution for the last few months now and I'll probably give up and just buy a new phone soon (as I don't like android and I can't even update it to 8).
Thank you in advance!
Click to expand...
Click to collapse
Did you already try drivers install via Flashtool? Open drivers exe file in /flashtool/drivers, and check boxes for fastboot, flashmode, and Xc.
levone1 said:
Did you already try drivers install via Flashtool? Open drivers exe file in /flashtool/drivers, and check boxes for fastboot, flashmode, and Xc.
Click to expand...
Click to collapse
Thank you for your response.
I don't think it's a driver issue. I flashed via flashmode before on Linux and Windows, and in those cases the green light stayed on, until I switched the phone off. Now the green light goes off, before it can even connect to my computer, so it seems like the flashmode crashes on the phone. Nonetheless I tried the driver install, but that didn't change anything.
The phone only lights the green light for a second, before it goes off and then it starts looping red -> green -> off -> repeat.