I know I am not the first but I was running Shift3r rom, flashed back to stock, ran the official 5.5.893 update and now I no longer have root. I tried the one-click for3v3er root but it didn't work. I realize I should have done the for3v3er root first but got ahead of myself. My question is: Is there anyway to regain root access with the new official update yet or do I just need to sit back and wait for one of the awesome developers to come out with one?
http://forum.xda-developers.com/showthread.php?t=1390536
Discussions in the above thread (just one is required)
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
It sounds like CWM hasn't reflected TWRP, have you tried using the tool kit again just to flash CWM? Or how about flashing CWM via Odin using the recovery in the below thread?
http://forum.xda-developers.com/showthread.php?t=2232856
Sent from my Nexus 7 using xda app-developers app
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
I think when you rebooted into system in CWM, you accidentally chose to revert to the old recovery
Thanks so much for the answers guys. I went ahead and flashed a rom anyway, figuri g that as long as A recovery was in place, it would be ok, and it seems to be so.
And it turns out I am happy with TWRP and as the old sayi g goes, if it aint broke....
I only chose CWM as the previous root had failed, so I tried with different variables, ot because of a burning preference for one over the other.
Thanks again for your help.
Wil.
Hi guys,
I got a situation. I just bought the lenovo K3 note from a guy and noticed he already installed SU, so I thought it's already rooted. Then I went to recovery mode and accidently deleted the OS without any backup recovery. Now i dont know what to do. The phone wont start since there is no OS installed. Any idea how i can install any rom on it.
Can somebody help me with that
http://forum.xda-developers.com/showthread.php?t=863209
Thread closed
I recently pulled my old Note 3 out of the drawer to do some misc tweaks, and think i screwed it all up...LMFAO!!!
Quick specs of phone...
Samsung Galaxy Note III (AT&T SM-N900A) 64gb (yes, i said 64gb and not 32gb)...but NOT why I am posting, so please don't even comment about it.
Steps that led to where I am...
First off I will say the device was originally rooted 4.3 back in 2013, and never updated since. Today I decided I wanted to update the phone to the last OS that worked perfect for a root, no i didn't just update it. I followed SuperSU's & TWRP instructions on first bringing the phone back to stock, didn't work and left me in recovery mode. Again, doubtful but may have been caused by me. So I was left with a wipe/restore because every time I attempted recovery via OneClickBin it would fail. After wipe/restore I was able to reinstall SuperSU and device was still rooted, obviously. So I attempted to completely remove root through SuperSU and it just kept getting stuck on spinning wheel. So then I attempted to reinstall TWRP and now I am stuck at the screen shown below in screen shots. Thanks in advance for any and all assistance, regarding this matter.
-Semper Fi
Oh yeah...and I'm a total and permanent disabled Veteran who doesn't have the ability to "go to AT&T store". So lets please try to fix this without going anywhere. Thanks again in advance.
Wrong forum you want the. A&TT note 3 forum .
Sent from my SM-N930F using XDA-Developers Legacy app
If the phone doesn't have a locked bootloader, you can try flashing back to stock with Odin and then run ota updates until the phone is running the latest stock ROM.
AT&T variant have a locked bootloader. You can't use TWRP or any other custom recovery.
Please follow this guide to fix your softbrick, root and update.
zlazaar said:
AT&T variant have a locked bootloader. You can't use TWRP or any other custom recovery.
Please follow this guide to fix your softbrick, root and update.
Click to expand...
Click to collapse
This was EXACTLY what I needed and worked flawless!! And I am so sorry for not responding sooner, as I have been in the hospital again.
DONE!! Thank You to those that helped!!
Hi all.
So it's been a while that I've rooted a phone (Note 4 years ago).
Getting a refurbished Note 8 very soon (UK).
I just want to root it and install only what's needed, without applying custom roms etc.
Just need it rooted for Titanium Backup, modded Google Play. Stuff like that.
Hope someone can help me in how I should go about it.
Also should I update the phone to 9.0 as soon as I boot it up?
Thanks.
Edit: Got the phone now. It took me to the home screen when first booted up. Looks like already updated to version 9. Does rooting still trigger KNOX?
skatlyup said:
Hi all.
So it's been a while that I've rooted a phone (Note 4 years ago).
Getting a refurbished Note 8 very soon (UK).
I just want to root it and install only what's needed, without applying custom roms etc.
Just need it rooted for Titanium Backup, modded Google Play. Stuff like that.
Hope someone can help me in how I should go about it.
Also should I update the phone to 9.0 as soon as I boot it up?
Thanks.
Edit: Got the phone now. It took me to the home screen when first booted up. Looks like already updated to version 9. Does rooting still trigger KNOX?
Click to expand...
Click to collapse
Yes rooting will trip Knox.
To flash TWRP just follow the steps in this thread - https://forum.xda-developers.com/t/recovery-official-3-3-1-x-twrp-for-galaxy-note8-exynos.3832962/ (just use the latest TWRP which is 3.5 I believe)
If you're just going to root stock filmware you will need to flash RMM/KG bypass or you will get locked out of your phone (only official filmware can be flashed error, then you will have to flash stock to fix it) - https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
If you are going to flash a custom rom they have the RMM state prepatched so this step would not be necessary. To flash a custom rom just follow the steps laid out in the OP of the rom you want to use.