P9 lite worst brick ever - Android Q&A, Help & Troubleshooting

Hi people, I don't know where to ask anymore. Sorry in advance for my english.
I have a serious problem with my P9 Lite VNS L21. It is no brand, as far as I know.
Everything started when I updated to EMUI 5.0 Android 7.0. (I know nothing about this stuff)
I started to have some bugs like: I couldn't turn on bluetooth, I couldn't open settings cause they always crash, and stuff like this.
So what I decided to do, hope I can turn back, was to install a custom ROM.
What I found was the Lineage 14, but the EliteKernel was required. And so on, I flashed it.
After that, bugs were becoming more and more annoying: I didn't even have the keyboard anymore.
So I did a factory reset.
Than, I was in an infinite loop in the first Wizard Setup. It was always restarting after I logged in into my google account and whatever I would press between Inizitialize a new phone or Restore from backup, it always went back.
After, I downloaded a new firmware to restore everything back and now.. nothing works. Always in black screen, I can't go into recovery, I can't fastboot, I can't even use dload.
I tried to remove battery and put it back, but it didn't work.
Sorry for the wall of text but I thought it was better to explain everything.
Thanks in advance.

Related

Help needed with crashes after recovery.

Last night I tried putting Cyanogenmod on my i9300, its a european model that is not locked.
I first tried with the nightly build of CM 11. Flashing went well, but after boot the Phone seemed to crash/freeze after a few minutes. It stopped responding and only gave sound when using the system buttons. after a few presses that freezes too. I was thinking this might be a problem in the nightly build, so I went back in the recovery, cleared things up againa and this time I tried the latest image from the unofficial CM 12 that can be found here: http://forum.xda-developers.com/gal...-temasek-s-unofficial-cyanogenmod-12-t3086689
It seemed that most people have little problem with this version so I gave that one a try. It booted and gave me an error just before the launcher had to startup. but after a reset by taking out the battery, the Phone booted fine and it all went so smooth... but as soon as i got to the point of entering my google account, the Phone frose again. I retried, and again... at that time it was late at night, and the Phone needed to be used today. So I desided to go back in recovery, clean everything out, and put back my backup. Things looked fine... but sadly, at random times th Phone freezes again. its not my Phone but my wife's, she says it hangs using Facebook or chrome. I did not get the chance to look for a pattern yet, but I hope you guys might have an idea whats wrong.
For now I asked her not to use the internet, I'm not sure if wifi or mobile date will influence it, but it doesn't hurt to try.
I have to go to work untill 9pm tonight, and by the time I get home it will probably be 10 or later, so I have little time to work on it.
If anyone can give me a direction to go in or a possible sollution then I would appriciate it. i might have missed something when putting the backup back.
Any idea's?

Of how WiFi won't turn on and I don't know that I'm doing - Galaxy Grand 2 G7105

I got my hands on a Galaxy Grand 2 sm-g7105. Performed a factory reset from device and the system worked nicely enough. A particular third party app I wanted to use wouldn't load so I kept tweaking.
I rooted and set up a CWM recovery with Odin, then considered going with Resurrection Remix. I made a backup with CWM, wiped the device and set it up. It looked great but 'audioFX.apk' or something along those lines kept crashing every 30 seconds or so. It didn't cause me any problem besides the annoying crash notification, so i figured I could just remove the apk and be done with it. To my dismay, then the notification then piled up non-stop and the system become unusable.
I went and restored the backup on CWM. Then I'd get error notifications for this and that stopping working (basically the apps present on the backup that weren't on the stock rom), so I figured the backup was useless. Another mistake, I guess.
Performed another wipe, deleted the backup for space. Tried removing every piece of bloatware I could find before unrooting (I wanted to do that). Finally everything seemed to roll... except I deleted some important apk, SecDownloadManager I've come to believe, and at that point the Play Store couldn't update a thing, it got stuck on 'Downloading'.
So I did another wipe, just to find out that didn't restore the missing apks. Got my hands on a stock rom for my model (a different build than my origibal one, but to hell with it... right?). I got that working work Odin, but to my surprise that didn't seem to completely restore the apk mess, and I got a ton of crash apl notifications and even after logging on Google the play store didn't let me in to try and see if apps could update.
Finally, I found what is supposed to be the device's original rom. Odin'd it all the way. Everything seems to be where it belongs, but I cannot really check 'cause... NOW THE ****ING WI-FI WON'T TURN ON. It's not like it doesn't connect to my network, it just won't activate. I press the switch, or goes back off.
I tried rebooting, taking out the battery for some seconds, performing a factory reset from within the system, wiping from CWM, dialing *#0011# to access service mode and deactivating power-saving mode. Nothing works.
HELP, please.
I'd be happy if the WiFi just worked, but knowing why the hell a stock rom should give any headache or what I'm doing wrong for it to go so wrong might be a step towards the solution.
PS: I'm writing this as I recall, so the details might not be completely spot-on, but the broader problems were those.

[Discussion/Q-A/Help] Tired of buggy Software/ROM, Need your help to Fix It.

So I bought a new Poco F1 few days ago. And since I've been using it, I've been facing bugs.
So when I got the device it had Miui 9.6.14 installed on it. And I just wanted to unlock it and root it asap. As you know you have to wait 3 days to unlock it. But as soon as I put in the unlock request i.e by going to fastboot and on mi unlock it shows 99% complete then it says you have to wait for this much time.
As soon as I did that, I faced the first bug. That was related mobile network settings/usb tethering/*#*#4636#*#* code (engineering mode IDK). So when I clicked on usb tethering, turned off mobile data/wifi, or the phone lost signal, it rebooted, from boot splash (not boot logo). Maybe this was the ROM's way of preventing any big bugs why do I think that? I'll explain later. So after rebooting I could turn on/off usb tethering but not mobile data or wifi. I can turn them off as soon as the phone boots but if I do it later i.e. after unlocking the phone, it rebooted.
So this is one of the bugs that has been consistent, the one that never got away. Well sometimes it did went away but not for long. Like sometimes if I haven't turned off the internet in a long time or restarted the phone properly, the data turning on/off doesn't reboots the device, IF the device isn't connected in usb tethering. Like few days ago I discovered that usb debugging could fixed it, but that didn't lasted long either. Sometimes turning off usb tethering then mobile data very quickly afterwards worked, but didn't lasted long or only sometimes it would work.
So the advice I got earlier was that, just flash a new software. While I didn't technically flashed the new software, I flashed the similar software, deleting all user data & everything, but that didn't helped. As it seemed in the beginning, that bugs weren't there but they started appearing later on. Now IDK if I used a locked un-rooted device, these bugs wouldn't appear, not too sure about that.
And you maybe saying, well you didn't flashed the newer version of the rom, then that's the problem, Well IMO it isn't. Here's why - So when I flashed the same rom, the phone got locked cause I forgot to select the "clean all" option in MI flash instead of "clean all and lock". So I unlocked it again, flashed twrp and as you may know that when booting twrp for the first time it asks you two options, "allow system modifications" & "read only". And the last time I flashed it I chose the read only option. But this time it didn't asked me. Now do you understand? As I'm not an expert in this, the guy who gave me this solution said maybe the device tree wasn't cleared. So how does flashing a new version is gonna make a difference if all of the files don't get deleted? If it's not gonna start fresh? I also used the command "fastboot erase recovery" (as suggested by that fella), that didn't helped either, just an FYI.
So I decided to install other roms, thinking maybe that could help. It seemed like working in the beginning but soon it started to fall down. First OS I installed, Pixel Experience, didn't had such bugs earlier, but there was a little one. If I disconnected the phone while it was in usb tethering mode, it would reboot the same way it did with miui. If you turned usb-teth off first, it didn't rebooted. So I thought I could live with that. But later more bugs started to appear. The same thing, turn off the internet and the phone restarts.
Remember when I first said maybe it was OS's way of not having bigger bugs, So that happened this time. New bugs like when I try to get into an app's info, the settings would crash (stopped working). BTW you could getting into an app's info if you are able to find the said app, by going into storage, then to apps. Moreover sometimes when I'd try to open the camera it would just show blank, or very dark image of the environment, not moving though, and sometimes, it would just work.
Then I installed Lineage OS. Didn't find such bugs, but I'm pretty sure if I do all this usb tethering stuff in there as well, I'm gonna find these bugs.
Now you might be thinking that how am I installing all these roms, well that's cause of MultiROM. And if anyone here is gonna say well that's the problem. STOP! Stop right there. These bugs were present there before I even used MultiROM.
Some other bugs I'm facing RN in Miui -
Auto Rotate not working. If I want to go landscape, I'd have to open an app/game that opens in landscape and switch from there, cause it gets stuck, vice versa for portrait. And you can only view it in default position i.e. you can't rotate to other landscape position if you wanted.
Camera not working, showing "can't connect to camera" error.
When I play offline games while these bugs occur. When I connect the headphones, the audio also comes out of the speakers. After I restart the phone properly, that stops. (This bug was also present in earlier stages when MultiROM wasn't used)
When going into second space, I created a txt file in mixplorer and when I try to open it, the system reboots. And I just checked by installing a root checker in second space, it says not rooted, wow!
When going to default file manager and tapping on storage, it said "disconnected" and few seconds later saying something like "couldn't add error 10000". This used to happen before but not now, neither I use the default file manager anymore. Though if I'm too quick and unlock the phone, open a file manager or any app that uses storage, it would go blank. Don't know if the storage crashes or something else. But after a restart, it's fine.
One thing, after the phone restarts when these bugs happen, "Find My Device stopped working" or something similar always appear, I don't remember the exact message.
[*]There are somethings Gcam related but I don't think they're 100% bugs related. Cause I installed the latest version on Lineage OS and it works as far as I used it even features like Night Sight and Slo Motion. Now those errors could be related to older android versions or something else IDK. Things like camera lagging in picture mode not in video mode and some version just straight up not working even when they're supported by older android 8.1.
Now could it be a hardware problem, IDK as I said I'm not an expert. These other bugs could've appeared cause of MultiROM or me flashing a new firmware over older rom version in order to install PE, again IDK.
Fair warning : If you're just gonna come here and say, Oh! this all cause of MultiROM or cause you didn't installed newer miui, then don't waste your time, cause I'm not gonna read any arrogant answers. Neither if you say, try to do this or that. I'm not here for that either. Cause if I wanted to do hit and trial, I could've done it myself
But if you understand the situation and can provide expert help, then only please reply. So if you're willing to help & understand properly, and you want anything from me, like logs etc. just tell me how to do it, I'll provide. Or if you know some way to do proper fresh install, only if that can fix the bugs so that I don't have to deal with them anymore, I'm looking forward to your reply.

Can't fix Bugged custom ROM

I have a Galaxy S III GT-I9300 I bought in 2014. After three years, I downloaded a custom ROM from xda-developers (android 4.3 is all I remember about it) and installed it successfully. It worked alright until one day when I wanted to sell the phone and a customer wanted to buy it on short notice, and I rushed to delete my files from the phone, but I destroyed the Android... I connected it to my laptop and shift-deleted some system files.... since then, the phone is delaying when trying to unlock (if i lock it now and try to unlock it a few times, it opens harder and harder), when I'm using apps it continously shows that some .com processess stopped working, and if I try to turn on the bluetooth, the phone instantly freezes and restarts itself.
I tried reinstalling two original ROMs, (version 4.1.2) successfully, but the data on the phone&the system problems remain the same.
I'd like to know how can I make a hard reset, meaning in deleting all the files&settings as it was brand new, just to clear everything, like clearing CMOS. I also think the recovery mode is damaged and I'd like to fix it somehow (if this is possible). The installation process I did for installing the custom ROM from XDA-devs was long and complicated, I had to do a lot of things... and I just want to get the phone fixed and restore to default (or even to fix bugs on this android version) its android, kernel & everything could be ,,reflashed''.
I'm willing to pay if someone helps me fix the problems and it really works. Thank you!

Can't fix Bugged custom ROM

I have a Galaxy S III GT-I9300 I bought in 2014. After three years, I downloaded a custom ROM from xda-developers (android 4.3 is all I remember about it) and installed it successfully. It worked alright until one day when I wanted to sell the phone and a customer wanted to buy it on short notice, and I rushed to delete my files from the phone, but I destroyed the Android... I connected it to my laptop and shift-deleted some system files.... since then, the phone is delaying when trying to unlock (if i lock it now and try to unlock it a few times, it opens harder and harder), when I'm using apps it continously shows that some .com processess stopped working, and if I try to turn on the bluetooth, the phone instantly freezes and restarts itself.
I tried reinstalling two original ROMs, (version 4.1.2) successfully, but the data on the phone&the system problems remain the same.
I'd like to know how can I make a hard reset, meaning in deleting all the files&settings as it was brand new, just to clear everything, like clearing CMOS. I also think the recovery mode is damaged and I'd like to fix it somehow (if this is possible). The installation process I did for installing the custom ROM from XDA-devs was long and complicated, I had to do a lot of things... and I just want to get the phone fixed and restore to default (or even to fix bugs on this android version) its android, kernel & everything could be ,,reflashed''.
I'm willing to pay if someone helps me fix the problems and it really works. Thank you!

Categories

Resources