Ok so I recently debricked my note 4. I went back to stock unrooted. I proceeded to install kingroot and flash twrp 2.8.7.0. It flashed fine but I can't get root to stick without bootloop. I'm on bpa1. If anybody can help I would much appreciate it
Root won't "stick" with Kingroot. You'll lose it for sure when you reboot and it's so flaky you can lose it in seconds between reboots.
use Kingoroot instead. Comes in two flavors, pc version and apk, suggest apk version
Related
ok so I have a vs985 that was rooted with twrp and was running stock 4.4.2 10b. Ive been on it for a while and wanted to update. went though my usually backup routine, then updated base band to 23c installed cyanogenmod 12.1 then went to install gapps but when it started it rebooted back in to twrp so I tried again with no luck same thing, so I figured I'd boot the phone and go out and grab a new download reboot into recovery and install gapps, but after rebooting wasn't able to boot back into twrp. for some reason the button combination wouldn't work nor an apps I downloaded from the browser as I didn't have play store. either way I was able to get into something that allowed for a safe mode and reboot but that was all. so I said ok I use recovery tool to flash 10b root then install twrp then same as before update modem, cyanogenmod then gapps, but after going back to 10b I was not able to get root using stump root as I had before. every time I tried loading the app and I got an error saying something about phasing and everything I tried I was able to get it to load. so I thought maybe I could run some updates and try and root from other methods and so far no luck. so I'm currently on 5.0.1 and still cant root this methods like lg one click root so others. any ideas why this is happening? I don't mind going back to 4.4.2 10b to get root but I've had no luck with the multiply stump root or others I've tried.
thanks
Andrew
so I decided to install second version of Pre-Rooted 5.2.1.0 ROM and only had a partial boot unlock. I managed to full boot unlock and install clockwork but then I tried to install the prerooted rom but missed the step about not imstalling a prerooted without busybox and bootmenu
Anyway I bricked the device and managed to recover to version 51.1.4.0.
I still have the full boot unlock and it boots into clockwork on startup but I can't root version 51.1.4.0 and can't seem to install a lower firmware version through clock work. I always get "error in update.zip Status 7 installation aborted"
I've tried these guides to put me back to lower stock firmware but no luck.
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/
I know you can't root 51.1.4.0. but is there any options if I already have the bootunlock and clockwork still installed.
I'm at my wits end at the moment. Any advice would be appreciated
It sounds like you tried flashing the 5.2.1.0 pre-rooted ROM using ClockworkMod, right? You can't do that. You must first replace ClockworkMod with TWRP and then use TWRP to install the Fire OS 5 per-rooted ROMs (like 5.2.1.0).
I'm not quite sure the damage you've done, so best to see if @rbox will reply.
Yep, I was trying to get to TWRP. I can still sideload apps and have kodi all working again but running off a SMB share now. No Usb access without the root.. So not all lost I guess. SMB share seems to work well on a wifi network
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
After several failed attempts to root my Galaxy S6 Edge+ (SM-G928T) with the latest firmware update to 6.0.1, G928TUVU4DPK6, this is what I had to do to get a working root solution. At no time did I ever have a problem installing TWRP with Odin. Ive been using Odin 3.12.3 but I had the same issues with Odin 3.10.7.
I started with a clean slate and performed a fresh install of the stock firmware which I downloaded from here:
http://forum.xda-developers.com/tmo...al/sm-g928t-stock-odin-g928tuvu4dpk6-t3516310
After flashing the stock firmware with Odin 3.12.3 I did the basic setup on my device to make sure I could boot and everything was working. Next, I shut down my device and booted to Download Mode by using the key combination of Volume Down + Home + Power. Once booted into Download Mode I used Odin again to flash TWRP 3.0.2-0, which is available here:
https://dl.twrp.me/zenltetmo/
After the flash was complete I booted to recovery using Volume Up + Home + Power. When TWRP starts it will ask you if you want to swipe to allow system modification. If you swipe to allow system modifications you will trigger DM-Verity and you will not be able to boot normally unless you flash a custom kernel that has DM-Verity disabled in the fstab or you can flash the no-verity-opt-encrypt.zip that I dowloaded from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
The newest version available is 5.0
So, I swiped to allow system modifications. Next, I transferred the no-verity-opt-encrypt.zip from my PC to my device and installed the zip in TWRP. Once this was completed, I transferred my root zip from my PC to my device. I used the PHH Superuser to root my device which is available here:
https://superuser.phh.me/superuser.zip
I installed the root zip in TWRP, wiped cache/dalvik cache and then selected Reboot System. I didnt know if I would be able to boot or not. I could never get past the T-Mobile boot animation each time I attempted to root this damn thing but low and behold everything went as planned and I was fully booted up and running. I went through the setup wizard and everything was working as it should.
I am using PHH Superuser instead of Chainfires SuperSU. Its a personal choice for me as I have been using PHH Superuser since the hand off of SuperSU to a new company, CCMT, LLC.
Once I was finally able to boot normally I downloaded PHH's app in the Play Store from here:
https://play.google.com/store/apps/details?id=me.phh.superuser
This is just my experience of what I had to do to get root working on my S6 Edge+. All of my root apps are working as designed. I cant remember the last time I didnt have a rooted device and it was starting to bother me. I was having root withdrawals. If anyone decides to upgrade to the latest firmware from T-Mobile and wants a working root solution, here is what worked for me. I have not tried to use Chainfires SuperSU again. If you dont want to use PHH Superuser and wanted to use SuperSU instead, try to insert SuperSU in place of PHH Superuser and see what happens. Do this at your own risk because I have not tested it with this solution that I found. Good luck. Happy Rooting!!
fast69mopar said:
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
Sent from my SM-G928T using XDA-Developers mobile app
Click to expand...
Click to collapse
Here is the one I used. works great
Venal_System said:
Here is the one I used. works great
Click to expand...
Click to collapse
I tried that version too and I ended up with the same problem each time. I figured it out last night though. Im going to update my OP with the steps I had to take to get it working and that way if anyone upgrades to the latest PK6 firmware for their G928T and has this problem my thread is available with a solution.
***EDIT***
Solved. Not sure what I did right, but installing SuperSU 2.82 via TWRP and wiping the cache twice seems to have done the trick. No pulling card or battery - ran through one bootloop and then settled down after a minute.
So I'm trying to set up a backup phone after successfully rooting my primary phone using 5.1.1 (BPA1) and having some problems. First phone went OK and is stable. This one is giving me fits.
Downgraded from 6.0.1 to 5.1.1 using Odin.
Used Kingroot and ADB to get root.
Installed TWRP 3.0.2.
Made backup before I did anything else.
Download mode shows DEVELOPER
The problem starts when I try to install SuperSU. If I install it from TWRP the phone goes in to bootloop on restart. I've pulled the SD card, re-partitioned it, reformatted it, etc.
Tried different versions of SuperSU (2.71, 2.74, 2.78) and all result in bootloop. Tried the SuperSU directly from TWRP - same thing.
RootChecker reports not rooted.
I can restore the backup with TWRP and that stops the bootloop, so I don't have a bricked phone or anything.
Any ideas how to install SuperSU and eliminate the bootloop? Or am I at some point in the process which requires something else?
Even though I was successful on the primary phone, that still doesn't mean I really understand what I was doing.
Thanks,
Spumco
Hi guys it's been a while since I've rooted any devices but decided to root my LG G PAD 8.3 (V500), since it is so outdated. I'm gonna go over exactly what I did on how I got here to better understand. Sorry in advance for the long winded post.
-Anyway, I had to downgrade to 4.2.2 by using the LG Flash Tool 2014.
-Then, I rooted my device by running root.bat Also, I had SuperSU when I rooted.
-After rooting, I installed TWRP via the play store, downloaded the most recent twrp.img and flashed it via the app. It took me forever to get to recovery by pressing power+volume down and then pressing power+volume down+volume up. But after what felt like 20+ tries, I got to TWRP recovery.
-I wiped my phone and flashed the most recent Lineage ROM. Unfortunately, after flashing the ROM, I could not flash GApps because it rebooted to the ROM after flashing. TWRP let me know that I had to update TWRP and since I did not have the play store and I was once again having trouble getting into recovery, I downloaded the most recent TWRP apk.
-When trying to open the apk, it gave me a "can't open file" message which I didn't understand why. After rebooting, for some reason, it then let me run the TWRP apk and installed the TWRP app. This is when I found out that I was no longer rooted because TWRP notified me. I double checked with root checker and indeed I was no longer rooted. I have no idea when or how that happened.
-Again, I couldn't get into TWRP recovery until I plugged in my phone to my PC and for whatever reason, it helped me get into recovery. I wiped the phone and proceeded to flash Lineage and GApps.
-I read that by flashing SuperSu I may regain root, so downloaded an updated SuperSu, went into recovery and flashed SuperSu. When rebooting, the LG screen came up with a message at the top left corner reading "secure booting error! Boot certification verify". At that point, I was in a bootloop and had to go into recovery, wipe and flash again minus supersu. So I am now on Lineage with GApps and no root.
How do I regain root? And anyone know how I was able to lose it? Back in the day when I was into flashing, I never had these problems and never lost root out of nowhere like this.
Also, if I wanted to get back to stock LG 4.2.2, how would I go about that? I know that currently, I can't use the LG Flash Tool 2014 because my current ROM does not have a USB Software option in order for the tool to recognize the tablet.
Any help would be greatly appreciated, thank you.