Hi all.
So this is quite strange (i think).
I managed to root my s20 fe 4g using magisk with the help of some people from here and a guide.
I have played around with it, installed some stuff, uninstalled some apps (using titanium backup) and was all well.
When I went to restart the phone to give it a clean break, it now wont load up again. Just gets stuck on the 'Phone is starting...' screen. Now this isn't a huge problem, i thought I couldjust flashthe stock firmware again and root the same way and perhaps it will be well. The problem is it wont boot into download or recoery because it is stuck in a cycle of trying to start itself. I can force it to restart by holding the vol- and power button, but that is the only combination that will make it restart, it instantly restarts before i can change the keys held to try and get it into download mode.
Does anyone know what I can do to try and remedy this so it will start again?
UPDATE:
I think i stupidly must have deleted the one ui launcher by mistake... Now I am trying to get an APK to the phone, but ADBdoesn't recognise it at the 'phone is starting' screen. My phon is at dead stage, so i can get it to boot into download now, but it doesnt seem to want to go into recovery, and i think its stock recovery, so not sure if ADB will work?
Any other suggestions to get the launcher apk pushed and installed?
if you can get download mode flash the rom again, hopefully you still have it from rooting.
don't use titanium backup to uninstall system apps. even using it to freeze apps can be a problem if it's not gonna boot up.
get a copy of a safe debloat list and stick only those listed packages that others have found to safe to deactivate.
Related
hey guys, i am not new to the scene but i have actually run into a big problem.
A few minutes ago i flashed a Hero rom followed by the ebi1 kernel, it booted up perfectly fine and went into installation, still no problems.
Once installation finished i learned that for some reason the home app(launcher) doesn't load, it just constantly gives an error force close when trying to go to the home.
Everything else does work.
I then decided to reflash the ROM, when booting my phone it would not go into recovery, i held the home button and it froze at rogers logo,
I tried again after a battery pull and same result, i thought uh oh, BRICK!
When i rebooted again( holding nothing down ) I learned that it apparently does boot! if i leave it alone, it does the whole buttons light up screen dims thing just before it boots, then the screen dies off and I hear a sound meaning usb connected, **(all this while it is still showing the second boot screen)**
The end button works to turn screen off and on but it it stuck at the second (MLGIN or whatever nexus style boot screen)
I nave now found a way to actually get past the boot screen, if i call the phone it will go into the dialer and I can actually use it as a phone!!, once in like this I can actually use the phone completely except for going to launcher(home), I can make calls (if someone calls me to get into the dialer), use the lockscreen, send a message (if someone sends one to me), enable usb mount.
I have a nandroid and a BART saved but like I said i cannot get into recovery.
Any help is GREATLY appreciated.
Please let me know if my post doesnt make any sense, i can try and get my thoughts out again!
EDIT I CAN get Droid explorer to work, this means i can install any apps that could help! but i dont think i could launch them
-with droid explorer i can use terminal, cant i launch stuff with that? also, when i click Bart manager it says i need to buy a license, aww
- I clicked on reboot into recovery in droid manager, the phone rebooted but it hung at the rogers logo, I really cant understand how the recovery doesn't work!
EDIT it WILL boot into fastboot mode!
Can i install an alternate launcher with droid explorer, I think that if i can do this, when i hit home it will give me the option of choosing which laucher right? i then choose the new one.
Any one know where to get a different launcher? or perhaps the launcher from this ROM so i can try and reinstall it
Because i can use droid explorer, the options are nice,
I still need help organising the above attempt, but if that fails I could also use the flash recovery image option in DE and try that.
Am i right in saying that I should first try and get a different launcher to work or should i go straight for the recovery. If the recovery doesnt wokr could I lose access to the phone booting? (thus droid explorer)
OK I would LOVE some community help here:
I think i wave 3 options
1) install any apk (namely a new launcher and get the phone to atleast function properly)
2) Re flash a recovery image
3) Flash a ROM
All of these would be done with droid explorer, i think i have listed them from least risky to most risky (if i flash ROM and that doesn't fix it i could be out of droid explorer)
Could you guys help me start up, where can i get what, my mind is racing too much!!!
ok, using droid explorer i re flashed the recovery, it now boots into recovery. i am going to reflash the hero rom as i really want to use it!
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.
Hello.
I was playing around a bit, and made a bad decision on disabling a sys app, with a root uninstaller app.
Now my phone starts up, but stays on the 'samsung' splash-screen.
My home doesn't seem to get loaded, so its stuck there.
I do, however, get notification sounds from text-messages and push-services.
My phone is rooted, but had no recovery installed, neither did I run busybox.
Not sure wether it runs 4.1.1 or 4.1.2, but I guess 4.1.1 because there's no intern recovery I can activate...
I tried flashing the recovery package with odin, still can't seem to get inside recovery... (Yes I can get into Download Mode)
I tried to reboot into the recovery via adb, but my phone - logically - doesn't respond to those.
Apparently, my USB Debug is not activated also... The phone connects, but I can't even do something with tools like GS3 Mini Toolkit.
Kies doesn't seem to connect either (even when the phone is on)... probably services that don't get started due to a battery saver app...
Long Story Short
Is there a rom & kernel, that can fully wipe my phone, via Odin, cause Download Mode seems to be my only option in recovering my phone.
Or any solutions that you could come up with.. because I already tested so much things,
and it's still stuck on the samsung 'lighting up' logo and a black screen.
The phone is for work & personal use... and I don't have the option to replace it atm.
I really need to get it working again... it was the only smartphone I ever had a decent battery life with (avg. 2.5days)
Thanks in advance!
- Fixed, I got into recovery mode, I forgot to stop pushing the powerbutton... so it rebooted. YAY :highfive:
Hello,
I've been rooted for a few months now and have never had any problems. I wanted to use that Milk Music app from Samsung so I followed the instructions and was able to get it working on my phone and have been for awhile. I recently decided it would be a good idea to change the build.prop file back to its original state, so I copied and pasted it in using Root Browser. (I had made a backup file stored elsewhere). Once I did that I rebooted my phone for the changes to take effect. After I did that I cannot get my phone to turn back on. It displays the LG animated logo screen and then goes completely black. The light on top of the phone radiates blue/green. I've read through several forums about this issue and have tried everything in order to get it to work and for some reason, using my computer and ADB always gives me an error: device not found. I have installed the drivers and everything. Anyone else run in to this problem before? I would really appreciate it.
If you are on stock rom, just rooted. I would think you should be able to factory reset through stock recovery.
Confirm the process but i think you power completely off. Then hold volume down and power at the same time when you see the lg logo release both buttons then press both buttons and hold them.
Should take you to factory reset.
Not 100% certain but this will probably be your next step if you can't get a computer to see it.
Good luck
2111
The factory data reset didn't really change anything. For some reason I cannot boot into recovery mode either. I can put it in download mode though, but my computer still has a problem recognizing it.
brody_low said:
The factory data reset didn't really change anything. For some reason I cannot boot into recovery mode either. I can put it in download mode though, but my computer still has a problem recognizing it.
Click to expand...
Click to collapse
If you can get into dl mode then you should be able to return it to stock which should reset everything. Returning to stock has its own downside but at least you'll be up and running again.
So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:
I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!
I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!
Yep
Ok
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.
Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.