Develop Bugs

[Q] Rooting problems

Hello i've some problem with my T-Mobile Galaxy Note 2.
Last week i updated my phone on Android 4.3 version.
Unfortunelly i had a wifi bug and I couldn't connect to internet, so I decided to downgrade it to 4.1.2. I've flashed my stock ROM with the newest one. (thanks to this link http://forum.xda-developers.com/showthread.php?t=2102380 )
Afterward, i would rooting my phone and install custom binary CWM by this thread, option 2.
However i can't modifiy system files. I consequently would verify my status root by Titanium Backup. And that's really strange because it is already rooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...
​
So i'd like to know how to resolve my problem, i how to modify system files?
(PS: sorry for my bad English!)
PS2: That's the same thing if i connect it on SSH/FTP protocols, unable to modify too.

I have T889 version and I just updated today with 4.3 with no problem.
I would say the best thing is just start from scratch and reinstall your app.
I don't even use TB anymore, I used to but I just happen to run into problem a lot.
I decided to just reinstall apps everytime I flash rom.

DLinkwit said:
I have T889 version and I just updated today with 4.3 with no problem.
I would say the best thing is just start from scratch and reinstall your app.
I don't even use TB anymore, I used to but I just happen to run into problem a lot.
I decided to just reinstall apps everytime I flash rom.
Click to expand...
Click to collapse
So, do you advise me to re-install the 4.1.2 version and re-root again?
update: I've re-installed and re-rooting my stock rom and nothing has changed. Can you help me please?

Zebra_Cat said:
So, do you advise me to re-install the 4.1.2 version and re-root again?
update: I've re-installed and re-rooting my stock rom and nothing has changed. Can you help me please?
Click to expand...
Click to collapse
Try using the Odin again and when you full wipe don't even do anything just update to the original 4.3 via Tmobile.
After that install CWM or TWRP, Like I said I never had any issues installing Rom back and forth.
Just don't skip a step and never rush things.

DLinkwit said:
Try using the Odin again and when you full wipe don't even do anything just update to the original 4.3 via Tmobile.
After that install CWM or TWRP, Like I said I never had any issues installing Rom back and forth.
Just don't skip a step and never rush things.
Click to expand...
Click to collapse
I didin't understood that happened to me,
After several minutes and after downloading an alternative file explorer, SU granted to me to modify system files.

Updating OTA after TWRP install

Hi all, i have unlocked the bootloader of my Note 8T and installed the latest TWRP, i was going to install xiaomi.eu ROM, but sadly things has gone "bad", when i try to format, it fails, giving me a lot of red errors lines, ending with Operation not permitted, so i stopped there and flashed back the stock MIUI ROM through Xiaomi Flash Tool. Now since the issues with TWRP, I'm wondering how can i update when i will receive new updates via OTA? I think i wouldn't be able to do that with TWRP since the errors it gives me just formating. You guys think i would be able to update by downloading the fastboot update and flash it through Mi Flash Tool?

MichaelMay said:
You'll recieve new OTA updates, the recovery (TWRP before, stock now) has been replaced completely and TWRP is no longer your recovery.
I know what the initial problem is as well, you need another TWRP and if you had just read the forums you'd already know that and all of this could have been avoided.
Click to expand...
Click to collapse
I'm sorry, but i've used the latest TWRP for Ginkgo/Willow as xiaomi.eu requires. Also i've read of other users trying others recovery and encountering the same issue anyway.

You try this way https://forum.xda-developers.com/t/...ion-errors-all-the-time.4203951/post-84523785

Datlevn said:
You try this way https://forum.xda-developers.com/t/...ion-errors-all-the-time.4203951/post-84523785
Click to expand...
Click to collapse
So flashing this Miui HellasTWR recovery should fix the issue? I can flash it through fastboot, or i have to flash it by the recovery (TWRP in my case) as shown on the video? Thanks for your help.

Me too but still OTA the latest version of miui eu 24-2-2021
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Datlevn said:
View attachment 5233255
Click to expand...
Click to collapse
So you got stuck with xiaomi.eu ROM? If you know any fix let me know!

Mi8T said:
So you got stuck with xiaomi.eu ROM? If you know any fix let me know!
Click to expand...
Click to collapse
I did and ran out of red error line by this flash Miui HellasTWRP recovery -> HellasTWRP will ask for password (lock screen password), data will be decoded and now you can install custom rom according to Conventional way (4 wipe).
Note that updates only via twrp are not available via OTA

Datlevn said:
I did and ran out of red error line by this flash Miui HellasTWRP recovery -> HellasTWRP will ask for password (lock screen password), data will be decoded and now you can install custom rom according to Conventional way (4 wipe).
Note that updates only via twrp are not available via OTA
Click to expand...
Click to collapse
So MIUI HellasTWRP Recovery is the cure for the issue? That's Nice! I'm going to try again then. A little question, did you flash the HellasTWRP through fastboot adb mode? Thanks for letting me know!

Yes, flash by adb mode

Problem rooting F41 with magisk and Android 12

Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?

Same problem here. VBmeta is giving me a lot of trouble.
Loking foward for a solution...

Hi guys...
Anyone have any luck rooting this f.... android 12 on Samsung M21s? It sucks.
I cant hold it anymore...
A beg a little help .
A want my cell phone back. kkkk
Regards...

.

Hi! When you get that in magisk can you direct install?
ps. I do not have this device but I rooted Samsung so I may be able to help

RodrigoC82 said:
Hi, i have rooted a few phones in the past without problems but it´s my first samsung and nothing seems to work... Read a lot a tutorials, tried a lot of things and for now, no success in any...
I'm on the latest version of Android (12) - ZTO-F415FUBS2CVF1
I did unlock the bootloader without problems... Extracted stock rom boot.img, patched it with magisk 22104. Put it inside a boot.tar, flashed it in Odin with success:
View attachment 5700249
View attachment 5700251
After the patch, i always go straight to stock recovery and wipe data...
It´s really weird, when i install magisk, after the flash, it only says this:
View attachment 5700257
I also did try to follow magisk instructions and flash the whole stock rom with the AP patched but it gives me an vbmeta error, so i reverted to stock firmware and kept trying to patch only boot.img...
Also tried to revert to android 11 with Odin but it gives me an wrong version error on download mode...
I don´t know if i'm using the wrong magisk version, or something is missing in the tutorials... Also tried to find something here but nothing seems to work... Can someone help me ?
Click to expand...
Click to collapse
Can I see the error? It may be because flashing just the ap in the first place shrunk your space.

Unable to update without camera issues?

I've been trying to get my oneplus 5t updated to 10, but whenever I flashed any of the OTA files my camera will not launch. The only way I've been able to get it to function is doing a complete wipe and installing 4.7.1. I tried to then update from that but it just gives me errors. What am I doing wrong?
Since I am on an older version (7.1.1) of android, should I flash the 10.0.0 firmware file before flashing the OTA? And I would probably need to be on TWRP 3.7 (I may be misunderstanding something, but I'm trying).
Let me try to explain more of what I've tried:
I've tried every version of twrp I can find (3.2.-3.7)
Manually editing the META-INF/com/google/anffdroid/updater-script
Using unbricking tools
EDIT:​So I installed a 9.0.0 Stock rom, and the camera is working just fine. I haven't tried yet to upgrade up to 10 or attempt to install any custom ROM. These were the steps I took:
Clean flashed the 7.1.1 (4.7.1) ROM , rooted with magisk and made sure everything worked.
Uninstalled Magisk using the twrp zip package. Cleared darvik/cache/data/system.
Flashed OOS 9.0 Stock OTA . Flashed Magisk and everything worked as expected.
Made a NANDroid backup.
Only TWRP that would work through it all: twrp-3.2.1-0-universal-codeworkx-dumpling.img
Oxygen 4.7.1 Rom: OnePlus5TOxygen_43_OTA_003_all_1711100210_e640.zip
Oxygen 9.0 Rom: OnePlus5TOxygen_43_OTA_042_all_1812232104_efa031659de.zip
TLDR:​I got Android Pie installed and the camera/flash is working correctly. I haven't tried to upgrade yet but I will do so tomorrow.
Now, a quick question: Do I need to be on an upgraded TWRP in or-er to get android 10-13 installed?
This is what recovery I plan to try: twrp-3.3.1-1-20190713-codeworkx-dumpling.img
Or should I go for the highest unofficial 3.7 version?

Do you really need/want TWRP? Because you don't need it, unless you're going to unlock the bootloader, root it, install all sorts of 3rd party roms, etc...
I noticed too when flashing clean OOS 10 that my camera also broke.
SO...
My bootloader is locked, with OOS 9 installed, as a clean wiped install. Then I started up 9, set it up and updated the apps in Play Store, then I booted into OOS Recovery, and sideloaded 10.0.1. I did not wipe it in Recovery, I only sideloaded it, known as a Dirty Flash, and my camera works fine!
Here, I just took these screen shots, getting messy with a cheeseburger! LOL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used the full flashable 9.0.11 from here;
[OP5T] [ROM] [OTA] [OOS] Mirrors for official OxygenOS ROMs and incremental OTAs
Welcome! As OnePlus doesn't always provide direct download links for all of the OxygenOS full zips & incremental OTA zips, we have taken the initiative of mirroring them on AndroidFileHost and consolidating all the links in one place, so that...
forum.xda-developers.com
Also after flashing 9.0.11, the system showed me there was an update I could do in the phone OTA, so no need to then flash 10.0.1 manually.
I also booted into the OOS Recovery and wiped 9.0.11, then booted 9.0.11 back up and did this OTA install too, to test it out, it also worked good..

Question Cannot activate Magisk after MUI Update

Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan

stefan_at_localhost said:
Hello,
I had a working Setup with TWRP + Magisk.
Then I had the stupid idea to accept the OTA update to MIUI 14.0.6.0 (eu).
As I lost my root permissions, I decided to install Magisk again. I used the boot.img from the rom and installed it via fastboot from magisk_patched-XXXX.img.
When I look into the Magisk App (v26.1), it still states: "Installed N/A".
I also tried to flash the patched boot image via TWRP, but there is no way to gain root access anymore :/
Current Version: MIUI V14.0.6.0.TKHCNXM | stable
Can somebody give me a hint, what i'm doing wrong? I also tried to flash the _a and _b slot...
Thanks,
Stefan
Click to expand...
Click to collapse
You'll want to use fastboot to boot recovery (not flash)
And install the recovery via the on device gui
Also, I would use orangefox recovery, it was built from twrp, but has more features.
Use "method 2" in this guide:
https://theandroidrush.com/how-to-flash-orangefox-recovery-on-xiaomi-phone/

Hi,
I flashed the patched magisk boot via orangefox, but no success. Magisk still N/A
Step1: Patch boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step2: Flash via TWRP or Orangefox
no screenshot available
Step3: Result, no Magisk (N/A)
I don't understand this. Is there a greater change in MUI14?
I also installed the Magisk APK via TWRP and Orangefox, but no other result.
Thanks,
Stefan

After serveral hours of debugging I found out, that there was a post on the net, which recommended to install the debug version of Magisk. This was a first step into the right direction. But the GUI crashed and removed the Magisk App.
The strange thing was, that all other whitelisted root apps worked. But no access to change the Whitelist.
So I tried to get the GUI back. But there was no way.
When I installed the APK, it was automatically killed and removed :/
After reinstalling via the xiaomi.eu repair (update) script I decided to to try an older Magisk Version (26.0). This crashed also, but I was able to re-run the app again.
Finally it seems that Magisk implemented a change, that crashes with my MIUI version. I will observe this and try to file a bug report.