I really really do hate asking for help and 99.63757% of the time I can fix things myself doing the necessary research into the problem(s) and potential solutions, but so far this one has me stumped and I'm too frustrated with it to just keep starting over so I'm asking for assistance from anyone that might be able to help, so here goes...
OK, so I picked up two H931 V30's the other day for $100 (for both, actually), one is slightly damaged (glass damage just under the Menu/Recents button area) but it's 100% functional, the second one is pristine. I did the conversion to the US998 without any issues on the undamaged one since the damaged one is for my Wife and she has no need for root/custom ROMs/massive amounts of tinkering like I've been doing for 20+ years or so. Unlocked the bootloader without issues too.
So, I get everything done according to the WTF guide (very nicely done piece of work, seriously) and it's up and running without issues. But then I decide to check and see if Magisk has an update so, I scroll over, find the Magisk icon, tap it, and I get that damned message I always get about updating to the latest version, either choose "NO THANKS" or "YES" and that's when the problems start. This is Magisk 18.0 by the way, and I've attempted this with 18.1 as well, and even the latest 19.1 and it still happens like this regardless:
The phone then suddenly turns into molasses in winter as far as operational speed goes. It chokes, then it dies, then the Home screen resets exceedingly slowly as if it suddenly went from the powerhouse phone it is to 1 frame per second or something in functionality.
The phone heats up like crazy, then I eventually am forced to hold Volume Down + Power and force it to reboot, and it does reboot and gets right back into the OS like nothing happened and everything works as normal.
But I cannot get Magisk to do anything at all, the app itself apparently never loads, doesn't function, I can't update it or get it to run in any way at all. Everything else works, including apps requesting root which is given by Magisk as it should. I know that with the unlocked bootloader Netflix won't install by default, and I know Magisk is installed and functional because Netflix shows up in the Play Store and I was able to install it and watch a video and the Magisk Manager icon is clearly right there on my device.
I've done this like 7 times now and I'm not going to do it again for the moment, I'm gonna end up corrupting something from all the flashing I think and then doing it again, then again, etc.
On my V20 I had this issue in the past (not recently) where when I attempted to execute the Magisk Manager app it constantly asked me that question when it starts up and regardless of "NO THANKS" or "YES" or even if it's updated to the latest version it always asks me that damned question and I've never been able to get it to stop. But with the V20 the app does load and I'm able to access features of the Magisk Manager.
On this V30, I can't do anything at all and I always have to reboot the phone hard and I'm kinda sick of doing that. So I started over again an hour ago, everything is working fine for the 8th time except probably Magisk. I haven't touched the icon but it's installed, root is working fine, but I really do want to understand WHY this crap keeps happening and WHY I can't get Magisk Manager to run properly without crapping out the phone.
If anyone can help or offer some suggestions I'm all eyes (given this is a text-based communication medium, obviously).
Thanks, and have fun, always...
bb
Haha I love that you got the mint one and gave your wife the dinky cracked one.
Well the damage is inconsequential, and she's been using a Stylo 2 Plus that has glass damage in almost exactly the same place, go figure. I'm tougher on devices than she'll ever be but I do the tinkering around with stuff, not her.
br0adband said:
I really really do hate asking for help and 99.63757% of the time I can fix things myself doing the necessary research into the problem(s) and potential solutions, but so far this one has me stumped and I'm too frustrated with it to just keep starting over so I'm asking for assistance from anyone that might be able to help, so here goes...
OK, so I picked up two H931 V30's the other day for $100 (for both, actually), one is slightly damaged (glass damage just under the Menu/Recents button area) but it's 100% functional, the second one is pristine. I did the conversion to the US998 without any issues on the undamaged one since the damaged one is for my Wife and she has no need for root/custom ROMs/massive amounts of tinkering like I've been doing for 20+ years or so. Unlocked the bootloader without issues too.
So, I get everything done according to the WTF guide (very nicely done piece of work, seriously) and it's up and running without issues. But then I decide to check and see if Magisk has an update so, I scroll over, find the Magisk icon, tap it, and I get that damned message I always get about updating to the latest version, either choose "NO THANKS" or "YES" and that's when the problems start. This is Magisk 18.0 by the way, and I've attempted this with 18.1 as well, and even the latest 19.1 and it still happens like this regardless:
The phone then suddenly turns into molasses in winter as far as operational speed goes. It chokes, then it dies, then the Home screen resets exceedingly slowly as if it suddenly went from the powerhouse phone it is to 1 frame per second or something in functionality.
The phone heats up like crazy, then I eventually am forced to hold Volume Down + Power and force it to reboot, and it does reboot and gets right back into the OS like nothing happened and everything works as normal.
But I cannot get Magisk to do anything at all, the app itself apparently never loads, doesn't function, I can't update it or get it to run in any way at all. Everything else works, including apps requesting root which is given by Magisk as it should. I know that with the unlocked bootloader Netflix won't install by default, and I know Magisk is installed and functional because Netflix shows up in the Play Store and I was able to install it and watch a video and the Magisk Manager icon is clearly right there on my device.
I've done this like 7 times now and I'm not going to do it again for the moment, I'm gonna end up corrupting something from all the flashing I think and then doing it again, then again, etc.
On my V20 I had this issue in the past (not recently) where when I attempted to execute the Magisk Manager app it constantly asked me that question when it starts up and regardless of "NO THANKS" or "YES" or even if it's updated to the latest version it always asks me that damned question and I've never been able to get it to stop. But with the V20 the app does load and I'm able to access features of the Magisk Manager.
On this V30, I can't do anything at all and I always have to reboot the phone hard and I'm kinda sick of doing that. So I started over again an hour ago, everything is working fine for the 8th time except probably Magisk. I haven't touched the icon but it's installed, root is working fine, but I really do want to understand WHY this crap keeps happening and WHY I can't get Magisk Manager to run properly without crapping out the phone.
If anyone can help or offer some suggestions I'm all eyes (given this is a text-based communication medium, obviously).
Thanks, and have fun, always...
bb
Click to expand...
Click to collapse
Are you thinking the problem is with Magisk manager or with Magisk itself?
Sent from my LG-US998 using Tapatalk
br0adband said:
So, I get everything done according to the WTF guide (very nicely done piece of work, seriously) and it's up and running without issues.
Click to expand...
Click to collapse
You're welcome.
br0adband said:
But then I decide to check and see if Magisk has an update so, I scroll over, find the Magisk icon, tap it, and I get that damned message I always get about updating to the latest version, either choose "NO THANKS" or "YES" and that's when the problems start. This is Magisk 18.0 by the way, and I've attempted this with 18.1 as well, and even the latest 19.1 and it still happens like this regardless:
Click to expand...
Click to collapse
When we first started rooting the V30 (first with the official LG bootloader unlock codes for the few that were eligible) over a year ago, we had Magisk 16.0, 16.1, then Magisk 17.1. (I think 17.0 was just very unstable if I remember correctly.) As each became more stable we upgraded to newer versions, but some in between were never used. For the longest time, I delayed recommending 18.0 until it was proven.
18.0 upgraded to 18.1 easily, but Magisk Manager keeps nagging me to update to newer version. Clicking on Magisk Manager keeps prompting me to install newer version (for 19.x) but it never successfully installs. I know I will have to flash the uninstaller in TWRP and then download 19.1 and reinstall in TWRP. I hesitate doing that because it was a major pain last time to re-choose all the apps I want root or want to hide.
One time while doing it it I ended up with TWO Magisk Manager apps in my App drawer. I had to uninstall Magisk again (in TWRP) and reinstall yet again.
All that to say this.... Have you tried flashing uninstaller for Magisk in TWRP, then reinstalling 18.1 or 19.1 or whichever one you want?
Here's the uninstaller...
https://github.com/topjohnwu/Magisk/releases/tag/v19.1
I'll give that a shot I suppose, can't really hurt much if it fails - and yes I'll do a TWRP backup first.
It's just odd because the root aspects are OK as stated, everything gets root that requires it (I only have a few apps like the root add-on for fx File Explorer, LTE Discovery to get some additional data, Titanium Backup which I don't even really use that much but paid for years ago, etc). I reached a point in the past where I was like "What do I really need to do all this crap for anymore, stock ROMs are actually quite nice and stable, that's more important over the long run that tinkering constantly..."
Been tinkering on consumer electronics since the 1970s when I was a wee tiny kid, just getting sick of it nowadays and want the devices to just work well. Sure I can eek out a bit more in terms of performance if I put in hours of tweaking and configuration but honestly, it works just fine as it is on the stock ROM and I'm OK with that so far.
I'll see about uninstalling Magisk and installing 18.1, see what happens when I do actually attempt to run the Manager and then if that fails uninstall it and give 19.1 a shot and report back.
EDIT:
OK, for whatever reason when I uninstalled 18 and then flashed 18.1 I got no dice, no idea why so I then rebooted to recovery again, removed 18.1, then flashed 19.1, got back into the OS, installed the latest Manager again and poof, voila, now it works.
Bleh, I tell ya, sometimes... 3rd time's the charm, or the 4th, or the 10th, or something.
Thanks for the responses, this one is now done.
FWIW, I upgraded 18.1 to 19.1 on my phone (VS996) a while ago and it's been working fine... just to provide a datapoint. Aside, this also allowed GPay to work properly as well.
Related
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
The last link you put up is a theme, not a Rom. Which ROM are you currently using?
Be sure when changing roms to wipe data and cache. Not doing so will cause a boot loop, which you described above. Also, if you have to reactivate your phone and can't get a dial pad, long press the menu button to bring up the keyboard and use the keyboard numbers.
Sent from my ultra fast Liberated Droid 2
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
I don't know what all roms you have tried that won't boot but there was one person who's phones could not boot my cfsv6 through cfsv8 kernels. I fixed the issue in cfsv9 kernel so check to see if the roms you have tried are using those kernels. I know the one you said booted was an older rom and was not using my kernel. CELBFroyo is using the v9 kernel if you want to test that. If that is your issue you can just download the cfsv9 kernel and flash it after flashing the rom of your choice. It was something to do with the hardware in a small percentage of eris's that the kernel would not work with. Maybe you have the same hardware as that case...
I've had the SGP 4.2 since August (North American version) and have become very fond of it. Although I've followed most of the dev areas, I have never rooted or installed any recovery, custom roms, etc...so it's on the stock Android 2.3.6 with 2.6.35.7 kernel and build number GINGERBREAD.UELD3. I have only installed things from the play store and amazon app store.
Sometime in the past week it has started shutting down randomly. Most times I notice when picking it up after hours of standby and it's fully off and need to boot up. A few times it has happened while in use - it just turns off. The battery level doesn't seem to matter, it can happen at 99%, 5%, and anywhere between.
Is there any way to tell if this is a hardware problem vs a software problem? Any other thoughts? I've not seen this problem in other threads, or at least not when running everything stock.
maybe a hardware issue.
see if samsung will fix/replace it
imgthat said:
I've had the SGP 4.2 since August (North American version) and have become very fond of it. Although I've followed most of the dev areas, I have never rooted or installed any recovery, custom roms, etc...so it's on the stock Android 2.3.6 with 2.6.35.7 kernel and build number GINGERBREAD.UELD3. I have only installed things from the play store and amazon app store.
Sometime in the past week it has started shutting down randomly. Most times I notice when picking it up after hours of standby and it's fully off and need to boot up. A few times it has happened while in use - it just turns off. The battery level doesn't seem to matter, it can happen at 99%, 5%, and anywhere between.
Is there any way to tell if this is a hardware problem vs a software problem? Any other thoughts? I've not seen this problem in other threads, or at least not when running everything stock.
Click to expand...
Click to collapse
that was happening to me too. i just bought mine from best buy about 1.5 months ago. everything was fine, mine also wasnt ever rooted or flashed anything - just oem with playstore apps. then every now and then after about a month of having it, it would turn off and on by itself (only if it was idle though, without me touching it) its never happend to me while i was messin around with it. and then it started freezin up on me and gettin really laggy at times with certain programs but it was random and i couldnt reproduce it to try and pinpoint the program that was causing it. but then i read up on rooting it and the benefits of root and cwm and backingup everything and roms and since then, everythings perfect. better than new as a matter of fact. so in my opinion, you owe it to yourself to root your device so you can make changes to your lil buddy. i made sure i learned all about rooting and flashing and backups etc first though so i can do it safely. i mean, cmon i dont know about you but i paid alot of money for mine which is why i owed it to myself to 'safely' release the full potential of my device. :cyclops:
Totally agree that I want to start to release the full potential, thats' whay I've been poking aorund here for months (and tinering with my Acer tablet is getting old). My hesitation to start down that path is if there's a hardware issue I don't want to compound the inevitable probelms and end up with an out of warranty bricked device
Maybe I'll see what Samsung says. Like the previous poster - i can't directly replicate the issue so perhaps they won't replace, I'll see and update this post accordingly.
imgthat said:
Totally agree that I want to start to release the full potential, thats' whay I've been poking aorund here for months (and tinering with my Acer tablet is getting old). My hesitation to start down that path is if there's a hardware issue I don't want to compound the inevitable probelms and end up with an out of warranty bricked device
Maybe I'll see what Samsung says. Like the previous poster - i can't directly replicate the issue so perhaps they won't replace, I'll see and update this post accordingly.
Click to expand...
Click to collapse
well one of the good things bout this forum is that it explains how to un-brick our devices if it happens. it was kind of intimidating at first for me too as this is the first android ive ever rooted and flashed diff roms. but as long as you make backups thru titanium and also a nand backup thru cwm and then use roms and kernals specifically made for your device that have been tried and tested and retried....then you really have nothing to worry about. and i also read somewhere that if you flash it yourself and somehow manage to brick your device, you can flash everything back to stock so your warranty wont be voided anymore - i could be wrong but im almost positive ive read that somewhere.
UPDATE: SOLVED
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
XDA mark said:
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
Click to expand...
Click to collapse
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
tallman43 said:
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
Click to expand...
Click to collapse
I can enter download mode normally, so I can use Odin to flash stuff.
I just flashed that kernel I wanted to flash before my phone went trippin, but after flash the same continues. Re-downloading ARHD 40 via my laptop now and going to reflash it via odin, hope that my phone can then let go of it's obsession of trying to get into recovery.
There must be a way to fix this, I didn't make a Titanium Backup for a while. Don't want to lose stuff just because I got some super rare weird problem... again. Why does tech hate me
EDIT:
Realized that I can't flash ARHD 40 because it only comes in zip not tar... anyway, tried flashing the newest version of philz touch recovery, still didn't change anything.
EDIT 2:
Flashed TWRP recovery via ODIN, now everything is fine again. It rebooted into TWRP normally, then choose to reboot the device. Everything is still there, like nothing ever happened.
THANK you lord!
Out of interest, how do you find the HTC 1 compared to the S3?
gsw5700 said:
Out of interest, how do you find the HTC 1 compared to the S3?
Click to expand...
Click to collapse
It's an entirely different phone, especially how it feels and looks. After using the One for such a long time, I find it super weird to hold a S3.. it feels so light and "cheap", though ergonomically the S3 is a tad easier to hold then the One. Overall I enjoy using the HTC One much more as it feels really solid.
Besides that it's fast and stable, what you would expect, but not much faster then a S3 with a good ROM. Screen is really excellent, this is also a big difference from the S3. It's a different type of screen and you can really notice. The speakers are the nicest you can get on a phone and compared to the S3 they are really a league above. The camera is average, sometimes it's great sometimes it isn't. Battery life is comparable to the S3.
Not that I didn't enjoy my S2 and S3 at the time, but I'm not really interested in the Galaxy line anymore at the moment. Samsung really has to do something amazing to get my attention again Will see what HTC brings with the successor of the HTC One, might upgrade to that one. I'm also curious about the iPhone 6 to be honest, the small screen is the main reason I haven't owned an iPhone in my life, if that changes I might want to try it. Or I might just use my current device for a second year for a change, since it's excellent
Many thanks for that, I now intend to take a look at the new HTC m8 - hoping the camera is better!
Me too. If they make a big leap with the camera and bring it on par with the iPhone 5S for example, it would be fantastic. Battery life should also be brought to the new higher standards of the LG G2.
If these 2 things happen they already got me, since it's a near perfect phone. Add some bonuses like making the bezels smaller/screen larger in the same body... don't think I could resist
Issues after rooting Alcatel 5065N
Went into as much detail as I possibly could
n00b made a b00b00
After I discovered Androids had the ability to access everything in the operating system by adding a standard Linux function, rooting it, it undoubtedly peaked my interest. As I went through various Androids, I'd read up on ways to customize the phones via rooting or other methods.. but was always hesitant on actually rooting the device and risk having to tell my mom I broke my phone, ha.
Now, (somewhat of) an adult, I decided to finally root an Alcatel Tru 5065n, *silent woo.* Eager and full of impatience, I did some research and ended up using KingoRoot, supposedly the only functioning way to root my specific device, and rooted it through my PC. After playing with my phone for a while, I noticed a few issues with it's performance.. Whicchhhhh led me to panic over the likelihood of causing severe damage to my device. To Google!
I decided I wanted to un-root the system entirely. First un-rooted it within KingoRoot itself, still laggy, KingoRoot was still present in device although all the apps were gone, but root permission was no longer available. I wanted to rid my phone of KingoRoot completely, but couldn't find a way to do so without using another root service name "SuperSu." Which required, of course, re-rooting and installing KingoRoot and it's apps. My phone turned off during root, and took way longer than usual to reboot but KingoRoot said it had completed rooting while the device was mid-boot. Once the phone turned on, it had the apps re-installed and root was back in action. Now to rid my poor Alcatel of all things root.
Luckily, I managed to find @evildog1's thread "Replace KingoRoot with SuperSU manually without Terminal." I followed the instructions word for word, educated myself on whatever I didn't know, and successfully had a working SuperSu. I thought maybe, "Hey, this could make my phone run smoothly and I can just keep it rooted " Still lagging and freezing here and there, I refrained from using SuperSu's Full Unroot option.
As the days pass, an abundance of cuss words have been added to my vocabulary more and more & I find myself restarting the device more than actually using it. Apps would freeze. The keyboard crashes, pops-up for a split second to type A BLOODY WORD and the refuses to resurface unless restarted. Everything lags, but sometimes if I'm lucky an app won't glitch out and send me to the Open Apps Tab, which allows me to close all open tabs but then stays showing me the little broom. SMS notifications vanish into thin air. My home screen won't show any apps and then the device just literally will not do a damn thing but force restart. Oh, and then it takes FORFFRIGGINEVER to turn back on because "Android is Optimizing Apps." Since it was doing nothing tempt me to throw my phone into my pool, I tried using SuperSu's fancy Full Unroot every raves about.
It stayed at "Uninstalling, please wait ..." for over an hour. I gave up at that point and just switched to my iPod since I don't go out much and it's just been sitting on my counter for days.
Now, when it's on, it restarts on it's own, but gets stuck on the MetroPCS screen until the batteries die unless I take the batteries out myself and turn on the phone for it to only stay on for an hour or two until it decides to continue taunting me. I am now the un-proud owner of a paperweight.
Please help. All I want is to un-root my phone and restore my phone to it's original state before I ruined everything.
The best way to go back to original state is re-flash firmware (which will wipe your user data).
If you don't have firmware, contact your manufacturer and tell them about your issues (Don't mention "root")
Contact page: http://www.alcatel-mobile.com/global-en/company/contactus
I'm afraid it will cost you money, I hope it's free
I had this similar problem on my tablet after using Kingroot for 3 months and switching to Kingoroot caused even more issues. Instead factory reset, I contacted my manufacturer if they wanted to send me firmware. They gave me instruction and files to flash. I did flash, then root with Kingoroot and switch to SuperSU. My tablet still working perfectly with no issues so far.
Hi guys.
I'm quite new here so forgive me if I put the post in the wrong place.
Let me try to describe my issues with my phone.
A couple months ago I got a new LG V60 from my wife (brand new but without warranty).
The first problem I noticed after a few days was that the fingerprint scanner wasn't working properly. I mean everyone can unlock my phone after a few tries placing finger on the scanner at an angle.
When I try to unlock the phone by fingerprint it takes ages (it's very difficult to unlock the phone for the first time). I was trying remove saved fingerprint and create a new one but the problems is still there.
Another problem is with losing signal from satellites when using navigation. I was trying Google maps, Sygic and TomTom and it's look like the Google works best but there is still problem with signal, quite often I get information about 'searching position'.
Next one is that the phone is freeze sometimes and I have to restart it to work properly. It's happening around once a week.
I was trying hard reset but it didn't fix it, then I downloaded the original firmware with android 10. I don't know if it helped because I got lots of updates and it ended up on the Android 12 again. At the beginning of use after this operation the phone was working better but after a couple of weeks the same problems came back.
I'd like to add if I want to do a back up I get information like this "the required google certificate has been deleted". On Android 10 this information wasn't appearing.
Do you have guys any idea what's wrong with this phone?
Thank you in advance.
emillo83 said:
Hi guys.
I'm quite new here so forgive me if I put the post in the wrong place.
Let me try to describe my issues with my phone.
A couple months ago I got a new LG V60 from my wife (brand new but without warranty).
The first problem I noticed after a few days was that the fingerprint scanner wasn't working properly. I mean everyone can unlock my phone after a few tries placing finger on the scanner at an angle.
When I try to unlock the phone by fingerprint it takes ages (it's very difficult to unlock the phone for the first time). I was trying remove saved fingerprint and create a new one but the problems is still there.
Another problem is with losing signal from satellites when using navigation. I was trying Google maps, Sygic and TomTom and it's look like the Google works best but there is still problem with signal, quite often I get information about 'searching position'.
Next one is that the phone is freeze sometimes and I have to restart it to work properly. It's happening around once a week.
I was trying hard reset but it didn't fix it, then I downloaded the original firmware with android 10. I don't know if it helped because I got lots of updates and it ended up on the Android 12 again. At the beginning of use after this operation the phone was working better but after a couple of weeks the same problems came back.
I'd like to add if I want to do a back up I get information like this "the required google certificate has been deleted". On Android 10 this information wasn't appearing.
Do you have guys any idea what's wrong with this phone?
Thank you in advance.
Click to expand...
Click to collapse
I also have the v600TM on Android 10. I have had no problems with the fingerprint except after the first time I unlocked the bootloader (see 1st post for the fix). I did not allow an update to Android 11 or 12. Maybe you should try the fingerprint on A10 for awhile before moving to 12.
Hopefully you don't have one of those Chinese refurbs pretending to be new!
AnnexedOne said:
I also have the v600TM on Android 10. I have had no problems with the fingerprint except after the first time I unlocked the bootloader (see 1st post for the fix). I did not allow an update to Android 11 or 12. Maybe you should try the fingerprint on A10 for awhile before moving to 12.
Hopefully you don't have one of those Chinese refurbs pretending to be new!
Click to expand...
Click to collapse
Hi
Thank you for the reply.
Maybe you right and I should try to use the phone on android 10 and see if it's works properly. I'll see what happens.
Do you know when android 13 will be available for V60?
As a owner of the V30, V40 I'm really disappointed of the V60 now.
emillo83 said:
Hi
Thank you for the reply.
Maybe you right and I should try to use the phone on android 10 and see if it's works properly. I'll see what happens.
Do you know when android 13 will be available for V60?
As a owner of the V30, V40 I'm really disappointed of the V60 now.
Click to expand...
Click to collapse
Hi,
You're welcome. When you are new to a forum or group, its like you are invisible.
My current main phone is the V30. The V60 has been more difficult than past phones to configure the way I want. When I installed TWRP a few months ago it was a DISASTER! Installing MicroG (to replace google play services) has also not worked out well. I have limited funds and I am beginning to wonder if the V60 was a good choice.
There is already an Android 13 beta for some versions of the V60.
The thing with V60 is that it is newer than V30. So a lot of fixes are not fully cooked. With LG gone from the scene, there is no incentive for developers to pursue it with any dedication. I don't know if TWRP will be fully built for this phone.
Audio_Lover said:
The thing with V60 is that it is newer than V30. So a lot of fixes are not fully cooked.
Click to expand...
Click to collapse
I do remember how slow the V30 was in the beginning. Now the V30 has a bunch of ROMs and an OFFICIAL LineageOS! I hope the V60 goes the same way. I doubt it, though.
Audio_Lover said:
I don't know if TWRP will be fully built for this phone.
Click to expand...
Click to collapse
I forgot to mention that I posted a possibly newer (than 3.6.0-11) version of TWRP for the V60:
TWRP 3.6.0-11
Here a updated recovery. All credit goes to @UnlockLG https://drive.google.com/file/d/1P-wc8aJ6zVDC1xiKfdTKfzGoh2kQHIPp/view?usp=sharing
forum.xda-developers.com
Hi guys
It's me again with another problem
As for the above problems that I wrote about, I decided not to do anything about it for now and patiently wait for the android 13 update and see what happens.
How happy I was when two days ago I received the opportunity to download the update.
The joy did not last long, as it turned out that I'm unable to download the update.
Previously, I got information like 'The phone is being use and update will be downloaded later' (or something similar). Now the update downloads for a while and pops up 'Installation problem' and cannot be downloaded (always in the same time). I restarted the phone, deleted apps, changed from WiFi to mobile data and still the same.
Do you have guys any ideas what can I do with it?
As far as I know the phone is from US (T-mobile) and I live in the UK.
Thank you in advance for your help
emillo83 said:
Hi guys
It's me again with another problem
As for the above problems that I wrote about, I decided not to do anything about it for now and patiently wait for the android 13 update and see what happens.
How happy I was when two days ago I received the opportunity to download the update.
The joy did not last long, as it turned out that I'm unable to download the update.
Previously, I got information like 'The phone is being use and update will be downloaded later' (or something similar). Now the update downloads for a while and pops up 'Installation problem' and cannot be downloaded (always in the same time). I restarted the phone, deleted apps, changed from WiFi to mobile data and still the same.
Do you have guys any ideas what can I do with it?
As far as I know the phone is from US (T-mobile) and I live in the UK.
Thank you in advance for your help
Click to expand...
Click to collapse
If you unlocked the bootloader, I hear that updates don't work.
AnnexedOne said:
If you unlocked the bootloader, I here that updates don't work.
Click to expand...
Click to collapse
Thank you for the reply.
How to check if the bootloader is unlocked?
As I said before I haven't done anything yet with the phone as I was waiting for the update but I'd like to check it, maybe the bootloader was already unlocked
emillo83 said:
How to check if the bootloader is unlocked?
Click to expand...
Click to collapse
When the phone is starting up (after being off or rebooting) it will say something like: This phone cannot be checked for corruption. Lock the bootloader.
If the bootloader is locked I suggest you backup before doing a factory reset.