I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
Missing ROM Due to a misunderstanding, you have already wiped all ROM data from phone (cache, dalvik, and system) and fastboot flashed the kernel. Now phone hangs on HTC boot screen and will not load Android. Only the kernel has been flashed, the screen hangs because there is no OS to load. Fear not, return to recovery and flash the ROM package that your boot.image originated from. Now select reboot to system and wait for your phone to restart. The kernel will boot, your OS will load, and all will be right with the world.
Click to expand...
Click to collapse
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
yoerz said:
I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
Click to expand...
Click to collapse
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
bigdaddy619 said:
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
Click to expand...
Click to collapse
Thanks for the help man, I'm just not sure HOW to flash the boot.img/kernel first then flash the rom from twrp
1. Where do I get the Boot.img/kernel? is it just a file I download?
2. What's the command to flash it to the device?
THANK U
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
bigdaddy619 said:
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Click to expand...
Click to collapse
Well, clearly "Flash Image GUI" isn't going to help me because as I stated before, my device is in boot loop.
I've placed boot.img in my C:\ROOT folder where I keep all my root related files (like ADB and FASTBOOT) but when I run the command:
fastboot flash boot.img
I get the error: unknown partition 'boot.img' error cannot determine image filename for boot.img
Should be
fastboot flash boot boot.img
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
yoerz said:
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
Click to expand...
Click to collapse
Try this
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Whats next
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
yoerz said:
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
Click to expand...
Click to collapse
Choose recovery from the bootloader then flash the rom like you normally would
ALL GOOD
NEVER MIND! That totally did it! Wonderful! Thank you so much for your help man!
I REALLY appreciate it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hi xda !
As the title says, my Prime can't get into recovery, and I can't factory reset it from within Android's settings either for some reason. How or why this happened, I don't know. I wish I knew, but it's as if everything related to recovery has just disappeared.
It can boot into Android no problem and I can connect to it via fastboot, which in my eyes just make this whole thing seem even weirder.
The tablet is running stock rooted Android 4.1.1, bootloader version is, I think - not completely sure, US_epad-10.4.2.15-20120917. I am not sure if that is the right number, so here you go:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When selecting the recovery option it just hangs there until I reboot the tablet.
So far I've tried flashing TWRP 2.6.3.0-JB through fastboot, which finished successfully (at least according to fastboot, anyway) with no errors. But still recovery is nowhere to be found.
Does anyone have any idea how to solve this problem and get recovery back on my Prime ? Or at least factory reset it without recovery ?
Tricky547 said:
Hi xda !
As the title says, my Prime can't get into recovery, and I can't factory reset it from within Android's settings either for some reason. How or why this happened, I don't know. I wish I knew, but it's as if everything related to recovery has just disappeared.
It can boot into Android no problem and I can connect to it via fastboot, which in my eyes just make this whole thing seem even weirder.
The tablet is running stock rooted Android 4.1.1, bootloader version is, I think - not completely sure, US_epad-10.4.2.15-20120917. I am not sure if that is the right number, so here you go:
When selecting the recovery option it just hangs there until I reboot the tablet.
So far I've tried flashing TWRP 2.6.3.0-JB through fastboot, which finished successfully (at least according to fastboot, anyway) with no errors. But still recovery is nowhere to be found.
Does anyone have any idea how to solve this problem and get recovery back on my Prime ? Or at least factory reset it without recovery ?
Click to expand...
Click to collapse
You have unlocked the bootloader ?
Thx Josh
lj50036 said:
You have unlocked the bootloader ?
Thx Josh
Click to expand...
Click to collapse
If the "bootloader is unlocked" text while booting the tablet is to be believe, yes, the bootloader is unlocked and the tablet is rooted. Recovery worked fine a couple years ago when I was using CM nightlies on it, then it just stopped working out of nowhere sometime after I got the current stock pre-rooted Jellybean rom on it.
I don't know if flashing Jellybean is what triggered this whole problem in the first place or if it's something that happened afterwards.
What really puzzles me though, is how I can flash TWRP through fastboot "successfully", and it just keeps on not working as if nothing happened.
Tricky547 said:
If the "bootloader is unlocked" text while booting the tablet is to be believe, yes, the bootloader is unlocked and the tablet is rooted. Recovery worked fine a couple years ago when I was using CM nightlies on it, then it just stopped working out of nowhere sometime after I got the current stock pre-rooted Jellybean rom on it.
I don't know if flashing Jellybean is what triggered this whole problem in the first place or if it's something that happened afterwards.
What really puzzles me though, is how I can flash TWRP through fastboot "successfully", and it just keeps on not working as if nothing happened.
Click to expand...
Click to collapse
Post the exact input and out put of flashing a recovery....
Thx Josh
lj50036 said:
Post the exact input and out put of flashing a recovery....
Thx Josh
Click to expand...
Click to collapse
Alright, just flashed recovery, here you go.
Code:
C:\>fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
sending 'recovery' (7934 KB)...
OKAY [ 2.915s]
writing 'recovery'...
OKAY [ 7.228s]
finished. total time: 10.145s
Exactly the same input and output as the other times I've tries this, but somehow it got me a working recovery this time around. I've no idea what changed for it to suddenly work, but I guess that's it for this thread.
Thanks for your help !
Tricky547 said:
Alright, just flashed recovery, here you go.
Code:
C:\>fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
sending 'recovery' (7934 KB)...
OKAY [ 2.915s]
writing 'recovery'...
OKAY [ 7.228s]
finished. total time: 10.145s
Exactly the same input and output as the other times I've tries this, but somehow it got me a working recovery this time around. I've no idea what changed for it to suddenly work, but I guess that's it for this thread.
Thanks for your help !
Click to expand...
Click to collapse
You can always hit the thx button .......
Great to see you up and running.....
Can you add 'SOLVED' to the thread title ...
Thx Josh
Hello everyone.
I wanna start this by saying that I'm very new to all this rooting and custom roms.
So I rooted my Nexus 5 and installed multirom and a couple of roms, being the tinkerer that I am, I went to the recovery settings to mess with it, and I wiped the phone clean by mistake. Everything gone, even the OS.
Now I have no idea how to fix it, any help will be appreciated.
iyzyz said:
Hello everyone.
I wanna start this by saying that I'm very new to all this rooting and custom roms.
So I rooted my Nexus 5 and installed multirom and a couple of roms, being the tinkerer that I am, I went to the recovery settings to mess with it, and I wiped the phone clean by mistake. Everything gone, even the OS.
Now I have no idea how to fix it, any help will be appreciated.
Click to expand...
Click to collapse
Boot into TWRP recovery and connect to your PC. Download a ROM from your development forums to your PC. You should see your nexus 5 internal storage listed on your PC. Drag and drop the ROM from PC to your internal storage. Flash ROM with TWRP, profit.
Evolution_Tech said:
Boot into TWRP recovery and connect to your PC. Download a ROM from your development forums to your PC. You should see your nexus 5 internal storage listed on your PC. Drag and drop the ROM from PC to your internal storage. Flash ROM with TWRP, profit.
Click to expand...
Click to collapse
When I choose Recovery Mode in the bootloader, I just get a black screen and it stays that way!
I don't know how you managed to wipe the recovery but here is how to fix it:
Download TWRP for nexus 5
Boot into bootloader, connect to pc and:
fastboot flash recovery /path/to/recovery.img
if that doesnt work do this:
fastboot boot /path/to/recovery.img
nagalun said:
I don't know how you managed to wipe the recovery but here is how to fix it:
Download TWRP for nexus 5
Boot into bootloader, connect to pc and:
fastboot flash recovery /path/to/recovery.img
if that doesnt work do this:
fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Sorry but how do I type this " /path/to/recovery.img" in the command prompt? I have the twrp file on the desktop.
iyzyz said:
Sorry but how do I type this " /path/to/recovery.img" in the command prompt? I have the twrp file on the desktop.
Click to expand...
Click to collapse
Make sure you have the TWRP.IMG somewhere where fastboot can find it, ie in your platform-tools folder. Open command prompt there by holding shift and right clicking in that location. Select open command window here. Then type: fastboot flash recovery (name of)recovery.img
I suggest renaming the TWRP IMG to either recovery.img or TWRP.img , remember, Windows will automatically add the extension so only rename it TWRP or recovery. Otherwise, you'll end up with a file named recovery.img.img
Then after renaming, you'd type:
fastboot flash recovery TWRP.img or if renamed to recovery:
fastboot flash recovery recovery.img
Evolution_Tech said:
Make sure you have the TWRP.IMG somewhere where fastboot can find it, ie in your platform-tools folder. Open command prompt there by holding shift and right clicking in that location. Select open command window here. Then type: fastboot flash recovery (name of)recovery.img
I suggest renaming the TWRP IMG to either recovery.img or TWRP.img , remember, Windows will automatically add the extension so only rename it TWRP or recovery. Otherwise, you'll end up with a file named recovery.img.img
Then after renaming, you'd type:
fastboot flash recovery TWRP.img or if renamed to recovery:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Oh nevermind I got it from here
When I try to flash the rom I get this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: IT WORKED! I downloaded a Cyanogen rom and it worked! Thanks a lot everyone.
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
hey so, as the title says, i'm currently unable to install the recovery on my phone and have been trying for the past 3 hours or so now :/
Phone's unlocked, adb and fastboot are working ecc.
but whenever i try to flash the TWRP recovery or even boot it i get the FAILED (remote: 'size too large') error and idk what to do about it.
It worked weirdly with the nikel recovery but even then it installed badly and wouldnt let me flash mido roms for whatever reason and yes im 100% sure my phone is a 4x with a snapdragon.
Thanks to anyone that replies and tries to help
biggestpoyo said:
hey so, as the title says, i'm currently unable to install the recovery on my phone and have been trying for the past 3 hours or so now :/
Phone's unlocked, adb and flashboot are working ecc.
but whenever i try to flash the TWRP recovery or even boot it i get the FAILED (remote: 'size too large') error and idk what to do about it.
It worked weirdly with the nikel recovery but even then it installed badly and wouldnt let me flash mido roms for whatever reason and yes im 100% sure my phone is a 4x with a snapdragon.
Thanks to anyone that replies and tries to help
Click to expand...
Click to collapse
Describe how are you trying to flash the file, like using cmd window or mi flash tool or by already rooted phone?
Ebebeeh said:
Describe how are you trying to flash the file, like using cmd window or mi flash tool or by already rooted phone?
Click to expand...
Click to collapse
So, downloaded the ADB and Fastboot tools, downloaded TWRP, went to the CMD and changed the directory to the adb.
From here i just used the adb reboot bootloader command to get into the fastboot.
Next i used the fastboot flash recovery x.img command to try to flash it but didnt work simply giving me a "FAILED (remote: 'size too large')" on the last part.
I even tried the fastboot boot x.img command.
Also yes when i said flashboot prieviously i meant fastboot mb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
biggestpoyo said:
So, downloaded the ADB and Fastboot tools, downloaded TWRP, went to the CMD and changed the directory to the adb.
From here i just used the adb reboot bootloader command to get into the fastboot.
Next i used the fastboot flash recovery x.img command to try to flash it but didnt work simply giving me a "FAILED (remote: 'size too large')" on the last part.
I even tried the fastboot boot x.img command.
Also yes when i said flashboot prieviously i meant fastboot mb
Click to expand...
Click to collapse
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Try this one :-
https://dl.twrp.me/mido/twrp-3.3.1-0-mido.img
Let me know if it works.
Ebebeeh said:
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Let me know if it works.
Click to expand...
Click to collapse
I'm using the MIUI global 10.2.1 so marshmellow but yeah, i've been trying that img along with older versions and what not but it just keeps giving the same error for whatever reason
Ebebeeh said:
Which rom are you using currently? If it is android nougat based then read below, if higher the commands are a bit different I guess,
That is the same way i did it but it might be cause you are flashing wrong recovery.
Try this one :-
https://dl.twrp.me/mido/twrp-3.3.1-0-mido.img
Let me know if it works.
Click to expand...
Click to collapse
Try using mi flash tool with the same image file, you will find the tool on their official website.
biggestpoyo said:
I'm using the MIUI global 10.2.1 so marshmellow but yeah, i've been trying that img along with older versions and what not but it just keeps giving the same error for whatever reason
Click to expand...
Click to collapse
You have MTK variant (Nikel) and trying to flash Snapdragon (Mido) TWRP.
updated to 11.0.2 MIUI and root disapeared , using ADB for TWRP installing , everything goes ok, but after command fastboot reboot , when phone reboots, there is no TWRP , only standart recovery, What I am doing wrong?
Hi, so I successfully installed TWRP from here, everything went well until this point. I flashed a more stable EU rom and then tried to flash Magisk, but when I rebooted it just went to fastboot mode.
Now everytime I try to turn it off or go back into TWRP it just goes to fastboot mode.
I have tried to flash using MiFlash but I can't seem to get the right thing to flash apparently.
When trying to reinstall TWRP
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.498s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.503s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zelyric said:
View attachment 5448807
Click to expand...
Click to collapse
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
akins0405 said:
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
Click to expand...
Click to collapse
Reading on that post I saw that there are issues with Ryzen powered computers, and I indeed have a Ryzen CPU. Really hopes this helps, thanks for showing me regardless - ill keep you updated!
@akins0405
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try flashing you stock boot img
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
Where do I find that?
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
You have it in fastboot stock rom
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
Try to transfer the rom to the system partition
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
adb doesn't show my device under adb devices but fastboot devices does show it..
MTP also is disabled
Zelyric said:
adb doesn't show my device under adb devices but fastboot devices does show it..
Click to expand...
Click to collapse
Flash in fastboot stock boot img, can you do it
akins0405 said:
Flash in fastboot stock boot img, can you do it
Click to expand...
Click to collapse
fastboot flash b boot.img
Sending 'b' (196608 KB) OKAY [ 4.817s]
Writing 'b' FAILED (remote: '(b_a) No such partition')
fastboot: error: Command failed
nevermind, i understood the partition wrong.
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.558s]
Writing 'boot_a' OKAY [ 0.707s]
Finished. Total time: 6.103s
what now?
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try firstly erasing your recovery partition with fastboot erase recovery
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Zelyric said:
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Click to expand...
Click to collapse
I'm glad you made it, hello