Can my device be fixed? - Xiaomi Redmi Note 7 Pro Questions & Answers

Hey guys,
Recently I installed PixelExperience 10 (beta) on my device and after successful installation I kept getting a repeated error message stating "android.process.acore has stopped working". It made the smartphone practically unusable because when using apps this error message would kick me back to homescreen or close the process.
After this I tried to install xiaomi.eu rom (wiped everything) but my phone wouldn't boot and redirected me to the recovery. As I was using Peter's TWRP I thought I was being a smartass by installing the other TWRP without decryption support as I thought that was the culprit for my smartphone not booting into the rom.
My phone now boots to the TWRP (3.3.1-0) but keeps hanging on the loading screen. If I connect my phone to the computer and start adb I can see the device being in recovery mode.
List of devices attached
4440ca36 recovery
Click to expand...
Click to collapse
However, when I boot into fastboot mode my smartphone is not detected by my laptop or other computers. Looking at the device manager In windows shows no uninstalled device (so it's not a driver issue, the smartphone simply doesn't have usb functionality on fastbootmode, atleast that's what I think).
Is my phone hardbricked or any possibility to fix it?

Use orangefox twrp
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
Download the zip and flash in twrp

Rookert said:
Hey guys,
Recently I installed PixelExperience 10 (beta) on my device and after successful installation I kept getting a repeated error message stating "android.process.acore has stopped working". It made the smartphone practically unusable because when using apps this error message would kick me back to homescreen or close the process.
After this I tried to install xiaomi.eu rom (wiped everything) but my phone wouldn't boot and redirected me to the recovery. As I was using Peter's TWRP I thought I was being a smartass by installing the other TWRP without decryption support as I thought that was the culprit for my smartphone not booting into the rom.
My phone now boots to the TWRP (3.3.1-0) but keeps hanging on the loading screen. If I connect my phone to the computer and start adb I can see the device being in recovery mode.
However, when I boot into fastboot mode my smartphone is not detected by my laptop or other computers. Looking at the device manager In windows shows no uninstalled device (so it's not a driver issue, the smartphone simply doesn't have usb functionality on fastbootmode, atleast that's what I think).
Is my phone hardbricked or any possibility to fix it?
Click to expand...
Click to collapse
If you still have access to TWRP then download any other rom and try clean flashing it?

TWRP is stuck at loading screen sadly, can't access the graphical user interface

Rookert said:
Hey guys,
Recently I installed PixelExperience 10 (beta) on my device and after successful installation I kept getting a repeated error message stating "android.process.acore has stopped working". It made the smartphone practically unusable because when using apps this error message would kick me back to homescreen or close the process.
After this I tried to install xiaomi.eu rom (wiped everything) but my phone wouldn't boot and redirected me to the recovery. As I was using Peter's TWRP I thought I was being a smartass by installing the other TWRP without decryption support as I thought that was the culprit for my smartphone not booting into the rom.
My phone now boots to the TWRP (3.3.1-0) but keeps hanging on the loading screen. If I connect my phone to the computer and start adb I can see the device being in recovery mode.
However, when I boot into fastboot mode my smartphone is not detected by my laptop or other computers. Looking at the device manager In windows shows no uninstalled device (so it's not a driver issue, the smartphone simply doesn't have usb functionality on fastbootmode, atleast that's what I think).
Is my phone hardbricked or any possibility to fix it?
Click to expand...
Click to collapse
U look and or ask in the twrp thread from ur recovery...
Other USB cable?
Adb installer plus driver
https://forum.xda-developers.com/showthread.php?t=2588979
Mi flashtool use the driver
https://c.mi.com/thread-1329226-1-0.html
I don't find fast a newer one?
Maybe one or together help

try changing cable and if possible check on other computer too.

Related

[Q] Did I just brick my phone?

I recently rooted my Nexus 5 by following directions in this post: http://forum.xda-developers.com/showthread.php?t=2515640 I then installed a few apps, the ClockworkMod ROM Manager and then also the MultiROM Manager (not sure why). When I rebooted after the MultiROM manager, I get the Google screen but then... nothing. Just blackness.
I can restart to get back into the Boot Recovery mode and back to MultiROM, though my laptop won't recognize my phone so I can't install a ROM. It seems at some point, the entire ROM was wiped but I can't install a new one without having USB access to transfer the file. Any thoughts/ideas?
Have you installed the right drivers on your laptop?
Sent from my Nexus 5 using xda app-developers app
Do you have a custom recovery installed? If so, you can use a otg connection to install another rom / kernel. Have you tried wiping data/cache via recovery? Fastboot should be working if you can go into fastboot mode, maybe you should check your drivers/cable or use another computer.
No custom recovery I don't believe... Android File Transfer (I'm on a Mac) pops up but says "Could not connect to device". I've connected this Nexus 5 many times before to this laptop (literally 20 minutes ago) so I don't think it's a driver issue.
I'm in the "Team Win Recovery Project", went into Wipe and then Factory Reset but when I reboot, nothing still.
jcalderone said:
No custom recovery I don't believe... Android File Transfer (I'm on a Mac) pops up but says "Could not connect to device". I've connected this Nexus 5 many times before to this laptop (literally 20 minutes ago) so I don't think it's a driver issue.
I'm in the "Team Win Recovery Project", went into Wipe and then Factory Reset but when I reboot, nothing still.
Click to expand...
Click to collapse
Use Philz Touch recovery, TWRP has many issues like this...
If your device isn't being recognized by your MAC, then I will suggest you to find a pc or if you have a OTG cable with you, you can use it to flash a rom...

YU Yureka with no OS stuck on a Bootloop and unable to enter recovery mode.

Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!
Hey! I'm having the same problem with my yu yureka.. Can anyone help me please!
Kaustubh M said:
Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!
Click to expand...
Click to collapse
Hi! I'm having the same problem with this post... Does anyone knows the solution of this problem. I'd be really glad if anyone could help me with this..please!
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.
im also having same problem i have also unknowingly wiped system & now im not able to flash any rom while flashing its rebooting automatically & i am able to enter in to fastboot mode then i have flashed factory firmware then also its not booting stucked on boot loop.
arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.
Click to expand...
Click to collapse
Bro tried that but nothing........
rss3183 said:
Bro tried that but nothing........
Click to expand...
Click to collapse
Can you be more specific ? Are you facing boot loop too?
anybody please help... facing the same problem and tried the solution as mentioned above but still facing Boot loop. what to do friends. please reply
I suddenly faced bootloop.....then I tried to flash stock rom without root...as a web page suggested me that....it was flashed successfully ...but still I am facing bootloop issue .....can someone pls help me to get out of this mess....pls help me...ASAP !!!
arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
Click to expand...
Click to collapse
as its in boot loop battery has come to an end.... now what? having same problem as the topic creator
If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device
arunbiju969 said:
If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device
Click to expand...
Click to collapse
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a point and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.
Yogesh1969 said:
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a p loopoint and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.
Click to expand...
Click to collapse
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Sorry for a late reply...
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
The problem got solved bcos it had a battery problem !!!! Battery showed 90-100%, but could not hold up on boot.
A very strange case. Thanks.
Hi, I flashed my Yu Yureka AO5512 Yesterday and entered into recovery mode and selected the wipe userdata option. When it was doing the process after 20min the process stopped all together and My phone does not start at all now. If i press any button there is no response at all. Looks like phones OS and everything is wiped out. How do i go about from here?
Same problem , Stuck in BootLoop
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks
YuganshT7 said:
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks
Click to expand...
Click to collapse
Sorry to hear that anyway,
By stock lolipop you mean you had the yureka plus with Volte From factory right!!...if so the twrp might have been for the yureka plus with the cm bootloader which got replaced in the new Devcice
I am facing the same problem and in my case I dont think its an battery issue...I was happily using the CM 13.0 Snapshot Rom since a long time...but today morning when I did a soft reset by going into the settings in my yureka...the phone has gone in bootloop...and nothing is working...using fastboot I even flashed the twrp again and also flashed the CM 12.0 Stock firmware..but nothing is working...after the YU logo it restarts....please help...
I am also facing problem maybe worst
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.
Aditi Apte said:
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.
Click to expand...
Click to collapse
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.
FAILED (remote: unknown command)
Yogesh1969 said:
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.
Click to expand...
Click to collapse
But when I am executing other fastboot commands it halts the process between with error "FAILED (remote: unknown command)".
I have read about this error and people suggested that I need to get into "Download mode" not "fastboot/bootload". To get into "download" mode I tried pressing "VoulumeDown+Power+Home", but nothing happened, it simply restarted the phone.
Please advise.
-Aditi

OnePlus One Recovery Help

Hi,
I have a OnePlus One and I was having a lot of battery and network issues on Cyanogen 13.1 build version MHC19Q. I tried to do a factory reset but my phone would just not boot after the reset. It was stuck on the Cyanogen logo for over 50 minutes. So I tried to shut it down and redo the whole thing multiple times but I was facing the same issue.
So I tried to flash the ROM (downloaded from the Cyanogenmod support page). I did this through ADB but every time the installation stops midway because of
"signature verification failed"
And my computer does not recognize my phone on fastboot mode. I can only get to recognize the device when I go to recovery mode, do apply update from ADB
Please help!! I do not know how to fix this and I cannot do anything with my phone any more

OnePlus 7 Pro 5G (Bootloop to Bricked)

So last night I had a fully working stock ROM (Android 10) rooted with TWRP installed and Magisk all working fine... this morning I have a bricked phone which even when putting it into Qualcomm Download Mode is giving me the "This device has malfunctioned error" so I'm going to stop what I'm doing and seek some advice from you wonderful folks
It all went wrong when I updated some modules on Magisk, that put me in a bootloop. From there I went into TWRP and flashed a backup of my boot.img (of course this was a stock boot.img so that was wrong), this then sent me into a Fastboot Bootloop. I tried the instructions on https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 to flash a stock rom via fastboot but that didn't do anything and it continually kept booting into Fastboot. I even tried doing this manually using the instructions. I also tried going into recovery mode here but again no success.
Doing some more reading I came across the MSM Tool https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 which I downloaded, followed the instructions and all started to go well until I got an error telling me the image didn't match? I left it a while but nothing happened so disconnected the phone and now it won't go back into Qualcomm Download Mode.
The phone will now not turn on, or boot into anything. When I plug it in it says "USB Device Not Recognised"
Anybody have any ideas on what I can do?
Pm sent

Stuck on bootloop.

I'm using Lenovo K6 Power... And wished to use custom ROM. So did all the procedures(ADB, TWRP, SuperSu, ETC). Now, at the time of installing custom ROM you have to wipe all data including your phone's UI (ROM) so I did that. Now I tried to Install that custom ROM several time but it didn't install, I don't know why. So I clicked on reboot button... And then boom... My phone is stuck at Lenovo logo. I know I made this mistake. I didn't understand that, How can a phone reboot if it's original OS is deleted.
It can't even enter in TWRP recovery mode. Fastboot can be seen sometimes.
So please me with this, I'm completely new in this. Read so many forums and watched so many videos on YouTube for this. But they didn't help me. Any help will be appreciated. Thank You.
Highlights-
1. Stuck at Booting Animation.
2. Can't enter into TWRP recovery mode any how.
3. Fastboot Appears on top sometimes.
sahil_am_18 said:
My phone is stuck at Lenovo logo. I know I made this mistake. I didn't understand that, How can a phone reboot it's original OS is deleted.
Click to expand...
Click to collapse
If phone gets powered on, then its bootloader get run ( comparable to UEFI/BIOS in Windows computer ) what , when its tasks have finished, tries to start/run Android OS.
jwoegerbauer said:
If phone gets powered on, then its bootloader get run ( comparable to UEFI/BIOS in Windows computer ) what , when its tasks have finished, tries to start/run Android OS.
Click to expand...
Click to collapse
I'm sorry ma'am but I didn't understand what you are saying.
sahil_am_18 said:
I'm sorry ma'am but I didn't understand what you are saying.
Click to expand...
Click to collapse
Is not bad: many do not understand
Eeach mobile device can get run, but without an OS it stops after bootloader finished, because it's just a box of bits.
simple
when bootloader shows up, or bring it up with key combinations, connect phone to PC, and in fastboot/bootloader (on phone) type
fastboot reboot recovery
or if not work then:
fastboot boot c:\twrp.img
and do the rest via twrp, like flashing custom ROM again, or just flash stock ROM
indestructible master said:
simple
when bootloader shows up, or bring it up with key combinations, connect phone to PC, and in fastboot/bootloader (on phone) type
fastboot reboot recovery
or if not work then:
fastboot boot c:\twrp.img
and do the rest via twrp, like flashing custom ROM again, or just flash stock ROM
Click to expand...
Click to collapse
Thank you very much mate...
My phone was successfully recovered into TWRP recovery mode. But now the problem is...
While installing ROM it is showing 255 error.
Any suggestions...
Or link to download Working ROM...

Categories

Resources