So I have a simple ImageView which loads images from a URL. When this is run on the PC in a Android Virtual Device (AVD), the image loads perfectly, but when I use my Samsung Galaxy S3 in Developer/Debug mode, the image doesn't load. Why is this? Is it my phone settings?
On the S3, I have Developer options enabled, and
Developer options > USB debugging enabled
In the Manifest, I have declared INTERNET permission.
Any ideas?
I updated via local upgrade coming from rooted 9.0.17 with magisk and twrp
But not I have lost twrp and magisk and don't want to deal with the stress of having to lose data and figure out how to get everything back..
So is there anyway to get the pill gestures back without root?
adb
If you're a Oneplus user running Android 10 and you've sifted through the different navigation options available for your device, you probably noticed that two-button navigation is no longer there. For proponents of this UI, such news might be pretty disheartening.
Well, grieve no more, two-button devotees! There's a way to resurrect the sweet harmony of modern gesture navigation and the coveted "back" button of yore, and it just takes a bit of ADB intervention to make it happen.
To begin, you'll need to download the latest version of Android Debug Bridge to your computer; for the most straightforward method, check out this Nexus Tools installer for Mac and Linux, compiled by Android Police's Corbin Davenport; Windows users can download the required SDK Platform Tools from here separately. You'll also need to enable USB debugging on your device, which you can do by following this path: Settings -> System -> About Phone -> tap build number 7 times to enable Developer options, then enable USB debugging via Settings -> System -> Advanced -> Developer options).
Next, make sure your phone is connected to your computer. Set the current navigation setting on your phone to the standard 3-button layout. Then open ADB and execute the following command:
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
And that's it! You should now see two-button navigation in your settings app.
Sandipmatsagar said:
If you're a Oneplus user running Android 10 and you've sifted through the different navigation options available for your device, you probably noticed that two-button navigation is no longer there. For proponents of this UI, such news might be pretty disheartening.
Well, grieve no more, two-button devotees! There's a way to resurrect the sweet harmony of modern gesture navigation and the coveted "back" button of yore, and it just takes a bit of ADB intervention to make it happen.
To begin, you'll need to download the latest version of Android Debug Bridge to your computer; for the most straightforward method, check out this Nexus Tools installer for Mac and Linux, compiled by Android Police's Corbin Davenport; Windows users can download the required SDK Platform Tools from here separately. You'll also need to enable USB debugging on your device, which you can do by following this path: Settings -> System -> About Phone -> tap build number 7 times to enable Developer options, then enable USB debugging via Settings -> System -> Advanced -> Developer options).
Next, make sure your phone is connected to your computer. Set the current navigation setting on your phone to the standard 3-button layout. Then open ADB and execute the following command:
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
And that's it! You should now see two-button navigation in your settings app.
Click to expand...
Click to collapse
Thanks for posting this. One problem, none of your links for the tools listed are showing up.
Sent from my ONEPLUS A6013 using Tapatalk
xRogerxC said:
Thanks for posting this. One problem, none of your links for the tools listed are showing up.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
That's probably because there are no links posted in the previous post.
I have Yoga Tab 3 Pro, model YT3–X90L
I did a factory reset, of course I don't know the original google account
Of course, OEM unlock was not enabled, of course USB debugging was not enabled.
Of course I do not have the original purchase invoice.
Now I cannot use it, it says to enter original google account.
I tried several accounts, but none of them worked.
I can start the tablet in Droidboot mode, recovery mode, adb sideload.... pretty much everything..... but what do I do next ?
I tried this - https://forums.lenovo.com/t5/Other-...ase/Unlocking-the-A2109-Bootloader/m-p/857215 - the driver is not good, still exclamation mark
Thank you for your help !
Found the solution!
Inspired by this: https://www.unlockunit.com/blog/bypass-google-account-verification-factory-reset-protection/#alcatel
Connect to your wifi network > try to connect to ANOTHER network > enter some random wifi password > show password > select text > Assist > in the search field type CHROME > launch Chrome > download TEST DPC APK (try different websites, it doesn't always work) > install > Setup as manager > restart tablet and that's it !!!!
Hi,
A few days ago, my Fire HD10(2019) refused to power on, or rather it would show some life (amazon screen IIRC), but go no further. Now it doesn't even do that.
On a PC I can see whats its doing across USB. "Bus 002 Device 083: ID 0e8d:0003 MediaTek Inc. MT6227 phone" on usb for about 45 seconds, then it disconnects for maybe 20s, and then repeats. Now I take the 0e8d:0003 device to be the amazon bootloader - so looks to me like the bootloder works, but crashes hard and restarts as soon as it tries to start android. So looks like the box is bricked.
I've tried the various buttons to go into fastboot - no success. Neither "adb devices" nor "fastboot devices" can see the device. On first booting, the machine brings up a serial interface (USB ACM device), alas I've not been able to connect to this.
So what are my options of getting into the machine? If I can't access the bootloader via the serial interface, are there UART pins on the board? If so where? If I can access the bootloader, can I switch to fastboot mode, so I can reflash the android OS? Where is the best place to look for info like this?
davidsummers said:
Hi,
A few days ago, my Fire HD10(2019) refused to power on, or rather it would show some life (amazon screen IIRC), but go no further. Now it doesn't even do that.
On a PC I can see whats its doing across USB. "Bus 002 Device 083: ID 0e8d:0003 MediaTek Inc. MT6227 phone" on usb for about 45 seconds, then it disconnects for maybe 20s, and then repeats. Now I take the 0e8d:0003 device to be the amazon bootloader - so looks to me like the bootloder works, but crashes hard and restarts as soon as it tries to start android. So looks like the box is bricked.
I've tried the various buttons to go into fastboot - no success. Neither "adb devices" nor "fastboot devices" can see the device. On first booting, the machine brings up a serial interface (USB ACM device), alas I've not been able to connect to this.
So what are my options of getting into the machine? If I can't access the bootloader via the serial interface, are there UART pins on the board? If so where? If I can access the bootloader, can I switch to fastboot mode, so I can reflash the android OS? Where is the best place to look for info like this?
Click to expand...
Click to collapse
It is actually the mediatek bootrom (your device can have mtk-su temp root access, if you downgrade). You must have one of the early release ones that have access to it. My guess there is something wrong with the preloader... While i can't pin it down, the information to reload is all in this thread...
New Fire HD10 2019 Bootless Root Method + Bootloader Unlock Brainstorming
There's a new Fire 10 coming out, with an Octacore processor, USB-C charging, and FireOS based on Pie: https://arstechnica.com/gadgets/2019/10/amazons-new-fire-hd-10-tablet-costs-149-and-charges-via-usb-c/ I most certainly don't need any more...
forum.xda-developers.com
Yes it was an early device. Alas it connected to the web, and updated itself from 7.3.1.0 before I disabled most of the amazon processes. So the original mtk-su for 7.3.1.0 never worked on my machine. Alas can't use this any more - as can't get into android any more.
I'm up to page 30 of the thread you posted, alas nothing read so far has managed to get into the machine.
And first progress - bypass_utility version 1.4.2. can connect (when run as root) and gives:
[2023-01-22 14:32:12.028038] Waiting for device
[2023-01-22 14:32:39.691833] Found port = /dev/ttyACM0
[2023-01-22 14:32:40.083041] Device hw code: 0x788
[2023-01-22 14:32:40.083391] Device hw sub code: 0x8a00
[2023-01-22 14:32:40.083586] Device hw version: 0xca00
[2023-01-22 14:32:40.083770] Device sw version: 0x0
[2023-01-22 14:32:40.083959] Device secure boot: True
[2023-01-22 14:32:40.084143] Device serial link authorization: False
[2023-01-22 14:32:40.087904] Device download agent authorization: True
[2023-01-22 14:32:40.088223] Disabling watchdog timer
[2023-01-22 14:32:40.092031] Disabling protection
[Errno 5] Input/Output Error
[2023-01-22 14:32:41.464834] Payload did not reply
davidsummers said:
And first progress - bypass_utility version 1.4.2. can connect (when run as root) and gives:
[2023-01-22 14:32:12.028038] Waiting for device
[2023-01-22 14:32:39.691833] Found port = /dev/ttyACM0
[2023-01-22 14:32:40.083041] Device hw code: 0x788
[2023-01-22 14:32:40.083391] Device hw sub code: 0x8a00
[2023-01-22 14:32:40.083586] Device hw version: 0xca00
[2023-01-22 14:32:40.083770] Device sw version: 0x0
[2023-01-22 14:32:40.083959] Device secure boot: True
[2023-01-22 14:32:40.084143] Device serial link authorization: False
[2023-01-22 14:32:40.087904] Device download agent authorization: True
[2023-01-22 14:32:40.088223] Disabling watchdog timer
[2023-01-22 14:32:40.092031] Disabling protection
[Errno 5] Input/Output Error
[2023-01-22 14:32:41.464834] Payload did not reply
Click to expand...
Click to collapse
It has been a long time. Maybe try disconnecting the battery, not sure if it is staying in bootrom mode.... I remember mine had to have the battery removed or it would try to goto the preloader (i think). I used the process to downgrade back to 7.3.1.0, but it was like a year ago.
Michajin said:
It has been a long time. Maybe try disconnecting the battery, not sure if it is staying in bootrom mode.... I remember mine had to have the battery removed or it would try to goto the preloader (i think). I used the process to downgrade back to 7.3.1.0, but it was like a year ago.
Click to expand...
Click to collapse
Yes - mine stayed in 0e8d:0003 mode, when the device bricked itself - made no difference with battery on or off, always when through the same minute cycle, where the device would disconnect, then reboot.
Interesting after running the bypass utility - it has stayed up in the 0e8d:0003 mode - and hasn't rebooted.
davidsummers said:
Yes - mine stayed in 0e8d:0003 mode, when the device bricked itself - made no difference with battery on or off, always when through the same minute cycle, where the device would disconnect, then reboot.
Interesting after running the bypass utility - it has stayed up in the 0e8d:0003 mode - and hasn't rebooted.
Click to expand...
Click to collapse
it disabled the watchdog timer. From what is can see everything points to a potential wrong setup..
bypass_utility/README.md at master · MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
This post shows the same error as you read through it.
Payload did not reply · Issue #13 · MTK-bypass/exploits_collection
[Errno 5] Input/Output Error Payload did not reply
github.com
OK - using SP_Flash_Tool v5.2008 to attempt to flash maverick-downgrade-7.0_PR7310_940N and I get the error:
Connect BROM failed: STATUS_SEC_AUTH_FILE_NEEDED(-1073545198)
Disconnect!
BROM Exception! ( ERROR : STATUS_SEC_AUTH_FILE_NEEDED (-1073545198) , MSP ERROE CODE : 0x00.
[HINT]:
Please select a valid authentication file or ask for help.)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,105))
So where do I get the authentication file from?
Michajin said:
it disabled the watchdog timer. From what is can see everything points to a potential wrong setup..
bypass_utility/README.md at master · MTK-bypass/bypass_utility
Contribute to MTK-bypass/bypass_utility development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
ah yes - that explains why it was rebooting. So guess I have to dig into [Errno 5] Input/Output Error.
Seems like only way I have into the tablet any more is the mediatek bootrom, but as the tablet is sick - if that doesn't work, then probably its permanently dead. E.g. even getting access to a uart wouldn't help.
You have to only do file by file.
5. bypass_utility run succes with message "Protection disabled"
6. Run SPFlash Tool and flash boot, recovery, vendor, system. Wait to finish
7. Hold power button 15s to power off (check Ports in Device Manager windows)
8. Hold volume up and power boot to recovery with triactangle icon
9. Hold power and tap volume up then choose reset factory
10. Reboot
Thanks Michajin - I'm obviously having problems with the bypass_utility, whilst it connects to the MediaTek bootrom, it is not able to disable protection - and test mode bombs out. I've taken this up on the bypass_utility thread:
xda bypass utility
I have watched multiple tutorials on how to use PotatoNV, but can't seem to get it working for me. I followed the step by step instructions on the PotatoNV GitHub page and got to the part “you should see an unknown device named USB SER”. I completed this step and saw USB SER under other devices. With this completed my device should have popped up on the devices list in PotatoNV but it does't. I have tried a lot of things but to no avail. If there is someone who knows more about this program it would be awesome if you could help me.
the scuffed said:
you should see an unknown device named USB
Click to expand...
Click to collapse
Quoting:
"Open the "Device Manager" – you should see an unknown device named USB SER, or Serial Port HUAWEI USB COM 1.0."
Launch PotatoNV and select HUAWEI USB COM 1.0 in the device list, maybe it will help you.
Well that's my problem, I can't seem to find HUAWEI USB COM 1.0 in the device list of Potato NV It doesn't show up. I just get an empty search bar.
-Alf- said:
Quoting:
"Open the "Device Manager" – you should see an unknown device named USB SER, or Serial Port HUAWEI USB COM 1.0."
Launch PotatoNV and select HUAWEI USB COM 1.0 in the device list, maybe it will help you.
Click to expand...
Click to collapse
Sorry forgot to Put the message above in a reply.
the scuffed said:
Well that's my problem, I can't seem to find HUAWEI USB COM 1.0 in the device list of Potato NV It doesn't show up. I just get an empty search bar.
Click to expand...
Click to collapse
If you have installed all drivers it should work. It was just my tip, I have no personal experience with PotatoNV. I have always unlocked the BL through HCU-client.