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.
Related
Short version - is it possible to copy files from my phone to my PC using fastboot (or perhaps adb)? The cyanogenmod WIKI for fastboot, among others, imply that you can (under the section Examples -> Manual Nandroid Restore it says "Make a Nandroid backup, and copy the folder off your SD card to your desktop."). Sorry I'm not allowed to post the link due to being a new user, but this is what it says:
"Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot"
If it is possible, is "flash" the correct command to be using? The description of the flash command when you run "fastroot help" implies it writes data to the phone, not from the phone to the PC... Unfortunately almost everything I search for around the flash command is examples showing how to load ROMs etc, I can't seem to find anything else that points to it being used to backup data...
[UPDATE] - From what I understand you can't copy files off the phone using fastboot commands, but can using adb - so a few questions:
- Does anyone know why adb wouldn't see my device (when I run "adb devices") but fastboot does (note that I'm on the fastboot screen)?
- Does adb require debugging mode to be on?
[UPDATE-2] - Still can't get adb working, suspect it's because USB debugging isn't enabled (though not sure how I can check?). I did try using fastboot to erase the /cache partition in case the lockout data was stored in there - but this didn't work unfortunately. Looking likely I'll just have to wipe it with fastboot oem unlock
Long version / background info:
Using a Samsung Nexus S with Android 4.1
The other night someone down the pub decided to try to unlock my phone, and apparently got the pattern wrong so many times it's now requiring me to enter my Google account details.
Fine, I enter the username / pass, only it says they're wrong - I know they're correct because I've just confirmed they are by logging into Gmail. It says they're incorrect so quickly that I suspect it's not even connecting to the web to check. The icons at the top imply there is signal, but it looks as though 3G / data is off, and there's no WiFi icon even though I'm sat next to my wireless router. I can't find any way to re-enable WiFi / 3G without first unlocking the phone - which requires a net connection. So I got into Fastboot Mode and selected Recovery and the device looks as though it's doing something (deleting all user data I assumed), but when it starts up it's exactly the same - which implies the user data hasn't been erased.
Then I installed fastboot, and the drivers for the Nexus S.
When I run "fastboot devices" I can see the phone listed, however bizarrely "adb devices" lists nothing.
"fastboot oem unlock" seems to work (the phone prompts me to confirm I want to give root access & delete all user data). I haven't done this yet as I want to see if I can save my data somehow using adb or fastboot commands.
For adb to work, your phone must be booted and USB debugging enabled. In your current situation, as far as I know, a factory reset is the only option.
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Thanks, I did try fastboot with a recovery image, but it currently doesn't work because I need to unlock the bootloader (which will wipe all data anyway). Sounds like I will need to just wipe it
kuisma said:
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Click to expand...
Click to collapse
Facing same issue.
Is there anyway so I could copy userdata.img to my pc and then delete gesture.key file (I am running Lollipop) with NO USB DEBUGGING ON in Fastboot mode.
I have gone through "unpacking and packing .img files"http://forum.xda-developers.com/galaxy-s2/general/ref-unpacking-repacking-stock-rom-img-t1081239
But it is out of my knowledge range can anyone get through it and explain me the same.
Hi! I am in the same situation... ADB not working, only fastboot... Any way to save my data? Do I need to unlock bootloader to install a stock recovery? Thank you!
Hi - I am in exactly same situation as well. I am using Oneplus 8t. Any help is greatly appreciated. thanks
Hello, first post and fisrst tutorial here.
So here I want to show you how you can restore completely died LG p760(or his brothers p765/p768/p769) showing nothing or just LG Logo and so well known "Security Error", or boot loop problems.
The goal is to flash stock recovery, x-loader and u-boot and to unlock the bootloader(u-boot), so it can boot Clockworkmod or TWRP recovery.
First of all you'll need a computer(preferably Win7/8), an died phone , some drivers on the computer and fastboot on the phone. Let's start.
I'm not responsible for any damage to your device made during this guide. You can continue at YOUR OWN RISK.
Please READ IT before taking any actions on your phone!
1. Get fastboot on the phone. How? You can see here and here, or search the internet. There is a driver package, install them following the instructions.
2. After you inserted phone, installed drivers, etc. start the fastboot loader script(I prefer Lelus's one, i'ts more option-rich), and select one option for ICS x-loader and u-boot for your phone. Follow the instructions, it may take 2 or 3 tries before the drivers are correctly installed. Start again if the drivers are not correctly installed.
3. Copy the bin folder that is inside the fastboot files folder in C:, press winkey+R, type cmd and press OK.
Then copy everything from v20c_00 folder inside the C:\bin\ folder, it's in attachments in the end.
Here is the time to say that this files are for p760 only, you can find x-loader, u-boot and stock recovery for you model from internet, or here in the forums. I flashed also the boot.img, but don't think it's necessary for the completion of the process. You can also extract the .img files from stock .KDZ rom with this tool here, thanks to user kuma82. In the archive is the tutorial how to make x-loader.img, it's easy.
Let's continue.
Type in:
Code:
cd C:\bin
Check if the phone is in fastboot mode with this command:
Code:
fastboot devices
It must show something like:
Code:
1234567890 fastboot
If not, check that you are in the correct folder(C:\bin\), go and check drivers(no yellow marks or unknown devices), read the instructions again.
Then after you copied the files from archive, or files that you extracted from your stock rom, type in, or copy and paste into the cmd window:
Code:
fastboot erase x-loader
fastboot erase u-boot
fastboot erase boot
fastboot erase recovery
fastboot flash x-loader 0-x-loader.img
fastboot flash u-boot 1-u-boot.img
fastboot flash boot 2-boot.img
fastboot flash recovery 3-recovery.img
You must be fast, because after 30-60 seconds(don't know exactly) of inactivity, the phone will exit the service mode it is in and try to boot. Nothing bad happened, just load fastboot again and repeat the above fastboot commands.
After all the commands are completed without any errors, plug out usb, plug out battery, put the battery in, start the phone. The "Security Error" message MUST be gone. If it's not, probably your recovery is wrong, flash recovery again, if not, try with other recovery. This is working on P760, at least on mine. Here the S/W Update mode must also work like a charm, and you can try with some KDZ updaters, but that's not for this tutorial.
4. Now for step 4 we will need the phone in Recovery Mode. With phone turned off and battery inserted, press VOL_UP+HOME+POWER, when LG logo shows, release POWER and hold other two while the LG Recovery Mode show up. The phone must go straight into recovery, not bootlooping or showing "Security Error". If this happens, probably you recovery or u-boot is wrong.
Now put the usb into the phone and install the drivers from usb_drv_windows folder that is in the fastboot archive.
5. Type into cmd window:
Code:
adb devices
It must show something like:
Code:
1234567890 recovery
If not, you know..
Then we will unlock the bootloader with this command:
Code:
adb oem-unlock
The phone will restart, don't touch nothing. You'll see screen with info on what to do. Guess what..? We must press the VOL_UP button to confirm that we want to UNLOCK the bootloader, so it can load unsigned recoveries like CWM or TWRP and not to show the annoying "Security Error".
6. The phone will go into fastboot mode itself, you must install the drivers, again from the folder in the archive.
Now we'll flash CWM recovery with the help of fastboot. Copy the recovery-clockwork-6.0.2.9-p760 or recovery that is for your model to C:\bin\ folder.
Write:
Code:
fastboot flash recovery recovery-clockwork-6.0.2.9-p760.img
fastboot reboot
The phone will reboot, and hopefully you will not see "Security Error" error message. Now try to boot into recovery - pull the battery out, the usb cable, put battery in, and hold down VOL_UP+HOME+POWER, you know..
7. If everything is successfull you phone will load the recovery and you will be able to load nandroid backup or stock update.zip or CyanogenMod on your phone. Don't forget to wipe cache/data and dalvik's cache. From here you can backup your data or do whatever you want.
If your phone is not totally bricked, and if you are lucky enough you can continue from step 4(if you have recovery in your phone and it's still loading).
DOWNLOAD
I want to attach them here to the forum, but I can't for now, so here is Google Drive folder.
https://drive.google.com/folderview?id=0B9wMsz4X38L2aE5VdGFZcWczcEk
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!
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