No Sim detected after OTA Update - OnePlus 3 Questions & Answers

Ok, so theres a tiny bit more to the story
Did OTA update -->
Used the toolkit to flash twrp recovery and install superSU
now no sim detected
Any help would be appreciated

What version of SuperSU did you flash? For nougat you need SuperSU sr5 (just google it). You can just flash that and everything should be fine

Fixed
thank you

Phew!
stelio_kontos said:
What version of SuperSU did you flash? For nougat you need SuperSU sr5 (just google it). You can just flash that and everything should be fine
Click to expand...
Click to collapse
My brother from another mother, you just saved a panic attack. Had the same problem, your solution worked. Thanks! :good:

Related

m8 shows no root after update

after updating my m8 to lollipop, the device says unroot. software status is still unlocked, I went through the rooting process again,flashed twrp recovery. but cant install anything aa it says device is not rooted.
kalim_714 said:
after updating my m8 to lollipop, the device says unroot. software status is still unlocked, I went through the rooting process again,flashed twrp recovery. but cant install anything aa it says device is not rooted.
Click to expand...
Click to collapse
Hi there,
i have the same Problem.
after ota to 5.01 i rooted my m8 with toolkit , everything goes fine (also perm root and install superSu).
But after restart and automatical apps updates, the supersu app says that su files is missing and there ist no root anymore.
How can i solve that rpoblem? thanks alot
John
John-Wu said:
Hi there,
i have the same Problem.
after ota to 5.01 i rooted my m8 with toolkit , everything goes fine (also perm root and install superSu).
But after restart and automatical apps updates, the supersu app says that su files is missing and there ist no root anymore.
How can i solve that rpoblem? thanks alot
John
Click to expand...
Click to collapse
I've never used a toolkit on my HTC devices, so I can't speak to their effectiveness. Perhaps they need an update to work with Lollipop.
I recommend using TWRP recovery (just because it's the one I used and I know it worked for me. Can't speak to CWM or Philz)
Flash the SuperSU update zip found here: http://download.chainfire.eu/695/SuperSU/
craig0r said:
I've never used a toolkit on my HTC devices, so I can't speak to their effectiveness. Perhaps they need an update to work with Lollipop.
I recommend using TWRP recovery (just because it's the one I used and I know it worked for me. Can't speak to CWM or Philz)
Flash the SuperSU update zip found here: http://download.chainfire.eu/695/SuperSU/
Click to expand...
Click to collapse
hi,
thanks alot. that's it!!
with toolkit i've already installed TWRP and with the updated SuperSu (your link) i've root again.
once again, thanks!

[Q] Lost Root

Running N910PVPU4DPC1 [http://forum.xda-developers.com/note-4-sprint/development/rom-t3352832]
It's been running fine for the past month or so, then yesterday, I went to run Titanium Backup, and it said my phone no longer had root access.
---------------------------------------------
SuperSU
There is no SU binary installed, and SuperSU cannot install it. There is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
---------------------------------------------
I've tried to re-root via CF-Auto-Root, it'll complete without error, but still no root access.
Anyway I can get root back without blowing out and starting from scratch?
If you have recovery just flash SuperSU itself.
SaintZ93 said:
If you have recovery just flash SuperSU itself.
Click to expand...
Click to collapse
Thanks for your reply SaintZ93.
Just tried that via https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Uninstalled my previous version of SuperSU, booted to TWRP 3.0.2-0, no errors on install, fire up SuperSU, I get the same error message as before.
I was really hoping to get SU back with out having to go and reinstall everything. Doesn't look like it's going to work out that way.
Actually I just noticed the same thing, its quite weird, I lost root also. I had root working fine with PD1 now its gone.
I believe a security update was pushed, well at I know one was on my Sprint Note 4, and I think it auto installed that's what made me lost root.
I simply flashed supersu from TWRP and I had root again.
Don't know if this would help, but I turned off firmware updates on my phone and haven't had an issue for the last 3 days.
I think the update was pushed out on Tuesday or Wednesday because I noticed I didn't have root on Thursday.
krakerx said:
Running N910PVPU4DPC1 [http://forum.xda-developers.com/note-4-sprint/development/rom-t3352832]
It's been running fine for the past month or so, then yesterday, I went to run Titanium Backup, and it said my phone no longer had root access.
---------------------------------------------
SuperSU
There is no SU binary installed, and SuperSU cannot install it. There is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!
---------------------------------------------
I've tried to re-root via CF-Auto-Root, it'll complete without error, but still no root access.
Anyway I can get root back without blowing out and starting from scratch?
Click to expand...
Click to collapse
I believe that the SuperSu that comes with that ROM is systemless, which you would need to flash SuperSu 2.68
I am in the same boat.
ianmb said:
I believe that the SuperSu that comes with that ROM is systemless, which you would need to flash SuperSu 2.68
Click to expand...
Click to collapse
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
krakerx said:
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
Click to expand...
Click to collapse
Glad it worked for you
can I stall SUPERSU 2.68 with stock recovery? how?
I extracted the 2.68 zip but can I install without a custom recovery?
krakerx said:
That worked like a f'n charm!
I uninstalled SuperSU, downloaded SuperSU 2.68 [https://download.chainfire.eu/924/SuperSU], installed via TWRP, and verified!
Thanks for all the help!
Click to expand...
Click to collapse
Same issue of lost root. Worked great so far. Thanks for the info.
Sent from my SM-N910P using Tapatalk

Root 3.2.8 bootloop

Hi guys i really appreciate if someone could help me rooting my oneplus 3 stock from 3.2.7 to 3.2.8.
I've tried flashing full rom 3.2.8 over 3.2.7 and latest SuperSu but is not working.. i also tried to do a complete restore starting from 3.2.8 but it's the same result i get bootloop everytime.. also with phils supersu and magisk
The phone only boot on 3.2.8 if i don't have root.. i don't understand what's the problem, i really like to update the phone for the new features but aswell keep the root.
No error in the TWRP's log when you flash ?
I see that you're trying to flash magisk, but do you flash suhide 0.55 ? Suhide can be a reason of a bootloop
Thanks for the quick reply No error when i flash SuperSU or phh's.. Everything works fine till I reboot..
And no I didn't flash suhide
the_sider said:
Thanks for the quick reply No error when i flash SuperSU or phh's.. Everything works fine till I reboot..
And no I didn't flash suhide
Click to expand...
Click to collapse
what version of SuperSU, did you try the latest sr5?
I Tried sr4 and sr5... But got the same result... Maybe it's a security patch issue with latest update??
the_sider said:
I Tried sr4 and sr5... But got the same result... Maybe it's a security patch issue with latest update??
Click to expand...
Click to collapse
Super weird. Never had issues with Super SU on stock OOS.
I'm running Magisk v9 with phh SU magisk r266-2.
Used MagiskManager v2.5 to get Xposed up and running on OOS 3.2.8
Had same issue, asked on reddit and someone told me to try this:
BETA-SuperSU-v2.74-2-20160519174328-forced-systemless
and it worked
Are you using F2FS filesystem? It doesn't work well with root. Root disappears periodically like that.
AvivEliyahu said:
Had same issue, asked on reddit and someone told me to try this:
BETA-SuperSU-v2.74-2-20160519174328-forced-systemless
and it worked
Click to expand...
Click to collapse
i'm gonna try with that one!!
Tikerz said:
Are you using F2FS filesystem? It doesn't work well with root. Root disappears periodically like that.
Click to expand...
Click to collapse
yeah i was using ElementalX Kernel... i don't know if that was the problem.. but i don't think because i made a full restore of the phone with stock kernel
@AvivEliyahu
after a factory reset and flash 3.2.8 it worked.
I still don't know what was the problem but anyway thanks to everybody that tried to help me! cheers!!!

Updated to NMF26O, Lost Root

Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
cantsingh said:
Hey - followed this guide (https://matthewtraughber.github.io/pixel_manual-update_guide/) to update my rooted XL to NMF26O, lost root along the process. Flashing the SR5 supersu.zip didn't give me any errors in TWRP, but supersu isn't installed on boot. If I go into the Play Store and install it manually, I get an error about the SU binary not being installed. Any suggestions?
Click to expand...
Click to collapse
That update permanently block root for your device
cwalker0906 said:
That update permanently block root for your device
Click to expand...
Click to collapse
Even if I have an unlocked bootloader already?
cantsingh said:
Even if I have an unlocked bootloader already?
Click to expand...
Click to collapse
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
cwalker0906 said:
No I'm messing with you, many people have had this problem. Easy fix, read last few pages of root thread
Click to expand...
Click to collapse
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
cantsingh said:
Lol you terrified me. What's the fix? I'm looking for the root thread right now..
Click to expand...
Click to collapse
Fastboot boot twrp alpha 2, flash the su zip, and reboot
cwalker0906 said:
Fastboot boot twrp alpha 2, flash the su zip, and reboot
Click to expand...
Click to collapse
Got it. Thanks, buddy. I'll post back here to confirm.
Confirmed. If you lost root when updating to NMF26O (or after installing TWRP RC1), then hot-boot TWRP Alpha 2 (fastboot boot twrp-alpha-2.img), flash supersu and reboot. Thanks!
confirmed - worked for me!
cantsingh said:
Got it. Thanks, buddy. I'll post back here to confirm.
Click to expand...
Click to collapse
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
miker2069 said:
Confirmed, this saved my life
I had a Pixel XL that had 7.1 on it and rooted it successfully. Not sure when but my phone got updated to 7.1.1 I was careful not to take the update, maybe I inadvertently clicked it (I don't think so) but I think it got forced on me. So I ended up with 7.1.1. Tried using my hotspot which worked before and it didn't. Fortunately my device boot loader was still unlocked, but previous root technique using twrp-3.0.2-0-RC1-fastboot-marlin.img didn't work (seems like it does but after reboot, no joy). Figured if I flashed stock 7.1 image that would do the trick - no joy.
Found this post
Followed suggestion above and used twrp-3.0.2-0-alpha2-fastboot-marlin.img and used same SR5-SuperSU-v2.78 - reboot worked great. FYI, I downloaded the stock 7.1.1 (marlin-nof26v-factory-1dce14a1.zip) and rooting works with that.
Note: turn off "Automatic System Updates" (obviously that was probably the originally culprit) under developer options.
Click to expand...
Click to collapse
You fastboot twrp rc1 but then flash the twrp rc1 zip and then it should be fine and then flash SuperSU 2.79 sr3.

recovery is not seandroid enforcing

I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.
Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html
So you twrp 3.1.1 and it will work right
I having the same issue
Thank you
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself
Trwp
What version of twrp I need to use
Thank you
timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.
Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4
Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran

Categories

Resources