Related
i used the cyanogenmod perm root which told me to push the new version of clockwork mod threw the adb. but i want to downgrade so i can use some bad ass font packages.. it wont let me threw clockwork mod so does that mean i have to push the older version threw adb to get ti to work?
thanks
orangezx10 said:
i used the cyanogenmod perm root which told me to push the new version of clockwork mod through the adb. but i want to downgrade so i can use some bad ass font packages.. it wont let me through clockwork mod so does that mean i have to push the older version threw adb to get itto work?
thanks
Click to expand...
Click to collapse
This is where it's going to get tricky. the older 2.5 Recovery images are designed for 2.2 ROMs, which are EXT3 based. Our Cyanogen(mod) ROM is 2.3.x, which is EXT4. The older recovery images might make things harder than it should be.
The easiest thing to do in your case would be to download Absolute Tools from the market, it is a paid app, and I use it to flash fonts. It works AMAZINGLY well, and has alot of other root tools that are really nice. 1) boot images, 2) fonts 2) ability to back up .apk's and 4) a root explorer.
as far as to answer your question. YES you will have to find an older version of Clockwork ROM recovery image, flash it either via ADB or in the fastboot screen.
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?
Get full root without get any bootloop, restart problem while mounting system..
actually i m not a owner of the scripts/apps used in this procedure, i m just sharing here..
all credits goes to original developer of towel root and reboot mount fix...
REQUIRED FILES:
Towel Root.apk
RemountReboot Fix by Abrar9322
STEPS:
First you need adb in pc..if you dont have or dont know what it is please install from here http://forum.xda-developers.com/showthread.php?t=2588979
Install towel root and execute it, then reboot.
Install latest SuperSU from playstore
Open supersu and click yes to install binary
Now Install latest busybox from playstore
Now open busybox and follow below according to ur device
For devices[C1904,C1905,C2004,C2005,C2104,C2105],install busybox in system/xbin[default]
For other devices,install busybox in sytem/bin[change it in busybox while installing busybox]
Copy remountrebootfix.zip anywhere on your computer and extract it.
Open the extracted folder and run install.bat
select option 1( SuperSu ) then press enter.
It asks you to connect your device.
Now Connect your mobile with usb debugging enabled...[Note: if you don't know how to enable usb debugging, click below to show the content]
go to settings > about phone > press on the build number 7 times until it says 'you are now a developer'
Go to settings>developer options>USB debugging.
Grant Root permission when prompt in your phone.
Follow on screen instruction.
Device will reboot, then enjoy full root with locked bootloader...!!!!
SPL Thanks to @geohot, @Snoop05, @mbc07 , @Abrar9322, @ananthtcr....
and if i didnt give credit to anyone..please pm or post here...i will add
or if this is already posted...or if i violated any rule of xda...moderators please remove this thread..
Reboot problem? what is that?can you explain more to me? i also root using towelroot but when i'm restarting my phone, it keep rebooting.. its the problem from towelroot?
BlueSky_Vincent said:
Reboot problem? what is that?can you explain more to me? i also root using towelroot but when i'm restarting my phone, it keep rebooting.. its the problem from towelroot?
Click to expand...
Click to collapse
r u used folder mount or gl2sd or link2sd??
if no, then try... you will get bootloop or restart problem...
actually reboot problem happens when we mount system partion...
so to fix this issue, we should apply reboot fix given by our xda developers....
ananthtcr said:
r u used folder mount or gl2sd or link2sd??
if no, then try... you will get bootloop or restart problem...
actually reboot problem happens when we mount system partion...
so to fix this issue, we should apply reboot fix given by our xda developers....
Click to expand...
Click to collapse
I have link2sd but im not sure whether i mount system or not. When im trying to restart the phone, it keep rebooting. Im flashing a ftf and after that, my phone cant boot up without connecting to the power source. Im already sent to service center but the say that is not battery problem. Can you help me?
Su Binary not installed , and cant install it !
SuperSu ..
I can’t get root on Acro S JB :/ , why ?
I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.
Mlight123 said:
I have a SM-T337A that I rooted with Kingroot, after which I installed Super-SU, then rebooted it and was soft-bricked. If anyone can help me, it would be much appreciated.
Click to expand...
Click to collapse
Sadly, I just joined your club!! lol I wanted to comment here incase anyone else can help us or if I manage to figure it out myself I can find this thread easily. I got it rooted with newest version of Kingroot too, then I used Supersume to update to SuperSU and everything was working fine. When I tried rebooting, same thing as you I presume, I get kernel is not se enforcing I think it said and got the dreaded Unauthorized software was found running on this device, please take to att for service.
Sorry I can't help with your current problem. But, did you ever try to reboot with the kingroot SU?
This is definitely a slippery slope with no installation image.
moonbutt74 said:
Reboot to recovery, connect to pc and via adb shell , do a manual unroot.
that usually consists of
adb shell mount /system
adb shell rm /system/xbin/su
adb shell rm -fr /system/bin/.ext <----.ext is a directory
adb shell ls -al /system/bin/app_*
lrwxrwxrwx root root 2014-06-30 09:42 app_process -> /system/xbin/daemonsu
lrwxrwxrwx root root 2014-06-30 09:42 app_process32 -> /system/xbin/daemonsu <---remove this symlink
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process32_original <---- rename to app_process32
-rwxr-xr-x root shell 73508 2008-08-01 08:00 app_process32_xposed <------ not there if you don't have xposed
-rwxr-xr-x root shell 13588 2008-08-01 08:00 app_process_init
Then search /data/app /system/app and /system/priv-app and remove the offending apk's base directory.
m
Click to expand...
Click to collapse
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?
Mlight123 said:
This is an answer to someone who had done the same thing as us, his question is on the same page.
Can anybody give more detailed instructions to this? And will it even help our situation?
Click to expand...
Click to collapse
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Shocked...
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.
Mlight123 said:
So... Despite what Klown80 said.. I flashed boot(LP_fix).tar from "Rooted NK2 AT&T t337a w/ Tutorial" and it booted right up but I noticed some thing the first time it booted, the unlocked custom logo was gone, and so it went through the normal boot, but it didn't get stuck at the AT&T logo, it booted to the lockscreen. So I preceded to uninstall everything root related, so that if it does get bootlooped I can take it to the store and hopefully get it restored and they have no proof of what I was trying to do, via going into SuperSU and uninstalling, then I deleted Kingroot, the SuperSU app, etc.. Then, now here is where I am really confused, I rebooted and the first thing I see is that unlocked lock logo with "Custom" under it, but at the top of my screen is says nothing about my kernal not being seandroid enforced or w/e, and it booted like normal to the lockscreen.
Sorry if that is at all confusing but I thought I'd just share my findings.. considering I have my tablet back!
Edit: I can, and will record this rebooting if anyone is curious to see what I'm talking about if they didn't understand the above statements.
Click to expand...
Click to collapse
Glad to hear it worked for you mate! Sadly, it didnt for me. I do have good news of my own though, I was able to have my wife take it by the local Best buy store and after they tried the normal factory reset and such, he must have had an Odin flashable 5.1.1 file or something because the tab is back to working order.
That is how I knew I was in trouble after I rebooted the first time after installing Kingroot and Supersume Pro. I also got the red lettered "Kernel is not SEandroid enforcing in top left corner too, but the next thing I saw was the " Unauthorized software detected, please power off and take to ATT ". I don't think I ever even made it to the samsung screen if my memory is correct (It might not be! lol) It sounds like either kingroot or SuperSU left something behind after install maybe? If you go to Settings > About tablet > Status and scroll all the way to bottom, the last entry says custom as well correct? The unlocked padlock on boot just means Syscope is detecting something not official installed somewhere it normally shouldn't be.
I just kept to odin folder and boot(LP_fix).tar on my pc because despite getting stuck in a boot loop you lose root after you fix it so it's kind of like a tethered root lol
Guys Iam having this same problem but I don't speak computer lingo can another walk be though step by step so I can fix my tablet?
Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
I had this same problem, I just ended up giving up, exchanging tablet for a new one. :c
Klown80 said:
Yes, the thread you got that info from I am familiar with. The Lp fix boot tar in OP of that thread will fix our issue only if you only used Kingroot then rebooted. To fix and be able to boot phone again, simply flash the lp fix boot tar. However, I also used Supersume Pro to swap kingroot for supersu and that is why even after using the lp fix boot tar I am now past the "unauthorized software detected, please power off and take to att store", message, but stuck now at the att logo on boot. I am thinking of taking it to best buy or even att and hope someone can help reflash the full 5.1.1 firmware. I do not think the above adb steps will help for me, to mount system don't we need root? after I flashed the lp fix boot.img, (It is just the stock 5.1.1 boot.img) that removed whatever Kingroot did to get me rooted. Now I am stuck without root on a tablet I cant boot. I can get into recovery but I can not get adb to see the device unless I choose adb sideload, then all I can do with that is use it to push files to the phone for recovery to flash if it is signed properly of course.
Click to expand...
Click to collapse
That's exactly the problem i had. But when i took it to best buy, they said that, their software cannot read my tablet, because of "an abnormal software has been found on this device" its probably because my tablet is custom...Any Fixes?
Can't you guys boot to download mode and flash the stock files via odin?
wp4jot said:
Can't you guys boot to download mode and flash the stock files via odin?
Click to expand...
Click to collapse
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
How about this?
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse
wp4jot said:
How about this?
http://forum.xda-developers.com/showpost.php?p=65481346&postcount=606
Click to expand...
Click to collapse
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system
Definitely worth trying. It's a bricked phone and there's nothing to loose.
thisisapoorusernamechoice said:
Definitely worth trying but something tells me an OTA file won't be able to install on a modified system
Click to expand...
Click to collapse
wp4jot said:
Definitely worth trying. It's a bricked phone and there's nothing to loose.
Click to expand...
Click to collapse
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
thisisapoorusernamechoice said:
Agreed. Also for those following along at home, wp4jot linked to the 10.1 AT&T OTA file, for the 8.0 AT&T OTA file, please see this post:
http://forum.xda-developers.com/showpost.php?p=63320598&postcount=459
Click to expand...
Click to collapse
wp4jot said:
Sorry about that. Read fast and didn't notice the 537. I will edit my post with the right link. Thanks!
Click to expand...
Click to collapse
I figured, no worries, just didn't want to confuse anyone else :good:
It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
thisisapoorusernamechoice said:
The problem is the only stock Odin file available is KitKat, and since they're on official Samsung 5.1.1, they cannot downgrade, even using the official Odin file (attempting to results in a bootloop if I've read correctly). For this reason I really want to make a 5.1.1 Odin file for this device, but I won't be able to until someone is able to make a system dump.
Click to expand...
Click to collapse
It has been reported that downgrading the system to kit kat will cause a bootloop but you can then apply the update.zip file for 5.1.1 on a extSD and run it in recovery and it should boot.
I tried downloading the Lineage OS rom but i just can't. i followed everything on the page and it gets me stuck to the bootloader. One time it even had me enter a pin and then it got stuck again. Can someone please help me fix this because i don't know what to do and i think i want to just go back to stock zte but i'm not sure how to download that or get started exactly. Also when i go to terminal it shows a # so i guess its rooted but when i type su it sayd su not found so what do i do there.
Thank you
RMSmoorenburg said:
I tried downloading the Lineage OS rom but i just can't. i followed everything on the page and it gets me stuck to the bootloader. One time it even had me enter a pin and then it got stuck again. Can someone please help me fix this because i don't know what to do and i think i want to just go back to stock zte but i'm not sure how to download that or get started exactly. Also when i go to terminal it shows a # so i guess its rooted but when i type su it sayd su not found so what do i do there.
Thank you
Click to expand...
Click to collapse
You're doing a mess of things... It's your fault, not thar your device doesn't want LOS to be installed...
Tell me:
-What version of TWRP are you on?
-What files do you flash and in what order?
-Do you wipe everything before installing the zips?
-Do you flash SuperSU after flashing everything? (and have you tried not flashing it?)
-Why did you say that you 'tried downloading the LineageOS rom' but couldn't? What, are you trying to install a half-downloaded ROM?
Also, you say that you see a # when you go to the terminal. No shlt. When you write 'su', you get root privileges, and the # appears. So if you issue 'su' when you already ARE in subst user mode, it's not like you're gonna get even more privileges :silly: just skip the 'su' command and do whatever you need to do (though I doubt you need to do something with the terminal)