Root from the pit of hell, desperately need help. - Android Q&A, Help & Troubleshooting

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.

Related

[Q] Why no GSM detected on Vibrant?

This is the deal:
I bought my wife and I Vibrants back in February and from the minute I got it I started looking into updating from eclair.
I was following the info on xda after researching about rooting phones, so I rooted my phone using the Superonclick method. Just before getting ready to flash custom roms, I read that froyo was available through kies. So I did that. It worked well enough for me, so I updated my wife's phone as well and hers works beautifully. I also changed the home launcher to LauncherPro. love it.
Mine however has been going on the fritz. I'm in the middle of using an app or I'm doing nothing at but turning on my phone and the screen will be all black with nothing but the notification bar showing.
The media scanner is constantly running.
No gsm is detected.
I keeps vibrating after touching the screen.
No amount of turning it on and off gets it past that state.
It just randomly decided to start working on its own.
Any Ideas?
Should I unRoot my phone. I don't want to,
I'm still researching changing the bootanimation, (waiting for a Portal 2 theme, also researching how to do it myself).
SOS guys.
sorry if tldr.
I would suggest restoring your phone back to stock Via Odin, and starting fresh. The problem you most likely had is that you updated to Froyo through Kie's while your phone was rooted.
Or, at the very least do a factory reset on your phone.
But if you need to go the Odin route, just search the forum, can't miss it.
oh wow, I didn't know that was an issue updating while rooted. I must have missed something while reading (so many threads -_-).
Guess I have some more light reading to do...
thanks.
Did a little research, should I unroot my phone first before factory reset? or is there a method that will take care of removing the root?

[Q] [N00b alert] Phone says unrooted when it /is/ rooted

First off, I'd like to say my S2 is the Virgin Mobile version (model i9210) so I'm not sure if it's okay for me to post this in this forum or not. Feel free to move it where it should be, I won't be offended.
Edit: Originally had posted this in the Samsung Galaxy S2 forum, but it was nicely moved to this forum in hopes that it would be seen more~ So to clarify, my phone is the Virgin Mobile Samsung Galaxy S2, running Android 4.1.2, model number SPH-D710.
The ROM I have is BiftorROM-V8-JB-XWLSN-NoWipe.
Onward. This is my first Samsung phone AND my first Galaxy, and when I decided to root my phone, I had no idea how much different it would be from my past phones. How I didn't completely brick this phone, is nothing short of a miracle. I had trouble with some ROMs so someone eventually linked me to a Sprint stock ROM, saying it was compatible with my phone.
Since then I've been using that ROM, despite having a Virgin Mobile phone, with no problem. Recently I noticed an app I use (SD Maid) was listing my phone as unrooted. It was weird but I ignored it, because the app still worked. Even later, I noticed other apps that require root access were not working correctly, so I decided to download a root checker.
Status: Unrooted
Well, then. I'm not sure how this happened, or what's going on, but I figured again, it was no big deal because my ROM was running perfectly and I had no desire to change my ROM or anything else soon. Last night my phone started acting completely different. Lagging like crazy, and when I tried to unlock my phone, it would take a good 15 seconds just for the screen to turn on and my lock screen to start functioning normally. Then another 20 seconds or so for the screen to register my touch and actually unlock my phone. I tried disabling all lockers, but my screen would just turn black and I would still have to wait.
A friend suggested that I simply go through the process of rooting as though my phone really were unrooted and just hope that fixes it, but I'm not sure if that would be a good idea. If my phone wasn't operating so slowly this wouldn't be as big of a problem, but it is, and I'm pretty afraid that I'll mess my phone up somehow.
I once found a forum with the topic the same as mine but I haven't been able to find it since, so I'm hoping someone here could point me in the right direction. Do I go through the root process, maybe try just reflashing my current ROM? I've also thought about just doing a system restore on my phone and see if that helps. Thanks in advance.

[Q] VM ZTE REEF N810 splash logo then blank screen/can run android recovery mod

Hello there. I am sort of a noob at rooting phones, this zte reef was my third successful root(or so I thought) of prepaid virgin mobile cheapies. I mainly root to remove and replace the obnoxious VM boot animation on startup--anyone who has owned one of these knows it can wake the dead, and will likely be the root cause of the zombie apocolypse sometime in the near future. I also remove a bit of google bloatware that, as far as I can determine, nobody on the planet actually uses--none of the fancy custom roms and whatnot, and replace the launcher with my beloved Nova.
Anyhow, being a silly noob, and having no prior issues with my previous devices, I did not save any sort of backup this time around, did not install CWM, and carried on as usual. Phone worked fine for several weeks. Then last night I fell asleep with it in my pocket. Battery died overnight as it tend to do in these situations. I awoke, plugged it in, charging screen pops up as usual. Hour later I try to turn it on and after being greeted by the android splash logo......blank screen.
Rebooted. Same result. Rebooted in android system recovery, wiped some things, reboot. Same result. Hard reset, still nothing.
Cannot find ANY rom compatible with this device, much less the stock one. ZTE of course will not provide me with any help. ZTE Reef N810 Virgin Mobile
So here is my question--does anyone have the stock rom for this device? Or is there any other way I could perhaps build a update.zip with the core apps that the system would allow to be installed from recovery mode(I suspect the launcher replacement may have destabilized the system, although why it waited this long to collapse is beyond me).
Throw anything you think of out there, I will try anything and have plenty of time to toy with it. Have to go to the library for computer access, but have access to another VM phone(unfortunately running 4.4 dangit)
Also am able to boot it into Field Test Mode, not sure if that could be used to communicate with the device in some way? Trying to cover all possibilities.
Thank you for reading, and btw xda your forums are, in a word, awesome. Well played!
ZTE REEF
Found anything yet?

Lags, Freezes and Force Closes after Device Factory Reset

Ok so I've never attempted to root my Note8 or modify it in any way. It's paid off and was going to sell it since I have a nother one via the BOGO deal with T-Mobile. I did a factory reset to prep the phone for the new onwer. I left it on the setup screen without ever going further. Today the buyer backed out so I decided to give it to my sister. Shes had the phone for only a few hours and hasn't even downloaded an app yet and the phone is acting very odd. It freezes often and backs out of any open app. Apps freeze while using them then force close. Stock apps. Facebook being the worst and it's a system app so I can't so much about it without root.
It lags, skips, freezes and has gotten pretty hot.
I did not modifying at all. No firmware reflash or anything. Just a simple factory reset due to just selling the phone. It had no prior issues before the fact.
Any help would be greatly appreciated. It's a fairly new phone and all I see is battery problems that I have yet to experience on either one of my Note8s.
Jacob3o5 said:
Ok so I've never attempted to root my Note8 or modify it in any way. It's paid off and was going to sell it since I have a nother one via the BOGO deal with T-Mobile. I did a factory reset to prep the phone for the new onwer. I left it on the setup screen without ever going further. Today the buyer backed out so I decided to give it to my sister. Shes had the phone for only a few hours and hasn't even downloaded an app yet and the phone is acting very odd. It freezes often and backs out of any open app. Apps freeze while using them then force close. Stock apps. Facebook being the worst and it's a system app so I can't so much about it without root.
It lags, skips, freezes and has gotten pretty hot.
I did not modifying at all. No firmware reflash or anything. Just a simple factory reset due to just selling the phone. It had no prior issues before the fact.
Any help would be greatly appreciated. It's a fairly new phone and all I see is battery problems that I have yet to experience on either one of my Note8s.
Click to expand...
Click to collapse
Do not another factory reset. If that does not help try reimage it.
Just root? Or custom ROM as well? Maybe go back to Stock Unrooted.

[Q] Issues with Magisk after the US998 conversion (ISSUE RESOLVED, THX)

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.

Categories

Resources