Hi, i recently got my xa screen shattered and i found another exactly same xa as mine but with signal problems (network not recognised and fails to make any calls, register to gsm)... becouse i bought it cheap and by the looks it's new XA i decided to revive it somehow, i tried to flash firmware newer and same version 33.2.A.4.70. Customization : RU but that didn't solve it. i then unlocked my bootloader, flashed boot and twrp recovery , booted in recovery and find out that some partitions is wiped. i believe this is the problem. im uploading pictures of partitions. can i somehow restore them? i mean i got 2 x fs3111 phones tho my shattered is with android 7 and locked bootloader, but if this is an issue i can solve and fix this phone i can downgrade to same version android 6, unlock, twrp it backup my partitions and restore it in phone that has wiped partitions, or maybe u can tell me better options? im uploading photos of wich partitions lost, take a look XX
AND i took its cover off and looks like it's new and no internal damage to components, i believe it's related to partitions somehow.... tho i'm not expert of android phones ... could that be? xx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where are u from?, I believe the problem isnt with the partition, maybe the phone is reported by imei, so you have this particular problem, for now on, use the motherboard of your previous phone, to make it work.
Related
Before anyone says anything, I know, there's no 'counter' itself, but what I found it's quite similar.
For those who enjoy flashing their devices like me, I'd like to show you how all flashes we made are stored in the TA Partition. It doesn't matter if we have open or closed bootloader, they're all stored there.
Simply make a backup of your partition using a tool like BackupTA 9.11, open the TA.img with N++ and in line 700 and later if you have Unlocked BL, or line 1360 and later on Locked BL, and check the contents.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
_________________________________________________________________________________
All flashes we made, via either flashtools or via PCCompanion, are stored there, with CDA contents, if we chose to erase UserData, the version we flashed, etc... So, just in case you just arrived here, and you need to send later your device to Sony to fix it, or repair it, I highly recommend you to root using whatever method you prefer, and then make a TA Bakcup before anything. I did it 1 year ago and this is how the TA looked in that time (quite clean):
Nice! Good job! Thats awesome!:highfive:
Are updates from PC Companion stored there? If not then it's flashtool thing
DavidMKD said:
Are updates from PC Companion stored there? If not then it's flashtool thing
Click to expand...
Click to collapse
I think so, because bootloader updates (EMMA) seems to be there, look at the Unknown lines...
In fact, I think that anytime we flash via S1 protocol, is stored there, as a log.
So i have the same problem as this video (youtube.com/watch?v=3dQGgcNvamc)
I Did everything same as tutorial, when i finish the unlock bootloader screen show it's unlocked but when i do the fastboot reboot appears "lock state - locked" i have tryed many times, i confirm the unlock, i do the fastboot reboot, i wait 5 minutes but still don't work, and my nexus are bricked so i need to unlock for flash de stock firmware HELP MEEEE
Sorry for my english is not the best...
Best Regards.
If the bootloader relocks itself when rebooted, the emmc chip is defective and can only be fixed via motherboard change.
audit13 said:
If the bootloader relocks itself when rebooted, the emmc chip is defective and can only be fixed via motherboard change.
Click to expand...
Click to collapse
thank u
About de motherboard change, Its cheap? WORTH IT ?
I recommend looking for a used nexus 5 with a damaged screen and working motherboard in your area. This should be cheaper than buying a new motherboard or used motherboard from a retailer or eBay.
Just for have sure, i get this error when i try wipe something in recovery mode, this is problem of motherboard or just in memory or some part or loose cable? because this phone fell to the ground and is with the cracked screen
Again sorry for my horrible english!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the bootloader keeps relocking, I am 99% sure that the motherboard needs replacement. I have two motherboards sitting in my drawer that always relock the bootloader when I reboot.
Hi all,
Scoured the forum for a while but, to be honest, I didn't even know how to search for my issue. Please feel free to redirect me to another thread.
Two problems.
1.
Tried to flash Cyanogen to my Xperia Z3. Unlocked bootloader and tried to do something [enter technical word, flash maybe] a root img file. This soft bricked my phone, took it to a shop, they said it's dead, bought another one. Is this salvageable? More details: Followed instructions here, got to "fastboot reboot", (flashed a cyanogen nightly) then phone only made it to the Sony screen on startup. Then followed these instructions to flash moonwalker but the result was a soft brick (try to turn it on, one lifeless vibration and nothing). Didn't root it beforehand (yep, idiot). I've heard you could flash an older ROM, but this leads me to the problem below.
2.
New phone. Looking to root it. Using flashtool and an ftf (D6603_23.0.A.2.93) downloaded here, but when selecting firmware, the file ftf appears to be empty. I imagine flashtool has undergone cosmetic surgery (update) as it appears to be different than other pictures, or perhaps I'm missing something glaringly obvious?
If anybody with a bit of free time has a moment to help me out, I'd be very grateful. Many thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not sure the image is working and not able to post external links. To explain it, the firmware appears (and is the correct model), but all other boxes (content, wipe etc.) are empty and the flash button is greyed out.
I have a G955U, and I installed a combination firmware and I went to see it and use the command * # 33725327 #, I just moved and erased my emei from my device, now everything was 0000000, could someone help me with some guidance, I already passed the combination firmware again, but it did not come back
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
will cost u 140$ for new imei ebay search (samsung s8 imei repair )
Friend, the problem is not to pay is to solve
eduluzamba said:
Friend, the problem is not to pay is to solve
Click to expand...
Click to collapse
You can restore a efs back up or try flashing stock firmware see if it comes back sometimes its due to incorrect basebands
TheMadScientist
And where could I find a backup of efs and restore because I did not back up the folder, I went to COMBINATION_FA70_G955USQU2ARA1, but nothing came of it, follow the photo
i also did the same formated imei via combination file n i lost it has to pay 140$ to get a new imei on my s8.
eduluzamba said:
TheMadScientist
And where could I find a backup of efs and restore because I did not back up the folder, I went to COMBINATION_FA70_G955USQU2ARA1, but nothing came of it, follow the photo
I think if I remember right there may be a back up on 1 of these partitions.
fsg -> /dev/block/sdd4
or
fsc -> /dev/block/sda3
If you load the combo then go to IME use this code. *#33725327# look around but do not do anything I think it tells you in there which partition it creates a back up to...
Click to expand...
Click to collapse
Hey everyone,
I have this issue with my device hopefully you know something about it: a while ago I rooted it, got Magisk on it all that. The device was just out so updates were still coming strong--or maybe I payed more attention to them than I do now, IDK--the case is that I accepted one of them and it undid the root and updated MIUI to something-something, regardless, since then I'm unable to flash a recovery image.
I thought the partitions got messed up or something and flashed the official system with the official Xiaomi spyware/adware suite "tools" hoping it would rewrite what needed rewriting then I tried flashing the recovery (TWRP) but no luck.
I'm using the XiaomiADBFastbootTools Java applet. It seemingly flashes the thing successfuly then it boots right into the system again, not in recovery. If I use force a recovery reboot through adb or with the buttons (which I've already forgot which were) the recovery the comes up is the official one, not TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every time finishes "successfully", then the device reboots taking just tiny bit longer then I see the MIUI logo with the sort of paint-spill animation covering it and then I'm back on stupid Mars again (the stock pseudo-interactive wallpaper). Not even my information is lost--not that I'd want to, but at least it'd be something.
Since I removed most bloat the phone became pretty much useless and I wasn't even thorough because there's stuff that just can't be removed. Rooting would allow me to get some utility back out of it. Can it be fixed at all??