I just used the nexus rootkit to root my nexus. It seemed pretty easy at first but now I am having a few issues. I rooted the device and installed drivers successfully. The only problem now is I went to install TWRP and then installed the open recovery scriot but after i did that I went to go and restore my apps from the toolkit and now whenever I open goomanager to do a reboot restore I get the android with the red exclamation point on his belly. What should I do next to fix this do I have to unroot and start the whole process over again? Should I flash a rom to see if it fixs this issue? When I go back into the goomanager I dont have the option to install open recovery script anymore. I have also noticed that before the root when I put the nexus 7 down the screen would shut off imediately and when i picked it up it would turn on as if there was a sensor but not after root that doesnt happen anymore. I know they sell certain magnet cases which when you cover the screen it will turn the screen off.
Related
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Should be easy
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
I think Xposed creates a rescue zip onto your SD card called Xposed-Disabler-CWM.zip
Try flashing that if you have a custom recovery. If you don't have a custom recovery or this doesn't fix it try reflashing the stock rom.
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
Whoa, an actual normal question about xposed. First time in a while.
You should be able to just reflash your rom
janekmuric said:
I think Xposed creates a rescue zip onto your SD card called Xposed-Disabler-CWM.zip
Try flashing that if you have a custom recovery. If you don't have a custom recovery or this doesn't fix it try reflashing the stock rom.
Click to expand...
Click to collapse
ldeveraux said:
Whoa, an actual normal question about xposed. First time in a while.
You should be able to just reflash your rom
Click to expand...
Click to collapse
victolabs said:
Hi i recently installed xposed on my acer A-480FHD rooted tablet kitkat 4.4.4. The reason i installed xposed was for the app greenify. As i scrolled thru the settings for it i noticed it said "On some devices this may cause them to enter a boot loop" and something else i dont remember. I installed assuming i was not part of that list. When i installed it it told me that xposed would be running next time i boot up. After a few hours i decided to reboot it. Because why not. I rebooted it using chain fires app live boot and used its reboot option. Then i went into boot loop. If you need any more info i have some screen shots of my tablets details. Can you help me get my device out of boot loop? I am fine if you wanna debug my tablet live.
Click to expand...
Click to collapse
Thanks for the help. None of those methods worked for me doe. As of this comment im reinstalling root now. But if others get in the same problem as i did i wont leave them in the dust. Here is what i did to fix my boot loop on my acer icona 8 A-840FHD.
First you wanna boot into stock recovery NOT CWM recovery. How i got into it was by holding the Power and volume up button at the same time. (assuming if your device is off) Then i was booted into recovery. If you are booted into fastboot then navigate to the "RECOVERY" Option using the volume keys and select it using the power button. The device will reboot into the appropriate menu. Then choose the option to WIPE your device, Factory reset Ect. After wipe is done reboot your tablet. Go thru the setup screen and proceed uninstall root using super su root manager. After that reboot tablet and update tablet to the latest ver. Then proceed to re-root tablet like you did the first time. And remember to not make the same mistake like last time. This is the guide i used to root my tablet.
http://forum.xda-developers.com/android/development/guide-root-acer-iconia-tab-8-a1-840fhd-t2933317
Guide 2.
Thanks! Victolabs
Hi all,
I am trying to build a car headunit system using the Asus memo pad 7 ME176CX (k013). I got everything sorted out and the last thing I had to do was to kill the player when the ignition of the car is off.
For that reason I installed llama and made an event to kill the player when on battery. This did not work so I decided to root the tablet so I could force-kill the app.
I downloaded the one-click zenfone root from and followed the instructions. Everything worked just fine and I got the Super SU icon and so on.
Unfortunately, llama still could not kill the process, so I decided I did something wrong and started the un-root.bat file. The process ended with success, but.......I got stuck to the ASUS logo with the loading
indicator below (just before the home screen loads) . I could still connect to the tablet and performed the CheckBeforeAction.bat - it worked just fine. For some reason decided that it would be a good idea to root again and did it - again successfully (or so says the shell).
However, I could not go pass that ASUS logo. So (as if I haven't created a big mess already) I entered into fastboot mode and performed factory reset. That did not help at all.
I followed the instructions and downloaded the stock 182 ROM (I saw the WW version from the fastboot screen), put it in the root of my external 16GB SD card and renamed it.
Well.....when I enter fastboot mode I do not see an option involving SD card. All options I have are droid reboot, something I can not remember but has nothing to do with SD, recovery, power off.
When I go to recovery there I see
- reboot
- apply update from ADB
- wipe data
- wipe cache
Strangely, I can no longer connect to the tablet via USB, so I do not know how to make use of the CWM.
I downloaded ADB_driver.zip and ASUS_Android_USB_drivers_for_Windows_20140325.zip, but for some reason these do not work - I get ERROR 10 when starting the driver.
Well, after all the things (probably really stupid) I did, now I am still not able to boot, but it also looks like I have no more USB access to the device and do not know how to take advantage of the
procedures that I have seen in the different threads.
Is there a way to still recover the device?
I wanted to try and hopefully learn little about rooting. Have been reading forumposts and tutorials for hours before I started.
Then I got this problem that I have been trying to solve for hours. But my conclusion is I need help solving it.
Tested on this phone that just were collecting dust.
Samsung Galaxy S5 Mini (SM-G800F) and I think it was running 4.4.2. (this is all I remember off the top of my head)
Problem / What happend (long version):
Rooted phone. Downloaded SuperSU and Flashify and installed TWRP 3.0.0 (http://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-0-0-t3313775). I had no SD-card so I skipped doing a backup. Everything worked fine (for a normal user). Downladed a Root Uninstaller app also Debloater-setup-v3.90.exe (http://forum.xda-developers.com/devdb/project/dl/?id=12623). Did not freeze or uninstall anything before checking in this forum that it was OK. But after a while I could not access my homescreen it just turned up blank but I could still use other functions/apps. Rebooted the phone in order to get it to work but got stuck at the bootscreen. Tried to fix it via TWRP but the program freezes after a while or just reboots the phone back into Samsung bootscreen.
Problem / What happend (short version):
Rooted - got Flashify and SuperSU
TWRP 3.0.0 installed (no backup made)
Debloater-setup-v3.90.exe and some Root Uninstaller app used (searched on this forum before doing any changes)
Homescreen just blank, other functions/apps worked
Rebooted the phone and got stuck at Samsung bootscreen
TWRP access but the program freezes/reboot after short time
I did try "Factory reset". But the screen froze and the phone slowly started to heat up.
Later on I searched about it and it might have something to do with KNOX?
Any solution is fine since I don't have anything thats need to be saved. I can try any working stock/custom ROM (just not sure how to get it into the phone, yet).
Yes I am a novice so the simplest thing might even work.
Have you tried to flash stock ROM for your device using Odin? If it fails you may want to check this:
http://forum.xda-developers.com/galaxy-s5-mini/help/g800f-failed-odin-firmware-upgrade-fail-t3131782
If it doesn't fix your phone you may have a hardware problem.
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.
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.