[HELP] S4 stuck booting after kingroot then knox removal - Android Q&A, Help & Troubleshooting

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.

Related

[Q] Samsung Galaxy Rugby: various issues

Hello all,
I'm sorry, but I couldn't find any device-related subforum for the Samsung Galaxy Rugby (GT-S5690M). If my questions are in the wrong section, please move it to the right place (mods)?
So here's the story: I just got my first smartphone. Since it's locked to Bell, it has some bloatware and need for sim-unlocking. I did a lot of reading and through some tutorials I managed to root Android and got rid of some bloatware (just four Bell apps). So far so good! Then I tried to unlock the phone. There are some apps in the Google Play that state that they can unlock the phone for free ("works on various Galaxy models").
I tried them out, but none of them could provide a solution. The last app I tried (Galaxy_S Unlock) requested that BusyBox were to be installed, so I did. During the installation the app remarked that already some BusyBox version was installed, but not the version that it was trying to install. I was suppose to try another type of installing (I used the normal/safe mode). But it said it was already installed, so good enough. Right? I tried the unlocking app again, but it still said it had errors getting to communicate with BusyBox. None of the unlocking apps gave me the impression that they changed anything in the system.
I figured that maybe a reboot of the phone would fix this. However, now the phone got several issues:
- booting takes forever (18 minutes) It does the animated Samsung logo (though, not with sound any more) and then keeps on slowing the glowing Samsung name.
- the speaker doesn't seem to be working at all
- it can no longer check for updates. After agreeing with the disclaimer, it says it can't connect.
- Samsung KIES (PC software suite) doesn't see the phone any more.
- the phone is generally very slow now. Even when typing a password the phone sometimes hangs for about 5-10 seconds. Loading the disclaimer for the Software Updater takes 10-15 seconds.
I tried to reset to factory defaults and reload the rooting zip file again, but to no avail.
I've been trying to read up on the isolated symptoms, but I'm simply starting to feel overloaded with all the info, especially since I'm a Android newbie.
Does anybody recognize these symptoms and, more important, has any tips on what to try to restore whatever has gone wrong?
Additionally, I would really be interested in knowing if there's a way to force-upgrade to Jelly Bean. It appears that this firmware hasn't been made available to Rugby users yet through the regular update channels. But are there alternatives?
I have a Bell as well
Yogi.B said:
Hello all,
I'm sorry, but I couldn't find any device-related subforum for the Samsung Galaxy Rugby (GT-S5690M). If my questions are in the wrong section, please move it to the right place (mods)?
So here's the story: I just got my first smartphone. Since it's locked to Bell, it has some bloatware and need for sim-unlocking. I did a lot of reading and through some tutorials I managed to root Android and got rid of some bloatware (just four Bell apps). So far so good! Then I tried to unlock the phone. There are some apps in the Google Play that state that they can unlock the phone for free ("works on various Galaxy models").
I tried them out, but none of them could provide a solution. The last app I tried (Galaxy_S Unlock) requested that BusyBox were to be installed, so I did. During the installation the app remarked that already some BusyBox version was installed, but not the version that it was trying to install. I was suppose to try another type of installing (I used the normal/safe mode). But it said it was already installed, so good enough. Right? I tried the unlocking app again, but it still said it had errors getting to communicate with BusyBox. None of the unlocking apps gave me the impression that they changed anything in the system.
I figured that maybe a reboot of the phone would fix this. However, now the phone got several issues:
- booting takes forever (18 minutes) It does the animated Samsung logo (though, not with sound any more) and then keeps on slowing the glowing Samsung name.
- the speaker doesn't seem to be working at all
- it can no longer check for updates. After agreeing with the disclaimer, it says it can't connect.
- Samsung KIES (PC software suite) doesn't see the phone any more.
- the phone is generally very slow now. Even when typing a password the phone sometimes hangs for about 5-10 seconds. Loading the disclaimer for the Software Updater takes 10-15 seconds.
I tried to reset to factory defaults and reload the rooting zip file again, but to no avail.
I've been trying to read up on the isolated symptoms, but I'm simply starting to feel overloaded with all the info, especially since I'm a Android newbie.
Does anybody recognize these symptoms and, more important, has any tips on what to try to restore whatever has gone wrong?
Additionally, I would really be interested in knowing if there's a way to force-upgrade to Jelly Bean. It appears that this firmware hasn't been made available to Rugby users yet through the regular update channels. But are there alternatives?
Click to expand...
Click to collapse
I have the same model and when I try to root it it fails. Also, after installing the drivers on my PC, it shows up as an external drive and when I try to open it, it tells me to put in a disc...??? Any help?
chilli1327 said:
I have the same model and when I try to root it it fails. Also, after installing the drivers on my PC, it shows up as an external drive and when I try to open it, it tells me to put in a disc...??? Any help?
Click to expand...
Click to collapse
The external drive will only work if you select "Enable USB Connection" in the Android menu.
I've revived my phone for a hobby project. Can't remember how I solved the above issues at the time, but it doesn't want to accept the stock firmware image. I can only find one old version on my external HDD with old backup data. Tried several Odin versions to no avail. 3.07 stays stuck at "SetupConnection". 3.04 fails with "Complete(Write) operation failed."
Galaxy Grand Duos
Please padone me for posting in the wrong LOC. It just that my Phone brake down,N I forgot my old XDA account password I had to Create a new 1
Now here is my Q: my galaxy grand dous GT-I9082 just is now on Boot Loop I can't write down any detail about the phone cose it can't boot sorry bout that. Now I boot into CMW then I mistaken navigate to Mount & Storage then On FORMAT SYSTEM after it successfully formated the phone can't boot it stock on the GALAXY GRAND GT-I9082 logo please I need urgent help please it really annoying I had to crearte a new XDA account cose of my phone

In desperate need of help ... T-Mobile US Samsung Galaxy Note 5 bootloop/bricked?

As mentioned in the title, SM-N920T. 64GB if that matters. Rooted with CF Auto Root but hadn't gotten around to TWRP or CWM or any custom recovery.
I must have misread some online instructions about the current wallpaper being found in /system/framework-res.apk, and moved that file to what I think was the / directory. Immediately I was unable to run any apps; every single one gave the "Unfortunately, ____ has stopped" error message. Upon an attempt to reboot the phone, it is now stuck in a bootloop -- it will get as far as the T-Mobile logo for about 15 seconds, then right back to the Samsung Galaxy Note 5 logo that comes up first in the normal boot sequence. I can get it into both download mode (light green background) and recovery mode (starts with "Android system recovery" and a list of nine options below that), but nothing else.
Attempts to re-flash the CF Auto Root files have done nothing. I went online searching for a factory stock (non-root) ROM, and tried that, but it failed in Odin. I have also tried ADB but am having a lot of trouble with that too; the Android SDK Manager app seemingly won't allow me to install the SDK platform tools, usually saying it can't find the output directory.
I don't really have $800 lying around for this thing to be permanently bricked, and will do anything it takes to rescue this one. That may quite possibly include a reward for anybody who can help me successfully save this phone.
Thanks in advance.
Larry
P.S. If this helps, when I get into recovery mode and select "apply update from external storage" or "apply update from ADB," I am told that both of these are disabled.

I think I bricked my Phone, Help

So quick back story then same facts.
Recently rooted my phone to use some GPS spoofing for Pokemon Go ;P
All worked well to start with. Flashed "CF-Auto-Root-zenlte-zenltedv-smg928i.tar" with odin, simple enough.
Phone booted up fine no worries, Downloaded Lucky patcher to move the GPS Spoofing apps to system/apps to get around pokemon gos "allow mock location" anti cheat measures. This part took a little bit longer to get right. Kept failing to copy to system/apps from what I could piece together that directory was set to read only. changed that copied accross fine.
tried a different app (which simulates walking to hatch those eggs) , didnt work.
double checked read only wasnt the cause....nope that not it.
Try copying it accross manually via ES file explorer. Says insufficient space. Not the phone itself but the system partition. Simple enough remove some unneeded files from here.
Now i think this is where i have gone wrong. I only selected some folders of downloaded apps that I do not use very often, Like samsungs game recorder, pretty sure i didnt select any major system processes. anyway end up copying the GPS app over and reboot the phone. Boot loop
Boot into recovery and reflash the auto root file i mentioned before. Boot loop
Boot into the other one (Volume up) wipe cache. Boot loop
Boot into it again , gulp factory reset. Boot loop ****
Downloaded the 6.0.1 firmware for it but it wont let me install it
I need some guidance on fixing this paper weight or even point me in the right direction atleast, I am not an expert in any means when it comes to android CFW etc but not a newbie.
For the love of pokemon please help me.
G9258I model
HelpMeImBricked said:
So quick back story then same facts.
Recently rooted my phone to use some GPS spoofing for Pokemon Go ;P
All worked well to start with. Flashed "CF-Auto-Root-zenlte-zenltedv-smg928i.tar" with odin, simple enough.
Phone booted up fine no worries, Downloaded Lucky patcher to move the GPS Spoofing apps to system/apps to get around pokemon gos "allow mock location" anti cheat measures. This part took a little bit longer to get right. Kept failing to copy to system/apps from what I could piece together that directory was set to read only. changed that copied accross fine.
tried a different app (which simulates walking to hatch those eggs) , didnt work.
double checked read only wasnt the cause....nope that not it.
Try copying it accross manually via ES file explorer. Says insufficient space. Not the phone itself but the system partition. Simple enough remove some unneeded files from here.
Now i think this is where i have gone wrong. I only selected some folders of downloaded apps that I do not use very often, Like samsungs game recorder, pretty sure i didnt select any major system processes. anyway end up copying the GPS app over and reboot the phone. Boot loop
Boot into recovery and reflash the auto root file i mentioned before. Boot loop
Boot into the other one (Volume up) wipe cache. Boot loop
Boot into it again , gulp factory reset. Boot loop ****
Downloaded the 6.0.1 firmware for it but it wont let me install it
I need some guidance on fixing this paper weight or even point me in the right direction atleast, I am not an expert in any means when it comes to android CFW etc but not a newbie.
For the love of pokemon please help me.
G9258I model
Click to expand...
Click to collapse
Hi Mate!
For The love of Pokemon am Here To help Can u send A sceenshot of phone In downloadmode
If u dont know how to get into Downloadmode
Pressing volumedown+powerbutton+homebutton Should Do the Trick
Once U r there Grab another phone if u have click whats on screen Post it here
osman34 said:
Hi Mate!
For The love of Pokemon am Here To help Can u send A sceenshot of phone In downloadmode
If u dont know how to get into Downloadmode
Pressing volumedown+powerbutton+homebutton Should Do the Trick
Once U r there Grab another phone if u have click whats on screen Post it here
Click to expand...
Click to collapse
No Second phone or camera sorry.
----
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G928I
CA_ TYPE: CA_3
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download : Enabled
KNOW WARRANTY VOID: 1 (0x0500)
AP SWREV: B:2 K:0 S:0
[Centered Download Icon]
Downloading...
Do not turn off target
Just realized this was posted in the wrong sub forum.
MODs please move to Samsung Galaxy S6 Edge Plus
Thank Clefairy i think i fixed it.
A full install of the firmware version from https://samsung-firmware.org/download/Galaxy S6 edge+/e07w/XSA/G928IDVU2BPE2/G928IXSA2BPE2/ seemed to fix it.
Thanks mate

Root Success, Phone Randomly Restarts, Root Gone

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

Magisk breaks password unlock?

Dear Android Community,
Disclaimer: I am new to rooting. Pls consider that & be patient. I might not understand everything in the first place :angel:
Okay - let's go.
1.) First off I installed the latest original firmware for my Samsung Galaxy J6 (SM-J600-FN)
2.) Then I installed the correct TWRP-version for my phone hopefully (TWRP-3.2.3-TwrpBuilder-j6ltedx-2018-08-21_14-15.tar)
3.) After that I used the standard Magisk rooting method by installing
no-verity-opt-encrypt-6.0
RMM-State_Bypass_Mesa_v2
Magisk-v19.3
4.) Then I installed Magisk Manager after my system booted for the first time and I am ready to explore everything rooting offers to me <3
BUT
What happened to me more than 5 times now. I installed everything I wanted, mostly rooting apps, Magisk modules & debloated my phone. My last step used to be to set a password, because I didn't want to always type in my password cause of the many reboots I had to make...
THAT HAPPENED
After I set my password, no matter what action led my phone to turn off it's screen, it told me to access my password & the result is still very frustrating because it said that the code is WRONG everytime?! How can that be I thought. First of all I thought I made a stupid mistake & couldn't remember it right...
BUT
Immediatetly after I typed the CORRECT password (I did this method min. 5 times, including installing original frimware with Odin or through installing my OrignialBackupFirmware through TWRP, so I know now, It's not my fault. It must be something else) the lockscreen said it was uncorrect and my phone put itself in a...
BOOTLOOP
This bootloop is different from what I've seen before, because it starts with the Samsung logo. Shows the lockscreen for some seconds (I can't enter my password from here) and starts to loop again. But from here I fortunately can get into TWRP recovery without having to install the system again with Odin.
THEN
I thought it had something to do with the software I installed, with magisk modules or with debloating, but now I've figured that this wasn't the case.
EVEN
When my system is just freshly rooted and everything is untouched this bad error happens.
NOW
I want to ask for help because I don't know how to solve this issue & I came across this post, where it says that I should delete following files:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
...but I don't want to risk encountering this roor again, because I want to spare time, energy and I am wasted from installing & rooting & configuring my system over and over again...
Thx for helping me!!
Your John One ^-^

Categories

Resources