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.

[Q] My GS3 is an impregnable wall. No rooting or flashing methods work.

Hi guys. First post to the forum, been lurking for years, just registered.
I recently updated my phone with the update that Samsung kept bothering me about every 2 hours or so. And It has messed my phone up, it's slow, it drags. It doesn't even show the clock on my lock screen without thinking about it for about 10 seconds. Train wreck.
I've rooted, installed custom recovery, and loaded custom roms on my Galaxy S i9000 and on my grouper Nexus 7. I kinda get how all this works, I'm not a total newb, but with this phone I am at a dead end and i've tried everything I know, and a bunch more tricks I learned here and nothing is working.
My Phone: Samsung Galaxy S3: Canadian (Bell) version SGH-I747M, supposedly the same as the S3 AT&T,
{
"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"
}
LINK IF IMAGE WONT IMBED: https://www.dropbox.com/s/dmgw0wj59ry70f6/Screenshot_2014-07-10-10-22-46.png
I had to use zadig to replace my drivers for Heimdall
Heimdall will sucessfully flash clockwork recovery, but it refuses to install my CM rom. I haven't tried any other roms, but from what I've read in the forum here, it doesn't seem to matter what rom you use, it just wont do it.
I get Assert, bootloader errors when trying to install from zip in Clockwork Recovery. tried the fix here: http://forum.xda-developers.com/showthread.php?p=41503727
and it does not work. Odin just says "FAILED" right away.
I thought maybe if I just rooted the phone first, I could at least flash a custom recovery and not have it over written everytime I boot.
I tried CF-AutoRoot, Odin says success, but nothing changes on my phone.
I tried OneClickRoot which worked wonders on my GS i9000 back in the day. No success.
I have tried CM Installer to do it automated, It says success, but no change.
People have reported that Knox may be the problem, but as far as I can tell I don't have it on my phone.
I've been working on this for a day and a half and all I've managed to do is factory reset my phone about 12 times. I need help.. I don't know what to do. Has anybody managed to root their phone or install a custom recovery or rom with a GS3 running 4.4?

If you are getting assert errors, try a different rom.
What firmware are you currently on?
Simple solution: flash firmware via Odin
Root using Towelroot
Install SuperSU from the play store
Open SuperSU and update binary and disable knox.
Done

I was having problems on my s3 running 4.4.2 NE6 after 2x failed root attempts. Then had sluggish performance.
Yesterday, I updated using kies to get the latest 4.4.2 NF2. Everything seems back to normal.
I heard in another thread that cf auto root works for NF2 but i personnaly haven't had the time to try it.

Ok, what im hearing is Towelroot won't work anymore on NF2. But most of our older methods should work fine. No idea about the problems you observed though. Root alone shouldn't have any effect on performance.

Moving back to stock from Cyanogenmod

Hi all, I just dug up my old S3 and need to go back to stock. It has a CM11 nightly on there with the MK3 baseband and CWM recovery (and no Knox loaded!). Needless to say, I've been out of the loop for the past year or so and all of these threads about Odin and the newer updates have my head spinning! I want to go back to stock but also want the ability to re-root and load a different ROM later on. If I use the Odin one click here (http://forum.xda-developers.com/showthread.php?t=2755793), would this cause any problem with re-rooting, recovery, or whatever else? I was burned on my newer Droid MAXX when I updated to a firmware that couldn't be rooted so I don't want that to happen in this case if possible.
TL;DR
If I'm on Cyanogenmod with MK3 (no Knox bootloader), what's the safest way to go back to stock with the ability to re-root later?
Thanks!

dcoaster said:
Hi all, I just dug up my old S3 and need to go back to stock. It has a CM11 nightly on there with the MK3 baseband and CWM recovery (and no Knox loaded!). Needless to say, I've been out of the loop for the past year or so and all of these threads about Odin and the newer updates have my head spinning! I want to go back to stock but also want the ability to re-root and load a different ROM later on. If I use the Odin one click here (http://forum.xda-developers.com/showthread.php?t=2755793), would this cause any problem with re-rooting, recovery, or whatever else? I was burned on my newer Droid MAXX when I updated to a firmware that couldn't be rooted so I don't want that to happen in this case if possible.
TL;DR
If I'm on Cyanogenmod with MK3 (no Knox bootloader), what's the safest way to go back to stock with the ability to re-root later?
Thanks!
Click to expand...
Click to collapse
Yes, that is fine and can be easily rerooted.
{
"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"
}

But if I was to use the one-click, wouldn't that load Knox and that would be permanently disabling any downgrading in the future? If I just flashed the stock 4.3 ROM and installed as normal through CWM, that should keep everything the same (bootloader,modem,etc) correct?

Yes... 4.3 has Knox by the way.

I flashed the 4.3 ROM and haven't had any issues so far. Still managed to avoid installing Knox somehow. Download mode doesn't mention anything about a warranty bit.

Android OS using lots of data

Noticed my Android OS is using almost 1gb of which doesn't seem right.
https://m.imgur.com/p1bAilv,XvmBuaw
Any ideas?

Edit 3: Updating will fix this properly.
Edit 2: That didn't fix it...
Edit: I've seemed to "fix" it. From my reading it is a background service trying to do a seamless update in the background. I disabled "com.qti.service.colorservice" using titanium backup and restore and it seems my background data usage has stopped. No negative consequences so far but it may prevent seamless updates. Another fix would probably be updating to the latest patch version...
Idk but I hope you get an answer... Been killing my battery.
{
"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"
}
Also seems to hit Wi-Fi...

for me the issue did not go away until I did a factory reset

danw_oz said:
for me the issue did not go away until I did a factory reset
Click to expand...
Click to collapse
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.

jhs39 said:
That would make sense if he was on stock but if he's using Titanium Backup his phone is rooted and might have other modifications. Flashing the latest factory image or if he's on a custom ROM doing a clean flash of the ROM would probably be the best idea under the circumstances.
Click to expand...
Click to collapse
It has been a while but I'll reply so anyone else who comes will know. My state before and after was the same. All that changed was my OS version. Flashed the flash-all.sh after removing the -w, flashed the April bootloader (so no boot signing stuff, not the safest or recommended thing), booted TWRP, flashed twrp, flashed supersu, and then rebooted. No other mods besides adaway.

Are you on stock, rooted or unlocked bootloader? I had the same issue on stock (unlocked bootloader) where it was trying download an update repeatedly. I had to actually flash a custom rom to make it stop. Verizon did credit me back for the data it used.
Feel free to read my forum post there and try those steps. - https://community.verizonwireless.com/message/1500910#1500910

Don't ask me how I know but this is a backdoor to access your device. Be careful!

paulJW said:
Don't ask me how I know but this is a backdoor to access your device. Be careful!
Click to expand...
Click to collapse
downloading the security update(s) is a backdoor in?
Riiiight

y2grae said:
downloading the security update(s) is a backdoor in?
Riiiight
Click to expand...
Click to collapse
he said dont ask him how lol

I had to factory reset before this stopped

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