I've rooted phones before with no issue. I've had to get a new phone recently.
Phone is an Alcatel Pixi Theatre. Root worked on first try with KingRoot. I go to start to download files to do a custom recovery and my phone randomly restarts and root is gone. This has happened on 2 phones now. I go to KingRoot and root again and it works but I know it will be gone when phone reset.
I know it has something to do with Knox or Bootloader. I've tried getting rid of the bootloader but I cannot get the phone into download mode. The buttons are weird and power up puts me into install, wipe, etc and power down starts the phone.
Phone needs to be rooted to set up custom recovery. Yet, every time I go to set it up I lose my root. Am I missing some steps or something? I'm about to lose my mind. Just trying to get Xposed on my phone. I can't even get SuperSU to show me my apps. Keeps saying binary occupied. Does that need to be downloaded before I root?
Thanks
Can anybody help? thanks
Does the same for me I read that I should use supersume and its supposed to change it from kinguser to superuser but I couldn't get it to work
Related
long story short. I tried to flash a newer updated copy of SuperSU or whatever to get root back after updating to 4.0.4 earlier this week.
Once I did that I was able to get back into the operating system and run Root Checker. Everything passed. I then tried WiFi tether and it kind of locked up on me for a bit. then I was able to stop it and exit out of it. I Force closed the programs. Life was good.
For whatever reason I restarted the tablet. once I did that I was stuck on the Samsung screen for at least 15 minutes.
I then tried to re-run root file and then the new updated SuperSU. Then everything went all to hell.
Then I get a message that says
"Firmware upgrade encountered an issue. Please select recovery mode from Kies & try again."
Now I can not boot into anything but recovery...
I am able to with that message on the screen, connect to Odin and proceed to run the "factory" restore. However it has been sitting at what I would assume is about 5% or so for a long time. at least 20-30 minutes. Should this take this long?
And is there anything else I can do to do a restore? I am fairly new to this tablet and I use it for work and of course I have a super full day of work tomorrow and really got to get this thing back up and going.
So I rooted my phone using king root and everything was working fine up until I tried to switch from kingroot to super su using super sume. After that my phone just reset and at first was endlessly restarting, after shutting it off and back on I was able to get it to stop endlessly booting but ran into a different issue. The phone boots up and reaches the "android is starting... Starting apps." Screen and doesn't go anywhere past that. I went into recovery mode and preformed a data wipe to see if that would work and the problem still persists. I am in fact running on stock no clockwork recovery or anything of that nature. If anyone can help that would be great! ?
123carlos123darkred said:
So I rooted my phone using king root and everything was working fine up until I tried to switch from kingroot to super su using super sume. After that my phone just reset and at first was endlessly restarting, after shutting it off and back on I was able to get it to stop endlessly booting but ran into a different issue. The phone boots up and reaches the "android is starting... Starting apps." Screen and doesn't go anywhere past that. I went into recovery mode and preformed a data wipe to see if that would work and the problem still persists. I am in fact running on stock no clockwork recovery or anything of that nature. If anyone can help that would be great! ?
Click to expand...
Click to collapse
Just let Android start apps. It might take 5 to 10 minutes.
me tooo
123carlos123darkred said:
So I rooted my phone using king root and everything was working fine up until I tried to switch from kingroot to super su using super sume. After that my phone just reset and at first was endlessly restarting, after shutting it off and back on I was able to get it to stop endlessly booting but ran into a different issue. The phone boots up and reaches the "android is starting... Starting apps." Screen and doesn't go anywhere past that. I went into recovery mode and preformed a data wipe to see if that would work and the problem still persists. I am in fact running on stock no clockwork recovery or anything of that nature. If anyone can help that would be great!
Click to expand...
Click to collapse
im in the same boat as you.
Damn....................
Im in the same hole as all of you or at least was....
So the problem with this is that these rooting programs such as kingroot and Kingoroot arent compatible with a lot of devices that aren't popular such as alcatel phones for instance....... although it is available for higher versions fortunately. The glitch that we have all had is due to trying to use 2 rooting programs (NEVER TRY THIS!!!!!!!) on one device and interference when booting up causes this annoying bootloop. Im assuming that no one here has managed to unlock the bootloader, so what you must do is plug your phone into a pc via usb and then try to download this firmware:
drive.
google.
com/open?id=
0BwBw9a_
6fkKUMmpWWno0S2ljTjA
Justt put it all together and download the firmware afterwards.... the pc must detect the phone first so this program can detect and install the drivers. Requires a format tho, so take that in mind. Hope it works for you guys......
Hi For my 1st root I decided to use kingroot due to the simplicity for my S4 GT-I9505. Carrier Optus & version 4.x (think might been 4.2.2) So yesterday I tried the APK root which failed so I tried the desktop v3.0 which also failed. Realised my antivirus might be messing with it so disabled it then tried again. Got stuck at 97% for couple hrs. Forced reset & it started normally. The kingroot app said no root but I had root access for programs & root checker said success when I allowed it. Attempts to update the supuser on kingroot website & rerooting with the program still failed. I thought I had removed the knox app prior to root but got random (successful) restarts. Found a thread saying it was cause knox was still active. So used sdmaid & this thread (http://forum.xda-developers.com/showthread.php?t=2514703) to remove all traces. All removed 2 knox files with same name as apks but dif extension that weren't on the list. Think they were something like .ocex. Did a device restart to make sure was gone but now wont boot. Goes through the s4 startup, then the carrier screen then gets stuck on the samsung screen after that. Tried holding the vol down for safe mode with sd card in & out from the 1st samsung screen. Going into recovery takes me to kingroot recovery v0.0.0.2 in Chinese. I saw the word cache in there so I reset cache & it made no difference. Kies 3 wont recognize it. I thought I had made a backup prior but it had failed miserably so I got msgs, call logs etc but not my media files like photots. If possible I would like try options that dont wipe my personal files 1st. I have no idea how I should proceed or what the Chinese says in the kingroot recovery mode. Any help would be much appreciated.
Does anyone know the kingroot recovery options? I read sometimes a hard reset can wipe the apps but leave personal files. Even if I loose them better than not having any access into the phone. I am also able to boot into load custom os menu.
Well, I just got this phone this week. It was actually a gift in fact since I broke my last phone a week before this.
As soon as I got used to the new phone. I started playing with it's guts. I rooted it with Kingroot, since it has never failed me before. Installed Xposed Framework, and flashed the 5.1.1 stuff for it to run. I had to flash TWRP to flash the Xposed Framework stuff (for some reason I couldn't get the sideload to work). Got a few modules for it. Got all my usual apps such as Facebook, ES FM, Instagram, etc. Got a few games. Spent some hours playing the games. You know, all the stuff you do when you get a new phone.
Then, I decided it was time to switch from Kingroot to SuperSU, as I do with every phone I root with Kingroot (and there were a few). I did it the same way as I have before, using w0lfdroid's method (I can't post links yet). The Kingroot app didn't automatically uninstall, but SuperSU was working. So, I uninstalled Kingroot manually with ES FM. That caused a lot of "unfortunately, com.kingroot.kinguser has stopped" dialogs that never stopped coming, and I decided a reboot might fix it.
I was wrong, the reboot did NOT fix it. It turns on, goes to the LG logo screen, goes to the Metro PCS screen, dims the background, [all of that within a minute and then] vibrates once, and then no sign of anything else. However, the phone does seem to be alive. When I plug it into USB the MTP starts working. It's also listed in adb's devices list. I can even use adb. I used adb to boot it into bootloader/fastboot, and it's even listed in fastboot's devices. It does still charge.
That damned Kingroot, I'll never use it again to shortcut through rooting. It has always worked, and I've been able to swap it with SuperSU everytime before this one. I just don't want to risk this happening again.
I'm lost on what I should do about this. What would you fella's do?
_____________________
I do have a warranty on it, but I've obviously voided that above. I could lock the bootloader back with fastboot (using "fastboot oem lock") so they don't see anything significant right away, but they could always dig in to see that I've done a lot of changing. Hell, all they would have to do is boot into recovery and see TWRP... xD
Well, I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
EDIT 4: I no longer have USB debugging access, since I re locked the bootloader (which seems to have reset it, again). So now I also do not have access to fastboot. I think I screwed myself...
unbricking
@ goatitalone can help you unbrick your device. I still have the files if he is OK with it I can help you too or if he can write a tutorial on here that would be great. @ goatitalone?
I have same exact problem howisit fixed?
Magik1 said:
I have same exact problem howisit fixed?
Click to expand...
Click to collapse
do you still have adb? if you do i can send a twrp backup
its been listed kingroot will brick you, currently the oneclick is compatible with our devices. you should have done some searchign before tinkering with your device in my opinion, if youre smart enough to unlock your bootloader .. you should be smarter in researching root methods.
youll have to reflash your device, contact goitalone - as noone that he's helped will help you with getting those files.
as for it being an ms3302 device.. i havent seen that device under our series.
Use this to unbrick http://forum.xda-developers.com/android/development/stock-firmware-rom-unbrick-lg-k7-k330-t-t3432878
Hi, this is my first post so don't be surprised if I don't ask the right questions/give the right information
Long story longer than needed, I rooted my Fire HD 6. Then I factory reset it, and my root access was gone. So I kept trying to get Kingroot, the app I used, to get me root access, but it couldn't really decide if I had root or not. What I mean by that is sometimes it would go to the Kingroot homepage but then say that root access was gone, and when I tried to root it again with Kingroot, it would always fail. So I brought in another app, Kingoroot or Kingaroot I think it was called, and it worked! But when I opened an app I use, Lucky Patcher, it said that something went wrong and the device needed to reboot. I did it and from then on it has been stuck in a bootloop, but I can get into recovery mode, but I can't get my PC to recognize it. That's not entirely true, it will recognize it in ADB, but instead of the device name it has a bunch of numbers and says the device is unauthorized.
I've tried everything I can think of, looked around online a lot, but nothing has seemed to work, so if anyone can help, greatly appreciated.
I am running stock Fire OS version 5.1.2