Develop Bugs

[Q] Device recognized by adb, but always offline

Recently got my new N7. First thing I wanted to do was to edit hosts file on it, but currently after fixing the issue with no visible devices in
Code:
adb devices
now I see my device, but it is always offline.

{
"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"
}

NetJunky88 said:
Recently got my new N7. First thing I wanted to do was to edit hosts file on it, but currently after fixing the issue with no visible devices in
Code:
adb devices
now I see my device, but it is always offline.
Click to expand...
Click to collapse
Is your adb version 1.0.31 or greater? Use "adb version" to see what version you are running.
device offline is usually wrong adb version
device not authorized is usually because you didn't accept the RSA prompt for the whitelist

sfhub said:
Is your adb version 1.0.31 or greater? Use "adb version" to see what version you are running.
device offline is usually wrong adb version
device not authorized is usually because you didn't accept the RSA prompt for the whitelist
Click to expand...
Click to collapse
First of all sorry for such delay in reply and my adb version is Android Debug Bridge version 1.0.29
UPDATE:
Updating tools through Android SDK Manager did help and now device is visible, but I have one more, what seems to me, easy question. Is it possible to edit one rooted file without rerooting whole main directory? I need to edit /system/etc/hosts file.

NetJunky88 said:
First of all sorry for such delay in reply and my adb version is Android Debug Bridge version 1.0.29
Click to expand...
Click to collapse
Upgrade your adb and you should see the RSA prompt and after accepting the prompt on the tablet, everything will work as you expect.

sfhub said:
Upgrade your adb and you should see the RSA prompt and after accepting the prompt on the tablet, everything will work as you expect.
Click to expand...
Click to collapse
As I wrote in update, that adb was successfully updated and it did help.

Just go to storage settings and untick mtp and ptp and try again. Sorry for muy english it's not muy native language
Enviado desde mi Galaxy Nexus usando Tapatalk 2
---------- Post added at 01:10 PM ---------- Previous post was at 01:06 PM ----------
I have the same problem and that solve it
Enviado desde mi Galaxy Nexus usando Tapatalk 2

Any way to mark question as solved?

Problem solved
Seems That 4.3 Jellybeen you need ADB newest drivers follow this guide http://www.droidextra.org/2013/12/24/solved-fix-adb-devices-offline-100-working.html

NetJunky88 said:
Any way to mark question as solved?
Click to expand...
Click to collapse
OP can edit title and include solved. That does help people too.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

[Q] Change root/sudo timeout value??

Hi all. Yesterday I installed my first custom firmware -- xelite gamer. . Really impressed with the performance of it over the stock Rom. . However I have 1 issue with it that I'm sure can be resolved... Root apps seem to lose their root permissions after a set period (about 15-20 minutes).. Then they have to reauthenticate their root permissions which is causing problems.. For example setxperia goes back to the default non-overclocked profile.. Gamekeyboard seems to stop working altogether until I tab to it and then back to the game.
How can I change (increase) the timeout value, or even make it unlimited???
Thanks for your help!

indstr said:
Hi all. Yesterday I installed my first custom firmware -- xelite gamer. . Really impressed with the performance of it over the stock Rom. . However I have 1 issue with it that I'm sure can be resolved... Root apps seem to lose their root permissions after a set period (about 15-20 minutes).. Then they have to reauthenticate their root permissions which is causing problems.. For example setxperia goes back to the default non-overclocked profile.. Gamekeyboard seems to stop working altogether until I tab to it and then back to the game.
How can I change (increase) the timeout value, or even make it unlimited???
Thanks for your help!
Click to expand...
Click to collapse
when you enter first time in app that need root, it'll ask you for permission and there is box that can be chacked, something like this "ask me again in 15 minutes" Just make sure that you didn't chacked that box and root time should be unlimited.

senadin001 said:
when you enter first time in app that need root, it'll ask you for permission and there is box that can be chacked, something like this "ask me again in 15 minutes" Just make sure that you didn't chacked that box and root time should be unlimited.
Click to expand...
Click to collapse
I uninstalled some of my root apps and reinstalled so I could check this.... Mine looks different:
{
"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 anybody else have another suggestion?
It's like, it remembers that they have root and never asks me again, but it also keeps re-authenticating every 15 minutes. There's got to be a setting. In my past experience with Desktop Linux, there was a way to change the sudo timeout so I wouldn't have to keep typing the password after the sudo command... This is pretty much the same thing.
Anybody?

Hm... Well since nobody knows, I just decided to install a different ROM. Still just as fast and no problems with the timeout there. If I ever figure it out I'll come back and post the answer in this thread in case anybody needs to know in the future.

Possible reasons:
-outdated busybox: install busybox installer from play store
-older su binary: from within Superuser app, update your su binary
Are you maybe using Doomlord kernel?
Or you can switch to SuperSU and see if it's working properly

Bakisha said:
Possible reasons:
-outdated busybox: install busybox installer from play store
-older su binary: from within Superuser app, update your su binary
Are you maybe using Doomlord kernel?
Or you can switch to SuperSU and see if it's working properly
Click to expand...
Click to collapse
Hm, no I was using Lupus Kernel. But I've switched to a different ROM. If I ever go back to the other one though (xelite gamer), I'll give it a try. Thanks!

Bootloader Unlock and phone's encryption support

Dear All,
I was on my way to yet another bootloader unlocked phone of mine, but I happened to have a doubt about a point mentioned on Motorola's official BL unlock link:
{
"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"
}
My concern lies with the possible loss of encryption support.
My questions are, will my Addison's encryption be lost if:
I unlock the bootloader but don't flash any custom ROM
&
I Root my phone and use system modifications like use Xposed and Viper4Android
Thank you for your patient and relevant help!
Cheers!!

I unlocked my bootloader and am rooted. Device still shows as encrypted. Not sure why they issued that warning.

are you all using the unlocked GSM model?

Milly7 said:
I unlocked my bootloader and am rooted. Device still shows as encrypted. Not sure why they issued that warning.
Click to expand...
Click to collapse
Thanks for that info.
With respect to why that warning by Motorola, I believe it is because once we unlock the bootloader and flash custom ROM that might not be complied to support encryption or there might be some bugs in the custom ROM that doesn't enable encryption or if we modify system in such a way after rooting that the encryption might be lost due to these changes.
Hence, I believe this is why Motorola says "You may lose encryption support."
This was my understanding but I wanted to get it cleared on xda.
Can anyone throw some more light on my understanding?
We can then close this thread after complete clarity to all members so this turns out to be a fruitful discussion to most members here.
Cheers!!

Milly7 said:
I unlocked my bootloader and am rooted. Device still shows as encrypted. Not sure why they issued that warning.
Click to expand...
Click to collapse
Rooted via systemmode Super SU or systemless?
LAst I had checked only systemmode was able to patch the boot image.

hmnk said:
Rooted via systemmode Super SU or systemless?
LAst I had checked only systemmode was able to patch the boot image.
Click to expand...
Click to collapse
Hold up, does systemless root actually work for the Z Play then? I haven't received mine yet, but I was under the impression anything systemless wouldn't work from reading around, like Magisk or systemless SuperSU.

lpchaim said:
Hold up, does systemless root actually work for the Z Play then? I haven't received mine yet, but I was under the impression anything systemless wouldn't work from reading around, like Magisk or systemless SuperSU.
Click to expand...
Click to collapse
I rooted my Z Play (XT1635-02) recently using phh superuser.
Installed Magisk after that, and it seems to me it's systemless
as Adaway wouldn't work till I did the systemless hack - plus /system was read only

ozblogger said:
I rooted my Z Play (XT1635-02) recently using phh superuser.
Installed Magisk after that, and it seems to me it's systemless
as Adaway wouldn't work till I did the systemless hack - plus /system was read only
Click to expand...
Click to collapse
I see, thanks. Yeah, magisk is definitely systemless, good to know it can be used normally.

Just for clarification, you can decrypt by formatting data on twrp. By just unlocking or rooting the encryption does not go away.
Enviado de meu XT1635-02 usando Tapatalk

[How-To] Root - PX5 HU with Android 9.0!

How-To Root PX5 HU with Android 9.0!
I had a little time and scripted a few files to make it a little easier to root!
Step by Step:
1. Download and Install "Joying Extra Tools" apk to HU, run and click on the button "Enable/Disable adb over WiFi" and "Enable" 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"
}
2. Reboot your HU!
You can do this in the Factory Settings with the Code "hctreboot".
3. After Successfull reboot, extract "SuperSU-PX5-Android_9.0-ARM64.zip" to Desktop and open the folder.
NOTE: It could fail several times, just open the .bat again until everything has run through cleanly. As on the screenshots it should look then!
4. Open "1. Disable DM-Verity.bat" and enter your IP-Adress from your HU!
Wait for Finish and press Enter!
5. Open "2. Reboot.bat" and enter your IP-Adress from your HU!
Wait for Finish and press Enter!
6. After Reboot open "3. Rooting.bat" and enter IP-Adress from your HU!
Wait for Finish and press Enter!
7. Open "4. Reboot.bat" and enter your IP-Adress from your HU!
Wait for Finish and press Enter!
8. After Reboot you can see the SuperSU App with Full Root Access!
Warning: When the SuperSU App asking for updating the binary, click on Cancel. Otherwise the ROM could not boot anymore.
9. Open "Joying Extra Tools" and click on the button "Enable/Disable adb over WiFi" and "Disable" it.
10. Reboot your HU!
You can do this in the Factory Settings with the Code "hctreboot".
11. Done!
Credits goes to @HvdWolf for the Joying Extra Tools Application!

Is there any difference between the latest super su and this „special“ PX5 Version?

LinkseD said:
Is there any difference between the latest super su and this „special“ PX5 Version?
Click to expand...
Click to collapse
Nope it's the same latest SuperSU from 2017..

Too bad, since i cant get Viper4Android and Adaway to work with SuperSu

LinkseD said:
Too bad, since i cant get Viper4Android and Adaway to work with SuperSu
Click to expand...
Click to collapse
I will try a rooting method with Magisk with patched boot.img!
I'm busy in the next 4 days!
Use Blockada instead of Adaway!

This would be super nice, like in the currently provided roms.

LinkseD said:
This would be super nice, like in the currently provided roms.
Click to expand...
Click to collapse
I can try, but I can't promise, because Magisk works in the kernel.

Works brilliant... Thank you!

Thanks,
Works for me...

Thanks my boss it's work for me

Thanks for the Feedback

It got stuck in the script so I manually ran the commands - All good

Hello,
Must I reboot the HU after every action?

1-2-Hak said:
It got stuck in the script so I manually ran the commands - All good
Click to expand...
Click to collapse
When it's stuck, close the .bat file and open the .bat again
Here from OP:
NOTE: It could fail several times, just open the .bat again until everything has run through cleanly. As on the screenshots it should look then!
Dricus68 said:
Hello,
Must I reboot the HU after every action?
Click to expand...
Click to collapse
Yes it's needed because deactivate DM-Verity and then rooting.

Thanks,
Works for me....

Thank you for the guide.
Everything works great.

Hi,
I have successfully rooted my mtce head unit with this method however it is not giving to ability change system files with root manager.

julien_blanche said:
Hi,
I have successfully rooted my mtce head unit with this method however it is not giving to ability change system files with root manager.
Click to expand...
Click to collapse
The same here. I can not change system files.

julien_blanche said:
Hi,
I have successfully rooted my mtce head unit with this method however it is not giving to ability change system files with root manager.
Click to expand...
Click to collapse
The same here is rooted but I can't change the system files.

It's known here..
Thx for feedback.
I try to fix it tomorrow and will share v2.0

How to bypass google account ?

In almost all tutorials on how to unlock a google account, there is a moment when you need to launch the YOUTUBE.COM application. When I want to do it, the phone first wants to update it and here the problem arises, because I have to log in to the old google account. Anyone know how to unlock this phone in another way? MiUI version is 12.

100h_SOT said:
In almost all tutorials on how to unlock a google account, there is a moment when you need to launch the YOUTUBE.COM application. When I want to do it, the phone first wants to update it and here the problem arises, because I have to log in to the old google account. Anyone know how to unlock this phone in another way? MiUI version is 12.
Click to expand...
Click to collapse
Also you would Bypass FRP!!! A Simple Question why you dont know the old Google Account? Is it your Device? I dont Support Criminal Aktions to Remove FRP to make the Device Usable!!! I have Found a Solution with 1 Search and one klick to this xD
{
"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"
}

System23 said:
Also you would Bypass FRP!!! A Simple Question why you dont know the old Google Account? Is it your Device? I dont Support Criminal Aktions to Remove FRP to make the Device Usable!!! I have Found a Solution with 1 Search and one klick to this xD
Click to expand...
Click to collapse
12mins Later i have Found 8 Files to Remove FRP/Methods to Remove FRP for Mi 10 Lite MIUI 13

i need it please
System23 said:
12mins Later i have Found 8 Files to Remove FRP/Methods to Remove FRP for Mi 10 Lite MIUI 13
Click to expand...
Click to collapse

nossairy said:
i need it please
Click to expand...
Click to collapse
Ya know the Reasons from my Post, telling me why you would do this / must do this?

The phone was found on the street and handed over to the lost property office. After the legally required period of 1 year, the owner was not found, so the phone came to me again. I have confirmation of this fact.
As for unlocking - I have already found the right solutions and the phone works fine.

100h_SOT said:
The phone was found on the street and handed over to the lost property office. After the legally required period of 1 year, the owner was not found, so the phone came to me again. I have confirmation of this fact.
As for unlocking - I have already found the right solutions and the phone works fine.
Click to expand...
Click to collapse
Ok ya become the files when you need it!! you must switch it into edl mode and Flash the files, Kontakt me PM if you need it

I found a right solution in yt. Thanks.

100h_SOT said:
I found a right solution in yt. Thanks.
Click to expand...
Click to collapse
yes thats method 2 with bypass it without Flashing everything!!! nice a Searcher that Found a way Itself!!