I'm trying to figure out what's going wrong here. It started with me trying to get Emoji Switcher working correctly. Busybox is installed to /system/bin/ and I wanted to try and use a different version. The installer crashes and reboots my phone, same with the flashable zips, TWRP just crashes. I am of course rooted with SuperSU v2.67, on Android 6.0.1, deodexed with xposed v80.
I think I may have included Busybox with Superr's kitchen, so maybe that's the problem.
To clarify, writing to the system partition flat out crashes the phone, in the OS and in recovery mode, as well as using adb push commands.
Furthermore, I keep trying to build ROMs in Superr's kitchen and after I install xposed, my phone just boot loops continuously. It keeps trying to optimize 24 or so apps then it seems like it soft reboots and does the same thing.
holofractal said:
To clarify, writing to the system partition flat out crashes the phone, in the OS and in recovery mode, as well as using adb push commands.
Furthermore, I keep trying to build ROMs in Superr's kitchen and after I install xposed, my phone just boot loops continuously. It keeps trying to optimize 24 or so apps then it seems like it soft reboots and does the same thing.
Click to expand...
Click to collapse
Hello @holofractal,
Were you able to resolve the issue with Busybox crashing your phone every time you tried to install it or flash it on your phone? I am running into the same issue.
I have a Sprint HTC One A9, boot loader unlocked, rooted, no parity installed, and have Magisk 12 installed. However, attempts to install Busybox fail and restart my phone. Upon restart I receive a message that I might need to reset my phone and the Google Play store services have to be reset and then reinstalled and all of my systems allow lose their settings.
Thank you,
CRasH180
holofractal said:
I'm trying to figure out what's going wrong here. It started with me trying to get Emoji Switcher working correctly. Busybox is installed to /system/bin/ and I wanted to try and use a different version. The installer crashes and reboots my phone, same with the flashable zips, TWRP just crashes. I am of course rooted with SuperSU v2.67, on Android 6.0.1, deodexed with xposed v80.
I think I may have included Busybox with Superr's kitchen, so maybe that's the problem.
Click to expand...
Click to collapse
Hi,
try latest superSU 2.82 and install busybox into su/xbin/. Works for me everytime.
Related
Hey guys,
I am pretty new to rooting, and I am sorry if I am noob to the max.
I just rooted my Nexus S 4G, and installed ROM Manager v5.0.0.7. I want to put cm9 (the release candidate) on my phone. Every time I open ROM Manager, and hit Flash ClockworkMod Recovery, it says "An error occurred while attempting to run privileged commands!"
Thinking this was an issue with the root access ROM Manager has, I looked at the app list in Super User, and nothing is there.
How can I fix this and get cm9 on my phone??
Thanks for your help.
EDIT: I uninstalled both SuperUser and ROM Manager, got the latest version of SuperUser (v3.1.3) and ROM Manager. When I hit Flash CWM, the blue bar at the top goes almost all of the way, then the program quits responding.
Why are you flashing a recovery when you already installed one??
you have not given Rom manager root access, hence nothing in the superuser app. try clear su's data and cache, and go to its settings>security>Automatic response>Prompt and clear rom manager's data and cache as well, and try again. this time, you will encounter a message titling superuser request and click allow and remember options and you're on your way to the ICS party, although im leaving in 2 weeks in favour of jellybean
Alternative: install TWRP, and flash it via adb, and use reboot recovery command in terminal
That didn't work.
MikeMBau said:
That didn't work.
Click to expand...
Click to collapse
what didn't go right? no prompt? more info please... and make sure you're actually rooted, not just install superuser app
Do you or do you not already have a recovery on your phone? Installing superuser =/= rooted. If you don't you should manually install a recovery so that: A. You have a better understanding of what you did (it's always better to know what you're doing when you're messing around with your phone) and B. If something goes wrong you know exactly what caused it.
If you already have recovery why are you bothering with Rom manager? Just wipe cache and data (make a backup first) then flash the Rom.
@063_XOBX it looks to me as if he didn't root, thus the rom manager error message, privileged commands=root required commands, and rom manager's not getting it. or it's the superuser app didn't allow it to access root
Billchen0014 said:
@063_XOBX it looks to me as if he didn't root, thus the rom manager error message, privileged commands=root required commands, and rom manager's not getting it. or it's the superuser app didn't allow it to access root
Click to expand...
Click to collapse
That was my first conclusion too, I just wanted to make sure before I flat out said that he wasn't rooted.
Just wanted to update the situation:
I definitely was rooted at the time of posting this, as I could tell by the open lock on the bottom of the boot screen under Google and it said S-OFF when I would boot into recovery.
I ended up just unrooting the phone and rerooting, and this seemed to fix whatever bug I had.
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Click to expand...
Click to collapse
Hi, are you using a custom ROM or the stock ROM? The apps reappearing issue is on the stock ROM and happens on the 4.1 Jelly Bean ROM because HTC in their infinite wisdom (lmao who did I copy) introduced a write-protect feature in the Jelly Bean kernel. So installing stuff will work, but only in recovery when the kernel isn't active. I assume this is how you installed Superuser - through recovery. To overcome this issue you can flash a custom ROM like ViperOneS or if you don't want a custom ROM you can flash a zip in recovery which I will provide the link to shortly
Edit: page 212 of the official jelly bean thread in the general forum
Sent from my One S using Tapatalk 2
... Or you can flash custon kernel (I.e.elementalS 2.5) if you want to stay on stock and have no write protection......
Sent from my HTC One S using xda app-developers app
tominozh said:
... Or you can flash custon kernel (I.e.elementalS 2.5) if you want to stay on stock and have no write protection......
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Until CM 10.1 reaches stable, I think i'll stay with stock rom..does a new kernel provides other benefits?
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Click to expand...
Click to collapse
is this a device you have unlocked and bought brandnew yourself? or used?
mayby you dont have full root (after flashing root)
if your on JB maybe you have to flash the edited init d file for full r/w in system
http://forum.xda-developers.com/showpost.php?p=36099646&postcount=2111
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
Jeeza said:
Until CM 10.1 reaches stable, I think i'll stay with stock rom..does a new kernel provides other benefits?
Click to expand...
Click to collapse
nightlys are stable enough to be daily drivers.
real187 said:
is this a device you have unlocked and bought brandnew yourself? or used?
mayby you dont have full root (after flashing root)
if your on JB maybe you have to flash the edited init d file for full r/w in system
http://forum.xda-developers.com/showpost.php?p=36099646&postcount=2111
Click to expand...
Click to collapse
Thank you all for your replies! I'll try and flash this zip with twrp..the phone was used, but the previous owner did nothing like flashing stuff, or rooting..
Does flashing this package allows me to permanently delete system apps?
And are there real benefits with flashing a non-stock kernel?
Meanwhile, bought flash image gui, flashed the kernel with it, and again with recovery. Now I can uninstall system apps permanently!
Jeeza said:
Hi all!
I rooted my S4 with the all-in-one toolkit but I have the feeling that something didn't worked out. First thing, I don't get the boot screen with the red writing..I still have the normal one. It installed TWRP recovery alright and it works well. It installed SU, but i had troubles installing busybox..it gave errors about permission, even if I gave the installer root permission at launch..I had to install busybox through recovery. Other thing it didn't work is uninstalling system apps..I tried with Titanium, Anttek app manager and even with manually delete the apks, but after a reboot the apps and the apks reappeared..
All this things made me think that something went "not-fully-ok" in the unlocking process...
Is there something I can do to verify this?
Edit: forgot to say i'm on stock rom, last update.
Click to expand...
Click to collapse
What version is your toolkit? 3.4?
It looks more like you S-Offed, because HBOOT didn't give a da*m about the red message when S-Offed.
You're running stock. Kernal reboot would force it to reinstall.
mr_verystock said:
What version is your toolkit? 3.4?
It looks more like you S-Offed, because HBOOT didn't give a da*m about the red message when S-Offed.
You're running stock. Kernal reboot would force it to reinstall.
Click to expand...
Click to collapse
On the Hboot screen it says clearly S-on...and i'm sorry but i didn't understand your "Kernal reboot would force it to reinstall"
I need help, I can't get root access back after flashing stock kernel...
Actually the first time that phone boots I got root but is gone after reboot
I already tried re-flashing SuperSU lastest version, but nothing works...
Any idea?
Maybe need a full wipe, but I dont want to lose all my apps data/savegames, and I can't back up anything cause titanium back up needs root
Hello,
i can help you:
1. Install Supersu from play Store
2. Launch it and install binaries via normal way.
This should work.
TheCrazyLex
Don't install from the playstore, eventually it gives binary errors and that is if it can install binaries the normal way.
That said, download this ( https://www.androidfilehost.com/?fid=23578570567719420 ) and flash it through recovery as if it was a rom.
You're done.
badjoras said:
Don't install from the playstore, eventually it gives binary errors and that is if it can install binaries the normal way.
That said, download this ( https://www.androidfilehost.com/?fid=23578570567719420 ) and flash it through recovery as if it was a rom.
You're done.
Click to expand...
Click to collapse
He did try to install it via Recovery.
I said to install it from Play Store, so it is right
I downloaded the Android 10 zip file from Oxygen Updater app. Went to settings app, selected local upgrade and installed the update. Since I already had root, and wanted to still have root, I went over to Magisk app, installed magisk (the way to do after installing an OTA) and I also flashed twrp and again installed magisk. After this is where everything went downhill. I rebooted the phone and I had Android 10 installed fine, but I didnt have root access. I wasnt able to use magisk, so to get back root access, I booted to twrp and there I had the problem where my internal memory was 0mb. So I followed a guide online and was able to fix it, but I lost all internal data, so I booted my phone and downloaded the magisk zip and went back to twrp, where again my internal memory was 0mb so I again followed the same steps and this time, I flashed the magisk zip using an otg pendrive. After all the android setup process, I couldnt find the magisk app anywhere. I assumed that my phone isnt rooted and since I was almost fed up at this moment, I thought, I'll manage a few days without root. After a while when I opened netflix it says that it isnt compatible with my device and on checking online, it seems that this problem occurs when the phone is rooted. I again tried to boot to the recovery to flash magisk but now the stock oneplus recovery comes. How do I get out of this situation? I want my phone either properly rooted or even if its totally unrooted its okay. I might have messed up on many things along the way, please help me fix it.
prathk said:
I downloaded the Android 10 zip file from Oxygen Updater app. Went to settings app, selected local upgrade and installed the update. Since I already had root, and wanted to still have root, I went over to Magisk app, installed magisk (the way to do after installing an OTA) and I also flashed twrp and again installed magisk. After this is where everything went downhill. I rebooted the phone and I had Android 10 installed fine, but I didnt have root access. I wasnt able to use magisk, so to get back root access, I booted to twrp and there I had the problem where my internal memory was 0mb. So I followed a guide online and was able to fix it, but I lost all internal data, so I booted my phone and downloaded the magisk zip and went back to twrp, where again my internal memory was 0mb so I again followed the same steps and this time, I flashed the magisk zip using an otg pendrive. After all the android setup process, I couldnt find the magisk app anywhere. I assumed that my phone isnt rooted and since I was almost fed up at this moment, I thought, I'll manage a few days without root. After a while when I opened netflix it says that it isnt compatible with my device and on checking online, it seems that this problem occurs when the phone is rooted. I again tried to boot to the recovery to flash magisk but now the stock oneplus recovery comes. How do I get out of this situation? I want my phone either properly rooted or even if its totally unrooted its okay. I might have messed up on many things along the way, please help me fix it.
Click to expand...
Click to collapse
Looks messy. I don't know the workarounds to get you through. If I was in your place, I would use MSM to reset it to factory settings, update to Android 10 as needed and then use a patched boot image to install magisk. I went that route this time as I really don't need twrp. Search xda for the exact steps to do this. Fairly easy.
life2018.jjn said:
Looks messy. I don't know the workarounds to get you through. If I was in your place, I would use MSM to reset it to factory settings, update to Android 10 as needed and then use a patched boot image to install magisk. I went that route this time as I really don't need twrp. Search xda for the exact steps to do this. Fairly easy.
Click to expand...
Click to collapse
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate? Meanwhile, I'll try to get things ready to try MSM tool once again.
prathk said:
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate?
Click to expand...
Click to collapse
You can try one of the fastboot stock ROMs: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Options for the fastboot ROMs, as I see it:
- Flash Android 9 fastboot stock ROM, root, and try to update and keep root (like you did before).
- Flash Android 10 fastboot stock ROM, and try to root by flashing patched boot image.
- Flash Android 10 fastboot stock ROM, and leave it unrooted.
prathk said:
I had alot of problems with the MSM tool the last time I tried to use it. Is there any other way that you could recommend me to start over with a clean slate? Meanwhile, I'll try to get things ready to try MSM tool once again.
Click to expand...
Click to collapse
I had similar issues and decided to fastboot oem lock my bootloader after upgrading to Android 10. This reset everything to stock on Android 10 and avoids the issue with Netflix for now. I may re-root at some point but the downsides of being rooted are a bit more glaring now with Android 10 (losing enterprise email for my work, worse version of Netflix, etc).
My assumption is you ran into the same encryption issue I had where the only way out was reformatting and wiping data in the process. Next time I do anything with TWRP/Root/OTA updates I'll be disabling my pin and fingerprints to see if that avoids the issue. I've had it happen 2-3 times now where internal storage is showing 0 and is encrypted with no way to enter my pin.
Just do it all over again, boot to OS install through local upgrade and open magisk, flash twrp first then install magisk OTA and reboot, that way it will go to the other partition.
I'm messing with my POCO X3 NFC a lot, reflashing new ROMs like a madman, messing with super partition trying to enable RW for /vendor, /product, /system... testing backup restore function, etc.
As a part of my flashing routine I always flash magisk (for root and required modules), since release of the version 22 I was using it without any problems on A11 ROMs, even latest A10 RR accepted it - until a point...
Not sure what went wrong in my device configuration, while reflashing it so many times (ROMs, super partition, data backups, encrypted, decrypted storage), but last week or two, suddenly any ROM cooperating with magisk 22 stopped behaved correctly (random freezes, navigation bar missing after reboot, flashed modules not working, loooong boot times).
I remember answering to someone asking if (at the time new) 22 version is working correctly on POCO X3 and my answer was - yes it's working ok. Well - that changed...
I was not able to restore my device to its original state where magisk v. 22 worked correctly, I tried to reflash MIUI base via recovery, or via fastboot, but nothing helped so far... the only thing I didn't try was to use Miflash ... I'm not that desperate, since I figured yesterday that magisk v 21.4 is working correctly (to be honest I looked for the problem anywhere, but in the magisk setup, so a lot of my time spend on finding what's wrong was wasted) ...
So, maybe you will find out that magisk v. 22 behave incorrectly on your phone too, simple try to use a lower version, that helped me...
Also any recommendations how to reenable magisk v. 22 functionality using fastboot or custom recovery?
Have you tried renaming the magisk.apk to magisk.zip and flashing it like in the old days (before magisk basically changed with v22)?
actually yes, I was flashing v.22 renamed magisk apk to zip...
This Magisk issue of longer boot times has been around since last January, see this issue tracker. Also a lot of people face segmentation faults patching their boot.img using version 2200 or higher, see this. I haven't tested this new version, since it is still a canary at this point. Just wait it out or patch your boot.img manually and report there if you get errors.
Hey jeryll, you replied to me in the ArrowOS thread
Did you try the v22 Magisk uninstaller? Maybe somewhere / something left a mark..
I also have a weird warning when flashing Magisk v22
'unable to detect magisk manager apk for bootsigner '
But installer completes successfully and none of the side effects that you are describing.
Beaster said:
Hey jeryll, you replied to me in the ArrowOS thread
Did you try the v22 Magisk uninstaller? Maybe somewhere / something left a mark..
I also have a weird warning when flashing Magisk v22
'unable to detect magisk manager apk for bootsigner '
But installer completes successfully and none of the side effects that you are describing.
Click to expand...
Click to collapse
thanks for the suggestion, can't believe that I overlooked this solution, but for now it seems that magisk uninstaller did its job, and I can use v22 again...
need to do more tests, but for now it seems working, thanks again