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.

SM-T320: Odin Failure while trying to root

Hey all,
First time I'm trying to root this device, and a long time since I've rooted any device, so I'm a bit rusty ...
While trying to flash with Odin, I'm getting this error (looks like a write permissions error?)
{
"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"
}
This is what's shown on the device after:
The current firmware on the device is the stock 4.4.2, and I'm using the latest CF Root for it: cfar_samsung_sm-t320_mondrianwifiue_kot49h.t320ues1aqa2_t0
Update:
I also went to updato.com, grabbed my latest firmware, flashed it in Odin (it passed), then re-tried the above: result was the same as above.
Any idea what step I should take next?
TIA

GeekDrop said:
Hey all,
First time I'm trying to root this device, and a long time since I've rooted any device, so I'm a bit rusty ...
While trying to flash with Odin, I'm getting this error (looks like a write permissions error?)
This is what's shown on the device after:
The current firmware on the device is the stock 4.4.2, and I'm using the latest CF Root for it: cfar_samsung_sm-t320_mondrianwifiue_kot49h.t320ues1aqa2_t0
Update:
I also went to updato.com, grabbed my latest firmware, flashed it in Odin (it passed), then re-tried the above: result was the same as above.
Any idea what step I should take next?
TIA
Click to expand...
Click to collapse
It's been so long i can't even remember the steps i took but if i were to do it right now I would probably flash twrp in odin, reboot directly to recovery and flash supersu.
Edit - here's a guide https://forum.xda-developers.com/ga...nstall-twrp-3-1-1-sm-t520-t3693342?styleid=21

Airtioteclint said:
It's been so long i can't even remember the steps i took but if i were to do it right now I would probably flash twrp in odin, reboot directly to recovery and flash supersu.
Edit - here's a guide https://forum.xda-developers.com/ga...nstall-twrp-3-1-1-sm-t520-t3693342?styleid=21
Click to expand...
Click to collapse
Thanks, but you have to root before you can install a custom recovery; I'm stuck at trying to get the chainfire root installed.
I'm still stuck, anyone have any other advice?

[QRCODE][/QRCODE]
GeekDrop said:
Thanks, but you have to root before you can install a custom recovery; I'm stuck at trying to get the chainfire root installed.
I'm still stuck, anyone have any other advice?
Click to expand...
Click to collapse
Nope. I always flash root with custom recovery on every single device I've own which is alot.
If you bothered to follow that guide i included you would see that too. But ok...

Airtioteclint said:
[QRCODE][/QRCODE]If you bothered to follow that guide i included you would see that too. But ok...
Click to expand...
Click to collapse
I did follow the guide ....

Hi, sorry for reviving an old thread but I had this issue last night and wanted to share how I resolved it
I have the same T320UES1AQA2 model but couldn't get the CF autoroot to work either. I ended up going into recovery (Power + Vol Up + Home) wiping data and then flashing CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip which worked perfectly.
I know this is super late but hope it helps and anyone else who stumbles across this

I think my phone is stuck in a boot loop

So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
{
"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"
}
Any help would be really appreciated guys.

Mikeando89 said:
So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
View attachment 5168879
Any help would be really appreciated guys.
Click to expand...
Click to collapse
Without even knowing what OS version you are on, or whether you are on Stable, Beta or Canary Magisk, or how you installed Magisk, or whether you installed or temporarily booted up TWRP, I'll make a couple of suggestions:
If you are on Android 11, you can't install TWRP and Magisk together. You will have to temporarily boot up TWRP with fastboot to flash Magisk, or alternatively, patch the stock boot image with Magisk and fastboot flash the patched boot image.
Also, Stable Magisk is not compatible with Android 11. You should be using Beta 21.1 (or latest Canary).
I would start there.

Mikeando89 said:
So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
View attachment 5168879
Any help would be really appreciated guys.
Click to expand...
Click to collapse
1) Never use a guide from 3 years ago
2) Heres how i flash most ROMS (aforementioned fastboot TWRP only included. Substitute the ROM zip name for LOS): https://forum.xda-developers.com/t/rom-pixel-2-xl-official-protonaosp-11-3-0.4188109/post-84079085
3) Actually heres the same info (including bonus links to TWRP) on the last page in the LOS thread youre referring to, which begs the question, why are you reading 3 year old guides offsite, and NOT the actual OP and last page or so (to see if theres issues/etc)of the ROM thread of the ROM youre installing? Thats bonkers : https://forum.xda-developers.com/t/...2-2-xl-december-17-2020.4165919/post-84138395
Always a good idea to actually read the OP (and last few pages) of the ROM thread of the ROM youre installing....you wouldnt have needed to ask anyone for help....

Mikeando89 said:
So I decided to root my phone and put Lineage OS on it today. It has been a while since I did this so I followed this guide https://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/. I did use updated versions of TWRP and Magisk but it won't boot past this screen below.
View attachment 5168879
Any help would be really appreciated guys.
Click to expand...
Click to collapse
Reading the step by step guide you linked, don't put your files in the fastboot folder. I suggest you download the platform tools from google and flash the stock google images then start over with the LOS installation.

Thanks for your replies everyone. I understand that I really didn't provide much detail. I have now fixed the problem. I have flashed LOS 18.1, NiKGapps and Magisk 21.1. Only problem I am having now is the finger print works with the lockscreen but not with apps such as PayPal or Enpass.

(BS3) Not rooted but banking app see my phone is rooted!

Hello
My phone is Black shark 3 Global version KLEN 2008060OS00MP3.
I've rooted it before using @KM7 rooting guide, i forgot to back up the recovery stock, only backed up Boot.img, yesterday i decided to unroot my phone, so i flashed first the stock boot but the phone doesn't update because it has TWRP installed.
After that i tried to flash MP4 through 1027 local update but it gives "error ota 20"
I did another try that i flash DPX beta global rom through local update, it accepted the install and switched to SLOT B, but i felt that this rom isn't stable with touch so i decided to twrp Back up @mr. Fros global MP3 backed up rom.
My problem now that i can't use banking apps because Saftey net error bypass and banks see my phone as rooted and also i can't update to mp4, mp5 . Etc
Any solution please?

Fully non rooted but banking app see it 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"
}

deathcode0 said:
Hello
My phone is Black shark 3 Global version KLEN 2008060OS00MP3.
I've rooted it before using @KM7 rooting guide, i forgot to back up the recovery stock, only backed up Boot.img, yesterday i decided to unroot my phone, so i flashed first the stock boot but the phone doesn't update because it has TWRP installed.
After that i tried to flash MP4 through 1027 local update but it gives "error ota 20"
I did another try that i flash DPX beta global rom through local update, it accepted the install and switched to SLOT B, but i felt that this rom isn't stable with touch so i decided to twrp Back up @mr. Fros global MP3 backed up rom.
My problem now that i can't use banking apps because Saftey net error bypass and banks see my phone as rooted and also i can't update to mp4, mp5 . Etc
Any solution please?
Click to expand...
Click to collapse
You have to flash the stock recovery with the same exact version of your current ROM (which is global MP3) , otherwise it won't work.
Try to uninstall magisk app (apk), or reset to factory, then try again. See if it's still see it as rooted or not.

slashyuz6 said:
You have to flash the stock recovery with the same exact version of your current ROM (which is global MP3) , otherwise it won't work.
Try to uninstall magisk app (apk), or reset to factory, then try again. See if it's still see it as rooted or not.
Click to expand...
Click to collapse
I got hands on Qfil KLEN2008060OS00MP3 global stock rom, i will firstly extract recovery.img and flash it through adb and check if internal updates going through or not. If not then i will flash the whole rom using Qfil.
About magisk, i already uninstalled but bank app still detecting. I checked Saftey net and got that result :
Check screenshot

Question Rooted Pixel 6 Pro - no longer receiving updates

Hi all, I have rooted my pixel 6 pro since day 1 and always used the magisk way of patching and restoring images for updates, since the February update Google tells me updates are no longer supported on my device per screenshots, anyone else had this issue and know how to resolve it?
{
"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"
}

You might want to backup, uninstall magisk in the app, reboot. Then full reset/wipe and reboot. Then manually update to the latest May 2022 version using adb or the android flash tool. Something has gone awry with your software. Better to be safe than sorry.

Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.

Gytole said:
Just used the android flash tool and flash the latest image without the wipes, then reroot, should fix it all.
Click to expand...
Click to collapse
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?

zamarax said:
But with my device rooted and my bootloader unlocked won't that throw me into a boot loop? Then I'll have to completely wipe and restore no?
Click to expand...
Click to collapse
Nope! Quite the opposite if I get stuck in a bootloop I just use the flash tool to fix it. No loss of data, but you need to re-boot the magisk boot image then reflash in magisk afterwards as it will completely remove magisk

So I did what you suggested and now my device is stuck in a boot loop with corrupt data, I did however patch the boot.img previously when I tried to send it to the device via ADB so I'm going to try to push that now and see what happens. Here are the options I selected for Android Flash Tool.

Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!

zamarax said:
Second attempt with not selecting 'Disable Verity' and 'Disable Verification' worked successfully.
Thank you, I really appreciate it!
View attachment 5608917
Click to expand...
Click to collapse