hello...
my pc specs (read before breaking everything):
- model: redmi 5 plus
- android version: 7.1.2 N2G47H
- MIUI version: MIUI global 9.2 | stabile 9.2.6.0(NEGMIEK)
- band base: 953_GEN_PACK-1.129634.1.131253.1
- kernel version: 3.18.31-perf-g439dbb6
ok, i tried to install it without success, the phone now goes in black screen and stays there.
I installed TWRP with
fastboot devices
fastboot flash recovery twrp.img
boot twrp.img
this step was ok, if i do it from a command line connecting my phone in fastboot mode to the pc, it starts.
then i went on "install" and installed the zip file
EvolutionX_4.5_vince-10.0-20200714-0943-OFFICIAL.zip
from here
https://forum.xda-developers.com/red...-plus-t4122467
after that, i rebooted the redmi 5 plus and boom, black screen after some seconds of "mi" screen.
can anyone help me?
Ok, I managed it.
for everyone who goes in a black screen / empty screen after installing a new rom, this thing saved my phone:
https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
Related
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??
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
DOWNLOAD
TWRP 3.2.3.0
Flashing Instructions
Make sure you have fastboot drivers installed and your bootloader is unlocked
Download the file
In fastboot open the directory of downloaded file and type
fastboot flash recovery recovery.img, after that type
fastboot oem reboot-recovery, You'll have a black screen on your display wait for 5-10s you'll be greeted with TWRP screen if you still didn't get the screen then press power button 2-3 times
BUGS
Data decryption ( For this you need to select Wipe -> format data (You'll lose all your data in this process) )
No Battery% ( I purposefully disabled it as the battery% always stays at 50% so I'll find the battery% path and fix this in the next build)
Flash force encrypt disabler in recovery to fix magisk module installation and other data partition related issues.
Source Code: TWRP source, Device Tree and Kernel Source
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
pankajyadav_18 said:
Tried to install recovery twrp v 3.3.0 and 3.2.3, stuck in bootloop flashing recovery is successful but while rebooting its continues in loop after showing lenovo sign (Orange Mode), started due to reboot problem, oem unlock was successful as well, please help
Click to expand...
Click to collapse
By reboot problem if you mean, the phone getting restarted randomly in loop then the only way to fix it is to go to the service center.
This was a thing from 2 years ago. On one night, my screen suddenly went dark during the use of the phone (I remember the last button I touched was about “image”.And the phone should have root permission). I tried to start it but It did not respond. After waiting for an hour, it was still the same. I can't wait anymore,so I removed the battery. Then the phone restarted automatically entered the recovery mode. then I restarted the phone, but it stopped at the first boot screen ... And then I decided to try to flash the machine, here is a list of all the things I've done:
1.Double wipe (/ data, / cache)
2. Use adb sidelode or update from sdcard to try to restore the entire os (always fails, explained below)
3. Use "fastboot boot boot.img" to test the boot.img in each OS released from the official website (also unable to boot, stuck in fastboot mode)
4. Use fastboot flash to Flash with all the OS , failed,too
4.5. Try to wipe all partitions I know with fastboot (boot,...)
5.Press all possible combination for more than 10 seconds. In factory mode, only clear test result and shutdown are available.
In list 2, I got the os from the official website of acer, and checked the model, but every time it said "assert failed" (I have tested every os on the official website, I even deleted all first line in the update-script [assert()], and the result still are failed.
Plz help if anyone know anyway to make my phone rework again, thanks
Note 1: Before the problem occurred, the TOOL DL Image fail! The problem sometimes appeared, but it was resolved after rebooting (yes, I haven't tried the sp flash tool, and I swear I didn't modify anything at the time ... Because I did n’t understand the system at the time)
Note 2: Below are my device information
Model Name: Z130
Part Number: HM.HD4ST.001
CPU(Maybe): MediaTek MT6572M 1 GHz - Dual Band
Storage: 4 GB
Memory: 0.5 GB
Connectivity:Wi-Fi IEEE 802.11b/g/n,Bluetooth 3.0,GPS,Micro SD slot, 3.5mm audio jack
Android version: Android 4.2
Btw English is not my native language... so there's might be some grammar fault, sorry here:silly:
I Installed an android 10 custom rom called pixel exp..on my redmi 5 plus which was at android 8 . Everything was fine except my phone didn't charge.so i installed another custom rom but it was the same. So i went to Xiaomi fastboot tool and flashed stock rom but it stuck on mi logo. So i cant boot stock rom and when in custom rom , it only charges when my phone is in recovery mode.
What to do?
@sriram000
Force device to reboot normally
Code:
fastboot reboot
@jwoegerbauer
When to reboot using fastboot ? U mean when stuck at that mi logo
After successfully flashing Linageos 19.0 vanilla build (no gapps) on Infinix smart 5 x657
I decided to get Bitgapps zip file
and because I don't have a custom recovery I used flashify app to flash Bitgapps.
But during the process the device just went off and I haven't been able to turn it back on.
Doesn't even bootb into bootloader or fastboot or recovery.
Also it wasn't detected by the pc i connected to