Related
Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - pics:
{
"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"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution
try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.
dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.
dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.
Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)
Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.
Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).
I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App
Maybe we should pin this or any other topic for people to post if they have bricked their device?
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.
Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.
ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps
m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.
was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.
Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash
Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App
I've tried going through all the steps to encrypt my phone, however, it seems I get stuck on the black screen with green "lock" android / robot. It never goes any further than that screen (it never reboots as the directions state it would).
I've tried a couple different roms (Frosty JB, Wicked, Synergy) and none seem to let me complete the encryption process. I haven't tried going back to stock yet, since someone with an i9300 (international SG3) posted they had the same issue even when they went back to stock.
Has anyone had this issue? If so, how did you fix it? I've been looking all over the place for days and haven't found anything.
EDIT/ANSWER:
After doing a bit more digging, evidently, there's something called a PIT file that has to do with partitioning in our phones. You need to use Odin to install it. These are the directions I followed:
Pull out the battery and reinsert.
Press and Hold Volume Down + Home + Power Button until you see a warning!!
Press Volume Up button.
Your device will now enter the download mode.
Connect your phone to the PC.
Let it install some drivers.
Open Odin and click on PIT
Select that .PIT file you downloaded.
Check the box – Re-partition and Click Start.
After the successful attempt to re-partition the device, Flash with new firmware(which you downloaded from SamMobile)
Browse the downloaded firmware to the PDA section in Odin.
Don’t check the re-partition box this time.
Click Start and wait.
As soon as the process completes, your phone will boot. and it won’t stuck at welcome screen.
PIT files for US ONLY phones can be found here:
http://forum.xda-developers.com/showthread.php?t=1848267 - SEE THE FIRST POST
This finally worked for me, but use at your own risk.
[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!
THIS GUIDE CAN APPLY TO ANY MODEL, PROVIDED YOU ENSURE TO GET THE PROPER FILES FOR YOUR VERSION!
I've had success myself flashing stock firmware from the M919V for Wind Mobile onto my I337M with no issue. This shouldn't be an issue. However, for the purpose of this guide, it is important that you get the firmware that was intended FOR YOUR DEVICE!
This was originally posted in the I337M forum as that's what I have, but here you go!
---
First head over here >> http://forum.xda-developers.com/showthread.php?t=2559693 >> and check out the original thread that helped me get to this resolution. Thank you to all the lovely people there!!
Before my softbrick occurred, I had flashed the NE1 modem through ODIN. I found that the same modem remained regarldess of the firmware I flashed. So I thought to match them up and give it another go. This worked great. This will work even if it was a regular S/W upgrade or install that caused the no sound and/or WiFi and/or Bluetooth issue.
Quick note before we begin: this guide assumes that you already went through a softbrick and have successfully come back from it, or went through a software update/firmware install which resulted in the same issue. Some of the steps in this guide may be able to be applied to some parts unbricking a phone, but this is NOT the intention. The intention is to help recover sound, WiFi and Bluetooth AFTER a successful unbrick or failed update/install otherwise.
DISCLAIMER: I am not responsible for your phone melting, imploding, turning into maple syrup or dying. Follow at your own will!
PRE-GAME CHECKLIST:
- Determine the ORIGINAL FIRMWARE that came on your device (this one was important for me, not sure how crucial it may be for others) - to be honest, I'm not 100% sure how to figure this out other than looking at the phone's box. It should notate which software version (SW-VER) it is. Before doing this, I was soft bricked, and had to use the very original 4.2.2 software for my carrier to recover from THAT. So maybe this part wasn't as important as I think, but I wanted to mention it anyway.
- The ORIGINAL USB cable for the phone - I suspect any high quality ones would work, but the one that came with the phone is a no-brainer
- ODIN 3.xx (I used 3.09)
- Samsung USB Drivers installed properly
- NO SD CARD (to be safe - this is optional as it should not be touched throughout the process)
- DO NOT, under any circumstance, use a USB hub for this procedure. Make sure it's direct into your computer with no extensions. I also recommend a cable that is 6ft or shorter if possible, but the quality of the cable is the most important
DO IT:
1) Download the ORIGINAL firmware that came with your phone (if you weren't able to determine this, I'd say the most recent one should be safe to flash, unless you softbricked while on 4.2.2 or 4.3 - in that case I would stick with the corresponding version, though I'm not sure how it would be affected since I didn't run into this)
2) Extract the file (I use 7Zip) and ensure there is one .tar.md5 file as a result - do not extract again
3) Boot up the phone into Download Mode (PWR off completely, then hold VOLDOWN + HOME + PWR together until the warning appears on the screen - click VOLUP to accept and proceed)
---PHONE WIPE---
This part is optional but I highly, highly recommend it.
4a) Flash Philz CWM (you can find the file and instructions on how to flash it through ODIN very easily)
4b) After flashing, it usually reboots into recovery. If it does not, do so manually: turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on.
4c) Make sure you close ODIN once confirmed the flash is done
4d) Tap factory reset and confirm it
4e) Once done, choose the clean ROM install option and confirm that as well
4f) Reboot the phone and continue on with the steps
NOTE: if there is anything to backup, now would be a good time to do this.
---
5) Open ODIN (IMPORTANT: In Windows, right-click and choose "Run as administrator" - this helped avoid an error for me)
6) Connect your phone directly to a USB on your PC and confirm that ODIN recognized it (it should highlight the first box and have "COM#" listed)
7) Click the second section (AP / PDA) and choose the .tar.md5 file you got in Step 1
***NOTE: ODIN may look like it's freezing or hanging here - IT IS NOT, BE PATIENT - it is a large file and it will take a bit of time to verify the MD5 for it
8) Click Start and sit back - it should take 8-10 mins or so (8:55 for me) with KitKat, and 5-7 mins or so with JB.
9) Your phone should have rebooted into a fresh Firmware. If you hear the Samsung boot sound, GREAT! You should be good (test WiFi and Bluetooth if possible) and you're done. Assuming that's not the case, which is why you're here, proceed to the next step
***If it's stuck in a bootloop, you need to force Recovery mode and do a factory reset. To do this, turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on. Use the VOL buttons to scroll to the factory reset option, and choose PWR to select. Then confirm on the next screen. Once that's done, wipe cache in the same way. Then, reboot, again in the same way. Now your phone should boot up
10) Go through setup and then go into Settings > More > About device. Observe the "Baseband version" section, and see if it matches the "Build number" section (starting from I337 and onwards). IF THEY MATCH, then repeat steps 5-10. IF THEY DO NOT MATCH, continue.
11) Download the matching modem file - ENSURE that the version of the modem you download MATCHES EXACTLY with the "Build number" in your phone's settings. Flash the file in ODIN in the AP / PDA section (if you need detailed instructions on this, it's a snap to find in XDA or Google)
12) Once done, reboot into the regular OS and verify that the "Baseband version" and "Build number" sections MATCH. If not, try to flash the modem again. After this has been verified, go ahead and follow steps 5-10 as many times as necessary until you hear that beautiful boot noise! It took me twice.
All the best and happy flashing guys! I'm not too much of an expert, just very good at explaining things, but I'll try to help as I can with any questions!
THANKS:
- All the great help thanks to input from around XDA in this thread (also listed in the beginning of this one): http://forum.xda-developers.com/showthread.php?t=2559693
- All the devs that work hard for us Canadian and AT&T guys over here
Hello everybody !
Ok, I am use to not ask any help, and to find out by myself. But I have to admit I don't have any idea remaining to solve this problem.
Let me explain you the situation :
I explain everything with details to not waste your time when you will help me !
When I first bought my Zenfone, everything worked properly. Then, I decided to flash a Custom ROM (to remove the bloatware, and to get the others optimizations). So what I did :
- I unlocked the bootloader,
- I flashed TWRP,
- I installed my custom ROM (SuperZen R15, super clean install) => at this moment, everything is working perfectly,
- I installed a custom Kernel (ProjectT, v56) by fastboot => here we are, the problem just appeared.
At this moment, the WiFi issues appear. When I boot the phone, I can turn on the WiFi (in most cases), then, WiFi just turn off. It is impossible to activate it again. In the best case, I can switch on/off the WiFi, but as soon as I download something, the WiFi just turn off immediately. Often, I just don't detect any network. In the worse case, it is impossible to activate again the WiFi, the ON/OFF button is grey.
So here is what I tried to get it back :
1) put the standard kernel with my TWRP backup => no success
2) flash another ROM (CM12, Paranoid Android, Barebone,...etc) => no success
3) flash my whole TWRP backup (system + kernel) => no success
4) flash the official Asus ROM (recovery.img, system.img, boot.img, droidboot.img) => no success
At the moment, I started thinking that maybe the WiFi just "forgot" my WPA key. So I modified the build.prop :
5) modification of the build.prop by adding the line ro.securestorage.support=false (instead of "true") => no success
6) flash the last Asus update 2.20.40... => no success.
...
I haven't any idea remaining !So I need your help ! This problem seems very standard, but I just couldn't find any solution yet !
P.S : I almost forgot. I talked about the wiFi signal, but it is exactly the same for the bluetooth signal : working on first boot, then when I use it, it just stop working and disconnect itself, and then, impossible to activate it again (grey button)
=> My last idea was to flash the radio directly by TWRP, but I didn't find any radio files for the zenfone 2...
Many thanks for your help, and thank you for reading everything !!
Max
Up !
BackDraft647 said:
Up !
Click to expand...
Click to collapse
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
[email protected] said:
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
Click to expand...
Click to collapse
You're such a genius ! I will try this evening ! Thanks a lot !
Didn't do anything. It's not working. I was thinking my wifi was just broken, but something creepy happened this morning. The Wi-Fi worked again (I downloaded one thing to be sure !) and then... My phone froze, and reboot... Is the devil inside my phone ??
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM : http://www.asus.com/fr/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
BackDraft647 said:
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM :
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
Click to expand...
Click to collapse
can you tell me what firmware you used exactly? because i tried to flash the first one, from the asus page.
But it says that i have a newest build and it doesn`t lets me past trough the installing part.
I am also having troubles with my wifi and i would like to fix it
Hello ! I don't remember exactly, I went on a website and selected the right version for my country ! But my problem wasn't solve at all actually... I brought my phone to the store, and they told me my motherboard was just burnt. They changed everything, and now it works like a charm ! Be careful with the custom kernel, I'm pretty sure that's how my phone broke (I'm very careful with batteries,...etc)
Well thanks anyway. I will try to take the phone to te oficial ASUS services from my country but i don´t think they give a new one. I live in Uruguay and this cellphone is not at sale over here
Does sideloading the firmware wipe your apps? Or is every thing still there when its done?
Sent from my ASUS_Z00AD using Tapatalk
A while back I got in a big fight with this phone (H8314 on Verizon) where I wanted to roll back to a previous version. Eventually I ended up flashing 52.1.A.0.672 and the phone worked fine. Today I decided to apply the latest update (52.1.A.3.49) and I THOUGHT that I remembered how to do it, but apparently I missed a step or something, and I need help figuring out what I've done wrong.
Here's the sequence of events:
1) When I flashed to 52.1.A.3.49, the network signal is gone (SIM is still recognized though, as it gives me the LTE bars, just no actual network signal) and WiFi was really intermittent.
2) Flashed back to 52.1.A.0.672 (which I had been on previously) and the problem persisted, still no network signal and bad WiFi
3) Used EMMA to revert to Sony stock, but all they have available is 51.1.A.11.51 (which is Android 8!) and now the network signal and WiFi works fine.
4) Tried flashing back to both versions of Android 10 and still had the same problem with network and WiFi
My exact procedure for flashing was:
1) Download firmware from Xperifirm through Flashtool
2) Make sure flashmode and fastboot drivers are installed in Flashtool
3) Delete all .TA files from firmware (both in main and boot folder) and unpack partition into partition folder
4) Copy+paste all firmware files into the newflasher folder
5) Connect phone in flashmode (volume up + plug in)
6) Run Newflasher; hit 'n' for no three times at start, and once in roughly the middle of the install
7) Close Newflasher and reboot phone.
What am I missing?? Is it something to do with the bootloader? Mine was unlocked at some point but now I'm really not sure how to tell what its status is. Something appears to be locking the SIM/network though and I know it's not an issue with the firmware itself (since one version of it was installed and working fine earlier today) so it has to be user error somewhere along the line...
Thanks!