boot up when plugged in Galaxy A70 - Samsung Galaxy A70 Questions & Answers

So guys,
recently I created a topic, but with the wrong approach.
I want to start the phone as soon it gets plugged in the power.
Some older phones supported this out of the box.
After searching the www I found out, that before getting the new android versions, there was the possibilty to do this via the LPM reboot.
But with the new android versions this insn't possible anymore.
Does anybody have a solution for this.
The phone is rooted and runs twrp.

Related

[Q] Rooting i9300 without PC

Hey Everyone
I've been looking around the site (and the rest of the web for that matter) and I can't find much on this that's helpful (at least not anymore).
I used to flash custom shizz on my phone regularly until I flashed back to stock for a while, and now I've decided to go back. The problem is, my USB port broke in the mean-time and I can no longer plug it in I know I could buy a new USB port, but it's a lot of work for a phone that I'm only going to be using for a couple more months (will be upgrading to the S5)
Is anyone aware of a way to root on the phone itself? So far I've tried http://forum.xda-developers.com/showthread.php?t=2352669 and Framaroot to no avail - I can't find anything else.
Any help would be massively appreciated.
Thanks!

LG G3 D852 (Canada/koodo) Comes up as "Device not Recognized" Windows 7

Hi all. I'm posting here because after countless (2) hours of searching online I haven't been able to find a proper solution for a problem. I'm hoping that you all can help me with this one.
I've been using the LG g3 for the past year and everything has been great. But since my screen got smashed I've had to replace it with a newer one. I got this last Thursday.
I've been sticking with stock because I'm quite fond of the stock marshmallow. But since I'm a tinkerer I can't help myself. So after I updated (yesterday) I was going to attempt to root and flash a shiny new rom. Unfortunately, I haven't been able to get that far, as my phone can no longer be recognized by my computer.
I will put it in, and it will pop up with "USB Device not recognized". Under device managers it merely shows up as "unknown usb device". So I uninstalled my LG drivers (which are normally installed once you plug in the phone, but I digress. It did all of this before the 6.0 update) and it will attempt to install usb drivers but fail almost immediately and say it experienced an "unknown error", very helpfully reminding me to try and unplug/plug the device or factory reset.
Factory reset is very difficult for me right now as I have just finally gotten the phone tweaked to my liking. I really don't want to have to re-download everything. I have tried almost every workarounds I could find on the Internet but I keep running in circles. I've downloaded several different drivers for my phone and none of them work. I'm really at a loss.
I'm assuming that it must be the marshmallow update, as I haven't rooted or installed cfw as of yet. And I can plug someone else's phone in and it will install the drivers in a heartbeat. I can charge my phone but it won't give me options for MTP/PTP/Charge mode at all.
Anyways that's about all I can ask at the moment. I just hope someone here has experienced this and knows what to do.
Okay, I have now tried factory resetting my phone and it still won't work. It's the 6.0 update that's causing this. I'm at a loss, either I have to wait for google to hopefully patch this or I have to take back my new phone and exchange it for a new one.
You should be aware that the correct model number for a Canadian G3 from Koodo is D852, not D820 as you mentioned.
Before taking back your phone, try to see if your phone is recognized with a different USB cable (OEM one preferred), plugged in a different USB port of your computer, or, if possible on a friend's Windows 10 or Windows 8 computer, just in case different drivers might recognize your phone.
Your suspicion (that the OTA update to MM caused this) is not well supported by the reality: the OTA update was quite uneventful for thousands of other Canadian G3 phones; we should have heard more complaints if the OTA update were botched by Koodo or Telus.

[tech support] Pumpkin PX3 MTCE HU, started bootlooping, need help recovering

Hello all,
I've run into an issue with my new head unit. I was just trying it out before installing it, got it powered up from my bench supply to test, and as soon as I installed a couple of apps (Plex and Google Play Music) it started bootlooping on me.
I figured I would go ahead and install a CFW since I do that for all my android devices anyway, but I've gotten myself into a pickle now. I can prompt the unit to attempt a firmware update, but all of the firmware releases I've found are in nupdate.img format, and the recovery is looking for a "kupdate.zip" format. I did try using the SD_Firmware_Tool to build an sdcard for this, but it seems to just be getting ignored.
The current behavior is that I get the "Pumpkin" bootloader logo, then it reboots. It no longer even shows the "android" loading screen as It did before I tried using the SD_Firmware_Tool.
For reference, I was trying to use the Hal9k rom from here
Getting to the onboard update menu works by holding the power button (pushing down the volume wheel) and hitting the reset button. I haven't been able to get it to boot into any other recovery modes yet, but if anyone happens to know of another button combo that should be working, please let me know.
I've put in an email to pumpkin support but I have a feeling they'll take a while to get back to me with the firmware, so hoping someone else might have something I can use in the meantime.
Well apparently I was mistaken about what CPU is under the hood of this thing (was going by a user review on the amazon page where I purchased it.)
According to the recovery it's loading into, this has an RK3368 rather than the RK3188 I expected
Little Update:
I'm trying out this unbrick for the PX5 to see if I can get it to use a more robust recovery. The current one keeps trying to mount a nonexistant drive location to run the kupdate.zip, and most of the pictures I've found of people's recoveries floating around on here have had the option to choose update files from different locations, so I think the recovery on this needs an update.
It's so far booting to a black (backlight on) screen and not progressing, so I hope the firmware update is going in the background and I just need to wait it out. Anyone know how long that firmware update process should take?
well I think my unit may just be new or different somehow, as none of the unbrick metbods seem to be working at the moment.
I've attached some pics of the unit's internals to see if that can help find a solution
How have you ascertained it to be an MTC(D/E) - it isnt
marchnz said:
How have you ascertained it to be an MTC(D/E) - it isnt
Click to expand...
Click to collapse
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Pyr0ball said:
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Click to expand...
Click to collapse
An XDA search for [kupdate] yeilds the information.
Made some progress on figuring this module out

Help with a unsupported build

I've been trying to figure this out for a while, and I have made some headway but I think I need to make custom build. If anyone could point me in a direction, it would be super helpful. I have a few ELO ESY15i1 android computers. They are EOL now, and only supported up to kitkat. ELO does not release their kernel source, but I do have their peripherals.
This is how far I have got with this thing, and what I was able to do/determine.
After a bunch of digging, I'm pretty sure that this thing is just a modified S4 i9505. Hardware specs seem to match, outside of the CPU only being 1.7 instead of 1.9ghz. I'm *assuming* that they have down clocked it maybe? The first unit I was working with, apparently had a bricked recovery (had bough it 2nd hand). I was able to boot it into TWRP using the jfltexx image, but I would get no picture. I know it was booted because I could access TWRP via cmd, and it was giving me responses back.
I was able to root it in a very round about way. Since I do not have any volume buttons, I'm limited to adb etc. I was able to root it with iRoot, convert that to supersu, and eventually get flashfire to install. I could finally access almost everything I needed. At some point, I got it stuck in a mode where "QHUSB_DLOAD" was shown to me, with a folder called "image" which I took a copy of. Any google results with that, was just people who had bricked their device, I was able to boot in and out of this, so I'm not sure what was going on or broken.
Here is what the device props listed out: hXXps://pastebin.XXX/FtgQ0DUE
This is the mobilodin report: hXXps://pastebin.XXX/BZrDAFg4
Finally, the "image" I copied: hXXps://anonfiles.XXX/lcQ7RfJ8o0/ESY15i1-image_rar
(sorry can't post links)
The first unit I was working on, I gave to a buddy to mess around with. The 2nd one I have, I have now bricked and it is officially stuck in the "QHUSB_DLOAD" mode. I made a poor choice, and modified the i9505 "updater-script" in lineage-17.1-20200723-nightly-jfltexx-signed to include my "msm8960" device. I flashed it via FlashFire which did go through, just bricked me in the process.
I had a samsung download jig, but I can't find it anywhere, so I have a new one on order. I'm too lazy to cut up a micro usb plug and make one. I have yet to get odin to recognize it at all, or get it into download mode. When I try over adb, it will reboot, try to go in some mode, then reboot again back to the rom.
Any input / help would be greatly appreciated. These machines are super cheap on ebay, the only problem is being stuck on kitkat. I can think of loads of things to use these for, doesn't look like anyone has tried to do anything with them. From all my searching I just found one guy who was trying to root one, and that was about it.
Hi,
I have one 22 inch unit, which I'd like to use with monitoring system and some else, but I need android version with multi windows support, so I'd like to ask you if you succeed with installing new ROM ?
Thanks in advance for reply
Maciek
Well, I've been dinking around with it again, I think I have the HW figured out. I'm pretty sure it's an LG Optimus G, LGE970 is what I'm trying.
I was able to take the stock "ATT-Stock-E97020j" non KDZ zip, pull the boot.img off of it, and flash that.
Now when I connect to my computer, I'm getting LGE Androidnet for Diagnostics, and LGE Androidnet USB serial, as 2 devices.
Just keeps hanging right away when I try and flash the KDZ.

Samsung Galaxy S20+ USB C issues

Have recently started to have issues with my S20+ super fast charging. Thought this could be the charger so tried a new one and the issue still exists. Seems to super fast charge as soon as the phone has rebooted and then stops and goes back to the "Check USB connection" message.
Also appears that the supplied USB C head phones no longer work connected to the phone. These work perfectly fine connected to my computer so i guess its unlikely an issue with the head phones.
Thinking back this issue appears to have started around the time the latest android was rolled out in the 2nd half of December. Has anyone else experienced the same issues and if so is there a fix?
Thank You
Android 11 One UI 3.0 is full of bugs on Galaxy devices. I won't install it unless it's improved. If you can factory reset to the original OS that may be your best option.
varcor said:
Android 11 One UI 3.0 is full of bugs on Galaxy devices. I won't install it unless it's improved. If you can factory reset to the original OS that may be your best option.
Click to expand...
Click to collapse
Thanks for your thoughts, i was coming to the conclusion this may be it. I did do a factory restore however this is the same OS (Android 11) - Would the only way to go back to Android 10 be downloading the ROM and installing it manually?
robonz said:
Thanks for your thoughts, i was coming to the conclusion this may be it. I did do a factory restore however this is the same OS (Android 11) - Would the only way to go back to Android 10 be downloading the ROM and installing it manually?
Click to expand...
Click to collapse
Here's a step by step tutorial to guide you through the process.
Downgrade Android 11 Back To Android 10 on Samsung Galaxy S20/S20+
In this comprehensive tutorial, we will show you the steps to downgrade the Samsung Galaxy S20/S20+ devices from Android 11 to Android 10.
www.getdroidtips.com

Categories

Resources