Hi
I followed this guide https://wiki.lineageos.org/devices/I01WD/install
but got stuck at the following step:
fastboot flash boot lineage-17.1-20200423-recovery-I01WD.img
it went OK, I got the following response:
Sending 'boot_a' (98304 KB) OKAY [ 2.434s]
Writing 'boot_a' OKAY [ 0.538s]
Finished. Total time: 2.999s
But after that the phone is stuck in the bootloader, wont go into recovery or start the OS, just loops back into bootloader.
What would be the best way to proceed?
Did you try to boot from a twrp image?
abprie said:
Did you try to boot from a twrp image?
Click to expand...
Click to collapse
No, I haven't.
Should I try the following?
fastboot flash boot twrp-3.3.1-4-I01WD.img
Without any other steps in between?
Yes, but I'd install this TWRP instead.
BeardKing said:
Yes, but I'd install this TWRP instead.
Click to expand...
Click to collapse
True, take care of the version. Worked for me...
Related
When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?
Akio8 said:
When I try flash a recovery image using the command prompt I receive the following error:
fastboot flash recovery recovery.img
sending 'recovery' (8956 KB)...
OKAY [ 1.105s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.355s
How to resolve error?
Click to expand...
Click to collapse
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?
htc_one_mini_m4 said:
Have you successfully unlocked the bootloader ?
Which recovery image are you trying to flash ?
Click to expand...
Click to collapse
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img
Akio8 said:
Yes the bootloader is unlocked. I'm trying to flash philz-touch-6.26.1-m4.img
Click to expand...
Click to collapse
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )
htc_one_mini_m4 said:
Can you try flashing TWRP 2.7.1.1 instead ? ( Just to see if it's a general issue or something related to your image file )
Click to expand...
Click to collapse
It's a general issue it doesn't matter what image I try to flash
Akio8 said:
It's a general issue it doesn't matter what image I try to flash
Click to expand...
Click to collapse
So, you're stuck with the stock recovery or with a custom one ?
I'd try to install an unsecured kernel + ROM like Jmz's and try flashing a new recovery after that.
Not sure if it would work, just my thoughts and gut says that it might
My honor 4c is stuck on logo and it does not even go to recovery mode even after pressing the power and volume buttons...i installed twrp and i messed up with stock kernel...plz help me i am naive in this
Tayyabmalik said:
My honor 4c is stuck on logo and it does not even go to recovery mode even after pressing the power and volume buttons...i installed twrp and i messed up with stock kernel...plz help me i am naive in this
Click to expand...
Click to collapse
Dload method is also not working?
Dload method will work only if i am able to access recovery menu which i can't...
I am only able to access fastboot mode...So, is there any way to hard reset/hard flash back to factory recovery/firmware/kernel through fastboot mode?
Also, is there any possible hardware solution to this?
Tayyabmalik said:
Dload method will work only if i am able to access recovery menu which i can't...
I am only able to access fastboot mode...So, is there any way to hard reset/hard flash back to factory recovery/firmware/kernel through fastboot mode?
Also, is there any possible hardware solution to this?
Click to expand...
Click to collapse
Extract recovery from firmware file..
Flash recovery via fastboot then perform dload..
hassanjavaid8181 said:
Extract recovery from firmware file..
Flash recovery via fastboot then perform dload..
Click to expand...
Click to collapse
Are u refering to the wifi recovery option in fastboot mode after which the phone asks me to insert a memory card to restore? Do i have to put a memory card with the zip file or the update file or some other file? Thank u for trying to help
hassanjavaid8181 said:
Extract recovery from firmware file..
Flash recovery via fastboot then perform dload..
Click to expand...
Click to collapse
C:\Program Files\platform-tools>fastboot flash boot boot.img
target reported max download size of 524288000 bytes
sending 'boot' (22704 KB)...
OKAY [ 0.672s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.704s
C:\Program Files\platform-tools>fastboot flash-all
fastboot: usage: unknown command flash-all
C:\Program Files\platform-tools>fastboot flash recovery stock.img
target reported max download size of 524288000 bytes
sending 'recovery' (9306 KB)...
OKAY [ 0.284s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.316s
These errors come up when i try to flash stock kernel and recovery images on fastboot
Tayyabmalik said:
C:\Program Files\platform-tools>fastboot flash boot boot.img
target reported max download size of 524288000 bytes
sending 'boot' (22704 KB)...
OKAY [ 0.672s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.704s
C:\Program Files\platform-tools>fastboot flash-all
fastboot: usage: unknown command flash-all
C:\Program Files\platform-tools>fastboot flash recovery stock.img
target reported max download size of 524288000 bytes
sending 'recovery' (9306 KB)...
OKAY [ 0.284s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.316s
These errors come up when i try to flash stock kernel and recovery images on fastboot
Click to expand...
Click to collapse
You rename recovery.img to recovery stock??
hassanjavaid8181 said:
You rename recovery.img to recovery stock??
Click to expand...
Click to collapse
Yes!!! This error comes up no matter whar i rename the stock recovery or stock kernel images...it probably means that phone space is not enough...what do i do now?
hassanjavaid8181 said:
You rename recovery.img to recovery stock??
Click to expand...
Click to collapse
Please help me...can u plz also refer this problem to other senior members?
Tayyabmalik said:
Please help me...can u plz also refer this problem to other senior members?
Click to expand...
Click to collapse
before installing twrp did you unlock your bootloader?
I dont know the product ID for requesting the unlock code...how do i obtain the product ID?
Hi
miststudent2011 said:
before installing twrp did you unlock your bootloader?
Click to expand...
Click to collapse
I do not know the product ID...phone is in bootloop...how do i get the product ID for unlocking bootloader? It is not written on the box
Shah65367 said:
Hi
Click to expand...
Click to collapse
Hey..please state your problem you facing.
hassanjavaid8181 said:
Hey..please state your problem you facing.
Click to expand...
Click to collapse
How do i find the product ID for requesting unlock code?
Tayyabmalik said:
How do i find the product ID for requesting unlock code?
Click to expand...
Click to collapse
Your device in bootloop..
I thick it should be written under back cover if you can remove your back cover..
hassanjavaid8181 said:
Hey..please state your problem you facing.
Click to expand...
Click to collapse
Hassan lineage 14.1 not installing in my huawei honor 4c its showing error 7
Shah65367 said:
Hassan lineage 14.1 not installing in my huawei honor 4c its showing error 7
Click to expand...
Click to collapse
are you using latest twrp?
hassanjavaid8181 said:
are you using latest twrp?
Click to expand...
Click to collapse
I am using 3.0.2 is it latest?
Shah65367 said:
I am using 3.0.2 is it latest?
Click to expand...
Click to collapse
No 3.1.1 is the latest one available for 4c get it from my thread in 4c section
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
What's the message that appears in ADB when you flash it?
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
Did u unlocked the bootloader?
Sent from my Redmi Note 7 Pro using XDA Labs
Naveenthemi said:
What's the message that appears in ADB when you flash it?
Click to expand...
Click to collapse
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
toyspeed said:
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
Click to expand...
Click to collapse
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Naveenthemi said:
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Click to expand...
Click to collapse
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
toyspeed said:
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
Click to expand...
Click to collapse
Did it work?
Naveenthemi said:
Did it work?
Click to expand...
Click to collapse
I actually decided to flash Superior OS instead, loving it so far!
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
jimmy987654321 said:
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
Click to expand...
Click to collapse
Use Peter's twrp or flash fastboot rom with miflash
urstrulynaveen said:
Use Peter's twrp or flash fastboot rom with miflash
Click to expand...
Click to collapse
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
jimmy987654321 said:
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
Click to expand...
Click to collapse
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
jimmy987654321 said:
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
Click to expand...
Click to collapse
Were you able to lock your bootloader
after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?
barbosa212 said:
after unlocking my bootloader i tried to flash magisk.zip in fastboot mode by typing fastboot flash boot magisk.zip
now im stuck in fastboot mode. Enter reason: boot failure
with oneplus devices you can always go back to stock with msm tool. is there anything like that for pixel devices? or did i just turn my new phone into a shiny new paper weight?
Click to expand...
Click to collapse
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.
Lughnasadh said:
To root you flash the patched boot image (the one you patched in Magisk), not magisk.zip.
Try flashing the stock boot image to get back to normal and then flash the patched boot image in fastboot.
See this guide.
Click to expand...
Click to collapse
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?
barbosa212 said:
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' (bootloader) unable to update boot image: use unmerged...
OKAY [ 0.144s]
Finished. Total time: 1.897s
now im at "waiting for rescue commands..." what do?
Click to expand...
Click to collapse
i held the power button until it rebooted successfully. Thank you so much
barbosa212 said:
i held the power button until it rebooted successfully. Thank you so much
Click to expand...
Click to collapse
If you want to root/flash, I recommend PixelFlasher. A simple and effective tool and saves you from trouble!