Database Develop

[Q] can't get Cyanogenmod working

I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1

adrazar said:
I'm new to using non stock ROMs and have heard good things about the Cyanogenmod and wanted to give it a try. I rooted my phone using Super One Click, I installed Clockworkmod to install the ROM and backup my settings, then I got the stable version of Cyanogenmod for my phone HTC Hero CDMA (update-cm-6.0.0-Heroc-signed.zip). I then followed the steps from the WIKI I updated the Radio, wiped my phone's data, then the cache, I selected the ROM to install from the root directory of my SD card, let it run through then told it to reboot the system. thats where the problem shows up it comes to the first HTC screen and will just sit there forever I even tried leaving it on overnight. I tried to flash it with different versions of Cyanogenmod and all had the same result, however I was able to get a version of damagecontrol to flash correctly on my phone so I know its not a brick.
I have searched quite a few posts but have not found anything that helps I have tried wiping multiple times and even wiped Dalvik cache. I ran a logcat to see if it might help me debug whats going on and it appears to be looping through the same things over and over I rebooted it again and had the same results. I can supply any info needed from the logcat needed but not sure what parts might help.
the different versions of ROMs I have tried to use are:
update-cm-6.0.0-Heroc-RC1-signed
update-cm-6.0.0-Heroc-signed
update-cm-6.1.0-RC1-Heroc-signed
Also tried Cyanogenmod nightly 87, 95, & 99
fresh-cdma-hero-1.1
DamageControlv2.08.1
Click to expand...
Click to collapse
try this:
using a rom that works flash a new recovery image using ROM Manager (find it in the market)
Tell ROM Manager to flash the recovery for ClockworkMod 2.5.0.1
Then Reboot to recovery.
**********NANDROID FIRST!!*********
Starting the flash:
1. Choose the "Wipe data/factory reset" then click "wipe cache partition"
2. Choose "install zip from sdcard" and choose "choose zip from sdcard"
3. Pick the zip file with the CM6 make sure it completes and the installer confirms that it is complete.
4. Reboot phone. This might take more then 5 mins on the initial boot, when it boots up all the way and everything has loaded, do one more reboot to clear out the cache from the initial boot and you are good to go
**If this doesnt work for you, follow step one, select a DIFFERENT ROM, reboot, then reboot into recovery, then wipe again, and flash back CM6.

I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.

adrazar said:
I tried this, I already had Rom Manager installed but checked to make sure it was all up to date, flashed it to 2.5.0.1 and rebooted to recovery. I wiped the data and cache and installed the CM6 and rebooted with teh same results of it being stuck at the HTC screen and logcat showed it cycling through the same actions over and over, I then tried to just reboot it and it did same thing. I then wiped and installed a different ROM (the Damage Control one) and it worked fine got all the way booted up. I then rebooted to the recovery manager again, wiped and reinstalled with the CM6and had the same results as the first time. out of curiosity I even tried installing the damage control and then installed CM6 without the wipe and it still did not work.
Click to expand...
Click to collapse
Find a new download of CM6, the one you downloaded was corrupt, try finding the thread, its in Development so find the extreme blue or redglass version.

I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.

Does anyone know what those error messages could be caused by or a way to get around this issue?

adrazar said:
I tried both the Extremely Blue CM6 Build (EXTBLUE_09NOV.zip) and the Red Glass CM6 Build (REDGLASS_09NOV.zip) that I got from the development area, a poste named
[ROM] (UPDATED 09-NOV) FroYo 2.2 - CM6 Extremely Blue, BlackMod, Red, Purple, Vanilla
the results as far as it looks are exactly the same as when I tried the other ROMs. I know two lines that kinda stand out to me in the endlessly repeating messages I get from logcat are:
E/dalvikvm( 326): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 326): Unable to process classpath element '/system/framework/framework.jar'
I'm not fully sure if these are the issue or if it is just random information about it failing to load the ROMs.
Click to expand...
Click to collapse
adrazar said:
Does anyone know what those error messages could be caused by or a way to get around this issue?
Click to expand...
Click to collapse
What recovery are you using?

I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid

adrazar said:
I use Rom Manager (clockwork mod) for installing the ROMs and its currently flashed to version 2.5.0.1 to recover my phone to the way it was before I flashed to to the cyanogenmod I use nandroid
Click to expand...
Click to collapse
That's probably the problem, try the 1.7 Darch RA, much better IMHO

Also ive noticed sometimes when I download a rom onto my computer for some reason it doesnt download the whole file correctly. So just make sure that when you download your rom to your computer the the size of the file is correct.If the rom is 50 mb make sure your download is the same.

I found a post that I believe I got that one from (RA-Darchstar.img) but it is an img file and i am having trouble getting that to install. i found another post elsewhere telling me to use commands from the SDK, it said to use
cd C:\android-sdk-windows\tools
adb devices
adb shell
flash_image recovery /sdcard/RA-Darchstar.img
exit
adb shell reboot recovery
which seems like it should work however when I do the flash_image recovery /sdcard/RA-Darchstar.img it tells me that the flash_image cannot be found. is this the wrong command line? and i do have the file on my phone's SD card in the root directory. or is there another way to get the 1.7 Darch RA?

never mind on my last question I figured it out, I wasn't in the Recovery program I already had when trying to do it. I got the 1.7 Darch RA on and working then tried to flash some of the ROMs again and every one of them failed with the same logcat errors as before.

Try backing up ur SD then taking out ur SD and formatting it on ur CPU then put it back in ur phone and format it threw the recovery I have a 28 MB swap and the rest for the system them go to ext and upgrade/update ur ext from ext2 to ext3 then try and flash CM6.1 hope this helps good luck.
Root-Hack-Mod-Always™

I formatted my card via the computer, formatted everything that RA-Darchstar will let me format, I then set up the partitions and upgraded to ext3, and then copped the CM6.1 to the phone and installed it (also tried EXTBLUE_09NOV). the end result was the same as each other time I have tried to install any of them CM6 ROMs.

Ok I ended up getting it to work by following some of the things I read on
http://forum.cyanogenmod.com/topic/...-cm-build-but-cm-6-nightly-tests/page__st__20
the part where they told this other person to extract the framework.jar to the PC and point adb to it.

The Very Corrected CM7 & Stock 1.2 Dual Boot Guide

Hello Nookers,
I myself and pndo1 of XDA have posted guides for dual booting CM7 and Stock 1.2. My first one was crappy, my second one was a little less crappy, and pndo1's was pretty good, but had too many steps. So yeah, I decided to clear this up once and for all. Alright, enough of that garbage, let's get on with the guide!
0. Make a CWM sd card using these instructions.
1. Download CM7 to your sd card. I recommend the latest version from here. Also, if you would like to overclock download this. Lastly, if you would like to remap Volume + and - to Menu and Back, download this too. Also, your gonna want (duh) have a copy of Nook Color Stock 1.2. This one is the best in my opinion. Also, if you would like to root Stock 1.2, get this. Now get gapps from here. Almost! Download thishere. And now the multiuboot! Grr... this is tiring... but lasties! Get it here. Put ALL the files you downloaded on your SD Card.
1. Boot into CWM. Go into Backup+Restore and create a backup. Then go into Mounts+Storage and unmount the sd card. Put in an MicroSD reader in your computer. Navigate to /sdcard/clockworkmod/ and find the backup. Copy it to your computer. You can now delete it from the SD Card. Put the SD Card back in the nook. Go into Mounts+Storage and hit "Mount sd card" Now from the same place, wipe system, data, and cache. Now go to the root menu (hit the power button once). Hit "Install zip from sd card" then "Choose zip from sd card" Select prep.dualboot.zip. Then redo the choose zip Select your downloaded 1.2 Zip. It should be called "update_nc_stock_1.2_keepcwm.zip" Flash that. Now wait for it to install. Reboot your Nook. It will boot and will ask you to setup the Nook. Set it up but if you don't have wifi, follow these instructions. After setting up, boot back into CWM using your sd card.
2. Now Choose the zip from sd again, but select ManualNooter. That will take one minute to flash. Reboot again. Make sure your root is setup. To confirm, download an app from the market. Any app.
3. Once that is done, boot back into CWM. Flash the zip "eclair-to-dualboot-0.2.zip" It will duplicate Stock 1.2 to the Second partition. Now go into Mounts+Storage, and wipe system+data+cache. Now choose zip again, but this time pick CM7. Then Choose again, pick GAPPS. Then anything else, like that KeysMod or OC kernel. Now flash Multi-Uboot-0.3.zip. Now reboot without holding anything. It should boot CM7. Reboot, but this time hold the home button. BAM! Stock 1.2. Hope it worked for ya!
To those whom it doesn't work:
yelloguy said:
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
Click to expand...
Click to collapse
Credits:
@GirLuvsDroid for the feedback and testing
@GabrialDestruir for 1.2 Manual Nooter
@Koush for ROM Manager and CWM Flashes
@yellowguy for telling us to flash prep.dualboot
@Anyone else who helped but escapes my mind at the moment
@pndo1 (Who has moved on to better things than our little NC's... aka Flyer) for this orignal project

I've been wanting to dual boot my NC for a while now, but I've read several sets of instructions and kept getting twisted up in them. I was also concerned that having a dual boot would make it difficult to impossible to continue installing the CM7 nightlies and the latest Dal kernels.
These instructions look really clear and easy to follow and I thank you for that!
I just want to clarify my understanding: both CM7 and stock 1.2 are run from eMMC, correct? And, because stock 1.2 is on the second partition, it's just business as usual to install the nightlies and the latest kernel on the first partition, right?
Again, thanks for taking the time to rework your instructions again. Your contributions are much appreciated!

Why a special uboot? Stock cm7 uboot (based on bn 1.2) already does multiboot... (hold down n on boot for info) and dalingrin's nook tweaks lets you set up default options from prefs menu...
That said, I didn't read the instructions carefully so maybe there's a reason...

@GirLuvsDroid Your welcome, and yes both run from the emmc. Flash nightlies and kernel like anything. Just nothing to the dual boot partition.
@fattire For me the CM7 Alternate boot option hangs. But again, that's me.

I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.

MHotovec said:
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
Click to expand...
Click to collapse
MH, it's the link in the OP that says this: "Last one (yes, really!) here." It's not the Multi-Boot-Uboot-0.3.zip but the eclair-to-dualboot-0.2.zip.
Disgregard this post -- I'm an idiot and apparently blind, as well.

Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.

MHotovec said:
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
Click to expand...
Click to collapse
I must be blind -- I don't see where it says to flash both. I only see the eclair-to-dualboot in the instructions.
Nevermind -- I found it. It's the last step. I stand corrected and I'm glad I do because I'm planning to do this when I get home from work tonight. Thanks for setting me straight!

Reflashing the eclair to dualboot wasn't the answer, now is doesn't even TRY to boot the stock 1.2.
Now where did I leave that drawing board....

I found the download link for the Multi-Boot-Uboot-0.3.zip:
http://api.viglink.com/api/click?fo...dified u-boot.bin based on B&N 1.2 source

GLD, if anyone tells you that you're not a goddess, you tell them that I said you are.
Of course, that didn't solve the problem. (sigh)
I ran the entire routine again, and this time used the v.03 multi-boot that you found, same problem. It will boot into CM7 just fine, but it hangs up when booting into stock.

ahhhhhh, that's just so sweet, MH!
I just went through the whole process myself and everything went perfectly right up until I tried to boot into stock 1.2. Exactly like you, it hangs on the N and won't boot up. CM7 boots just fine, though.

Well, at least I know it's not just me.
By any chance, have you run the app that changes your Nooks RAM from 'new way' to 'old way'? (1gb data, 5gb apps).
I have, I wondering if that has something to do with it (just fishing of course, it's not like I actually KNOW anything).

Yes, I had a blue dot NC that I repartioned, but I did it using the custom partition (around 2GB data).

Well, multi-boot link added.

Oh, to those whom it doesn't work (stuck on N), try flashing 1.2 zip and manual nooter without rebooting and then eclair2dualboot then wipe system,data, and cache. Then flash cm7 and goodies. Not one reboot. Try it and only then say if it works or doesn't.

I'll try this no-boot method when I get a chance tomorrow. One question for you -- assuming I get this to work, is there any reason I can't restore /data from the CWM backup of my original setup that I made before I started the dual boot process?

I get the same result with the no boot method. CM7 boots fine, Nook stock hangs on the 'N' screen.

I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.

@GLD Yes, I think you can restore safely.
@yellowguy You don't need prep dual boot because eclair2dualboot already takes care of that. And if my instructions didn't work, try yellowguys, a slightly refined method.

t679 HELP! stuck in boot-loop after root-stock.zip install

grabbed root-stock.zip and cwm just below it (first 2 links on this page http://forum.xda-developers.com/showthread.php?t=1686384 ) carefully followed instructions, even watched videos on youtube and everything went swimmingly except after system reboot following root-stock.zip install. i must have grabbed the wrong file (dont know how, it was recommended by everyone on every other thread regarding the rooting of the t679) anyway now i need assistance, which root.zip file should i use? how do i get it onto the phone's internal "usb storage" folder? or can i use another device to grab file, transfer to ext. sd, then put ext. sd card into t679? i understand its critical at this point to make no mistakes, i believe i can recover, assuming i get competent advice...
please advise...
- zCHEMDAWGz
p.s. i am attempting to repair wifi and bluetooth errors (assuming its the drivers not loaded properly following system update 2.3.6) though im not certain of the culprit of these errors as i am the 4th owner of this device. assuming an internal battery has NOT leaked onto circuit board causing corrosion, pretty sure its software not hardware issue. phone/sms/network WAS connecting just no wifi/bluetooth. gotta have wifi cuz im out in the woods on the "EDGE" network, home network is fast as can be.

In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app

Dvarl said:
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
hey thanks for helping me i really appreciate it. so i tried your advice, in every order possible. fix permissions, wipe (everything), load rom, reboot... wipe, load, fix, reboot... to no avail though. all results in same loop... im getting good at wiping and loading =)
also the location of the rom and cwm files prior to transferring to "usb storage" folder was "downloads" on my windows 7 pc... does this make a difference? i have noticed people saving these types of files to their desktop... just trying to find out where i went wrong... thanks again.
- zCHEMDAWGz

SIDE NOTE: i tried loading different rom "t679-root-v1.8.zip" with exact same results... however i noticed that when i load either version of the new rom when cwm begins installation, and when the progress bar at the lower part of the screen shows about 2-3% complete it is then all of the sudden finished with "complete" confirmation at the end. total time less than 5 seconds. according to instructional videos this process should take minutes, instead of seconds.... just an observation.
- zCHEMDAWGz

That's just root not a ROM. If your willing to start fresh you can try this.
Wipe everything x3
Under mounts and storage mound system and data then format both x3
Flash rooted community rom
Reboot
It should work. If you flash any recent ROM make sure you have the latest cwm or you will get status 7 error.
Sent from my SGH-T679 using XDA Free mobile app

success!! wifi/bluetooth still getting error though... tried *#*#526#*#* (wlantest engineering mode) reports "Notset Driver Loaded [NG]"
any ideas?
a-thousand thank yous
- zCHEMDAWGz

Issue with installation of rom with temporary cwm recovery by shaaan

I am having issues with the installation of a Custom ROM on my Galaxy S Advance.
I have done it before, and it went smoothly. But later I reverted back to official one.
Now I am doing it again. But having a few problems with the CWM recovery (v6.0.2.8). I am having an old file which was probably uploaded by Shaaan.
The file name is "update.zip".
I tried downloading the new file from one of his new threads, but that download infected my laptop with a large number of viruses, malwares and adwares that were on the host site. So I am using the old file itself.
So the issue is, I used the "root.zip" file to root my phone and it was done successfully as the Root Checker app also verified the root.
Later, I booted using the CWM Recovery.
Did the Wipe Data/ Fatory Reset.
Did Wipe Cache Data.
Did Wipe Dalvic Cache.
Then I moved to Installation of ROM.
When I select the option, "CHOOSE ZIP FROM SDCARD", there comes an error saying...
"E: Can't Mount /sdcard/"
I browsed the internet and found a solution that said CHANGING THE FILE SYSTEM OF THE SDCARD. So I did that too. Tried with NTFS as well as FAT32, but nothing happened.
I even tried to install by placing the ROM files in Internal Memory since they are not even getting cleaned after Wipe Data operation. But that too resulted in negative.
This is happening every time. By now, I have installed the official firmware 4 times, so as to start the process afresh, but no luck.
The ROM files are also not corrupted, as I have used them earlier.
Here are the images of the issue I am encountering. (Please tell how to upload images, as all that I can see is an option to add URL and not an image, also an error like posting 10 posts)
EXPECTING A SOLUTION TO IT ASAP, as the Official Jellybean version has again started to lag too much.

Correct root and TWRP recovery for OOS 4.1.6 on OP3T - please.

I've been all over the OP3T forums looking for current information about the correct versions of TWRP and (Magisk or SuperSU) to use with stock OOS 4.1.6. I kept my old TWRP 3.0.4-1 and when I tried to apply SuperSU 2.79 SR3 I got an unusable system and had to restore from nandroid backup. I updated to TWRP 3.1.1-2 as per the Official TWRP app and now every time I try to reboot to system from TWRP it warns "No OS installed", but the reboot works fine. I have Magisk 13.2 ready to install but I'm reluctant until I know I have the right combination - the TWRP 3.1.1-2 backup is missing some partitions and I want to make sure I can at least recover my system if Magisk screws things up.
I've been all over the forums and all the relevant threads were closed months ago, or are written about OOS 4.0.3 or 4.1.1, or describes some hideous way someone turned their 3T into a pile of molten lava. Is there any current information about what combination of TWRP and a root zip will work with the latest OOS 4.1.6? Everything is stock except the unlocked bootloader. I don't want to flash a different ROM, I don't care about passing SafetyNet, I just want to root and go on with my life.
A couple of numbers is all I ask. I can't be the only one. Please - I've been without root for a week and it's bugging me.

TWRP 3.1.1-2 has got at least one major bug where it reports the OP3T as a OP3. That'll mess up your OP3T specific installations... Don't know if there are any other bugs, since I'm staying on 3.1.1-0 until they fix that bug. You also have the option of using blu_spark's TWRP. I've never tried it, but many users swears by it.
What works for me:
OOS 4.1.6
Franco Kernel r25
TWRP 3.1.1-0 (official)
Magisk v13.2
Magisk Manager 5.0.6
No issues whatsoever (for me)...

Thanks for that. I'd rather not change kernels, though. How likely is it that the same combination works with the stock kernel? Does anyone have that running?

OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?

OK, I tried it. Swiped the Magisk 13.2 zipfile in TWRP. The script ran partway through and then said "Can't mount system" in red letters. Now the phone boots into OOS, Magisk Manager is there and says "Rooted but no root permissions, not allowed?" It has reported several times that it needs to update, to the same version of Magisk and Manager that are already there. I allowed it to go through the cycle and reboot, with no change to behavior. When I try to run an app that needs root I get the permissions screen, but when I grant I get the dialog that says "Rooted Android required" - Either the su binary could not be found or you did not allow root permission..."
So, the phone works fine but unprivileged as before. I'd like to try clearing the cache, but since TWRP still reports no OS found (3.1.1-0 does this, just like -2) I don't really want to write into a system the recovery can't see. Besides, the existence of the su binary doesn't seem like something a cache clear will fix.
Advice?

Scratch that request. Things seem to be turning around - su works in terminal emulator, lets me ls privileged directories like /data. Root Explorer is working again. The only thing that isn't is AdAway, which can't write the hosts file. Otherwise the system seems to be rooted and working OK.
I'm still nervous that TWRP can't see that there's an OS on the phone, and I haven't seen any other reports of this.

It looks like Magisk can't mount /system read-write. Adaway won't install, and neither will Busybox. Titanium Backup also reports problems. I tried installing Busybox and the installation failed when it tried to remount system /rw.
Will look for solutions to this problem and report back here.

I've found many solutions to this problem, like installing busybox (Stericson Busybox apparently doesn't work in OOS 4.1.6, tried two others. Problem is, busybox will only install into a partition on /system, which requires that /system be read/write.

When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...

JMB2K said:
When I have issues with mounting system or anything like that, I go mount system myself in TWRP and it usually starts working after I reboot....I don't know why, it just works for me....if I see that error, that's the first place I go, everytime...
Click to expand...
Click to collapse
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.

mobilityguy said:
That won't work either. When I go to the Mount page in TWRP I can't get the checkbox next to /system to check. It just stays empty.
Click to expand...
Click to collapse
I seem to remember having that problem once before.... Can't recall what I did, I think it involved something with the terminal... I'm not at my desk right now, I'll look into it shortly and see if I can remember

Problem solved. The more I looked at the symptoms, the more I realized that the OTA I took after unrooting with SuperSU corrupted the system partition somehow. The first time I tried applying the OTA with the stock recovery it failed, but I was able to reboot and apply 4.1.6. That's when the trouble began - I was unable to reapply SuperSU. Fortunately I had done a nandroid backup between the upgrade and the attempt to re-root, and after the SuperSU script failed I was able to restore the backup (made and restored using TWRP 3.0.4-1) and continue working. It was either at that point or earlier, during the OTA itself, that /system was damaged - not badly enough to prevent the phone from working perfectly well, but enough to keep TWRP from mounting /system read/write. From that point on I was doomed. None of my other attempts to fix the problem had a chance as long as TWRP was restricted to mounting /system read-only. Then it got worse.
After a semi-failed attempt to install Magisk (rooted applications worked as long as they didn't try writing to /system) I restored my pre-root 4.1.6 backup one more time. After that, TWRP wouldn't mount /system at all, which prevented me from making any more nandroid backups.
It was time to act. I could keep using the phone unrooted, but the longer I went on the more work would be required to put things completely right. The risk would increase because I couldn't take any more snapshots of the phone to fall back to if I munged the device again. I also had a positive reason to fix things - during the two days the phone was rooted but couldn't access /system, Titanium Backup kicked in and did a full backup of all my software and settings.
With a damaged file system and full backups, there was no reason for halfway measures. I copied all my user data off the phone and used LloydSmallwood's unbrick tool to flash the phone back to its original OOS 3.5.4 state. That took care of rebuilding all file structures. As soon as I rebooted, OOS upgraded to 4.1.6 in one step, taking care of the system upgrade. Unlocked the bootloader, installed TWRP 3.1.1-0 (not 3.1.1-2, which has a serious bug for the 3T as someone posted above). I was able to mount and unmount /system from TWRP's mount screen, no problem. Ran Magisk 13.3 script without a problem, installed Titanium Backup, and tested an app restore. No problem. I'm now in the midst of copying all my stuff back onto the phone, after which I'll restore all missing apps and be back in business (I hope).
It's possible I could have done something tricky like reformatting /system and restoring the partition from my last good nandroid backup. But I always would have been concerned that problems would have popped up later, maybe during the Android O upgrade, when it would be way too late to recover my then-current setup. After seeing virtually every combination of working and non-working features, it just made sense to build from a clean system.
So thanks have been given to LloydSmallwood for his absolutely indispensable unbrick tool (this is the second time it has saved my phone). I should also thank my Galaxy S3, running the current build of LineageOS, which has gotten me through the two days it took to set my OnePlus straight. The Galaxy has performed better than a five year old phone running brand-new software should ever be expected to - if it supported LTE I could consider using it as a daily driver. This has been an education, and a reminder of how important it is to keep good backups at every step throughout an upgrade - and routinely during production use.
Thanks to all who gave advice in this thread.