Related
pakidermo5000 said:
Ok, I need some help here to understand pretty basic things. I think I am trying to do the wrong thing. I get into bootloader mode. I get the black screen and detection of "class for rockchip" in device manager.
Now, I want to flash TWRP. My idea was to get into bootloader mode and use ADB to flash TWRP. But, I cannot connect to HuiFei when in bootloader mode because adb does not see any device.
Instead, if I boot the unit and use Wifi ADB, then I can connect to the unit.
So, should I flash TWRP through wifi ADB with the unit booted, or should I do it through bootloader mode? I could probably do it via recovery, but I do not really know how (just do update from sd card and select the TWRP I downloaded from 1-2-hak ?) otherwise, how do I do it if my adb does not detect any device?
sorry for the basic questions, but it is the first time I am doing this...
Click to expand...
Click to collapse
You dont need bootloader to flash TWRP. You just need to know how to get there if something goes wrong.
Check this link http://www.freaktab.com/showthread....itions-from-android-No-PC-needed-For-rockchip
get the flash_image from the link.
the get your wifi adb going
do a
adb push flash_image /sdcard/flash_image
adb push TWRP_KGL-7650G /sdcard/TWRP_KGL-7650G
then i go to adb shell
usually just cp them to dev
cd /sdcard
cp flash_image /dev/flash_image
cp TWRP_KGL-7650G /dev/TWRP_KGL-7650G
then flash it
/dev/flash_image recovery /dev/TWRP_KGL-7650G
then if you want to test
reboot recovery
you will need an mouse attached.
I am gong to see if I can get the touch working in this when I get my unit back.
Do a backup of the whole system in TWRP.
Then you are pretty well set.
Not sure if you need original recovery to update new MCU.images. When i uploaded mine I just flashed back the original recovery in the same way.
You can back up the original recovery by the steps in the link above. Which is good to have a complete copy of what you have now before tinkering too.
Hope that helps.
v3 with init.d support!
Here are v3 images for both screen resolutions in both KGL and KLD variants:
KVV_KitKat_XRESxYRES_yymmdd_rooted_light_reparted_init.d_v3:
rooted:
- ClockworkMod's Superuser apk, su binary and root daemon (root daemon needed on 4.3+ roms)
reparted: (seems popular these days )
- system reduced from 768MB to 512MB
- oem reduced from 128MB to 64MB
- data increased from 1GB to 3GB
- internal sd in now a bit less than 4GB
removed apks:
- Gmail2 (available on Play Store)
- Maps (available on Play Store)
- GoogleSearch (available on Play Store)
- VoiceSearch (included in GoogleSearch on Play Store)
- Talkback (available on Play Store)
- Google TTS and its libs and files (available on Play Store)
- Adobe Reader and its libs (available on Play Store)
- Instructions (surely useless, not relevant and badly translated from chinese...)
- Chinese and Japanese Keyboards (also removed their libs that are now useless)
- Navgear (just a stupid shortcut to the selected nav app in settings...)
updated/added apks:
- Google Play Store (updated to latest version)
- Google Play Services (updated to latest version with libs correctly installed so no more Google Play Services errors! Fixed on 1024x600 v3.1 thanks to @ESTIMULO)
- Browser bookmarks sync adapter (added, missing in KLD and KGL)
- Google calendar sync adapter (added, missing in KGL)
- Google contacts sync adapter (added, missing in KGL)
modded:
- init.d support added (late in boot process so every external storages are mounted), you can drop your scripts to /etc/init.d (chmod 755)
- added compatibility symlinks for storage mount points (it may fix issues with apps using hard-coded path to access sdcards and usb, if not it won't hurt anywway!)
- flash_image binary by Androtab, with dump_image and erase image symlinks to flash/erase/dump full partitions (dump_image return an error at the end but you can ignore it, dump is valid)
IT WILL WIPE YOUR DATA AND INTERNAL SD so backup first!
Please note that 1024x600 versions are untested as I don't own such a device but it's modded the same way so it should work flawlessly.
Updated TWRP image
This is an updated Team Win Recovery Project image based on 2.7.0.0 by Abdul from freaktabs (most credits goes to him! )
Updated fstab to new KK part scheme (was mounting kpanic and oem instead of system and internal sd)
updated kernel, modules and config files (full SElinux support)
Still no touchscreen you have to use a mouse. I've spent days trying to make touchscreen work but no luck, I'm starting to think that touchscreen is handled by mcu which then emulates a touch device or some weird things like that...
Now with a 1024x600 image
Please note that 1024x600 version is untested as I don't own such a device but it's Updated the same way so it should work.
Download latest versions HERE
How to flash recoveries back and forth to backup/restore data over flashes
Install Jack Palevich's Terminal Emulator for Android from Play Store and use a root explorer to save the apk file to your sd card or usb storage.
Download flash_image binary and use a root explorer to copy it to /system/bin and change permission to 755 rwxr-xr-x (if you are on one of my modded fw it's already installed you can skip this step).
Launch Terminal Emulator and type su to gain root, then type cd /path/to/recovery/folder, then type flash_image recovery twrp.img
You now have twrp installed, type reboot recovery to reboot to twrp.
In twrp use a mouse and go to backup menu to backup data (do not backup to internal sd it will be formatted by update).
Now reboot to system and place update.img at the root of you external sd or usb storage but don't update if prompted
Launch Terminal Emulator and type su to gain root, then type cd /path/to/recovery/folder, then type flash_image recovery recovery.img
You now have standard recovery installed, type reboot recovery to reboot to recovery.
Now you can flash update.img from the menu using power button.
When back into Android use backed up Jack Palevich's Terminal Emulator for Android apk to reinstall it quickly without having to set up google account.
Launch Terminal Emulator and type su to gain root, then type cd /path/to/recovery/folder, then type flash_image recovery twrp.img
You now have twrp installed, type reboot recovery to reboot to twrp.
In twrp use a mouse and go to restore menu to restore data.
webdude12 said:
Just a quick update.
I have copied over multiple different SU using TWRP to my stock 1024 x 600 4.4.2 unit. All them result in the same thing. Superuser not being able to use it. I have confirmed its there, messed with permissions on su and the system folders.
On thing I noticed through the TWRP command line is that SELinux is enabled. So thinking I might to research that to figure out if I need to do anything to get around that.
Back to the drawing board.
Click to expand...
Click to collapse
I've updated the twrp image for 1024x600 with 100% scaling factor so it should fit the whole screen now. Grab it HERE if you want to try.
Why don't you just flash a superuser zip from twrp, it will take care of the files, permissions and starting the daemon for you. You can grab ClockworkMod's superuser installer here: http://download.clockworkmod.com/superuser/superuser.zip
Note:
You can get required files here: https://docs.google.com/file/d/0B3FXCUVt554Mb1Nnai14eWM2cWc/edit
This is not provided by me! I copied the link from @pakidermo5000's old OP-Post
With TWRP MCU-Updates are no longer possible!
Normally you do not need TWRP as any custom roms can and have to be flashed using original recovery
coudu said:
I've updated the twrp image for 1024x600 with 100% scaling factor so it should fit the whole screen now. Grab it HERE if you want to try.
Why don't you just flash a superuser zip from twrp, it will take care of the files, permissions and starting the daemon for you. You can grab ClockworkMod's superuser installer here: http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
"Twrp image" Link is dead
Guy I know this is bringing up a thread from the dead but a question. I did install TWRP but my issue is when in TWRP to do a backup it is only backing up about 60MB of data even w/ all partitions chosen. It shows 0MB in data, is there a way I can back up the entire ROM like you can do on my android based phones w/ TRWP or CM recovery? Also I've read how to switch to stock recovery but whenn I go to TWRP and backup it just backs up TWRP backup files (ext4.win) no .img file is created. I think I just need a copy of the stock recovery.img and then i'd be golden. Am I wrong? If im not, does anyone know where I can find that?
Thanks
Dave
TT_Vert said:
Guy I know this is bringing up a thread from the dead but a question. I did install TWRP but my issue is when in TWRP to do a backup it is only backing up about 60MB of data even w/ all partitions chosen. It shows 0MB in data, is there a way I can back up the entire ROM like you can do on my android based phones w/ TRWP or CM recovery? Also I've read how to switch to stock recovery but whenn I go to TWRP and backup it just backs up TWRP backup files (ext4.win) no .img file is created. I think I just need a copy of the stock recovery.img and then i'd be golden. Am I wrong? If im not, does anyone know where I can find that?
Thanks
Dave
Click to expand...
Click to collapse
Yea i need the same, managed to lose my back up of it.
Have you guys ever gotten this to back up the data partition? It always says 0mb.
Was able to take the recovery.img from a joying update.. if someone needs it let me know ill send a link.
PLEASE!!
TT_Vert said:
PLEASE!!
Click to expand...
Click to collapse
Pm'd, xda isn,t letting me post links just yet. I guess i can not be trusted. Let me know if that works for you!
Must appreciated man, it was perfect. It seems TWRP is pretty much useless on these devices for bare metal backup/recovery like they are on phones.
Courtesy of jgarci44. Stock joying recovery
hi, this talk is the TWRP recovery for rockchip 3188? Excuse my intrusion would like to know how to install on my unit "kit kat 4.4.4"
don't waste your time currently.
TT_Vert said:
don't waste your time currently.
Click to expand...
Click to collapse
Why are you saying this ? Explain.
bettuccio said:
Why are you saying this ? Explain.
Click to expand...
Click to collapse
If you have to ask how to do it, most likely you won't be able to do anything with it at this point.
Sent from my Nexus 5X using XDA-Developers mobile app
---------- Post added at 08:37 PM ---------- Previous post was at 08:31 PM ----------
bettuccio said:
Why are you saying this ? Explain.
Click to expand...
Click to collapse
If you must here is a website where I got it (although not much you can do with it) be sure to have a mouse as the touch screen doesn't work. If you need to revert, which you will if you plan to update you will need to find a copy of the stock recovery.
http://freaktab.com/forum/main-category/freaktab-downloads/11780-twrp-2-7-0-0-for-rockchip-s
Sent from my Nexus 5X using XDA-Developers mobile app
rollback recovery stock
Hi.
Do you have any idea how to get back to the recovery stock version? I installed the TWRP under Rk3188 Stereo Card, it works fine but at the time of updating the file upgrade.img does not work.
Thanks you for your help.
I have a post on this somewhere. Search for it but here is what I have documented. Here is the joying stock recovery if that'll help you. https://www.dropbox.com/s/h5o46v24911nbsp/Joying stock recovery.img?dl=0 Same process as my post on installing TWRP on these except you use this image.
Dave
Ok, let me get this straight...
1. With TWRP you can't flash mcu.img (but you can flash update.img? how does this exactly work? how do I flash an update.img from TWRP? or do I lose the ability to flash update.img as well?)
2. The ROMs do not come with recovery images and overwrite TWRP? I thought they did, like other ROMs...
Recently got a kindle fire 7" and wanted to root it and flash a rom onto it, but having troubles with that part.
Using this guide https://forum.xda-developers.com/amazon-fire/general/root-t3471289
Rom:
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
Usb debugging/install from unknown sources/kingroot done
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Tried with and without mounting
Crashes after and starts a boot loop going into the amazon logo only
I'm new in regards for rooting, sorry if I'm a bit slow with this.
Thanks in advance for the help!
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Mr McBoatface said:
Check the rom you downloaded is not corrupted, verify hash value. Store it on the tablet not an sd card when flashing.
Reboot the tablet after you install supersu and flashfire. Before you flash the rom, make sure you remove the usb cable.
Don't use auto mount. Make sure you follow the flashfire instructions below. Make sure to move wipe to top of the order !
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
Still nothing, leads me into another boot loop.
New things:
Rebooted after installing flash fire
Verified the hash
Move the rom onto the internal drive (flashed from there)
No Automount
Any other ideas?
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Shugumi said:
Process:
Stock firmware (5.3.1) after amazon recovery tool
Kingroot root
Supersu-me
Update su
Tried once with and without rebooting
Rootjunky super tool, installed google play store
Install Flashfire (from play store) ver. .55
Also tried with an apk file ^ (ver. .53)
Set up a wipe for (dalvik, system, 3rd party)
Click to expand...
Click to collapse
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
ggow said:
Fresh installation from FireOS via FlashFire >= 0.55.1
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Fire Nexus ROM Zip
- Accept defaults
- Move "Wipe" to the Top of the order
- Press the big FLASH button.
- Ignore any warnings that appear
Click to expand...
Click to collapse
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
crazyates said:
IIRC, I had similar issues when first installing a ROM onto my Fire, but that was many months ago, and my memory is a bit fuzzy... IIRC, it had to do with the location of the ZIP. I believe I had to put the zip on my SD card, and then when I wiped my system, I also wiped my data volume. Speaking of wiping...
Maybe I'm reading this wrong, but are you saying you're installing the zip, and THEN wiping the system? That's going to erase the installation you just flashed. You should be wiping the system, and THEN flashing the zip. The original instructions are here:
IIRC, if you put the ZIP onto the internal storage, it puts it in the Data volume, which is then going to be wiped. FF wipes the data, and then can't find the zip (because it just deleted everything...). Does that make sense?
Click to expand...
Click to collapse
Had the zip on storage and wiped before flash, nothing :/
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Mr McBoatface said:
Was kingroot fully removed and SuperSU correctly installed ? Are you using the latest nexus ROM dated Feb 2017 ?
Try again this time use fire flash 0.53 included in super tools. Don't install play store or upgrade SuperSU, use the SuperSU included in super tools. Again make sure you restart the tablet after installing SuperSU and after installing fire flash.
With flashfire 0.53 make sure automount is deselected. Include wipe cache options too.
So wipe System data, 3rd party apps, Dalvik cache and cache , flash the nexus ROM. Again make sure before you hit the flash button the wipe action is moved to the top of the list. Make sure no USB cable connected to the device too
In my experience 0.53 flashes really quick , 0.55.1 "can" show a black screen, you might think its failed but it's working in the background but might take 5 mins to flash.
0.53 sometimes fails to open and crashes but i have only seen that when it was used on a device with a custom ROM already flashed on it. It should be fine for flashing on the fire OS system.
Click to expand...
Click to collapse
I might disagree with a few things you said there...
You only have to remove KingRoot if you're using v5.0 or newer. If you can use 4.9.6 to root, which I believe is what the SuperTool uses, then you can download SuperSu from the play store, update SU binary, then uninstall KingRoot with no issues.
As far as FF is concerned, the ROM developer says 0.55.1 is required, so I wouldn't stray from that.
The only other thing I would recommend is using the not-newest version of the ROM. For the last 6 months, the ROM has been based on a 5.3.2 boot.img, and recently switched to a 5.1.4 boot.img. Maybe the newer firmwares don't like the downgrade? I would try the Feb-2-2017 version of the ROM and try again.
Steps:
Restore to stock 5.3.2 (NOT 5.3.2.1)
SuperTool to install KingRoot 4.9.6 & GPlay
Kingroot to root
Install SuerSU (newest) & FF (newest) from Gplay
Use SuperSu to update SU binary
Put Feb-2-2017 zip on SD card
Use FF to wipe System, Data, Cache, Dalvik, 3rd party apps, & then install zip from SD.
Let sit for 5-10 minutes & do it's thing.
Having 2 root managers is not a good idea.
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
The version of flashfire shouldn't matter, but he is having issue so best to rule it out. The behavior of 0.53 is different to 0.55.1 . it flashes a lot quicker and is fine to use. I've used it several times in the last fortnight with the latest ROM.
The current ROM is fine, boot image and binary change won't cause the issue experienced here. The older ROMs are broken , in so far as either the camera or screen cast won't work. The latest ROM with the proven and stable binary is a better option, everything works
EDIT , also there are reports of several users losing supersuser seemingly random after upgrading to the latest SuperSU , hence why I suggested sticking with the current one on supertools.
I also suggested wiping cache, just incase an amazon update has downloaded while rooting and attempts to install at the same time at the nexus ROM is being flashed.
I have a Fire running Nexus Fire ROM (2/8/17), and my fiance has a Fire running stock 5.1.2 with root, OTA updates disabled, Nova Launcher, and Gplay Store. I wanted to flash hers from Stock to Fire Nexus, and ran into the same issues I had before.
FF was supposed to Wipe System Data, 3rd party apps, Dalvik, and Cache, then install zip, then inject SuperSU. When it did the wipe, it deleted the ZIP on the Internal Store, so FF sat there for 15 minutes not doing anything, and I didn't have a system to reboot into anymore.
I had to do a sideload recovery of 5.1.2, root, install FF, and do all the same steps as above, but this time install the zip from an SD card. Worked great.
Mr McBoatface said:
Kingroot uses it's own su binaries which may cause problems and clash with SuperSU. Using the script in supertools is a better option as it replaces the superuser su binary with a SuperSU compatible one.
Click to expand...
Click to collapse
I used the SuperTool to root, and this is what I did also. Afterwards, I used the Gplay to update the SuperSU, which updated to the newest binary. I haven't seen any problems as of yet.
Unless internal storage was selected that shouldn't have happened, unfortunate that it did for you. The only time I've seen FF hang was when wipe was in the wrong order or when the USB cable was connected..... Don't know why the USB cable has that effect but I've seen it on 2 devices, other people have not had any problems.
Not seen the issue with SuperSU myself but read plenty of reports about it.
It seems users are affected by several random issues even if following the same instructions.
@Shugumi any update ?
Been swapping out roms and trying each suggestion but its been giving me the same boot loop.
So, I returned the kindle fire, and am waiting to try it on the new coming device :/, but thanks to everybody that replied to this thread. Even though we didn't get to root my kindle, it was great help! Thanks everybody.
I'm almost entirely new to messing around with stock firmware on a locked bootloader, its been unlocked for 2 years. I relocked it, TA keys are fine, I had TWRP, I was able to write to the system partition, I had external storage write permissions, and all of those things have dissapeared entirely. I was able to use an xposed module for getting external storage permission back.
-I can't install TWRP again because the installer on a locked bootloader requires the system to be remounted rw or already have access to a recovery.
-The xposed solution to the exteral sd isn't ideal, and again I need TWRP or to do it manually by mounting the system rw.
-FlashFire doesn't work regardless of what variation of options I give it.
-I pulled the kernel image out of the pre-rooted zip I initially used but it won't fastboot. It says USB debugging isn't enabled when I try it using flashtool, though it is on when the system is up. I was hoping that the rewrite permissions or possibly even TWRP would be available if I reflashed the kernel image. This won't work.
The reason for being on Lollipop is that for whatever reason, push notifications still really suck for me on Marshmallow, enough so that it isn't a workable option.
Having either TWRP or being able to remount the system rw would, from the look of it, lead to being able to fix the thing entirely.
The only workable solution I have right now is to flash stock Marshmallow, install TWRP which is rather easy on current MM, then reinstall the pre-made zip I already had for Lollipop. This is a huge pain given that I just put a lot of time into my setup and even just the settings I'm using in Xposed would in itself be difficult to restore as its quite a lot. Everything is backed up via Titanium.
Essentially, "Is there a workable solution to my problem that doesn't involve flashing MM, putting TWRP back, reflashing LP, then setting up what I know I need to all over again followed by the inevitable supprise down the line of still needing to re-do some of my apps that didn't quite go well? The goal is to get TWRP back, and this seems like it isn't going to happen if I can't write to the system.
??
Also, If I just pull /data entirely via adb, my laptop already uses ext4 for the filesystem, but it there a way in this scenario where I could absolutely ensure that I could do it, and then put it back while not screwing up file permissions assuming I did the whole falsh MM, install TWRP, flash LP thing?
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.
Context: my motorola g4 is 5 years old and saw many different kinds of root attempts and amateurish handling (like modifying the system image) in its early days. I settled on magisk when it became a thing. Now I'm trying to go back to being rootless, including removing left-behind stuff like addon.d scripts.
TWRP shows a /supersu folder in the root fs, containing the usual apk, sh scripts, etc. I can delete this folder, but next time I boot my device (even just recovery!) it gets restored _somehow_. This is the only remaining trace of rooting I'm aware of, aside from the image just "not being untouched stock" anymore.
I'd like to get this folder permanently removed, without erasing my data.
Things I've tried:
- flash the stock rom: somehow it's defective (Package Installer crashes and I can't fix it by any means), despite it being the same zip I flashed two years ago and still use today, so this is not an option
- flashed stock boot
- unSU https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
- installed supersu just to run its own unroot procedure, then ran unsu again, then flashed stock boot again
It just keeps coming back after every time I delete it and I'm out of ideas to stop it. All the threads I've found online offered only the above solutions that don't work.
Thanks for any good tips
@Marnes That sounds like it's TWRP's superuser. It won't exist if you are not booted to TWRP and it'll be repopulated everytime you boot to TWRP...
@Didgeridoohan I hadn't considered that possibility... I guess there's no way to verify it since checking after a regular boot if the folder is there would require rooting again. Thanks for the input!