sony android update phone bootloop - Sony Xperia X Compact Questions & Answers

hello forums,
today I installed an android update onto my sony xperia x compact which resulted in my phone ending up in a boot loop.
I see the sony logo, then the Xperia slogan and then it reeboots again.
The companian app does not recognize my phone.
What can I do to backup data on my phone?
Should I flash the boot loader to use backup / restore functions?
My phone is also encrypted. will backup / ADB even allow me to get the data stored on my phone?
Thanks

Did you unlock your bootloader, I think if you have unlocked bootloader, you can't update straight away from the phone? Mine stuck on "Sony" screen once, and then it restart itself and boot into the system. The update failed,but I can boot back to the system. Maybe you should try starting the device again and if it stuck in "Sony" wait it for a while
Ps: better do a backup before system update.

I am sorry I didnt mention that before.
until now, the phone is using stock bootloader and stock rom
can't I replace the boot loader with a custom one to use adb to backup my data?
that worked with my old flashed phone, because rom and OS are separated from each other.

soomon2 said:
I am sorry I didnt mention that before.
until now, the phone is using stock bootloader and stock rom
can't I replace the boot loader with a custom one to use adb to backup my data?
that worked with my old flashed phone, because rom and OS are separated from each other.
Click to expand...
Click to collapse
Unlocking BL won't help you to backup data. On contrary it will wipe your data. If it is really bootloop, what you probbaly can do is flashing the same firmware (before the failed update) without selecting to wipe data
PS: Regarding the unlocking of bootloader, Don't do it unless you know what you are doing. It will wipe the TA needed for the camera. Please please do research on how to backup TA before you ever unlock your bootoader.

sadly I cannot reflash the same rom as all is stock software, one mistake I will not make again.
Sony support sais I have to do a factory reset and there is no way to save my data beforehand in the current state. also, it seems they just dont care about customer data as they do not make a backup of the data or the OS before screweing it up.
if you know how I could reflash the firmware, please tell me. I don't know how
So I guess I am screwed?

Related

adb backup without touch and with black screen

I dropped my 6p and now have no screen and no touch.
The device is rooted on stock 7.1.1 with unlocked boot loader. and fingerprint scanner is working. I can answer the phone and make phone calls with Bluetooth and hear notification sounds but dark display and no touch.
I want to backup my data before sending it to repair. So far I was only able to adb pull the SD card. I cannot use adb backup because it requires the confirmation on the phone. any suggestion how I can backup the data without any touch access on the phone?
Also, if I go to bootlaoder and flash the entire stock there, all my data is erased right? what happens to fingerprint data stored on the device? If I relock the bootloader, will it do a factory reset? in another word what is the best way to do a factory reset and erase everything without access to phone screen and touch?
Any help is really appreciated.
mnlv said:
I dropped my 6p and now have no screen and no touch.
The device is rooted on stock 7.1.1 with unlocked boot loader. and fingerprint scanner is working. I can answer the phone and make phone calls with Bluetooth and hear notification sounds but dark display and no touch.
I want to backup my data before sending it to repair. So far I was only able to adb pull the SD card. I cannot use adb backup because it requires the confirmation on the phone. any suggestion how I can backup the data without any touch access on the phone?
Also, if I go to bootlaoder and flash the entire stock there, all my data is erased right? what happens to fingerprint data stored on the device? If I relock the bootloader, will it do a factory reset? in another word what is the best way to do a factory reset and erase everything without access to phone screen and touch?
Any help is really appreciated.
Click to expand...
Click to collapse
If you do a clean flash of the factory image all of your data is erased including your fingerprints. You shouldn't lock the bootloader before flashing the factory image. If you aren't fully stock including recovery and lock the bootloader you could brick the phone. There isn't really a need to lock the bootloader before sending it for repair.
jhs39 said:
If you do a clean flash of the factory image all of your data is erased including your fingerprints. You shouldn't lock the bootloader before flashing the factory image. If you aren't fully stock including recovery and lock the bootloader you could brick the phone. There isn't really a need to lock the bootloader before sending it for repair.
Click to expand...
Click to collapse
Thanks. I just did a backup in TWRP using adb.
If I receive another refurb 6p instead of what I send, Can I restore this backup to a new phone or something will not work because the data partition is encrypted?
Should I do a wipe data and system in TWRP before going to bootloader and flashing the factory image?
mnlv said:
Thanks. I just did a backup in TWRP using adb.
If I receive another refurb 6p instead of what I send, Can I restore this backup to a new phone or something will not work because the data partition is encrypted?
Should I do a wipe data and system in TWRP before going to bootloader and flashing the factory image?
Click to expand...
Click to collapse
I'm pretty sure you can't restore the backup from one phone to a different phone even if it's the same model. Maybe somebody knows a way to do it. You don't really need to wipe anything in TWRP if you are going to do a clean install of the factory image. The install will wipe everything.
If you have Usb debugging enabled you could also use Hisuite by Huawei. Do a google search for it as I can't post a link due to new account.

[URGENT] Any way to recover my data after flashing a rom?

Dear all
My Nexus 6p was hard bricked yesterday and keep bootloop. I did flash twrp and a stock image by adb but the phone still could not turn on.
I try to use the hair dryer to heat my phone like this way (youtube.com/watch?v=fVghgGWoWa4) (sorry that I am a new user and I cant post the link)
And then my phone can be booted into the system but all of my data lost since I did flash the stock rom.
So may I ask that is there any way for me to recover back my data in this case? ( especially app data and my photo since there are some extremely important data for me......)
Thanks so much and appreciate for your help!!!
kwan826 said:
Dear all
My Nexus 6p was hard bricked yesterday and keep bootloop. I did flash twrp and a stock image by adb but the phone still could not turn on.
I try to use the hair dryer to heat my phone like this way (youtube.com/watch?v=fVghgGWoWa4) (sorry that I am a new user and I cant post the link)
And then my phone can be booted into the system but all of my data lost since I did flash the stock rom.
So may I ask that is there any way for me to recover back my data in this case? ( especially app data and my photo since there are some extremely important data for me......)
Thanks so much and appreciate for your help!!!
Click to expand...
Click to collapse
Hello,
How did you flash a stock ROM with ADB? adb sideload? Full OTA? Shouldn't have wiped internal storage.
Or you flashed a factory image from bootloader with flash-all script? Or fastboot flash?
If you used flash-all or you fastboot flashed userdata.img, i think your datas are lost.
Good luck...
5.1 said:
Hello,
How did you flash a stock ROM with ADB? adb sideload? Full OTA? Shouldn't have wiped internal storage.
Or you flashed a factory image from bootloader with flash-all script? Or fastboot flash?
If you used flash-all or you fastboot flashed userdata.img, i think your datas are lost.
Good luck...
Click to expand...
Click to collapse
Ys i did flash it from bootloader with flash-all script......:crying::crying::crying:
Now my data are all wiped out and the system is clean.
So is there any way to recover my data back? Because the data is really important for me:crying::crying::crying::crying::crying:
kwan826 said:
Ys i did flash it from bootloader with flash-all script......:crying::crying::crying:
Now my data are all wiped out and the system is clean.
So is there any way to recover my data back? Because the data is really important for me:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Hello,
You should likely have thought about it before flashing a factory image...
Maybe there are professional forensic tools that could work. But unfortunately i don't know their names or where to find them.
Good luck...
5.1 said:
Hello,
You should likely have thought about it before flashing a factory image...
Maybe there are professional forensic tools that could work. But unfortunately i don't know their names or where to find them.
Good luck...
Click to expand...
Click to collapse
I flashed the image because i thought there is no any other way to boot my phone....
I have never thought that I can save it with a hair dryer I brought my phone to the mobile fixing shop and they did say the phone could not be fixed therefore i just flashed the image and try.
Thanks anyway
If there are any way to save the data, please let me know!!
Hans Brown said:
Looks like fail to flash a ROM because forgot to unlocked bootloader or wipe data in recovery mode, while the ROM you flashed is a stock one, no a custom one. If you have unlocked bootloader, you can see a lock appear in the boot screen.
You can go to the recovery mode and try to fix your brick phone by wipe data and cache partition, maybe you can boot you phone successfully after doing these.
You data is not really gone, in fact, you can recover the data by using some tool.
See this guide about how to fix bricked Nexus 6P and recover data from the bricked phone after flashing a ROM.
Click to expand...
Click to collapse
Hey,
This tool seems designed for a phone that bootloop. Not a device which userdata partition has been wiped and overwritten afaik...
Cheers...
I know it's too late.
I normally edit the flash_all to *NOT* wipe the phone and only do an update.
You can have your photos if Google sync is on, but your App data is gone.
Yeah the flash-all script includes a -w wipe command. You could of removed it before flashing to keep data. But after that it's bye bye baby. The only way is probably some type of software forensics tool. But keep searching cause I don't everything and maybe you can tell the FBI there info on it about terrorist and they can brute force in. Then you got your pics back.

What to backup to recover before flash ROM?

I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Splice_9 said:
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Click to expand...
Click to collapse
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
I backed up all 53 partitions and stored in my harddisk. It's less than 5GB.
I left out only the data partition because for that I use Titanium Backup and RSync.
Yet I haven't backed up the partition table, also this is important...
NZedPred said:
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
Click to expand...
Click to collapse
if i backup my efs and persist in a custom rom 64 bits that backup won't work in stock right? it is intact
Backup everything... although it may be too late already, but any working backup is better than nothing.
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
nicolap8 said:
Yet I haven't backed up the partition table, also this is important...
Click to expand...
Click to collapse
acejavelin said:
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
Click to expand...
Click to collapse
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
prokaryotic cell said:
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
Click to expand...
Click to collapse
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
acejavelin said:
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
Click to expand...
Click to collapse
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
Click to expand...
Click to collapse
Yes, you can restore your efi folder to correct this most of the time, if you have a clean backup. Otherwise you need to get it JTAG programmed
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device.
Click to expand...
Click to collapse
Just to clarify that you understand, you can't return your bootloader status to untampered but you can lock it again. However it really isn't necessary to do that just to get OTAs. All you need to do is return to your stock with stock recovery and no-root (fastboot method not TWRP flashable.) OTAs work fine once you have done so. I have restored a TWRP backup just by booting into TWRP but it seems like I had some issue unrelated to OTA, although I don't recall what they were and is was on my previous phone (Moto G4).

TWRP corrupted? Won't restore, won't backup, won't wipe.

I bought a new XT1575 a couple of weeks ago. Once I'd read enough to have confidence I followed the instructions to extract that long number to paste into the form on the Motorola web site and ask them to send me a code. They did, I input the code, I got a notice that my bootloader was unlocked. Once that was done I installed TWRP via ABD (I think, whatever the directions said). TWRP worked, I wiped the stock OS, flashed a custom ROM (Lineage 14) and everything worked perfectly.
Today I wanted to backup my existing ROM, wipe the device and install a different custom ROM. I booted into TWRP and I think it completed the backup. When I went to wipe though, it would crash partway through and boot back to the bootloader unlocked screen. If I tried to simply overwrite the existing ROM with the new ROM that would crash and boot to the bootloader unlocked screen too. Now I can't complete a backup either.
As I'm writing this I'm wondering if the micro USB card could be at fault, since that's where I want to back up to and that's where the new ROM is. However, if it was a corrupted card wouldn't the wipe function still work?
Any idea if reflashing TWRP would solve my problem? Any better solutions?

First time ever installing a custom ROM. I have some questions. Moto G5 Plus stock.

I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!
Raploz said:
I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!
Click to expand...
Click to collapse
Answer for your questions
1) losing of IMEI no is possible on custom ROM too, but taking the backup of EFS and persist will retrieve them, so no problem. And losing of IMEI is random occur when moving from one rom to other.
2) just let the android boot once, so everything get loads up with unlock bootloader (no need to setup).
3)after installing the twrp, it won't ask for password since your device got format when unlocking bootloader, so it won't ask. If you want to remove encryption then format< type yes. It will remove your encryption.
4) for talking backup of EFS and persist use this method.
Code:
Use the following command to create a backup and save it at /sdcard/persist.img:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
To restore use the following command:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
If you have saved a backup using different name then use that name instead.
And seeing your plan, everything seem good, you can continue with your plan.
Note:- for some user PE won't work for them with 2gb version, so I suggest you to take a backup of stock ROM or keep an other rom file in case it needed.

Categories

Resources