Related
Hi, All -- I rooted my Google Play Edition Galaxy S4 using Chainfire's method, and it's now generating an error when it tries to install the OTA update to Android 4.3. I've unrooted the phone using SuperSU and have wiped it, but it still won't install the OTA.
Can anyone help?
Thanks, Alan
carrot34 said:
Hi, All -- I rooted my Google Play Edition Galaxy S4 using Chainfire's method, and it's now generating an error when it tries to install the OTA update to Android 4.3. I've unrooted the phone using SuperSU and have wiped it, but it still won't install the OTA.
Can anyone help?
Thanks, Alan
Click to expand...
Click to collapse
Have you re-locked the bootloader?
gee2012 said:
Have you re-locked the bootloader?
Click to expand...
Click to collapse
Ah. No, I haven't. I didn't realize that was necessary, and I'm searching now and not finding instructions on how to do that. Can you point me in the right direction?
Thank you!
Alan
carrot34 said:
Ah. No, I haven't. I didn't realize that was necessary, and I'm searching now and not finding instructions on how to do that. Can you point me in the right direction?
Thank you!
Alan
Click to expand...
Click to collapse
Look here for how to http://forum.xda-developers.com/showthread.php?t=2363025. For locking the BL type: fastboot oem lock.
carrot34 said:
Hi, All -- I rooted my Google Play Edition Galaxy S4 using Chainfire's method, and it's now generating an error when it tries to install the OTA update to Android 4.3. I've unrooted the phone using SuperSU and have wiped it, but it still won't install the OTA.
Can anyone help?
Thanks, Alan
Click to expand...
Click to collapse
If you rooted using CF-AutoRoot then it's likely your recovery was replaced. You need to flash the stock 4.2.2 recovery in all likelihood.
To be sure, what error does the screen show when you try to install the OTA. That will help us diagnose what isn't passing the OTA pre-check.
I have same issue here trying to update OTA update. Device rooted and bootloader unlocked.
When trying to install 4.3 OTA update, it rebooted into TWRP and start flashing but twrp mentioned some files not found and aborted, didn't even get a chance to look at the errors. After boot back up, it still show 4.2.2 and checking system update doesn't say new update found anymore.
tublah said:
If you rooted using CF-AutoRoot then it's likely your recovery was replaced. You need to flash the stock 4.2.2 recovery in all likelihood.
To be sure, what error does the screen show when you try to install the OTA. That will help us diagnose what isn't passing the OTA pre-check.
Click to expand...
Click to collapse
Thanks so much for helping with this. The screen just says "error." Is there any way I can get more information? And if flashing stock 4.2.2 recovery is what I need to do, how would I do it?
Thank you!
Alan
carrot34 said:
Thanks so much for helping with this. The screen just says "error." Is there any way I can get more information? And if flashing stock 4.2.2 recovery is what I need to do, how would I do it?
Thank you!
Alan
Click to expand...
Click to collapse
No problem. Go to this thread http://forum.xda-developers.com/showthread.php?p=43500355 and follow the steps, but try at first only doing the step that flashes recovery. Can you take a photo of your screen? What recovery are you using to flash the OTA?
tublah said:
No problem. Go to this thread and follow the steps, but try at first only doing the step that flashes recovery. Can you take a photo of your screen? What recovery are you using to flash the OTA?
Click to expand...
Click to collapse
Thanks, but there isn't any thread listed there. Could you try posting it again?
I can get a screen shot of the error message, but it will take a little while. All it says is "Error!"
Thanks, Alan
carrot34 said:
Thanks, but there isn't any thread listed there. Could you try posting it again?
I can get a screen shot of the error message, but it will take a little while. All it says is "Error!"
Thanks, Alan
Click to expand...
Click to collapse
I updated my previous post. If you really want fool-proof working 4.3, you can follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2388504 and just ODIN the full stock 4.2.2 and then try to apply the upgrade.
tublah said:
If you rooted using CF-AutoRoot then it's likely your recovery was replaced. You need to flash the stock 4.2.2 recovery in all likelihood.
Click to expand...
Click to collapse
This. I was stuck on this for a while. You first need to make sure you have stock recovery. I also had to reflash a new system IMG but the recovery was a big problem.
OK, I followed the instructions to re-lock my bootloader, which seems to have been done successfully, but I'm still facing the same error (as seen in the attached photo). So I guess I need to flash the stock recovery. I'm game to try the Heimdall approach or the ODIN approach that have already been suggested, but I wonder if there's a simpler way to do this. Based on what I read here, it sounds like I could just download stock recovery from here, and then just type these commands to flash it:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Does that approach make sense? And sound safe? Or would I be better off going down the ODIN or Heimdall roads?
Thank you all for your help in navigating this!
Alan
carrot34 said:
OK, I followed the instructions to re-lock my bootloader, which seems to have been done successfully, but I'm still facing the same error (as seen in the attached photo). So I guess I need to flash the stock recovery. I'm game to try the Heimdall approach or the ODIN approach that have already been suggested, but I wonder if there's a simpler way to do this. Based on what I read here, it sounds like I could just download stock recovery from here, and then just type these commands to flash it:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Does that approach make sense? And sound safe? Or would I be better off going down the ODIN or Heimdall roads?
Thank you all for your help in navigating this!
Alan
Click to expand...
Click to collapse
Its worth a try. Not sure but you might have to he unlocked to flash stuff.
Sent from my Nexus 10 using XDA Premium HD app
tublah said:
Its worth a try. Not sure but you might have to he unlocked to flash stuff.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
OK, that didn't work. I get a "Secure check failed" message.
tublah said:
No problem. Go to this thread http://forum.xda-developers.com/showthread.php?p=43500355 and follow the steps, but try at first only doing the step that flashes recovery. Can you take a photo of your screen? What recovery are you using to flash the OTA?
Click to expand...
Click to collapse
OK! Thank you all for the help. This Heimdall method fixed me up and let me install the 4.3 OTA without a problem. (The ADB commands I mentioned in the previous post not only didn't work, but left me with a phone that wouldn't boot!) Next step is to figure out how to re-root...
Alan
carrot34 said:
OK! Thank you all for the help. This Heimdall method fixed me up and let me install the 4.3 OTA without a problem. (The ADB commands I mentioned in the previous post not only didn't work, but left me with a phone that wouldn't boot!) Next step is to figure out how to re-root...
Alan
Click to expand...
Click to collapse
This is basically what I followed to re-root after 4.3. Worked fine. You're just booting to CWM recovery temporarily to install the SuperSU update. Then it will revert back to stock recovery.
ack154 said:
This is basically what I followed to re-root after 4.3. Worked fine. You're just booting to CWM recovery temporarily to install the SuperSU update. Then it will revert back to stock recovery.
Click to expand...
Click to collapse
Thanks! Can you share the instructions you followed to do that?
Alan
carrot34 said:
Thanks! Can you share the instructions you followed to do that?
Alan
Click to expand...
Click to collapse
Crap, forgot the link. Sorry. Here you go:
http://forum.xda-developers.com/showthread.php?t=2365555
ack154 said:
Crap, forgot the link. Sorry. Here you go:
http://forum.xda-developers.com/showthread.php?t=2365555
Click to expand...
Click to collapse
Awesome!!! That worked great and very easily. Thank you so much!
Hey guys I could really use some help...I have twrp recovery but unfortuunately when i try to flash stock recoveryy back, it will not change. I have tried fastboot, nexus toolkit by wug, flashify, image flash gui, etc. Do you guys have any suggestions? Thanks so much!
Are you still unlocked or did you relock?
sfhub said:
Are you still unlocked or did you relock?
Click to expand...
Click to collapse
I am still unlocked
I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img
sfhub said:
I don't think twrp recovery has the option to restore recovery (or I might have missed it last time I looked)
Are you doing
fastboot flash recovery stock-recovery.img
Click to expand...
Click to collapse
Yea i did that put recovery.img in platform tools folder and executed the command....its almost like the recovery is flashed permanently...cant even flash cwm
Did you enable usb debugging in developer options before trying to flash recovery?
geckocavemen said:
Did you enable usb debugging in developer options before trying to flash recovery?
Click to expand...
Click to collapse
yes i did that...have you guys tried it? maybe its just a problem for everyone idk
slamdunksaliby said:
yes i did that...have you guys tried it? maybe its just a problem for everyone idk
Click to expand...
Click to collapse
Ive tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?
chuck313 said:
Have tried to reflash the stock recovery image and ended up with the same problems, anyone able to reflash the stock recovery after flashing twrp?
Click to expand...
Click to collapse
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol
slamdunksaliby said:
I even did a factory reset and still its sticking....i even tried to rename recovery-from-boot.bak back to .p and still nothing
I guess ill just flash cleanrom for now since the recovery is here forever lol
Click to expand...
Click to collapse
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.
TG2708 said:
I had a similar problem flashing the one that has "for razor" in its name. Found a different one and it worked fine.
Click to expand...
Click to collapse
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot? If you could maybe link the working one that would be much appreciated
slamdunksaliby said:
interesting mine was from one of the stickies above...but ive tried multiple recoveries too...did you use fastboot?
Click to expand...
Click to collapse
Yes i did use fastboot.
TG2708 said:
Yes i did use fastboot.
Click to expand...
Click to collapse
Hmm well if you could link to the working one that would be greatly appreciated I like twrp no doubt but i feel like this recovery may not even be updatable let alone changed if I ever needed to
update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great
slamdunksaliby said:
update: after some testing It looks like the stock recovery file in the sticky above is actually twrp recovery...if someone can upload the real stock recovery file that would be great
Click to expand...
Click to collapse
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.
Thank you so much I'll let you know! Ah it looks like the stock kernel is in the last one too that's good..hopefully sometime soon we can get factory images to make things easier haha
geckocavemen said:
I've found three recoveries floating around on the forum so far. Two are in this thread -- one is in the first (1st) post under the "recovery" subtitle and the second is in the seventh (7th) post.
The other one is in this post. You have to download the Nexus_7_Restore_F.zip file and unzip it. Once you do that you will find a recovery.img file in it.
Hope one of these works. My bet is the last one will at the very least. Let us know how it turns out for you.
Click to expand...
Click to collapse
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).
minazaki said:
I tried flashing all of the above. With the third one (contained within the Nexus_7_Restore_F.zip), when I reboot to recovery, I get the Android with the red exclamation mark, no go. So I manually flashed TWRP back. It seems that until we get an official factory image from Google (if ever), we're stuck on TWRP. Unless there's something I haven't considered.
Click to expand...
Click to collapse
That is what you are supposed to see.
Please see this post for instructions:
[Info] Guide to entering safe mode, bootloader, stock recovery
geckocavemen said:
Unless I'm mistaken the Android with a red exclamation is what you should see if you have the stock recovery installed...which means it was successful. At that point there is some combination of buttons that must be pressed to restore the recovery but I don't remember what it is (I think it might be Vol up + Power but I don't know for certain so I wouldn't try that until someone else confirms it).
Click to expand...
Click to collapse
sfhub said:
That is what you are supposed to see.
Please see this post for instructions:
Info] Guide to entering safe mode, bootloader, stock recovery
Click to expand...
Click to collapse
Oh right. I actually knew that too. Been so long since I had seen stock recovery.
Model : SGP312
Android: 5.0.2
Market: Germany
Build : 1273-3719_10.6.A.0.454_R2E
Included:
- UPDATE-SuperSU-v2.46.zip
Rom is prerooted but XZDualRecovery isn't working for TabZ with Lollipop at the moment so it's not included, check this thread for news about it : http://forum.xda-developers.com/showthread.php?t=2261606
Flash this zip from 4.4.* recovery and you're done
https://mega.nz/#!YFlihZoa!qR87H4kkVdE9GEG5kkxJ59-EBlc6CdsimqKgNJRJoTw
Thanks a lot for this... Any chance to have and md5 so as to make sure it has been downloaded correctly?
botsaris said:
Thanks a lot for this... Any chance to have and md5 so as to make sure it has been downloaded correctly?
Click to expand...
Click to collapse
Sure : MD5 Sum is 2245197dac0a7388d7f2f2b3ae63c26a
Tried twice but its not booting.....
*justintime* said:
Tried twice but its not booting.....
Click to expand...
Click to collapse
For me everything went fine...First boot takes while.
I know first boot takes a while. But its not booting at all. Screen stays off and i can only enter fastboot. But never mind. I while take a different route
Does it work with locked Bootloader?
redsk1n said:
Does it work with locked Bootloader?
Click to expand...
Click to collapse
yes, it's stock rom with stock kernel
Confirmed working.
Thank you!
Problem...
I think I did something wrong.
Flashed in PhilZ, installation (Rom and SuperSU) worked fine.
Selected "Reboot now" afterwards.
Now it's dead.
Nothing on power on, no fastboot, no flashmode...any suggestions?
DatFrosty said:
I think I did something wrong.
Flashed in PhilZ, installation (Rom and SuperSU) worked fine.
Selected "Reboot now" afterwards.
Now it's dead.
Nothing on power on, no fastboot, no flashmode...any suggestions?
Click to expand...
Click to collapse
Try VOL+ Power to reset it.
Thanks!
That actually did the trick.
I guess the tablet was stuck in some sorta weird power-state.
Tried it once, but probably held the buttons down too shortly.
Managed to get it to flash once, the three times.
Got into flashmode from there, everything running fine on 5.0.2 stock atm.
I guess next step is to root it
Thanks again man.
DatFrosty said:
Thanks!
That actually did the trick.
I guess the tablet was stuck in some sorta weird power-state.
Click to expand...
Click to collapse
This happens if tablet hangs with screen off.
hi, currently i'm in jb 4.3 with cwm installed..
Can I upgrade directly via cwm? thanks!
duke_dreadmoore said:
hi, currently i'm in jb 4.3 with cwm installed..
Can I upgrade directly via cwm? thanks!
Click to expand...
Click to collapse
Yes you can. But this ROM on 1st post doesn't contain recovery, so you will have to install .zip with it via CWM too.
Hi everyone.
Can I update from official kitkat with this rom?
My device is rooted but that's all. No recovery or unlocked bootloader. SGP311.
If it's possible how can I do that? Can I keep my data and apps?
Thanks.
bobo1425 said:
Hi everyone.
Can I update from official kitkat with this rom?
My device is rooted but that's all. No recovery or unlocked bootloader. SGP311.
If it's possible how can I do that? Can I keep my data and apps?
Thanks.
Click to expand...
Click to collapse
without root and recovery no way to update.
Can anyone post a new link to the zip file? Mega no longer is hosting the file
Thanks in advance.
Rassilon7 said:
Can anyone post a new link to the zip file? Mega no longer is hosting the file
Thanks in advance.
Click to expand...
Click to collapse
Hi, I should update my post with new build 10.7.A.0.22 (android 5.1.1) tomorrow
Thank you, that's very kind.
After i boot in twrp with n preview asking a password for decrip device. I cannot install any kernel,need change anything?
You need to flash a modified boot.img for it to be able to decrypt properly, there's a link in section 2 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
There is an updated TWRP that you can flash that is able to read/write and doesn't ask for a password.
Heisenberg said:
You need to flash a modified boot.img for it to be able to decrypt properly, there's a link in section 2 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I try but stuck in twrp first screen.
matheus_sc said:
After i boot in twrp with n preview asking a password for decrip device. I cannot install any kernel,need change anything?
Click to expand...
Click to collapse
Disable forced-encryption, and decrypt your 6P first. Here is my tutorial: http://www.droidorigin.com/decrypt-nexus-6p/
Once you have, you can flash TWRP easily.
matheus_sc said:
I try but stuck in twrp first screen.
Click to expand...
Click to collapse
What version of TWRP are you using?
Heisenberg said:
What version of TWRP are you using?
Click to expand...
Click to collapse
3.0.0.1, without format user data/decrypt, i cannot flash any kernel?
I made flash a kernel with flashfire app now all fine here.
I'm stuck too. What should I do? Did you figure it out?
Drewski_1987 said:
I'm stuck too. What should I do? Did you figure it out?
Click to expand...
Click to collapse
It is an issue with TWRP right now. It wouldn't work until you have disabled forced-encryption and decrypted your device.
Here is what you could do: http://forum.xda-developers.com/showpost.php?p=66354239&postcount=746
So does twrp work at all with the n previews? How does one root the previews without twrp? Looking at installing the fourth one, but I'm not willing to lose root.
I accidentally let the OTA try to update from Preview 3 to 4. It stuck on the TWRP splash screen 3.0.2-0 (I think). It didn't seem to fail or anything but it just would never go past that splash screen. I was being dumb, updating without access to a C to A cable so I thought I was screwed but I decided to try something else out. I hit the BP Tools button on the Bootloader menu and for some reason that booted my phone up like normal. I then tried to see if I could boot it up normally. No luck, same TWRP splash screen. BP Tools worked again, but I know its some developer setting and I don't want to mess with anything that could mess me up later. Does anyone know how to get past the TWRP screen? Also anyone know why BP Tools would boot but the regular boot wouldn't work? I guess this is what I get for being a dumbass. I knew I shouldn't but I get so damn excited about updates!
Thanks a lot.
51D7H3K1D said:
I accidentally let the OTA try to update from Preview 3 to 4. It stuck on the TWRP splash screen 3.0.2-0 (I think). It didn't seem to fail or anything but it just would never go past that splash screen. I was being dumb, updating without access to a C to A cable so I thought I was screwed but I decided to try something else out. I hit the BP Tools button on the Bootloader menu and for some reason that booted my phone up like normal. I then tried to see if I could boot it up normally. No luck, same TWRP splash screen. BP Tools worked again, but I know its some developer setting and I don't want to mess with anything that could mess me up later. Does anyone know how to get past the TWRP screen? Also anyone know why BP Tools would boot but the regular boot wouldn't work? I guess this is what I get for being a dumbass. I knew I shouldn't but I get so damn excited about updates!
Thanks a lot.
Click to expand...
Click to collapse
Same issue for me. Stuck on the splash screen with both 3.0.2-0 and 3.0.1-0.
Im here in N preview 4 also stuck on TWRP splash screen
Edit: i guess is because im encrypted
matheus_sc said:
I try but stuck in twrp first screen.
Click to expand...
Click to collapse
Drewski_1987 said:
I'm stuck too. What should I do? Did you figure it out?
Click to expand...
Click to collapse
DJBhardwaj said:
It is an issue with TWRP right now. It wouldn't work until you have disabled forced-encryption and decrypted your device.
Here is what you could do: http://forum.xda-developers.com/showpost.php?p=66354239&postcount=746
Click to expand...
Click to collapse
if you have a backup (titanium or nandroid), or don't mind starting from scratch you can make TWRP work with DP4 by:
fastboot erase cache
fastboot erase userdata
There's got to be a way to get around the encryption problem without decrypting the phone...
Would this work: when twrp asks for passcode to decrypt, say skip. Then take the SuperSU zip from my computer and put it on my phone via USB, and flash it from twrp.
Would it work even though twrp can't read my storage?
If your phone is encrypted, the only twrp that works is 3.0.0.0
You can use it to adb sideload supersu zip and root the phone. But won't be able to mount my partitions as it cant decrypt the phone.
Sent from my Nexus 6P using Tapatalk
asj0422 said:
So does twrp work at all with the n previews? How does one root the previews without twrp? Looking at installing the fourth one, but I'm not willing to lose root.
Click to expand...
Click to collapse
Look for CF Auto Root. This worked for me without TWRP on DP4.
mochamoo said:
Look for CF Auto Root. This worked for me without TWRP on DP4.
Click to expand...
Click to collapse
So you're encrypted and rooted on dp4? I might have to try that then...
asj0422 said:
So you're encrypted and rooted on dp4? I might have to try that then...
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 6P using Tapatalk
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
It's not just you.
TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
ME too. TWRP installer for sure.
Tulsadiver said:
ME too. TWRP installer for sure.
Click to expand...
Click to collapse
Installing SuperSU from the RC1 img or installing RC2 and then installing SuperSU from there?
Looks like I'll wait on May factory images ...
sliding_billy said:
Installing SuperSU from the RC1 img or installing RC2 and then installing SuperSU from there?
Click to expand...
Click to collapse
After booting into TWRP, flashing twrp pixel installer, then trying to boot back into TWRP bootloops without even getting to supersu.
The reasons to stay stock, are starting to out weigh the reasons to root.
Tulsadiver said:
After booting into TWRP, flashing twrp pixel installer, then trying to boot back into TWRP bootloops without even getting to supersu.
Click to expand...
Click to collapse
Gotcha. That stinks! I have never booted back into TWRP after installing. I have just went straight to SuperSU installer after RC2 install. I imagine that would have just created a different issue.
sliding_billy said:
Gotcha. That stinks! I have never booted back into TWRP after installing. I have just went straight to SuperSU installer after RC2 install. I imagine that would have just created a different issue.
Click to expand...
Click to collapse
They will probably figure something out. Nexus 5X didn't have any problems with their May update.
Tulsadiver said:
They will probably figure something out. Nexus 5X didn't have any problems with their May update.
Click to expand...
Click to collapse
I'm sure. I am in no hurry for what is most likely just a security update.
Sideloading the correct image now. Pisses me off there is a separate image for Verizon. I flashed the Verizon version instead of the standard one.
---------- Post added at 04:42 PM ---------- Previous post was at 04:35 PM ----------
Loaded the May images on the 5x. Magisk is good to go for the 5X. Pixel is stock right now.
Glad I came here before installing the May update.....
TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
CatThief said:
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
Click to expand...
Click to collapse
Both
CatThief said:
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
Click to expand...
Click to collapse
Tulsadiver said:
Both
Click to expand...
Click to collapse
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Misterxtc said:
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Click to expand...
Click to collapse
Works for me. Thanks Misterxtc!
Misterxtc said:
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Click to expand...
Click to collapse
How did you do that?
UPDATE: Problem solved...
Swerner1975 said:
How did you do that?
UPDATE: Problem solved...
Click to expand...
Click to collapse
If you didn't figure it out or anyone else needs help I downloaded both the K and L updates, installed L, rebooted to bootloader and ran the following command with the K bootloader then reboot bootloader. After that you can install TWRP and root.
Code:
fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126
Misterxtc said:
If you didn't figure it out or anyone else needs help I downloaded both the K and L updates, installed L, rebooted to bootloader and ran the following command with the K bootloader then reboot bootloader. After that you can install TWRP and root.
Code:
fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126
Click to expand...
Click to collapse
THX!
If you flash manually you just skip the first step. The bootloader part.