So I installed Resurrection Remix (Android 6.0) on an i9205. I did this because I want to enable boot on charge for this phone because it will be installed in a car dashboard.
Enabling this on the stock ROM didn't work so I hoped for more success with a custom ROM. However, all the default files that are used for this in system/bin do not exist. These files can be lpm, playlpm, charge_only_mode, chargemon etc. Again, these do not exist with the custom ROM.
I also cannot get a popular fastboot command to work because afaik Samsung does not work with Fastboot. When I try an ABD command to boot into fastboot it only reboots.
Does anyone know what file controls the 'battery bootup' when the device is switched off and connects to USB?
I also heard about the old app NoMoarPowah! but that one doesn't work on my device either.
Related
I had NOS Google Play ROM on my phone, but now it won't boot up and I forgot to set a backup file. Now I am stuck in TWRP since I can't boot up the phone. Also, I deleted the ROM file from my phone. Yes call me stupid all you want but I seriously need this fixed.
So what happens is, I boot the phone, goes to the boot screen, and shows it is booting, but it never does boot. It's in some kind of an infinite loop.
On top of that, I can't transfer files in TWRP!!
Does anyone know how to fix this? I know there is a fix to this, but I can't seem to get any to work or most just don't make any sense.
If you have boot loader unlocked (most likely) try fastboot flashing boot.img in fastboot mode
Sent from my DNA
hddr3 said:
I had NOS Google Play ROM on my phone, but now it won't boot up and I forgot to set a backup file. Now I am stuck in TWRP since I can't boot up the phone. Also, I deleted the ROM file from my phone. Yes call me stupid all you want but I seriously need this fixed.
So what happens is, I boot the phone, goes to the boot screen, and shows it is booting, but it never does boot. It's in some kind of an infinite loop.
On top of that, I can't transfer files in TWRP!!
Does anyone know how to fix this? I know there is a fix to this, but I can't seem to get any to work or most just don't make any sense.
Click to expand...
Click to collapse
USB OTG Cable, thumbdrive, rom image on thumbdrive, install from external SD.
Boot into recovery and connect the device to your pc and open a terminal and type in adb devices to make sure the pc recognizes your phone and it should. The just adb push a different Rom to the sdcard wait for that to finish and flash. Or if you can get adb sideload to work you can do that too.
You can use adb push/pull in recovery without mounting anything or at least it works for me...
Sent from my dlx using XDA Premium HD app
I have a problem connecting to Blutooth. I bought a car 2DIN radio for android. My phone turns on blutooth and connects to a call without a phone call. My radio with other smartphones connects seamlessly, has a problem with my phone only. My phone connects properly with the handsfree, with the speaker and other devices, just does not want to connect with my radio. I had an original Image, now I changed to MUI, but it is the same.
Is it really so difficult to repair if no one else has encountered such a problem?
Help
I'm fighting for 3 days and I do not know where I'm making a mistake. I was looking for a solution for bluetooth connection with 2DIN radio. I found the image in EUI 5.8 15S still works well. I had TWRP installed so there was no problem, I found the image I installed. Unfortunately bluetooth does not work. I wanted to install MIUI so I downloaded the image and here my problem starts. I am in TWRP unfortunately I can not access the phone memory. I will start everything from scratch. I will do everything as described:
I have ADB installed on my PC
on the phone I enter the system developer set
in the directory where I have downloaded twrp with shift PPM and the command window opens
adb devices command - correct answer
adb reboot command bootloader - telefin into bootloader mode
fastboot oem unlock command - correct answer
fastboot flash twrp twrp.img - install twrp
button + volume and power - twrp mode
in the twrp install button - and again the same I can not access the memory.
If I choose the memory, I have 0 mg memory and OTG memory
What I do is not where the error is.
wojt_wc said:
Help
I'm fighting for 3 days and I do not know where I'm making a mistake. I was looking for a solution for bluetooth connection with 2DIN radio. I found the image in EUI 5.8 15S still works well. I had TWRP installed so there was no problem, I found the image I installed. Unfortunately bluetooth does not work. I wanted to install MIUI so I downloaded the image and here my problem starts. I am in TWRP unfortunately I can not access the phone memory. I will start everything from scratch. I will do everything as described:
I have ADB installed on my PC
on the phone I enter the system developer set
in the directory where I have downloaded twrp with shift PPM and the command window opens
adb devices command - correct answer
adb reboot command bootloader - telefin into bootloader mode
fastboot oem unlock command - correct answer
fastboot flash twrp twrp.img - install twrp
button + volume and power - twrp mode
in the twrp install button - and again the same I can not access the memory.
If I choose the memory, I have 0 mg memory and OTG memory
What I do is not where the error is.
Click to expand...
Click to collapse
When you start it, is TWRP asking for a password? If it does, that means your phone is encrypted, which, for example, is the default for Indian firmwares. It's a bug, but not the end of the world. You have to hit cancel at the password prompt and restart recovery. It will eventually start without asking for a password and then you'll have access to the internal memory. Once, I had to restart TWRP about 10 times until this worked, so you have to be patient.
Thanks a lot. Actually I had to start again and it was OK. But now I have a bigger problem. I downloaded the picture MIUI 9. The installation ran smoothly. MIUI 9 has been installed but I can not take over the configuration. Even though the SIM card is inserted it does not see it. Can not find no IMEI. Can not set up MI Acccount. The phone is hot all the time and it's still on Mi Account. Can you stop it? Can I upload another image?
Yesterday at a late hour I managed to run everything on a regular basis on SmailSUI. I reinstalled the memory cleaner and it works fine. All the time I'm waiting for MIUI 9. As you work on this image you can check if BT is working properly. At me mixed with different images from this began. So far I have not found a system that works properly BT. When connected to another Android BT connects without a phone. You can not receive or call BT.
Thanks again for your help.
Hello everyone, I hope one of you could help me.
I've been using a 8.1 LOS ROM for some time but I want to get back to stock to use Android Pay and avoid a lot of the bugs I've been experiencing lately.
To be able to flash Oreo, I remember I had to install a modified kernel, so I don't know if it has anything to do with it.
My PC nor my Mac were able to detect my phone on ADB or fastboot anymore, so I flashed the most recent system.img and boot.img provided by erfanoabdi on androidfilehost and was able to get a stockish phone, but no OTA, since I still have TWRP.
I tried uninstalling and reinstalling phone drivers, ADB and fastboot too, but nothing happens when I connect my phone to the PC.
I have revoked ADB permissions but even so I don't get the prompt to allow USB debug when I connect it, even though I have the option enabled under developer menu.
I really don't know what else to do and have tried many of the suggestions here, but maybe the problem might be something else entirely.
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
UPDATE :
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
I tried to navigate in the device with the terminal app, so i put this command in terminal to make ADB run
command adbd, and this appears on terminal:
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
i try to run command logcat.txt, but terminal cant move to sdcard.
i try to adb over network and that connect but can´t do anything because stuck on <waiting device>, i look the blankflash but
didn´t works to me, and in the configurations usb settings looks greyed so cant switch between then.
when i run the command ls i saw this files:
init.usb.configfs.rc
init.usb.rc
init.recovery.qcom.usb.rc
maybe there is my problem? Thanks for read, thanks to @erfanoabdi he works very hard to make this possible, i hope somebody can
help me.
Anyone??
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com