Black screen+Only Fastboot+FRP Locked= Hardbrick? - Huawei P Smart Questions & Answers

Yesterday i got my Fig-LX1 (L11-C432) back from repair and thought it would be nice to root it now. I did this for my cousine a few weeks ago and thought it would'nt be a problem. I unlocked the bootloader and did all that, but after i used TWRP two times to update and install magisk it refused to turn on, just leaving me with a blank screen and a headache because i googled for quite some time now.
I can use fastboot but even though i used a full firmware to update 9.1.0.142->8.0.0.?->9.1.0.142 and afterwards pushed everything i can over fastboot from that same image, it refuses to work. FRP is locked and bootloader unlocked. I can't get recovery or erecovery going and it doesnt vibrate anymore. I tried dload and HurUpdater but both refused to work.
The only thing i noticed was as I downgraded to 8.0.0 it refused to factory reset because my google account was linked in, otherwise everything was like normal.
Anybody got an idea how to manage this? It would be sad to throw it away after waiting 2 months

Have you tried to boot it into Hisuite's Recovery mode ?

Related

Nexus 6P - Bootloop and cannot enter recovery mode

A couple of days ago my Nexus 6P suddenly rebooted while in normal use. Now it is stuck in a bootloop ("Please lock the bootloader"-screen -> White "Google" logo -> brief black screen -> repeat).
The device is unlocked, and I am able to enter fastboot mode. Flashing partitions is possible, but I am NOT able to enter recovery. When selecting "Recovery mode" from the menu, the device just goes into the same bootloop. I tried to flash and boot different recovery images (Stock, CM, TWRP) without success. The bootloader and fastboot appear to working normally otherwise.
Does anyone have any idea what is going on?
Thanks
This just happened to me yesterday.. I've tried flashing different recoveries too but no dice.. I reflashed factory image and still the same bootloop..
This happened to me too like a month ago. I was just checking facebook and stuff, when suddenly it rebooted. Didnt think about it at first as I know it reboots some times, but it just got to the "please lock your bootloader" - message and then the white google-logo. Was able to access bootloader but not recovery. So i flashed stock to see if it helped, but it didnt. Got in contact with the store that sold me the phone, and they said it had to be repaired. Obviously I never told them that it was unlocked, never mentioned I saw the "please lock" - message, only the white google logo. So as I had already flashed stock I just locked the bootloader and returned it to the store and a week later I got it back. They had replaced the circuit board so yeah, nothing you can fix by flashing.
So get an RMA on it, or you will have a very pretty and expensive brick
Hope this helps you
Jaggenite said:
This happened to me too like a month ago. I was just checking facebook and stuff, when suddenly it rebooted. Didnt think about it at first as I know it reboots some times, but it just got to the "please lock your bootloader" - message and then the white google-logo. Was able to access bootloader but not recovery. So i flashed stock to see if it helped, but it didnt. Got in contact with the store that sold me the phone, and they said it had to be repaired. Obviously I never told them that it was unlocked, never mentioned I saw the "please lock" - message, only the white google logo. So as I had already flashed stock I just locked the bootloader and returned it to the store and a week later I got it back. They had replaced the circuit board so yeah, nothing you can fix by flashing.
So get an RMA on it, or you will have a very pretty and expensive brick
Hope this helps you
Click to expand...
Click to collapse
Oh my.. I was hoping against hope nobody would say this..
Thanks mate!

Hard brick? Can't boot to recovery

So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!

I think my phone (ALE-21 *574) is stuck in some twilight zone (not bootloop or stuck)

I've had some problems with my phone. My first phone ended up getting bricked 2 weeks after i bought it.
I was lucky enough to get it replaced by the store. After that i was careful with unlocking the bootloader and rooting.
I had some issues with the rooting (i have posted this in other threads already, so i won't bring that up again) ending up with having to flash a stock version of 574 from a page with roms available.
I was happy to see that the phone was again working. But ever since i flashed the stock rom, things are becoming very strange.
I'm unable to flash TWRP. The only way to access Fastboot is by first connecting the phone to the computer. And then hold vol down and power.
I am able to access Huawei eRecovery (but only by doing like with Fastpass using the computer).
I'm not allowed to update eRecovery or run recovery from eRecovery.
If something require a reboot, i need to use the cable, fastboot, vol+ into eRecovery and then select reboot.
Today i was prompted to upgrade from 574 to 584 (OTA) and the download and installation begins normally.
Only to end up having to... you guessed it:
cable+fastboot+eRecovery.
And the update fails.
The phone is working great apart from these issues. And i do not know why.
And this is why it feels like it is in some Twilight Zone. Or Hybrid-mode. Bootloader is unlocked. Firmware is stock.
But i always need to use the cable to start the phone.
Does anyone have a clue what is going on?
What kind of error it gave when you tried to flash TWRP?
No error. When i do adb reboot the phone shuts down, but does not reboot into fastboot.
If i first go into fastboot and flash twrp everything appear to be ok. But when trying to reboot nothing happens.

L31 bricked by flashing rollback package

Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.
Thanks! I sent you a PM.
Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore
Thanks, but the Toolkit says it can't find the device.
Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk
Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!
Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!
I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.
Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?

Please help! Soft bricked, unrooted, untouched, 100% stock phone brick during update

I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Cecil12 said:
I am in need of serious help! I dropped my phone off a 2nd story, smashed the screen completely. So I took my wife's old stylo 2 plus (exact same phone) stuck my Sim and SD into it, registered through metro pcs, and it worked great.
I did software update because I was really excited (my old stylo 2 was rooted and had many problems along with being unable to update android software).
Update took about an hour, then said failed. After that it has been unable to boot up. I tried recovery mode, it offers to factory reset. Again reboots and stuck at logo screen. Says error device is corrupt, cannot be trusted, will not boot. I press power it says press power again to boot anyway. Restarts and sticks at logo screen. Device is basically untouched. No oem unlock, no debugging, no developer options, nothing has been touched ever, the phone is 100% stock. I even did factory reset before I started using the phone.
Can someone please help me at the least flash trip so I can fix this??
I am not new to this, but has been 5 years since I flashed anything. The problem is, is that it's still locked, and can't boot up. The phones bricked and never been touched!
If I can get twrp flashed I can go from there, I need a way to unlock it, or flash without unlocking.
Please help me I need my phone for work. I'd rather not switch back to an old smashed screen
Click to expand...
Click to collapse
You need to download the kdz(device firmware) and flash it in download mode using lg up.
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
LG Stylo 2 Plus
Cecil12 said:
Sorry for the super long delay. I did what you said, and was able to use my phone again in no time. Thank you very much!
Click to expand...
Click to collapse
Hey would you be able to tell me which firmware worked or possibly even a link. I am having issues with getting one to work on the lg stylo 2 plus using lg up.

Categories

Resources