My le eco le pro 3, during a normal day, stopped working.
If i try to turn it on i see the "LeEco powered by android" and after 10 seconds it turns off with a blue led.
I can not access the recovery mode, only the fastboot mode.
What fastboot command do i have to do to fix this? :crying:
If you can reach fastboot that is great already, i dont know if they bundle their devices with a recovery so you'll need to find a recovery for your device (quick google search, look for TWRP)
Also grab the drivers for your phone so you'll be able to write the recovery you downloaded.
Download the Google Universal ADB + Fastboot package (the 10 seconds installer)
Once everything is done, you'll need to go to the folder containing ADB and Fastboot with a command prompt
In the same folder you put the downloaded recovery. Put your phone in recovery mode, plug it, and type in the cmd : fastboot devices
If it recognize something you are good to go, you type fastboot flash recovery recoveryname.img
Then lookup for a Rom, i'm sure there is plenty of it, you'll flash the Rom either with sideload or if you have TWRP via Transfer
Gtahero74 said:
If you can reach fastboot that is great already, i dont know if they bundle their devices with a recovery so you'll need to find a recovery for your device (quick google search, look for TWRP)
Also grab the drivers for your phone so you'll be able to write the recovery you downloaded.
Download the Google Universal ADB + Fastboot package (the 10 seconds installer)
Once everything is done, you'll need to go to the folder containing ADB and Fastboot with a command prompt
In the same folder you put the downloaded recovery. Put your phone in recovery mode, plug it, and type in the cmd : fastboot devices
If it recognize something you are good to go, you type fastboot flash recovery recoveryname.img
Then lookup for a Rom, i'm sure there is plenty of it, you'll flash the Rom either with sideload or if you have TWRP via Transfer
Click to expand...
Click to collapse
Thank you so much.
I have type c broken, so i cannot plug it into my pc (i have found replacement).
I found this guide https://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
If i don't want to root, do i have to unlock the bootloader anyway?
It might be a stupid question, but I do not know much about this.
Yeah you will need to unlock the bootloader in order to flash a new rom
But roms aren't rooted so you can relock your bootloader after
Related
I am having a REAL BUGGER of a time with my Xiaomi Redmi Note 3 Pro (Snapdragon)!
1. It is not recognized by ADB in Fastboot mode.
2. I suspect it shipped wit a vendor ROM, and I'm trying to flash latest Official MIUI Global Dev (Marshmallow) ROM, but I keep getting errors in MI Flash (screenshot attached).
3. I want to Flash TWRP, BUT ADB isn't working, AND I cannot get to the download page for the cracked bootloader.
4. Seriously considering Resurrection Remix ROM, instead, but most of the above issues still apply.
I am NOT new to custom recoveries, flashing ROMS, ADB etc, BUT I am dealing with a new PC (Windows 10 Home, 64 bit, like my old (dead) laptop), and I'm new to this device.
PLEASE HELP. (Quite frustrated)
Fastboot won't recognize adb commands you have to use fastboot.
What you can try is booting into emergency download mode and using my flash to flash it from there. I think it's " adb reboot edl" while the device is on with USB debugging or using the mi updater app ( tap the three dots I think).
I think that this is not the correct section for your question, and i dont know the procedure that you follow but try to follow this procedure:
-Connect the phone at pc with USB cable
-Make sure that debug mode and OEM unlock was abilitate in dev settings
-Copy twrp.img in adb folder
-Shut down the phone and press power botton and - vol buttons for enter in fastboot mode
-Run this commands by terminal open in adb folder
fastboot devices
-If fastboot recognize correctly the device run this command
fastboot fash recovery nameoftwrp.img
-After reboot the device with this command
fastboot reboot
When the phone reboot press immediatily vol + for enter in twrp
Good luck
GOT IT! FINALLY!
-I finally got ADB to connect, and was able to enter EDL through ADB.
-Re-downloaded ROM from web.
-Re-extracted.
-FLASHED SUCCESSFULLY!
-SETUP COMPLETED SUCCESSFULLY!
-YAY!
(I think the original download was corrupted, somehow.)
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
please some can you help with the porting of twrp for this phone
even some help with official firmware v217 then we can root with magiusk and recovery image
this phone has the mtk processor MT6765
Infinix hot 8 pliss, i can instal twrp
Yes, help sir ? :good:
Infinix Hot 8 Need Support
Please really need support for root and twrp for this device,, this device is really nice,,
guys again some try and get the firmware v217 so we can extract the boot.img for magisk
i hope a update is coming soon plan to get thta to find this boot.img
online the v174 firmware is not the same
OTA Update for Infinix
X650C-H626DE-P-191005V224.zip
240Mb
capture via usbdebugg
http://www.mediafire.com/file/24dmq3hk7wbu6b3/X650C-H626DE-P-191005V224.zip/file
Mtk(mediatek) processor devices are not supported by custom ROM developers. Don't expect custom rom support for hot infinix 8. Sorry.
Did anyone try Readback in SP Flash tool? So far, I have not been successful in doing so.
got it
To unlock Bootloaded withour error in Fastboot use command
fastboot flashing unlock
and then on the phone select volume up key to acknowledge
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
darylzero said:
phone is booted into fresh android
and now rooted with magisk
thnx guys all done for now
off topic if you have a pihole on rasberry pie you can see that this phone is THE WORST i do mean UTTER DISREGUARD for user privacy and send EVERYTHING and i mean EVERTHING home to china
included is user app usage
user data
crash analytics
with root i will NOW TAKE CARE to THIS
any one needs boot.img modified for firmware 216 for magisk root will upload it
Click to expand...
Click to collapse
Screenshots
and UPLOAD THE orignal+patched BOOT.img
With complete VERSION INFO
Sent from my Infinix-X650C using XDA Labs
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Thank you very much.
My phone now has root access
Are you installed TWRP Recovery in your device.???
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
Are you installed TWRP Recovery in your device.i want TWRP recovery.can I install TWRP recovery after root my device.tel me.
https://forum.xda-developers.com/android/help/infinix-hot-8-t3986799/post80598837
Check this Thread for complete guide on
* UNLOCKING-BOOTLOADER
* ROOTING
* TWRP
* OPTIMIZATION
* UN-BRICKING
* CUSTOM-ROM
Sent from my Infinix-X650C using XDA Labs
How can I root my infinix hot 8 v x650D
Misbahu said:
How can I root my infinix hot 8 v x650D
Click to expand...
Click to collapse
Same method as I stated above.. just use compatible TWRP
Sent from my Infinix-X650C using XDA Labs
darylzero said:
Boot.img Magisk patched
https://www.mediafire.com/file/0nzyd8t9yu8vqpd/magisk_patched.img/file
Original Boot.img
http://www.mediafire.com/file/32gtumg9q6r46bi/boot.img/file
downloaded the uploaded firmware from google drive v236 i think
used techno tool to flash this to phone to VERIFY the firmwareis good and proper
once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it
got this patched boot.img back to computer
now for the flashing part
install ADB drivers
on phone activate usb debug and oem unlock in developer mode in settings
check ADB is working and sees phone n computer via usb with command
"adb shell"
shouls show a valid response indicating phone is ADB ready
next get it into Fastboot mode with command
"adb reboot bootloader"
wait till phone reboots into fastboot mode check fastboot mode is active with this command
"fastboot devices"
now to unlock bootloader in fastboot else it will give error
use command
"fastboot flashing unlock "
this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree
once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched
i have uploaded this to medifire please download
place this file named
magisk_patched.img on desktop
use command boot
"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"
wait till magic is done
after use to
"fastboot reboot "
after phone reboot it will b factory reset and rooted check root with magisk manager installed
root checked verified
https://www.mediafire.com/view/a2ivwbm530gdb9v/Screenshot_20191210-122733.png/file
Click to expand...
Click to collapse
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Papichoolo said:
I have an Infinix Hot 8 X650B.
I am trying to root the device. I have installed all ADB required files and the drivers.
The computer detects the drivers and the device is showing in ADB Device list.
But it's not being listed in fastboot devices check, and no fastboot command is working.
Please what can I do?
Click to expand...
Click to collapse
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
AshhRED said:
Try Installing driver's on an different computer and check if it loads to fastboot.
Sent from my Infinix-X650C using XDA Labs
Click to expand...
Click to collapse
I tried on a different PC with Windows 7, same issue. ADB Loads and detects, but fastboot doesn't.
It shows under ADB Devices but when I type, adb reboot bootloader.
The phone goes into fastboot mode, but isn't detected when using command, fastboot devices.
Drivers and eveything is setup correct on it too.
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Message me on telegram @benzoylperoxide
Hope I could help you with this situation.
If you got data, download fastboot rom based on nought and fastboot rom 9.5.30
Download latest miflash tool from miglobe website.
Install proper drivers from miunlock tool zip file.
And Hope for the best.
Ping me tommorow at anytime.
Good night Bro
incertam7 said:
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Click to expand...
Click to collapse
Flash system error in MiFlash? Probably the stock rom you downloaded and extracted is corrupted.
Please try flashing MIUI 9 for your Redmi 5.
Yeah, users have had issues with twrp being replaced by stock rom.
For TWRP,
fastboot flash revovery (recovery name.img)
Fastboot boot (recovery name .img)
After that flash your custom rom after wiping system,boot, vendor, data and cache, Internal format might be needed if it's encrypted.
Then, after custom rom is flashed, flash gapps and then twrp zip in TWRP, yeah you saw it right, flash twrp zip in TWRP. This way, twrp won't get replaced.
You can give directly flashing TWRP and flashing custom rom the way I told, Flashing Miui isn't important if your goal is to flash custom rom.
Hi! I would like to mod my AC2003 upgraded to oxygenos 12.1 (android 12) version AC2003_11_F.13
Could you please tell me the steps to proceed? I can't find a guide that answers all my questions ... Do I need to unlock the bootloader first? Then the recovery and the rom? I would be oriented towards the pixel experience, can it be a good choice? Does it support 2 sims? How to do with the root for the bank's applications? Many questions, and nowhere to start ... Thanks in advance
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Be aware that you will miss some camera features with any custom rom... Full camera features are only available with the stock rom..
Thats why I moved back to stock rom and debloated all unuseable stuff...
But a custom rom offers many other opportunities that the stock rom doesn't have...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wan't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat, it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
Wow! You wrote the bible for the beginner ... I don't know how to thank you for your patience, now I have a great starting point
I've a problem, fastboot can't see my device... I've installed the oneplus drivers, but windows continues to use Microsoft's drivers. I tried to update the drivers from the device manager indicating as drivers those installed in the Oneplus folder, but windows keeps telling me not to find drivers compatible with an x64 system in that folder. I also tried to disable the digital signature check, without success. This is on both windows 11 and windows 10 PCs. I've also enabled debug usb...
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
dabyd64 said:
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
Click to expand...
Click to collapse
It seems you're not in fastboot Mode?
Do you see this screen?
dabyd64 said:
It seems you're not in fastboot Mode?
Do you see this screen?
Click to expand...
Click to collapse
The cable was the problem...Now i've tried with it's original cable and yes, i can see it! Thank you so much...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
After flash recovery, when i go to the recovery mode, i see this mex:
"The current image (boot/recovery) have been destroted and can not boot. Please flash the correct image or contact customer service to fix"
Fortunately i have solved with msm....
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
gorro8 said:
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
Click to expand...
Click to collapse
Hi,
I am on OS12 stock currently.
At which stage of the guide posted above I need to use the unbrick tool ?
Many thanks
Hi bro.
If you want to flash any custom ROM, then you need to go to unbrick tools thread, download drivers and MSM tool firmware and step by step flash it.
After that flash custom rom you need also with it instruction in the thread.