Develop Bugs

[Q] [UPDATED] USB trouble and brickish issues

UPDATE:
I'm thinking I could download rom manager and use it to install the stock rom... but given the trouble that I had with flashing roms before:
(My phone had a working version of Axiom 2.4 on it. I decided to try to flash a few new roms (gummy, liquid, codename android) and all had the same issue, they would boot, go to the upgrading android screen, finish that and go straight to the homescreen without the "welcome to android/activating" screens, then freeze after 10 seconds requiring a battery pull. Sorta led to this mess)
I'm not sure its a good idea.
Any thoughts? I really just need to get rid of the lock on the splash screen.
I'm considering just letting it sit till an ota comes out and either A: relocks the phone so I'll return it, or B: effs it so badly I can return it.
Drop box + 4G can be an annoying workaround for usb functionality.
Having some trouble with the GNex.
I was stuck in recovery, now I have it booting with minimal apps in my nand of a stock rooted rom. (Minimal apps as in I have none of the system apps I uninstalled nor any user installed apps. Luckily I do have the android market)
However my underlying issue with the USB remains.
I am unable to connect it to a computer and have it recognized, whether the phone is booted (trying to mtp or whatever so I can see the files) or in adb or fastboot. The same error 43 comes across on both of my computers. The phone DOES charge via usb.
I'd like to return it to VZW claiming a broken usb, but the phone is still unlocked, and it shows the unlocked icon with the google splash screen. Is there anyway I can relock the thing and return it, or alternatively does anyone have any ideas on getting the usb working? I've tried both the pdanet method of drivers and the ones from the samsung site to no avail.
Thanks in advance!

You could try reinstalling the USB drivers. I'd suggest downloading pdanet on your computer and run the wizard.
Edit: I should have read your last paragraph. Sorry :/
Sent from my Galaxy Nexus using xda premium

Found this on the GS2 forum.
http://forum.xda-developers.com/showthread.php?t=1203802
People had success cleaning their phones USB port with a toothbrush.
Sent from my Galaxy Nexus using xda premium

El Daddy said:
Found this on the GS2 forum.
http://forum.xda-developers.com/showthread.php?t=1203802
People had success cleaning their phones USB port with a toothbrush.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Didn't seem to work but thanks for the tip!

[Q] Can't get phone to re-root, please help

Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.

And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?

Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium

AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium

Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )

AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium

IT'S DONE!!! Again thank you both so much1

[Q] Unsure if my LG G3 is fixable, please say it is

Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.

xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.

epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.

I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.

Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.

Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone

Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!

Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.

xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?

epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.

LG Optimus G E971 (Rogers) - Bricked_Help

Alright ... after 2.x years I yet again pickup this beauty.
Unfortunately the one I got is nowhere near the one I had from my old employer, this one was $80 and has seen much better days, but I figured I'd get back into looking what Android had to offer, for me.
So I take a look and I realize I HATE KitKat ... horrible standard OS and if LG keeps doing this to the Android OS it would suck!
Ok ... so I do the following:
Root using SuperSU ... sweet.
I download to the PC FreeGee - realizing no longer needed after 2hrs last night but I'm tired and I say screw it.
So I download FreeGee directly on the LG ... Bootloader unlocked. Sweet.
I copy the zip file for the CM 12.1 for Android 5.1, I think it's for 5.1 but the subsequent events may tell I'm wrong.
(File: cm-12.1-20150521-UNOFFICIAL-geeb)
Now, device installs the OS and reboots successfully. Sweet jesus this looks beautiful! I navigate around the menu and I think all is good and a few icons I have no clue what is going on with the one in the tray on the bottom right.
So I launch it and it goes through first page of info and I realize it's Google's Camera which saves everything in the cloud ... NOT a fan of that, and there is a check box to disable location information I disable it.
I exit the Google Camera app and then the screen goes blank. I see 3 Red LED blinks in the notification light and 6hrs later I STILL cannot power it on!!!
1. Can't power it on!
2. Can't get Bootloader to show up (the one with the Android heart exposed)!!
EEEK.
3. Just the damn LED blinking, consistent blink!!
4. I try Volume UP/DOWN buttons, connect USB to the G, then to Win7 and nothing!
I suspect Google Camera trying to connect to Google's services which may NOT be in CM12.1 for this device. I also suspect since I installed the CM12.1 with the USB connected it tried to connect using ADP, which I feel it KEEPS doing in Win7. I have the factory drivers and the updated drivers NOTHING fully works; just the connect then immediate disconnect chime in Win7.
Files I have: (I'm using Win7 64bit)
These files I've all acquired through various threads there.
LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1.exe
UPDATE-SuperSU-v1.94.zip (SuperSU to root)
cm-12.1-20150521-UNOFFICIAL-geeb.zip (This was installed before going dead with LED blinking Red.
LGMobileSupportTool.exe (because I do NOT have the S/N, it's in the OS which will NOT boot I cannot download the original OS from LG's servers, arrrgh!)
LG-KK-4.4.2-Intl-Cdn.zip (supposedly the original OS yet HOW the FUNK can I load this onto the LG if I cannot see anything on the screen? Hmmmkay ...
so does this mean I've got a permabrick and i'm fubar'd? IF not would anyone please led an assist, please would you?
Thank you kindly, in advance.

Supa_Fly said:
Alright ... after 2.x years I yet again pickup this beauty.
Unfortunately the one I got is nowhere near the one I had from my old employer, this one was $80 and has seen much better days, but I figured I'd get back into looking what Android had to offer, for me.
So I take a look and I realize I HATE KitKat ... horrible standard OS and if LG keeps doing this to the Android OS it would suck!
Ok ... so I do the following:
Root using SuperSU ... sweet.
I download to the PC FreeGee - realizing no longer needed after 2hrs last night but I'm tired and I say screw it.
So I download FreeGee directly on the LG ... Bootloader unlocked. Sweet.
I copy the zip file for the CM 12.1 for Android 5.1, I think it's for 5.1 but the subsequent events may tell I'm wrong.
(File: cm-12.1-20150521-UNOFFICIAL-geeb)
Now, device installs the OS and reboots successfully. Sweet jesus this looks beautiful! I navigate around the menu and I think all is good and a few icons I have no clue what is going on with the one in the tray on the bottom right.
So I launch it and it goes through first page of info and I realize it's Google's Camera which saves everything in the cloud ... NOT a fan of that, and there is a check box to disable location information I disable it.
I exit the Google Camera app and then the screen goes blank. I see 3 Red LED blinks in the notification light and 6hrs later I STILL cannot power it on!!!
1. Can't power it on!
2. Can't get Bootloader to show up (the one with the Android heart exposed)!!
EEEK.
3. Just the damn LED blinking, consistent blink!!
4. I try Volume UP/DOWN buttons, connect USB to the G, then to Win7 and nothing!
I suspect Google Camera trying to connect to Google's services which may NOT be in CM12.1 for this device. I also suspect since I installed the CM12.1 with the USB connected it tried to connect using ADP, which I feel it KEEPS doing in Win7. I have the factory drivers and the updated drivers NOTHING fully works; just the connect then immediate disconnect chime in Win7.
Files I have: (I'm using Win7 64bit)
These files I've all acquired through various threads there.
LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1.exe
UPDATE-SuperSU-v1.94.zip (SuperSU to root)
cm-12.1-20150521-UNOFFICIAL-geeb.zip (This was installed before going dead with LED blinking Red.
LGMobileSupportTool.exe (because I do NOT have the S/N, it's in the OS which will NOT boot I cannot download the original OS from LG's servers, arrrgh!)
LG-KK-4.4.2-Intl-Cdn.zip (supposedly the original OS yet HOW the FUNK can I load this onto the LG if I cannot see anything on the screen? Hmmmkay ...
so does this mean I've got a permabrick and i'm fubar'd? IF not would anyone please led an assist, please would you?
Thank you kindly, in advance.
Click to expand...
Click to collapse
Try these threads, it might help you.
http://forum.xda-developers.com/showthread.php?t=2498102
http://forum.xda-developers.com/showthread.php?t=2797190

Advice needed - dead Z5 premium Dual E6883

Hi
So I woke up this morning early for some reason and saw that my charging phone was off (no dimmed clock) and the notification light was a constant red.
Obviously I tried several reboots and safe boots but no joy. Installed the latest Xperia companion on my laptop but when I connect the phone its not recognised, unless I try the option to repair then the notification light flashes between red and green before staying green and then a popup message appears on Xperia companion stating that the phone is locked with instructions on how to unlock it (if it were working), etc. After about thirty seconds or so it reverts back to the constant red light so I assume that the connection to the software times out.
I have tried a long 6/8 hour charge but that hasn't helped (something to try that I read somewhere).
The only constant is when I power up the phone the notification light flashes slowly five times red, then the red light stays on constantly until I hard reset again.
I have not been able to find out anywhere what this five slow blink error notification means so was hoping someone could tell me.
The only thing that had happened before this event was that for the past few weeks every now and then it would reboot itself several times randomly so I deleted apps to free up internal space.
Any factual pointers would be very helpful.
Many thanks

Sounds like it is soft bricked. I assume that you are totally stock (not rooted, no recovery). If this is true, I think the easiest thing to do is to 1) download Flashtool; 2) through Xperifirm (integrated into latest version of Flashtool), download a factory .ftf file for your unit (single sim vs dual sim); 3) ensure all needed drivers are installed on your computer; and 4) flash the new factory ROM.
Further, to be better prepared if this should ever happen again, download the flash the rooted .ftf file from the most popular post in this section ([FTF][Android 7.1.1][ROOT][R/W][32.4.A.1.54] E68xx + Patched Kernels (Google Drive). Then you'll be rooted and have a TWRP recovery that can be used to much more easily cope with bricked situations. Good luck!

wicozani said:
Sounds like it is soft bricked. I assume that you are totally stock (not rooted, no recovery). If this is true, I think the easiest thing to do is to 1) download Flashtool; 2) through Xperifirm (integrated into latest version of Flashtool), download a factory .ftf file for your unit (single sim vs dual sim); 3) ensure all needed drivers are installed on your computer; and 4) flash the new factory ROM.
Further, to be better prepared if this should ever happen again, download the flash the rooted .ftf file from the most popular post in this section ([FTF][Android 7.1.1][ROOT][R/W][32.4.A.1.54] E68xx + Patched Kernels (Google Drive). Then you'll be rooted and have a TWRP recovery that can be used to much more easily cope with bricked situations. Good luck!
Click to expand...
Click to collapse
Many thanks for your reply wicozani! It's very much appreciated! I actually thought it was something along the lines that you mentioned as I had a feeling that the issue occurred because an app updated and the internal memory filled up to the pint where the phone can no longer operate. (I have too many apps installed).
You are correct in assuming that my phone is completely stock as I've never bothered with any modifying, etc.
Funnily enough, during my research the most useful advice I've seen was a YouTube explanation/guide and they used Xperifirm so I've had a look at the website to familiarise myself.
One question, what drivers should be be looking for, where would I install them on my pc and at what point would they be used in the flashing process - I've not seen this mentioned at all anywhere before?
And thanks for the tip for future proofing - I've already had a look at that post to try to make sense of it.
Many thanks.

DANORAK said:
Many thanks for your reply wicozani! It's very much appreciated! I actually thought it was something along the lines that you mentioned as I had a feeling that the issue occurred because an app updated and the internal memory filled up to the pint where the phone can no longer operate. (I have too many apps installed).
You are correct in assuming that my phone is completely stock as I've never bothered with any modifying, etc.
Funnily enough, during my research the most useful advice I've seen was a YouTube explanation/guide and they used Xperifirm so I've had a look at the website to familiarise myself.
One question, what drivers should be be looking for, where would I install them on my pc and at what point would they be used in the flashing process - I've not seen this mentioned at all anywhere before?
And thanks for the tip for future proofing - I've already had a look at that post to try to make sense of it.
Many thanks.
Click to expand...
Click to collapse
I used that link to root my Z5P for the first time last year. One must follow the directions exactly. Then, you'll be on a base ROM that you can easily flash Joel's LOS 14.1 ROM over the top. It is awesome to have my 5-year phone now featuring an Android Security Patch Level of April 5, 2020! Both Xposed Installer and Substratum are working like a charm. If you want to install Magisk, be sure to uncheck "zip-verified file" (or something like that), and it will install fine. I had several instances of failing to install Magisk until i wised up and unchecked the zip-verified signature box. Good luck!