xperia z3c, bricked during restore - Xperia Z3 Compact Q&A, Help & Troubleshooting

Hello!
I had my phone MB replaced during service and before that I got a full TWRP backup, including system and TA.
After I got it back (new MB) i rooted it and restored the full TWRP backup, without thinking too much..
Unfortunately the phone now is hard bricked, only the red light will blink when connected to PC but that's about it. No flashmode or fastboot.
The question is if I can do anything to salvage this phone.. I only have a full TWRP backup (system and TA taken before the MB swap), but I don't know if this can help. Can I try to use S1tool for this, or there is no chance?
any suggestion is welcome, thanks!

correction..
Actually, i did get a full twrp backup before restoring that old backup that crashed the phone. but it is on the phones internal memory, and i have no access anymore.
Assuming that i could get basic adb access to pull that backup out and get a ta.img out of it, or to somehow directly restore the full twrp backup - then it could work by using the s1tool method.
but i dont know if this basic access is possible.. any thoughts? i don't want to disassemble the back if it is hopeless in the first place..

If the phone can't be detected by ADB Access and all other attempts have failed most likely its a hard brick.
There's a great guide on how to recover from problems like such though I cannot guarantee it would work, but its better to try. Click Here
A last resort option would be to send it to Sony

thanks but it is a hard brick in any case, cause i restored a wrong ta (imei, etc). I was hoping to be able to wipe the ta by unlocking the bootloader, via s1tool, but i am not sure this can wipe the ta to the extent that i can reboot the phone or use adb with it. anyone knows?
if i could manage to use adb with it i could pull out the correct ta from the twrp backup in my internal memory and use that to revive the phone, as others have done.. but it seems like a long shot.
also if anyone has any info on where the test point is for this device..
thanks

Related

Sony Z1 Fastboot File Recovery

Hey All!
I have a Sony Xperia Z1, which although advertised as waterproof, somehow got water damage after a day at the waterpark, even though all the flaps were perfectly closed and the phone even had a case that covered the whole back and sides of the phone.
After a few days of letting the phone dry out, now I'm able to connect it to my laptop, but only in fastboot mode as the phone won't boot up and I can't turn on USB Debugging to try and do something via ADB. Anyway, the bottom line is that I need to recover the files from my phone. I read about pulling files out through ADB, but I have no idea if it's possible to somehow acces the phone memory through Fastboot mode or at least switching to ADB using fastboot. The phone has insurance so I don't really care about the hardware, I just want my photos and files(which I realise I was an idiot for not backing up regularly).
Please help!
P.S. The phone isn't and has never been rooted.
Try here: http://forum.xda-developers.com/showthread.php?t=1849170
Thanks. I read everything but unfortunately the information found on that page and the links provided there doesn't help in my situation. From what I read there, the solutions include wiping all the data off the phone, which is exactly what I don't want to do. I would just need to somehow switch from the current Fastboot mode(blue light) to ADB, so that I can use the "pull" cmd and download my files from the phone.
Sorry to hear mate. Perhaps you find some ideas here:
http://forum.xda-developers.com/showthread.php?t=2229250
Thank you. I tried those solutions last night, I managed to enter flash mode, flashed only the system files, without wiping the data, everything was succesful, but unfortunately there was no change in my phone's state. Still no response when trying to power it up, still no ADB access. I'm starting to think that my data can't be recovered in the phone's current state
If you can get flashmode and flash system files succesfully and without errors you could also try to flash whole ftf of your device and wipe everything else but data.

[Q] Nandroid without functioning screen?

Is it possible to do a Nandroid backup without a functioning screen, assuming the rest of the phone works fine? If I connect to my computer can I used ADB or some other tool to initiate the backup?
Spaded21 said:
Is it possible to do a Nandroid backup without a functioning screen, assuming the rest of the phone works fine? If I connect to my computer can I used ADB or some other tool to initiate the backup?
Click to expand...
Click to collapse
Take a look here EDIT:- Never mind I just noticed this "The app also lets you restore backed up data to your device. Before you back up, you'll be prompted to generate a password you'll also have to type into the app on your phone before the backup can begin"
You could use adb pull to pull the contents of your partitions though
Spaded21 said:
Is it possible to do a Nandroid backup without a functioning screen, assuming the rest of the phone works fine? If I connect to my computer can I used ADB or some other tool to initiate the backup?
Click to expand...
Click to collapse
Their are non touch versions of CWM recovery try one of those
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-m7.img
Is there a guide for this version?

SOLVED! Phone pratically death after TWRP swap between 2 XPERIA Z

Hi
- I forced a full TWRP backup of my C6603 phone to another phone xperia z (C6616) -
To do that I renamed the repertory identity of the C6616 with the C6603 code name (renamed twrp\backups\CB5A1TRTGJ to twrp\backups\CB5A1SWVAJ) I do that to see the TWPR backup in the menu.
Result is catastrophic:
- No boot, no vibration, no vibration when hard reset too
- Cannot go into fastboot, adb not working, usb debugging was on in recovery but don't work
- When I connect to wall charger a continuous blinking red light, battery level is ok but I don't know if charging
- Never seen again yellow, blue or green light
- Tried flashtool, the phone is detected but not identified! Process jammed when tried to reading the phone, cannot read model and identity.
- In flashtool phone showed in flash mode, no need pressing low volume, no blue light!?
- Always flashmode detected but phone deconnect and reconnect after 2-3 min
Processing of loader.sin finished with errors
I tried PC companion. Detect the phone but cannot identify it, so process cannot continue.
Bootloader seem corrupt.. And it is locked
I have the original TA backup of the phone but how I can write it?
Here is a way to write bootloader with original TA ?
A way to force a "RAW" write of the bootloader with TA ? Skipping model detection ? Trim Area ? Jtag?
I read a lot of topics but I did not find any solution. Help please!
Carl
Y did u do dis
When I had problems with flashing through the flashtool on Linux, Windows was there to help. But my Z was in a good shape compared to yours.
Sorry, but I don't know how to help you.
Your 6603 twrp backup that you forced to restore on your 6616, may have contained a TA backup. If this is restored to a different device, then a permanent, unrecoverable hard-brick is enivitable.
Mobo replacement is the only option.
I sincerely hope this was not the case in your situation. Check your twrp backup files and see...
Exactly my case... But I have a TA backup!
shoey63 said:
Your 6603 twrp backup that you forced to restore on your 6616, may have contained a TA backup. If this is restored to a different device, then a permanent, unrecoverable hard-brick is enivitable.
Mobo replacement is the only option.
I sincerely hope this was not the case in your situation. Check your twrp backup files and see...
Click to expand...
Click to collapse
The TA partion was in the backup But I have a backup of the TA !
The only way I can communicate to the phone is with S1Tool and probes test. Error #0017 msg at the ends, MINOR ERROR [ 0x80080021_, err: 0017 ]
error while uploading final HDR block. Here is a way to convert the TA file and upload it with S1tool ?
Thanks¸
Carl
Solved hard brick c6xx ))))
SOLVED!!!
I used a tool to convert my TA partion backup to a S1tool compatible file !!!
Incredible !! Resurrection ))))
I used probe test point, run S1tool, emergency mode, flash generated file and WOW
Thanks all
Carl
shoey63 said:
Your 6603 twrp backup that you forced to restore on your 6616, may have contained a TA backup. If this is restored to a different device, then a permanent, unrecoverable hard-brick is enivitable.
Mobo replacement is the only option.
I sincerely hope this was not the case in your situation. Check your twrp backup files and see...
Click to expand...
Click to collapse
Congratulations:thumbup:
This is the first instance I have heard of whereby a user has restored their Ta partition to a bricked device
Maybe you should make a detailed tutorial about how you did it. I'm sure there are other users in a similar situation
can you help me out im in the same boat what probe test point s1tool etc
thanks
RE help
Do you have the original TA partition backup of the phone?
if yes, send me a picture of the back with the back cover removed
If not I cannot help you
Carl

[ROM][Bootloader][Root] Warning! Please read before you unlock bootloader.

[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Bricked is right !
quyvinh said:
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
My recovery is still untouched, so does bootloader. That is why I said mine os softbrick. It means if I have the stock ROM, then I am ready to go back alive again. I cannot imagine how could you erase the stock recovery? Unless you failed the custom recovery, then it probadly hard bricked. If I can find how to fix it then I will post here. I am currently working around with MTK Droid tool and SP Flash tool, but they are working partially only. Cannot write out the scatter file. Man, this phone is tough.
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
min1968 said:
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
Click to expand...
Click to collapse
Did you do this?
emowing said:
13. select wipe, format data, type in yes (this fixes the boot looping issue -- credit @acotto)
Click to expand...
Click to collapse
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
This is because first these phones are MTK67xx phone, and 2nd they are running on new android 5.1. So the way they are rooted different with the old ways.
grampyog said:
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
Click to expand...
Click to collapse
eksasol said:
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
Click to expand...
Click to collapse
Here you go. this is a twrp backup.
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
how do i restore the rom im kinda a newb i rooted my phone than restored and now im stuck a startup and it wont go it. just gets stuck on "checking connection" i have the vivo XL and i am in need of help so how do i get this rom back to original because i dont know what to do:fingers-crossed:
Bam-Great
Followed all of the instructions and many tries later I have a phone that boots and works just fine. What I'm not finding is an image of the original rom anywhere. Pretty sure I've looked closely but if anyone has a link take me to your leader. My thanks to the awesome person that put this tutorial together. If anyone has bricked their phone trying to root follow these instructions.
Note: The stock MS drivers did not work make sure to load the VCOM drivers.
Many thanks again,
Ken
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
Any ideas if this restore method with Bypass the Factory reset protection?
Just as a quick update. Simply formatting with the flash tool. And installing the gionee firmware was enough to bypass the Google factory reset prevention. Hope this helps anyone else that forget there Gmail address they used.
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
cas8180 said:
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
Click to expand...
Click to collapse
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
xdadev_user11 said:
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
Click to expand...
Click to collapse
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
cas8180 said:
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
Click to expand...
Click to collapse
That's strange. grampyog had the same problem. But the backup rom worked for me and eksasol. Very strange.
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
xdadev_user11 said:
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
Click to expand...
Click to collapse
That did it my good man! I have a complete bundle now with boot logo and the nvram secro files you included I feel compelled to mirror so let me work on that. Thanks a bunch thanks to you I am back in business!
Here is the link for the complete TWRP backup that should be able to restore any device back to stock. https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip?dl=0

locked stock ROM Mi5 in bootloop - recover data?

Hi friends,
Please help me! I dropped my Mi5 (64GB version) by mistake few weeks back. It has gone into bootloop since then.
I had bought this phone approx. 6 months back. So, it has locked bootloader and I didn't enable usb debugging as well so adb is out of the question. It doesn't boot in recovery. The only thing I can get it to boot in fastboot mode. I am kicking myself for not taking the backup. Is there a way to recover the files (photos, videos)? Has someone tried testpoint method and can confirm the data was not lost? Recovery of data is primary for me so I won't mind striping it down and pull out the memory card if possible. Please help.
Thanks a lot in advance!

Categories

Resources