Related
I have S off by way of Rumrunner on an HTC One Verizon. I have TWRP as recovery and i am completely stock just S off and superuser. When i accept the OTA from Verizon it boots into recovery and TWRP pops up and i am stuck from there. I cant find the file to install and the phone wont upgrade. Please help. Thanks
lan04 said:
I have S off by way of Rumrunner on an HTC One Verizon. I have TWRP as recovery and i am completely stock just S off and superuser. When i accept the OTA from Verizon it boots into recovery and TWRP pops up and i am stuck from there. I cant find the file to install and the phone wont upgrade. Please help. Thanks
Click to expand...
Click to collapse
You need to be on stock recovery as well to take the OTA. Check the bottom of post 2 of this
mademan420 said:
You need to be on stock recovery as well to take the OTA. Check the bottom of post 2 of this
Click to expand...
Click to collapse
ok i flashed stock recovery and it accepted the OTA thanks....now how do i get superuser privileges back...it says i am missing the binary
lan04 said:
ok i flashed stock recovery and it accepted the OTA thanks....now how do i get superuser privileges back...it says i am missing the binary
Click to expand...
Click to collapse
i reinstalled TWRP and flashed superuser from TWRP recovery...all seems well now thanks...btw the stock files would not go into recovery it simply went to black screen and rebooted
You mist be new. Never take otas if you need to update after soff and root do so via flashing the rooted ROM of the newest update.
Sent from my One using Tapatalk
yes i am new and trying to learn...thanks for advice
So, am I correct in understanding that my phone will not take the OTA with twrp installed? As in nothing to worry about?
Is there any command I can run in terminal to make it stop asking if I want to install the OTA?
Sent from my stock (but rooted) VZW HTC One
BaBnkr said:
So, am I correct in understanding that my phone will not take the OTA with twrp installed? As in nothing to worry about?
Is there any command I can run in terminal to make it stop asking if I want to install the OTA?
Sent from my stock (but rooted) VZW HTC One
Click to expand...
Click to collapse
Just follow the 2nd post here, then reflash TWRP. The OTA doesn't break root.
Does Voodoo OTA Root keeper work on the HTC One?
Please delete if off topic!
edster00 said:
Does Voodoo OTA Root keeper work on the HTC One?
Please delete if off topic!
Click to expand...
Click to collapse
Yes, I just used Voodoo today to restore root after taking the .15 OTA. Will not work after 4.3, though (according to Google Play).
lan04 said:
i reinstalled TWRP and flashed superuser from TWRP recovery...all seems well now thanks...btw the stock files would not go into recovery it simply went to black screen and rebooted
Click to expand...
Click to collapse
I can confirm this works fine as well. I had S-OFF through rumrunner and had flashed TWRP. To take the OTA, I re-flashed the stock recovery (.10) from the link given in this thread, then took the OTA. After the OTA installed with no problems, I re-installed a recovery (I changed to CWM, just for fun). I tested it by booting into recovery, and when I rebooted from CWM, it asked me if I wanted to re-install root (su). The phone now has the OTA (.15), still has SOFF and root was easily recovered.
I flashed the .10 stock recovery and I'm getting an error when I try the ota, any ideas why? I followed these instructions and I end up with a red triangle with exclamation point the reboot and phone works fine. Thanks for any help.
Edit:I got the congratulations message but when I checked it says failed, error 410. I've downloaded it a couple of times.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?
Yep always PDA
Sent from my SM-P900 using Tapatalk
Worked! I now have rooted KOT49H.T900UEUAND4.
Good stuff
Sent from my SM-P900 using Tapatalk
OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?
JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.
JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great
The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!
S-off VZ M9. Still on 5.1 stock ROM. I was rooted with twrp installed. I have unrooted using Supersu. Checked with root checker and I am indeed unrooted. Rebooted. Flashed stock recovery. Rebooted.
I took the OTA, and while installing it fails with "Status 7 Error". I've searched for that but the fixes say to make sure I've done everything I've already done. Not sure what the problem is.
longboardskier said:
S-off VZ M9. Still on 5.1 stock ROM. I was rooted with twrp installed. I have unrooted using Supersu. Checked with root checker and I am indeed unrooted. Rebooted. Flashed stock recovery. Rebooted.
I took the OTA, and while installing it fails with "Status 7 Error". I've searched for that but the fixes say to make sure I've done everything I've already done. Not sure what the problem is.
Click to expand...
Click to collapse
I'd run 5.1 ruu to make sure you're on 100% stock. (Status 7 error usually means system was modified, most likely from rooting, even though you unrooted the system was still modified) That or use the 3.37.605.7_OTAPkg.zip from Santod040
Alright, so I flashed 3.37.605.7_FULL_firmware.zip from that thread using ADB. Everything seemed to be going well until I rebooted. Now I'm stuck on the red Verizon screen.
EDIT: By holding down the power/vol up buttons I'm able to get into HTC FTM mode. From there I am able to get into bootloader, recovery, and download modes. What should I do?
longboardskier said:
Alright, so I flashed 3.37.605.7_FULL_firmware.zip from that thread using ADB. Everything seemed to be going well until I rebooted. Now I'm stuck on the red Verizon screen.
EDIT: By holding down the power/vol up buttons I'm able to get into HTC FTM mode. From there I am able to get into bootloader, recovery, and download modes. What should I do?
Click to expand...
Click to collapse
RUU... then take the OTA...
http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397
longboardskier said:
Alright, so I flashed 3.37.605.7_FULL_firmware.zip from that thread using ADB. Everything seemed to be going well until I rebooted. Now I'm stuck on the red Verizon screen.
EDIT: By holding down the power/vol up buttons I'm able to get into HTC FTM mode. From there I am able to get into bootloader, recovery, and download modes. What should I do?
Click to expand...
Click to collapse
Download the rom he just posted. Copy to SD. Flash in twrp. You aren't booting because you mistakenly only just flashed the firmware. That's like doing half the ota.
Sent from my SM-T810 using Tapatalk
andybones said:
RUU... then take the OTA...
http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397
Click to expand...
Click to collapse
That's the old one. There's a 3.X one posted and also sync has the newest available as well already.
Sent from my SM-T810 using Tapatalk
So some might remember me awhile back ago... https://forum.xda-developers.com/pixel-xl/help/unlocking-verizon-bootloader-t3557290
I got tired of not having a unlocked/rooted device since I just dropped so much money on a new phone for my 27th bday sooo I took it back to verizon and swapped it for a new one. I was having the battery problems where my phone would hit 30-15% and just die on me OR the screen would die on me but the phone stayed on no problems.. I'd be in a phone call and the screen would shut off and I couldnt get it to turn back on without plugging in a charger or battery bank.
I've got my new phone now and everything is working flawlessly.. It's unlocked, has twrp installed and rooted just fine..
Now I remember seeing something about once I unlock/root the device my OTA becomes disabled so where do I get the OTA update for the device so I can go to 7.1.1 or later this month 7.1.2? I found this https://developers.google.com/android/ota and I see the 7.1.1 update but it's 800mbs which means I'm guessing if I flash that i'd be completely reinstalling a new copy of android and lose all of my data and have to go through setting up my phone again etc..
How do I just get the update itself and flash that? When I use the OTA on my Pixel XL the download is only like 200MB it doesn't install though just says it failed. Still new to all of this but I'm learning and how else am I gonna learn if I don't ask questions
a point in the right direction would be great.
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
wyrdtrtle said:
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
[QUOTE=
If you go to that link in the post above you can download the newest firmware. Unzip it and open the bat file with note editor or something like that and remove the -w and it will update without losing your data.
Dimmizer said:
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
Click to expand...
Click to collapse
You use your original link and sideload it with TWRP.
TonikJDK said:
You use your original link and sideload it with TWRP.
Click to expand...
Click to collapse
Thanks
Upper left corner Link to OTA's smaller
Sent from my Pixel XL using Tapatalk
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Dimmizer said:
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Click to expand...
Click to collapse
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
You did not decrypt it. That isn't currently doable.
TonikJDK said:
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Click to expand...
Click to collapse
Doing what you said now
[
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
I wouldn't unroot with that, doesn't work all the time just flash the newest firmware and you will be unrooted. You are going to have a bad time if you do.
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Hit the link below, it explains it well and you will see it worked for others.
https://forum.xda-developers.com/pixel-xl/help/rooted-twrp-recovery-how-update-ota-t3524279
If you ever bootloop don't freak, its an unlocked google phone. Flashing back to stock is easy.
The only thing that was in question was the bootloader unlock, once its unlocked your safe. It wont relock unless you lock it. But, if you do lock it, its locked for good. Afaika
Sent from my Pixel XL using Tapatalk
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Dimmizer said:
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
Click to expand...
Click to collapse
I flashed OTA with twrp on my buddy's pixel for the Feb update worked just fine. Just make sure it's the OTA and not the factory image. But the best way would be using fastboot
Most anything you flash (stock updates, custom roms, will overwrite recovery. But not a problem, you just re-boot it to flash it, or just boot it and flash su and reboot device.
Sent from my Pixel XL using Tapatalk
awesome , thanks again everyone for your time and the help, very much greatly appreciated.
As the title says is it possible to root, install modifications to stock ROM and is there a fast way to revert everything is something go wrong? I'm asking because support for 5X has ended, and I can't permanently unlock bootloader. I don't want to hard brick this phone by mistake and also I don't want just look how this device is being wasted.
So here's some probably noob questions that I want to ask:
1. Can I install TWRP on NO RPMB bootloader and boot it without issues? If so, how?
2. What recovery version should I install 4-core or regular 6-core?
3. Can I root device and hide it with magisk?
4. If an security update appear how to install it since stock recovery is replaced with TWRP?
5. If something go wrong like 2nd death loop how to revert everything? Can I simply flash stock system image in TWRP to "fix" device?
Thanks in advance.
You might try the solution the user in this thread suggested, https://forum.xda-developers.com/nexus-5x/help/rpmb-bootloader-locked-t3481906/page2
So I have to unlock bootloader, then flash TWRP, Super SU, compatible Magisk in one attempt, then I'm ready to go? Will TWRP boot and work like nothing happened?
Sent from my Nexus 5X using XDA Labs
I haven't tried it but based on the steps I would think it should work. It won't hurt anything. It also won't stop the bootloader from locking upon a reboot. But as long as you can unlock it prior to flashing any of the partitions as the reddit thread suggests you could be ok.
Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels
Banan PL said:
Locked bootloader won't allow to boot custom kernels that's sure, but will it boot modded stock kernels from this thread https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169 since they're stock kernels
Click to expand...
Click to collapse
I'm running custom kernels just fine with locked bootloader.
CazeW said:
I'm running custom kernels just fine with locked bootloader.
Click to expand...
Click to collapse
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).
Banan PL said:
So there's still hope, cool! Are there any side effects (will Jolla's multiboot and drivedroid work)? What if device suddenly stop working? Flashing stock image doesn't count since we have locked bootloader, so what to do if CPU die again? I prefer to have an emergency plan just in cause. You made my day. With locked bootloader we can't boot customs, right, just asking because it was possible on my Xperia J.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Haven't tried Jolla's multiboot or drivedroid. As long as you can get into fastboot, you can just unlock it again and flash stock (though you will obviously lose everything that's on the device). Haven't tried flashing custom ROMs but as custom kernels are working, I don't see why custom ROMs wouldn't.
negusp said:
As long as TWRP is installed and "stuck" (ie: boot directly into TWRP after flash), you can basically flash anything (custom ROMs/kernels etc.).
The worst thing that can happen is that you brick the ROM without TWRP installed and the ROM is bricked/the oem unlock flag is reset (not tripped). Even then there's a .tot file somewhere here on XDA that can recover the phone.
I'm assuming that an upgrade to O is also possible via stock images (unlock bl, flash stock images, boot into O, trip the OEM unlock flag, unlock BL and follow the steps described).
Click to expand...
Click to collapse
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
In short unlocking bootloader JUST allows to flash system images in fastboot, nothing more nothing less? So if I flash TWRP then Lineage it will boot and work like nothing happened (like on 5X with unlocked bootloader), it's sounds so good that I can't even believe.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't own a device without RPMB (I got a fairly new refurb), but I've used TWRP/flashed ROMs and kernels successfully with the bootloader locked and TWRP installed.
Alright I'll flash TWRP take nandroid and hopefully device will boot. Can someone give me link to 4-core TWRP, I can't find it?
Sent from my Nexus 5X using XDA Labs
Google 4 core twrp 5x xda. It's in that thread. https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?
Banan PL said:
Strange I can't flash recovery it's getting replaced by stock. TWRP shows a message, but I'm unable to read it. It appear for a while then device reboot into system.
It says something like "Renamed stock recovery file to /system to prevent the stock ROM from replacing TWRP" or something like that. Any help?
Click to expand...
Click to collapse
Did you unlock and then without rebooting flash the TWRP?
CazeW said:
Did you unlock and then without rebooting flash the TWRP?
Click to expand...
Click to collapse
I've unlocked bootloader then flashed TWRP and rebooted into recovery
Banan PL said:
I've unlocked bootloader then flashed TWRP and rebooted into recovery
Click to expand...
Click to collapse
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?
CazeW said:
Did you then do a factory reset and flash root? That should make it stick. If not, you can always just use the TWRP app to get into TWRP when needed.
Edit: You also booted to recovery straight from fastboot after flashing, without rebooting the phone?
Click to expand...
Click to collapse
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.
Banan PL said:
This is what I've done: unlocked bootloader, format data in fastboot, flashed twrp, rebooted into twrp. Here device keep rebooting into system and replacing twrp with stock recovery.
Click to expand...
Click to collapse
So you are not actually getting into recovery at all. Try with different TWRP image.
CazeW said:
So you are not actually getting into recovery at all. Try with different TWRP image.
Click to expand...
Click to collapse
I tried with regular TWRP 4-core modded TWRP and with Multiboot TWRP. Same result.
Sent from my Nexus 5X using XDA Labs