I have recently been interested in wanting to install a ubuntu onto my tablet, so i am installing twrp first, i have downloaded the android SDK files and have extracted them with adb and fastboot into my c: drive, i have also unlocked my device by using the Asus unlock tool, i then when into the i believe its called bootmenu where you can choose between usb,rck,coldboot,ect and downloaded the fastboot driver into my usb 3.0 after that i flashed twrp using "fastboot -i 0x0b05 flash recovery twrp.blob" in cmd everything went well the blue bar loaded, the cmd said it finished.
Now this is where the problem starts when i enter RCK (recovery mode) it just freezes there like the fastboot, the icon stops flashing and text appears saying "booting recovery image kernel" but nothing happens. To my knowledge and the guide i am following it should boot to twrp if im not mistaken.
I am using windows 7 for my pc and have updated my tablet to 4.1.1, i have also check the Md5 codes. I am also following this guide (http://forum.xda-developers.com/show....php?t=2038464).
If anyone could help out someone trying to get into roms for andriod that would be awesome thank you.
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
You should unlock the bootloader first after rooting your device
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Ospider said:
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
Click to expand...
Click to collapse
Check my thread for custom marshmallow rom and twrp recovery .
https://forum.xda-developers.com/android/general/bliss-rom-lenovo-vibe-c-a2020a40-t3567812
rolland.arriza said:
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Click to expand...
Click to collapse
But how about a person WITHOUT PC? Including me.
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
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.