Related
I've been away for a while, and I'd like to update my M8. My phone says that I am currently on build 4.4.3. I am rooted, and unlocked. I wondered.....are there any special steps that I need to take, to get up to current build/ROMs? If so, I would very much appreciate it if someone would be so kind as to give me some steps.
Thanks in advance!!
ddodge68 said:
I've been away for a while, and I'd like to update my M8. My phone says that I am currently on build 4.4.3. I am rooted, and unlocked. I wondered.....are there any special steps that I need to take, to get up to current build/ROMs? If so, I would very much appreciate it if someone would be so kind as to give me some steps.
Thanks in advance!!
Click to expand...
Click to collapse
Latest TWRP 2.8.6
schneid said:
Latest TWRP 2.8.6
Click to expand...
Click to collapse
I'm currently on Team Win Recovery Project v2.7.1.0. It's been a long time since I messed with my phone much. Can you tell me how/where I update to the current version?
ddodge68 said:
I've been away for a while, and I'd like to update my M8. My phone says that I am currently on build 4.4.3. I am rooted, and unlocked. I wondered.....are there any special steps that I need to take, to get up to current build/ROMs? If so, I would very much appreciate it if someone would be so kind as to give me some steps.
Thanks in advance!!
Click to expand...
Click to collapse
Hit the link in my signature below. Good place to start.
ddodge68 said:
I'm currently on Team Win Recovery Project v2.7.1.0. It's been a long time since I messed with my phone much. Can you tell me how/where I update to the current version?
Click to expand...
Click to collapse
For starters I posted a 5.0.1 firmware zip in tigerstowns firmware thread that actually contains the latest twrp all in one shot. Then there are many roms you can chose to flash. Take your pick but get firmware updated first. Make sure you do the one with twrp 2.8.5 included. Older twrp on new firmware will cause you some pretty bad issues.
dottat said:
For starters I posted a 5.0.1 firmware zip in tigerstowns firmware thread that actually contains the latest twrp all in one shot. Then there are many roms you can chose to flash. Take your pick but get firmware updated first. Make sure you do the one with twrp 2.8.5 included. Older twrp on new firmware will cause you some pretty bad issues.
Click to expand...
Click to collapse
Any chance you could link me, so I avoid getting the wrong file? Thanks for the help!!!
ddodge68 said:
Any chance you could link me, so I avoid getting the wrong file? Thanks for the help!!!
Click to expand...
Click to collapse
This is the firmware zip.
https://www.androidfilehost.com/?fid=95916177934537898
dottat said:
This is the firmware zip.
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
I'm really sorry for asking all of these questions. So that I don't brick my phone...I just put this zip file on my ext storage, and flash it using the current twrp? Or maybe you've got complete directions in a post, somewhere? Thanks again, very much, for the help!!!
ddodge68 said:
I'm really sorry for asking all of these questions. So that I don't brick my phone...I just put this zip file on my ext storage, and flash it using the current twrp? Or maybe you've got complete directions in a post, somewhere? Thanks again, very much, for the help!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Not for flashing via twrp.
HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks
Disregard the message.
Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg
All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?
Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L
I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
thanks! Ah OK I see so that's the whole ROM there as opposed to just an update
davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse
The file I quoted is not a whole ROM, it's 31 MB.
AH OK, sorry I thught you referred to the 500mb file
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
I'm having the same issue. Anyone?
Got the same problem. Any idea?
duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?
Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
its ok you can, but make sure you have Stock recovery installed not the TWRP
ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
shashank1320 said:
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
Click to expand...
Click to collapse
Not necessary!
You just have to flash stock recovery!
gaebzn said:
Not necessary!
You just have to flash stock recovery!
Click to expand...
Click to collapse
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
shashank1320 said:
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
Click to expand...
Click to collapse
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
gaebzn said:
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
Click to expand...
Click to collapse
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
shashank1320 said:
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
Click to expand...
Click to collapse
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
gaebzn said:
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
Click to expand...
Click to collapse
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Thank you mate!
shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
gaebzn said:
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
Click to expand...
Click to collapse
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
RedSkull23 said:
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
Click to expand...
Click to collapse
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
gaebzn said:
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
Click to expand...
Click to collapse
You may try uninstalling the busybox and then retry to see if it works.
I rooted following Maxwell's tutorial (OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk
).
Now that all is said and done, and my phone is rooted, I noticed that:
1) The wifi does not work. It will not let me enable wifi. Just keeps switching back to off.
2) The speakers don't work.
I need to know how to fix it. What do I do?
I am new to android so I am not sure the steps needed to fix this botched install/operating system/root whatever
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
download
Bradl79 said:
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
Click to expand...
Click to collapse
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
jfny100 said:
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
Click to expand...
Click to collapse
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Bradl79 said:
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
Click to expand...
Click to collapse
Okay. That was it (flashing the wrong boot.img) It's working now - I upgraded to latest OS. Downloaded correct boot.img. Redid the root process with correct files this time, and it worked. Wifi is good. Speakers are good. Everything is good. Thanks for the help. Also, I removed any criticism of the tutorial creators in my post since it turns out I was the idiot. I'm brand new to android though so go easy on me.
djsubterrain said:
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Click to expand...
Click to collapse
I didn't read the post until after I encountered errors. I was going off of the video. One problem I had was that the video assumed I had a basic knowledge of some steps, so they didn't mention them. I did not have this knowledge since I am brand new to android. Anyways. I was able to fix these errors via the steps discussed in earlier comments. Everything is working now. I removed any criticism of the tutorial creators from this post since it turns out I'm the idiot.
Glad you got it working
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
BC that is just an extra step not really needed, I haven't even flashed twrp on my device yet, if I need it I will just boot to it, it's so much easier doing this.
I always thought the same thing u did, until I just flashed the patched boot and updating is so much easier too.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
Because I'm just following along with the tutorial xda put on YouTube and that's what they say to do
Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best
The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
henschn3435 said:
Hey Everyone,
I'm looking to try LOS 19.1 for the first time on my new OP8T.
I always see TWRP as a suggestion for the best custom recovery, but on the download page "twrp-installer-3.7.0_11-0-kebab.zip" is the file name. I'm confused, as the 11-0 means it's for Android 11, but I saw that TWRP 3.7.0 is supposed to support Android 12.
Can I use TWRP for installing LOS 19.1 on Android 12 or should I use the LOS-recovery?
And if I do, can I still use Magisk (on their page they say to use TWRP)?
Sorry for this newbie question. Thanks in advance!!
All the best
Click to expand...
Click to collapse
3.7.0 is recovery release version and 11-0 means it's for Android 11.
BillGoss said:
The official TWRP doesn't support A12.
Use the unofficial one from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
Click to expand...
Click to collapse
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
It works on both the 8T and the 9 9R. If you want to be sure try to boot into it before flashing.
Dior DNA said:
The download link in that unofficial one forum OP presents a lemonade (Oneplus 9) TWRP...
Am I missing something? @BillGoss : do you have the download link for an OOS12 supported Oneplus 8T TWRP (that preferably can make (and restore) backups since Orangefox one can't make backups (it errors))?
Click to expand...
Click to collapse
TheNewHEROBRINE said:
It works on both the 8T and the 9. If you want to be sure try to boot into it before flashing.
Click to expand...
Click to collapse
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).
BillGoss said:
If you look at the title of that thread you'll notice that it says "TeamWin Recovery Project (8T / 9R)".
So, yes, it's for both the 8T and 9R (lemonades) but not the 9 (lemonade).
Click to expand...
Click to collapse
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
Can you share the full log?
TheNewHEROBRINE said:
Can you share the full log?
Click to expand...
Click to collapse
sure, give me another day ...I just deleted the Orangefox and TWRP directories
Dior DNA said:
OK thanks ! lemonade versus lemonades ... I did not know about this subtle name difference
The recovery image boots indeed. I would like to make backups...
Unfortunately the backup (of LOS 19.1) fails with similar message as Orangefox with:
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
Thanks all! One should perhaps forbid files under /data/fonts/files/ ... After deleting those, I could finish both (unofficial) Orangefox and (unofficial) TWRP backup just fine. Agreed, this does not 100% prove ERROR root cause but sure does consistently correlate. So now maybe one should harden custom recovery images to avoid the trap, especially since the trap seems to be a known one by some people (like @BillGoss).
BillGoss said:
That happens if you have files under /data/fonts/files/, but you would need to check the recovery.log to confirm that is what's causing the problem.
Click to expand...
Click to collapse
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?
Rootk1t said:
BTW, do you know the reason why files inside fonts/files folder prevent backup process from going?
Click to expand...
Click to collapse
No, I never understood what the problem was with those files.
BillGoss said:
No, I never understood what the problem was with those files.
Click to expand...
Click to collapse
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?
Rootk1t said:
When installing ota zips from TWRP, оne should restore stock boot and recovery because checks are inside ota zips?
Click to expand...
Click to collapse
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.
BillGoss said:
Correct, but only in incremental updates.
But I don't think the current TWRP can process OOS incremental updates - the last time I tried I got an error.
Click to expand...
Click to collapse
BillGoss said:
Flashing OTA zips - both full and incremental. Note: incremental OTAs need stock boot and recovery installed so make sure you flash these before starting the install, otherwise it will fail.
Click to expand...
Click to collapse
Has something changed from your post?
Rootk1t said:
Has something changed from your post?
Click to expand...
Click to collapse
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.
BillGoss said:
Lol! I think I'm going senile!
Given that I tend to test before making statements like the one you quoted, I'd say that that is correct for the 1-4 version of TWRP.
But it may not be true for 1-5 as I've found some issues with it (eg, fastbootd doesn't work) and I've not fully tested flashing otas with 1-5.
Click to expand...
Click to collapse
Thanks for letting us know
Rootk1t said:
Thanks for letting us know
Click to expand...
Click to collapse
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
I wanted to test using TWRP to install an OTA zip on OOS 12. The first time I tried I got an error because it was expecting the current version to match those of C.33 but they didn't - even though I was on C.33. So I used `resetprop` to set the proper values and then it sort of worked, but still gave errors.
I was using the latest version (1.5 or 220827) of TWRP.
Click to expand...
Click to collapse
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.
BillGoss said:
I went hunting and I found the conversation where I flagged the problem with flashing OTAs on the latest TWRP (on the TWRP development site):
And now I'm wondering how correct my statement about flashing OTAs working on the previous version. I'll have to do some more digging to see if I can find solid proof of OTA working on TWRP 12 v1.4.
Update: I found where I tested flashing OTAs on TWRP 12. That was back on 220805. That was before 1.4 came out (220818). But I didn't expect that this function would get broken, so I never actually tested on 1.4.
Click to expand...
Click to collapse
So as i understood correctly flashing OTAs in TWRP is broken on v1.4 and works on prior versions?