Followed all directions meticulously even tried recovery wipe and resintall ping pong and supersu tried again same result says installing then reboots nothing happens.
Also tried a Odin flash to stock and it appeared to complete in odin but then when the os booted the flashfire icon was still there...... not sure what the problem is..... used OE2 Rom.
Figured out what the problem was I had one of those headphone buttons in the stereo jack and somehow this broke flashfire from working once i removed it it flashed no problem.
Related
I was able to root my device using these instructions
http://forum.xda-developers.com/showthread.php?t=2401901
I can confirm that it is rooted, TWR is loaded as the recovery and superSU is running as well as some root-only apps.
The problem is that no matter what or how I try, I cannot get a new kernel to install nor can I flash a ROM.
If I try to do either via Odin it completes without errors (either on the computer or tablet) but when the tablet is rebooted, no changes.
If I try to flash a rom from the recovery it just errors out and fails
I even tried using Odin to unroot and reset back to stock and that worked but when I re-rooted it again I was back to where I'm stuck!
Has anyone ever seen this before?
rek410 said:
I was able to root my device using these instructions
http://forum.xda-developers.com/showthread.php?t=2401901
I can confirm that it is rooted, TWR is loaded as the recovery and superSU is running as well as some root-only apps.
The problem is that no matter what or how I try, I cannot get a new kernel to install nor can I flash a ROM.
If I try to do either via Odin it completes without errors (either on the computer or tablet) but when the tablet is rebooted, no changes.
If I try to flash a rom from the recovery it just errors out and fails
I even tried using Odin to unroot and reset back to stock and that worked but when I re-rooted it again I was back to where I'm stuck!
Has anyone ever seen this before?
Click to expand...
Click to collapse
1), If you used the TWRP from that post, then you need to update to a newer recovery. TWRP for KK
2). Telling us that "it errors out" is pointless. You need to tell us exactly what error you are getting.
3). Attach the recovery.log from the failed attempt to flash a rom. Google can tell you how to get the log.
welp, I feel dumb - it was the wrong version of TWRP that was causing the problem all along
Hi all. I've got a Sprint Note 2 that's not active with any plan and I just want to use it as an extra mini tablet.
I want to use it for music and videos as well as for making music with Caustic. For this to work with low latency I need lollipop.
Previously the phone was rooted and was running twrp and various kitkat ROMs.
I found a version of cyanide ROM that's a tablet style rom with no mobile data or calling enable. Wifi only.
plus therebwas this Shift package that would enablenetflix to work. Great.
So i downloaded cyanide tablet version, shift and gapps. Using twrp i did a full wipe and flashed the rom and shift but gapps wouldnt flash.
So for the time being I gave up on gapps (though I will definitely need the play store to load my purchased apps.
When I tried to boot the phone it just hung at the bootup animation.
Someone suggested I use philz recvery. I flashed philz with odin and booted into recovery. Sure enough philz was working. So then i wiped again and tried to flash the cyanide rom again. This time not even worrying about gapps until i could verify that the rom would flash boot up.
Again it got stuck in the boot animation screen. I tried flashing it with odin instead of from the microsd card. Again stuck in the boot animation.
I reinstalled twrp and tried flashing with that again. Same issue.
So then I tried cw12.1. Even though netflix doesn't work on it last I checked. I wiped and flashed and again stuck in boot animation. Though this time its the cm animation. So i know the rom was at least flashed.
This i thought perhaps somehow i lost root so none of these kernels would load. So i downloaded cf autoroot and flashed with odin which said it was successful. Phone rebooted...again stuck at bootup animation.
So basically the phone is bricked. What should I do? Install stock rom with stock recovery, then root and wipe and install cyanide? Or should NOT wippe and install it? How shoud I root it, with what methos and when during the flashing sequence. Ive tried every combination I could think of
So i was trying to flash hacker kernel
It bootlooped.
So i reflashed renegade and tried reflashing.
it rebooted
now everytime i try and flash anything it reboots
super su is missing.
I installed super su from play store
when i go to flash binaries it reboots.
I updated TWRP
still same thing.
If i flash anything it just boots back to recovery.
Any thoughts?
Flashed back to stock and rerooted.
Did the trick.
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
koop1955 said:
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
Click to expand...
Click to collapse
No I had previously been rooted fine and dandy. for some reason TWRP started just rebooting on any flash.
so is it not going into bootloop mode anymore? because i've been having this problem for the last 6 months. i thought i'd try again and still doing the same, it'll get to the setup at the beginning and then reboot back to twrp????
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