I S-offed my HTC one then I RUUed it to remove tampered then tried to flash back a recovery and that wouldn't work even erased cache. If i erase cache to many times it seems to remove system. So I read I have to get a tampered flag back up. Right now it just says
*Unlocked*
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
**
**
OS-3.17.502.3
Any ideas on getting any recovery to stick?
Irish Enigma said:
I S-offed my HTC one then I RUUed it to remove tampered then tried to flash back a recovery and that wouldn't work even erased cache. If i erase cache to many times it seems to remove system. So I read I have to get a tampered flag back up. Right now it just says
*Unlocked*
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
**
**
OS-3.17.502.3
Any ideas on getting any recovery to stick?
Click to expand...
Click to collapse
sounds strange are you using the correct commands? download latest recovery (CWM or TWRP) from the xda threads, place it in your adb folder, then
abd reboot bootloader
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
and enter RECOVERY, should be no problem. if it still fails, copy/paste your command prompt here
nkk71 said:
sounds strange are you using the correct commands? download latest recovery (CWM or TWRP) from the xda threads, place it in your adb folder, then
abd reboot bootloader
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
and enter RECOVERY, should be no problem. if it still fails, copy/paste your command prompt here
Click to expand...
Click to collapse
UPDATE it worked with CWM. All the Twrp flashes were "successful" but they wouldn't stick. Now the latest clockwork sticks no problem. There's something wrong with twrp 2.6.3.0 for GSM. It doesn't work at all.
Yes i downloaded the file many times.
Any ideas i want twrp...
Irish Enigma said:
UPDATE it worked with CWM. All the Twrp flashes were "successful" but they wouldn't stick. Now the latest clockwork sticks no problem. There's something wrong with twrp 2.6.3.0 for GSM. It doesn't work at all.
Yes i downloaded the file many times.
Any ideas i want twrp...
Click to expand...
Click to collapse
Can you post the link from where you downloaded it. I'll give it a shot an let you know if it works on my phone
Hit the thanks button if i helped
nkk71 said:
Can you post the link from where you downloaded it. I'll give it a shot an let you know if it works on my phone
Hit the thanks button if i helped
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2173870
Irish Enigma said:
http://forum.xda-developers.com/showthread.php?t=2173870
Click to expand...
Click to collapse
Worked just fine; download was a bit tough, kept stopping and restarting (i use a download manager)
1- verified MD5: 216d3f836264fc568fe8054263fa26ba
2:
Code:
C:\ADB2>[B]adb reboot bootloader[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.856s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 2.636s
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
entered recovery, and screenshot attached:
nkk71 said:
Worked just fine; download was a bit tough, kept stopping and restarting (i use a download manager)
1- verified MD5: 216d3f836264fc568fe8054263fa26ba
2:
Code:
C:\ADB2>[B]adb reboot bootloader[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\ADB2>[B]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.856s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 2.636s
C:\ADB2>[B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB2>[B]fastboot reboot-bootloader[/B]
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
entered recovery, and screenshot attached:
Click to expand...
Click to collapse
....wtf is wrong with my phone....
Irish Enigma said:
....wtf is wrong with my phone....
Click to expand...
Click to collapse
did you verify MD5?
EDIT: I'll upload it for you, hold on...
---------- Post added at 04:20 PM ---------- Previous post was at 04:15 PM ----------
Irish Enigma said:
....wtf is wrong with my phone....
Click to expand...
Click to collapse
OK, here you go:
openrecovery-twrp-2.6.3.0-m7.img 10.3 MB
https://mega.co.nz/#!KRN3WJjZ!DmbbAR4ZVgbWQTVyv0kOkj3vAF0bTzMg5epyGMZJLk0
verify MD5 is: 216d3f836264fc568fe8054263fa26ba
then
adb reboot bootloader
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
enter RECOVERY
copy/paste your command prompt like I did, to see if we can spot anything wrong.
Hit the thanks button if I helped
nkk71 said:
did you verify MD5?
EDIT: I'll upload it for you, hold on...
---------- Post added at 04:20 PM ---------- Previous post was at 04:15 PM ----------
OK, here you go:
openrecovery-twrp-2.6.3.0-m7.img 10.3 MB
https://mega.co.nz/#!KRN3WJjZ!DmbbAR4ZVgbWQTVyv0kOkj3vAF0bTzMg5epyGMZJLk0
verify MD5 is: 216d3f836264fc568fe8054263fa26ba
then
adb reboot bootloader
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
enter RECOVERY
copy/paste your command prompt like I did, to see if we can spot anything wrong.
Hit the thanks button if I helped
Click to expand...
Click to collapse
i gotta get back to you on that. my phone is encrypting @ %72
Irish Enigma said:
i gotta get back to you on that. my phone is encrypting @ %72
Click to expand...
Click to collapse
encrypting you won't be able to access it from custom recovery anymore. or is that something that is now supported?
nkk71 said:
encrypting you won't be able to access it from custom recovery anymore. or is that something that is now supported?
Click to expand...
Click to collapse
it's not actually. I flashed everything I needed. I have to RUU it to decrypt it.I have recovery issues. I can flash and access recovery I just have to ADB sideload everything now.
Irish Enigma said:
it's not actually. I flashed everything I needed. I have to RUU it to decrypt it.I have recovery issues. I can flash and access recovery I just have to ADB sideload everything now.
Click to expand...
Click to collapse
uh i need someone to analyse my partition tables they seem screwed up.
Irish Enigma said:
uh i need someone to analyse my partition tables they seem screwed up.
Click to expand...
Click to collapse
what do you mean? start reading here: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
before formatting anything, what do you think is corrupt?
first thing is to do this "cat /proc/emmc"
read here: http://forum.xda-developers.com/showthread.php?t=2504542&page=8
Related
Hello.
I don't know if this is the right section ( and if it isnt I deeply apologize)
I think I ruined my HTC One last night though not sure.
I had it unlocked and with Trickdroid on it.
Then I wanted kitkat, did everything by the book, the ROM installed and everything. Everything was good until the first restart.
Since then, it kept on trying to restart. It attempts to enter in recovery mode ( I can see the pink text for few sec) and then is rebooting over and over, in the same sequence:
- wants to reboot but can't
- attempts to enter recovery but falls back into rebooting
I tried EVERYTHING to try and fix it but I think I've ruined it
While holding volume down and power button I can go into recovery ( I think) but no matter what I chose, it follows the same pattern. Attempting, failing, starting over.
If it's any use: I have the S-OFF ( I think, as I did it last night)
Is there anything I can do ?
PLEASE help, Im without a phone..
Re-flash recovery and type fastboot erase cache. See if you are able to get in recovery.
Post your fastboot getvar all output (remove imei/sn)
sent from my mobile device
SaHiLzZ said:
Re-flash recovery and type fastboot erase cache. See if you are able to get in recovery.
Post your fastboot getvar all output (remove imei/sn)
sent from my mobile device
Click to expand...
Click to collapse
First off, let me thank you so much for taking the time to reply.
Your language is way too complicated for me
Im just a graphic designer.
I don't know how to re-flash recovery and where/how to type fastboot erase cache.
OK. You will need to catch up on how to use adb and fastboot commands. There are a few guides which detail their usage. Please familiarize yourself
sent from my mobile device
SaHiLzZ said:
OK. You will need to catch up on how to use adb and fastboot commands. There are a few guides which detail their usage. Please familiarize yourself
sent from my mobile device
Click to expand...
Click to collapse
But...I need help now.
I can't...familiarize myself in a domain I didnt have contact with, in a matter of hours.
Please help me do it. Like I said, I have no phone now, I need a phone
Please, ANYONE ???
Please?
You chose to install a rom without knowing how to troubleshoot. Your phone is S-OFF (supposidly), you have YET to provide ANY information using fastboot getvar all, and you are expecting someone to hand hold you and fix your phone, do I have it right so far??
Better get started on learning how to use ADB, ADB Push, Fastboot commands so that some hand-holding can commence.
[GUIDE] How to ADB Push to fix a formatted /sdcard (Mac + PC) http://forum.xda-developers.com/showthread.php?t=2325853
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash http://forum.xda-developers.com/showthread.php?t=2317986
SaHiLzZ said:
You chose to install a rom without knowing how to troubleshoot. Your phone is S-OFF (supposidly), you have YET to provide ANY information using fastboot getvar all, and you are expecting someone to hand hold you and fix your phone, do I have it right so far??
Better get started on learning how to use ADB, ADB Push, Fastboot commands so that some hand-holding can commence.
[GUIDE] How to ADB Push to fix a formatted /sdcard (Mac + PC) http://forum.xda-developers.com/showthread.php?t=2325853
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Ok, here are some informations I managed to obtain.
INFOversion: 0,5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.401.13
INFOversion-misc: PUT SHIP S-OFF
INFOproduct: m7_ul
INFOPlatform: HBOOT-8064
INFOcidnum: HTC_Y13
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:ALL FAILED (status read failed(Too many links))
finished.total time: 0.069s
Is that helping ?
Sir_Hannibal said:
Ok, here are some informations I managed to obtain.
INFOversion: 0,5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.13
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.29.401.13
INFOversion-misc: PUT SHIP S-OFF
INFOproduct: m7_ul
INFOPlatform: HBOOT-8064
INFOcidnum: HTC_Y13
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:ALL FAILED (status read failed(Too many links))
finished.total time: 0.069s
Is that helping ?
Click to expand...
Click to collapse
Well the first question would be, where did you get that getvar all? it is customary to copy/paste output of the getvar all (XXXing out anything but the first two characters of IMEI and s/n), cause above getvar has way too many faults in it.
But we're not being helpful here are we
so now get yourself TWRP 2.6.3.3 http://techerrata.com/browse/twrp2/m7
(don't use a download manager on that site, and make sure MD5 is correct)
then flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
now, if the <rom i want to install>.zip is not already on your phone:
adb push <rom i want to install>.zip /sdcard/ <- this will take about 5 minutes without any progress
then in TWRP, select "install" -> "choose zip" -> and select the <rom i want to install>.zip
nkk71 said:
Well the first question would be, where did you get that getvar all? it is customary to copy/paste output of the getvar all (XXXing out anything but the first two characters of IMEI and s/n), cause above getvar has way too many faults in it.
But we're not being helpful here are we
so now get yourself TWRP 2.6.3.3 http://techerrata.com/browse/twrp2/m7
(don't use a download manager on that site, and make sure MD5 is correct)
then flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
now, if the <rom i want to install>.zip is not already on your phone:
adb push <rom i want to install>.zip /sdcard/ <- this will take about 5 minutes without any progress
then in TWRP, select "install" -> "choose zip" -> and select the <rom i want to install>.zip
Click to expand...
Click to collapse
It doesnt matter that when I installed Trickdroid, I used Clockwork recovery, right?
I can just install twrp over it or something, corect?
P.s. Thank you SO VERY MUCH for your help. I don't know how else to repay your kindness but if you need an avatar or a forum signature, I promise to do one for you that you will love ! Thank you
Sir_Hannibal said:
It doesnt matter that when I installed Trickdroid, I used Clockwork recovery, right?
I can just install twrp over it or something, corect?
P.s. Thank you SO VERY MUCH for your help. I don't know how else to repay your kindness but if you need an avatar or a forum signature, I promise to do one for you that you will love ! Thank you
Click to expand...
Click to collapse
1- "It doesnt matter that when I installed Trickdroid, I used Clockwork recovery, right?" -> yes it does, if you're using any 4.4 ROM, at the moment the most reliable/recommended custom recovery is TWRP 2.6.3.3 (possible 2.6.3.4), anything else and you may encounter bootloops or failed installation.
2- yes, you can just flash it over CWM, no problems there.
3- xda forum has that little thanks button (on the lower left, of a post), when you feel someone actually helped, it's one way to reward them
4- i should get around to an avatar, maybe i'll take you up on that offer sometime
Let me/us know if you need more help
cheers
@nkk71, as OP is S-OFF, would probably flashing RUU ZIP for 401 region be good?
This one should do the job... http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
Or http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
SaHiLzZ said:
@nkk71, as OP is S-OFF, would probably flashing RUU ZIP for 401 region be good?
This one should do the job... http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
Or http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
Click to expand...
Click to collapse
Hi SaHiLzZ, hope all is well
yes he could, but since I can't really say whether that getvar is correct (sorry no offense to OP), because it has too many unknowns (to be more precise: mistakes) for the output he/she posted, i'm hesitant to recommend flashing a ruu
nkk71 said:
Well the first question would be, where did you get that getvar all? it is customary to copy/paste output of the getvar all (XXXing out anything but the first two characters of IMEI and s/n), cause above getvar has way too many faults in it.
But we're not being helpful here are we
so now get yourself TWRP 2.6.3.3 http://techerrata.com/browse/twrp2/m7
(don't use a download manager on that site, and make sure MD5 is correct)
then flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
now, if the <rom i want to install>.zip is not already on your phone:
adb push <rom i want to install>.zip /sdcard/ <- this will take about 5 minutes without any progress
then in TWRP, select "install" -> "choose zip" -> and select the <rom i want to install>.zip
Click to expand...
Click to collapse
Ok so now, the situation is like this.
1. My phone is connected to the PC and it's on FASTBOOT USB ( nothing happens on its screen)
2. I have 3 cmd windows open
- fastboot recovery openrecovery bla bla.img ( it says: sending "recovery" (9184 KB)
- fastboot erase cche (it says: erasing "cache")
- fastboot reboot-bootloader (it says: rebooting into bootloader...)
NOTHING happens. It's been like this for the past 15 min.
Im doing something wrong clearly so...can you tell me what Im doing wrong?
Sir_Hannibal said:
Ok so now, the situation is like this.
1. My phone is connected to the PC and it's on FASTBOOT USB ( nothing happens on its screen)
2. I have 3 cmd windows open
- fastboot recovery openrecovery bla bla.img ( it says: sending "recovery" (9184 KB)
- fastboot erase cche (it says: erasing "cache")
- fastboot reboot-bootloader (it says: rebooting into bootloader...)
NOTHING happens. It's been like this for the past 15 min.
Im doing something wrong clearly so...can you tell me what Im doing wrong?
Click to expand...
Click to collapse
first copy/past command prompt, stop typing it, if your command prompt isnt in quick edit mode, check out attached screenshot
second, when it went back to bootloader, did you use VOLUME buttons (to scroll) + POWER (to select) and enter RECOVERY?
nkk71 said:
first copy/past command prompt, stop typing it, if your command prompt isnt in quick edit mode, check out attached screenshot
second, when it went back to bootloader, did you use VOLUME buttons (to scroll) + POWER (to select) and enter RECOVERY?
Click to expand...
Click to collapse
Yes, I did just that to get to RECOVERY.
And when you say that I should copy/paste, you mean that I should copy all 3 commands you wrote in your previous post and then paste them into my cmd window here? All 3 at the same time and in the order you wrote them?
Sir_Hannibal said:
Yes, I did just that to get to RECOVERY.
And when you say that I should copy/paste, you mean that I should copy all 3 commands you wrote in your previous post and then paste them into my cmd window here? All 3 at the same time and in the order you wrote them?
Click to expand...
Click to collapse
when i meant copy/paste the output, it would look something like this, as in what YOU typed, and what YOU got out:
Code:
C:\ADB3>[COLOR="Blue"][B]adb reboot bootloader[/B][/COLOR]
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery stock_recovery.img[/COLOR][/B]
sending 'recovery' (9594 KB)...
OKAY [ 1.230s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 2.010s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
^^^ this is just an example of what a command prompt output could look like; not yours.
are you in custom recovery now?
nkk71 said:
when i meant copy/paste the output, it would look something like this, as in what YOU typed, and what YOU got out:
Code:
C:\ADB3>[COLOR="Blue"][B]adb reboot bootloader[/B][/COLOR]
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery stock_recovery.img[/COLOR][/B]
sending 'recovery' (9594 KB)...
OKAY [ 1.230s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 2.010s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
^^^ this is just an example of what a command prompt output could look like; not yours.
are you in custom recovery now?
Click to expand...
Click to collapse
Yeah, because I opened a cmd window for each of the commands you wrote After seeing that the first one does nothing that is.
And yes, I think I am in custom recovery now.
What happens when I use the Vol/Power keys ( I have to, otherwise my phone is stuck in that reboot loop) Vol Down+ Power, is that I get to this screen ( wish I could take a screenshot but I dont have a phone)
TAMPERED
UNLOCKED
M7-UL PVT SHIP S-OFF RH
CID-HTC_Y13
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013,15:46:23-1
HBOOT
(VOL UP) to previous item
(VOL DOWN) to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
No, if I press on FASTBOOT, I get this:
The same first text and digits
Then FASTBOOT USB
Then the whole VOL UP/DOWN thing
And then the following choices:
BOOTLOADER
REBOOT
REBOOT BOOTLODER
POWER DOWN
No matter what I chose ( apart from power down) it send my phone into this rebooting loop.
Sir_Hannibal said:
Yeah, because I opened a cmd window for each of the commands you wrote After seeing that the first one does nothing that is.
Click to expand...
Click to collapse
Why? One command prompt is more than enough.
Sir_Hannibal said:
CID-HTC_Y13
Click to expand...
Click to collapse
Are you intentionally mistyping stuff? or is this what it actually says?
Sir_Hannibal said:
And yes, I think I am in custom recovery now.
Click to expand...
Click to collapse
Well either you are or you are not, nothing to think about.
nkk71 said:
Why? One command prompt is more than enough.
Are you intentionally mistyping stuff? or is this what it actually says?
Well either you are or you are not, nothing to think about.
Click to expand...
Click to collapse
I swear to God, I don't do anything wrong on purpose, including mistyping. That is EXACTLY what it says there.
I know one prompt should be enough but after typing your first command and nothing happened ( but it looked as if its sending something) I opened 2 more, for the other 2 commands. Call me an imbecile...most likely I am...
And I think I managed to get the getvar all as you requested.
So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing
SMOKYxPANDA said:
So I have an LG D415 and I don't know if it's bricked, softbricked, hardbricked or whatever, i'm really a noob and would really appreciate some help, I've included a picture, that shows what pops up when I try entering "Download mode" but I've already tried flashing the KDZ files, I've tried factory resetting the phone, nothing seems to work, phone always shows 0% battery even after charging for over an hour, and so I tried getting into the fastboot commands and stuff, I extracted the laf dz from the kdz files, renamed it to laf.img, put it in the same folder as my fastboot drivers (not even sure if I have the correct drivers) I open up command prompt inside the folder, type in "Fastboot flash laf laf.img" and the following appears in cmd:
target reported max download size of 536870912 bytes
sending 'laf' (13312 KB)...
OKAY [ 0.586s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.739s
I feel like I am missing something or missing some steps, I've got the laf partition, the fastboot drivers(I think) phones in fastboot mode even though at the top it says download mode, no idea as to what to do or try next, if anybody could help it would be very much appreciated...
https://drive.google.com/file/d/0B0shRlbnxbQpTFhYTnpnX3RhVUE/view?usp=sharing
Click to expand...
Click to collapse
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.
0000.0000.00 said:
What ROM are you using? I think you should try flashing the bootstack with recovery from here >> https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. When you flash the bootstack, recovery gets rewritten with an old version of twrp so you probably want to have an IMG of twrp to update to the latest version.
Click to expand...
Click to collapse
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing
SMOKYxPANDA said:
I'm not aware of what ROM the phone is using, and I don't even know if the bootloader is unlocked, or if the phone has TWRP or root, and I don't want to mess the phone up even more (if that's even possible) phone was a friends and he gave it to me, said I could keep it if I could fix it, and i don't currently have a working phone, so it would be really nice to fix this one, i'm really a noob when it comes to this stuff, but I'm willing to learn if that's what it takes to fix the phone, I also included a link that shows a picture of the information that appears when i type in "fastboot getvar all" in command, not sure if that could help you
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view?usp=sharing
Click to expand...
Click to collapse
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?
0000.0000.00 said:
So the first to do is run the command fastboot oem unlock with the phone connected to your computer with fastboot. Then download the latest twrp from https://dl.twrp.me/w7/twrp-3.1.1-0-w7.img and flash it with fastboot flash recovery twrp-3.1.1-0-w7.img making sure that you move the twrp IMG to the directory where fastboot is unless fastboot is on your path where you can just flash it from cmd in the downloads folder. After that, try to factory reset the phone and it should boot into twrp where I would flash the lollipop bootstack linked above with adb sideload "zip name here" where you put the full filename of the zip in zip name here and remove the quotes, boot into the download mode thing which is fastboot and reflash recovery with the instructions above.
---------- Post added at 11:07 AM ---------- Previous post was at 11:02 AM ----------
Also, are you trying to save any data?
Click to expand...
Click to collapse
No, i'm not trying to save any data, I want a fresh start, the problem when trying the "fastboot oem unlock" command is that it gives me an error, again i put a link below to show you what appears when trying that command..
https://drive.google.com/file/d/0B0shRlbnxbQpeFlxcWxjS0l1eE0/view?usp=sharing
This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing
SMOKYxPANDA said:
This is what appears on the phone, yet nothing happens
https://drive.google.com/file/d/0B0shRlbnxbQpQzVXMjZ4d3E5S3M/view?usp=sharing
Click to expand...
Click to collapse
Something probably happened..
Can you please send the results of fastboot getvar all so I can check.
I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view
SMOKYxPANDA said:
I had already sent it, but here it is again:
https://drive.google.com/file/d/0B0shRlbnxbQpR09LNDljU0k0dWM/view
Click to expand...
Click to collapse
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s
SMOKYxPANDA said:
This is the only response I get:
...
FAILED (remote: unkown command)
finished. total time: 0.002s
Click to expand...
Click to collapse
Then try flashing twrp and the bootstack and Tell me how it goes from there.
0000.0000.00 said:
Could you please run fastboot oem device-info and send me an image of the result. I am just checking if the bootloader got unlocked.
Click to expand...
Click to collapse
0000.0000.00 said:
Then try flashing twrp and the bootstack and Tell me how it goes from there.
Click to expand...
Click to collapse
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img"
Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...
SMOKYxPANDA said:
How can I flash TWRP?
I've got a TWRP file named "TWRP_2.8.0.0_26.09.14_L90.img" Tell me where to go from there, and also, the phone isn't even detected using the command "adb devices" it says list of devices and does'nt ever show anything...
Click to expand...
Click to collapse
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
---------- Post added at 02:51 PM ---------- Previous post was at 02:43 PM ----------
0000.0000.00 said:
Flash twrp by first moving the twrp IMG to where fastboot is and running fastboot flash recovery TWRP_2.8.0.0_26.09.14_L90.img with the phone in the download mode thing and connected to the computer.
Also, could you please re-run fastboot getvar all even if you have already run it because its output probably changed and send me an image of what it shows.
Click to expand...
Click to collapse
After that, run fastboot reboot recovery to reboot into recovery. Press the advanced button and then press the button that says adb sideload with the touchscreen and start it. Then to install the zip run adb sideload zipname where zipname is the name of the zip you want to flash.
After that boot back into the download mode thing to reflash recovery and then reboot into recovery with fastboot reboot recovery. After that I would flash the zips for a ROM and optionally gapps with adb sideload.
This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing
SMOKYxPANDA said:
This is what I get:
https://drive.google.com/file/d/0B0shRlbnxbQpN3ZrendPbkI4R1k/view?usp=sharing
Click to expand...
Click to collapse
Were you able to flash recovery and boot into it?
0000.0000.00 said:
Were you able to flash recovery and boot into it?
Click to expand...
Click to collapse
No, you can observe in the picture where it gives me the same error message, unknown command
SMOKYxPANDA said:
No, you can observe in the picture where it gives me the same error message, unknown command
Click to expand...
Click to collapse
Could you please send me a picture of the output of fastboot devices.
---------- Post added at 08:52 PM ---------- Previous post was at 08:48 PM ----------
I think the fastboot on the phone has issues because it seems to not flash anything. I think you should try this >>> https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
asahi7 said:
guys, i am in the exact same situation..phone stuck on lg logo, no recovery possible, no download mode available, only fastboot
i have downloaded and extracted the img files from the original firmware, but i cannot do anything with flashboot commands..pls see below
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
c369bc71 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 5.029s]
finished. total time: 5.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 536870912 bytes
sending 'laf' (15872 KB)...
OKAY [ 0.501s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (13824 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.469s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
all:
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Try https://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
thanks, already did, unfortunately seems like there is a problem with the rom. i flash each file but when i test again i always get slb1 corrupt. no recovery, no download mode. it was worth the try
Hello,
I am trying to update from the old cyanogen recovery to the TWRP recovery in this post: https://forum.xda-developers.com/showthread.php?t=3557606
I have enable to write the cyanogen recovery in the developer options.
I have rebooted into flashboot and executed:
----
[email protected]:/tmp/xperia/TWRP# adb reboot bootloader
[email protected]:/tmp/xperia/TWRP# fastboot flash recovery twrp-3.1.1-0-z3c_V02.img
target didn't report max-download-size
sending 'recovery' (14296 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.502s
[email protected]:/tmp/xperia/TWRP# fastboot reboot
rebooting...
----
Unfortunately the system boots in the cyanogen recovery anyhow.
does anyone knows what am I doing wrong ?
Many thanks in advance
There's an app called NDR Utils that lets you choose which recovery to boot to, but I don't know of a clean link where you can get it.
I got it with Nut's Dual Recovery:
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26
I mean you have to unlock your bootloader with:
Code:
fastboot -i 0x0fce oem unlock 0xhex_unlock_key
(see here)
also you have to erase the old recovery with:
Code:
fastboot erase recovery
(claimed in this guide here)
Edit: I forgot you used a CyanogenMod Recovery, which is stored in FOTAkernel,
so you have to use also :
Code:
fastboot erase boot
fastboot erase FOTAKernel
I did read it here
Hope that does help you
Thanks a lot !
imascara said:
Thanks a lot !
Click to expand...
Click to collapse
I updated my last posting
My attempt to install a custom rom has failed horribly and I'm left with a wiped phone. Is there a way to reinstall EMUI? Or still somehow get a custom rom?
I flashed lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bvS.img on system, but although there was no error message it didn't seem to do anything.
It's a LLD-L31
hasl3r said:
Is there a way to reinstall EMUI?
Click to expand...
Click to collapse
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
-Alf- said:
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
hasl3r said:
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
hasl3r said:
The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
Do you have TWRP installed instead of Recovery or eRecovery?
hasl3r said:
It's a LLD-L31
Click to expand...
Click to collapse
What is your regional variant? (Cxxx)
-Alf- said:
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
Click to expand...
Click to collapse
That worked, I'm not around a PC at the moment, I'll run the commands as soon as possible
-Alf- said:
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
Do you have TWRP installed instead of Recovery or eRecovery?
Click to expand...
Click to collapse
That booted into TWRP as well, so I guess?
-Alf- said:
What is your regional variant? (Cxxx)
Click to expand...
Click to collapse
How to I find that out? I tried google but didn't find information.
All else I got are the IMEI and:
Serial number: FPM4C18622002338
Product ID: 71171281
Many thanks already for your help btw
hasl3r said:
How to I find that out?
Click to expand...
Click to collapse
through the mentioned fastboot commands.
-Alf- said:
through the mentioned fastboot commands.
Click to expand...
Click to collapse
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)
hasl3r said:
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)
Click to expand...
Click to collapse
Okay, try the following:
1. Download Service ROM
Unpack it, there's a dload file in Software folder. Copy dload as it is to the SD Card (without unpacking it!)
2. Download TWRP 3.2.1 https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
and copy it to SD Card
3. also copy to SD stock Recovery_ramdisk-9.1.img , download here:
https://mega.nz/#!M0FHlYhb!4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
4. Boot into your TWRP, select storage - SD Card, select "Install image", find TWRP-9.1 file and mark eRecovery, swipe. Go back, find recovery_ramdisk-9.1 file , mark Recovery, swipe.
5.Turn off the phone, use option 'Power Off' in TWRP's menu.
6. Press and hold Power & both Volume buttons .
-Alf- said:
Okay, try the following:
Click to expand...
Click to collapse
Amazing, thank you so much!
-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.
hasl3r said:
Amazing, thank you so much!
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.
Click to expand...
Click to collapse
Glad to help
-Alf- said:
Glad to help
Click to expand...
Click to collapse
Sorry to bother you again, just wondering if you have any advice. I tried flashing LineageOS 17.1, but realised that the bootloader is locked again. My unlock code doesn't seem to work anymore (check password failed) and I figured it's because I have to downgrade EMUI 9.1 to 8.0. Took me a while, but turns out that was not the issue.
Do you happen to have any idea what to try? Do I have to buy another DC Unlocker license?
I don't know if it's related, but "adb reboot fastboot" just reboots the device and I have to use the volume down key to get there.
hasl3r said:
the bootloader is locked again.
Click to expand...
Click to collapse
it's normal after using dload method
hasl3r said:
My unlock code doesn't seem to work anymore
Click to expand...
Click to collapse
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)
-Alf- said:
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)
Click to expand...
Click to collapse
Turns out the problem was copy/pasting the unlock code instead of hand typing it..
So I could flash it, but then the reset failed. Just realised that EMUI 9.1 is a requirement though, so I'll flash that first and try again.
Edit: Nvm fixed it. Sorry if you got a notification anyway.
-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s
hasl3r said:
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s
Click to expand...
Click to collapse
1. be sure that your bootloader is unlocked, try to unlock it again
2. In fastboot mode run command
fastboot erase system
and try to flash GSI again
3. Install TWRP 3.2.1 gaguga edition, in TWRP select Mount - mark System, go back, select Wipe > Advanced > mark System > Repaire or etc. > Resize file system > confirm, reboot .
Then flash back stock recovery and try to install GSI.
4. Downgrade to the lower build number via dload method
5. idk...
I'm trying to install custom recovery and ROM on my Redmi 9. I've used XiaoMiToolV2 (https://github.com/francescotescari/XiaoMiToolV2) built on my mac to unlock the boot loader.
But I seem to be stuck trying to replace the recovery.
I tried TWRP- this sent me into a boot loop,
so I tried orangefox from here: https://orangefox.download/device/garden which fixed the bootloop, but everytime I go into recovery it shows me the MIUI Recovery tool.
I also tried pitchblack recovery from here: https://pitchblackrecovery.com/lancelot/ which gives me the same problem.... booting into recovery always shows MIUI Recovery tool.
This is the command I've been using to flash the recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
then a restart, then:
adb reboot recovery
Am I missing something?
supagu said:
I'm trying to install custom recovery and ROM on my Redmi 9. I've used XiaoMiToolV2 (https://github.com/francescotescari/XiaoMiToolV2) built on my mac to unlock the boot loader.
But I seem to be stuck trying to replace the recovery.
I tried TWRP- this sent me into a boot loop,
so I tried orangefox from here: https://orangefox.download/device/garden which fixed the bootloop, but everytime I go into recovery it shows me the MIUI Recovery tool.
I also tried pitchblack recovery from here: https://pitchblackrecovery.com/lancelot/ which gives me the same problem.... booting into recovery always shows MIUI Recovery tool.
This is the command I've been using to flash the recovery:
adb reboot bootloader
fastboot flash recovery recovery.img
then a restart, then:
adb reboot recovery
Am I missing something?
Click to expand...
Click to collapse
Unlock the bootloader before installing the Twrp.
https://miui.blog/any-devices/mi-unlock-tool-mac-linux/
https://www.xiaomitool.com/MiUnlockTool
Twrp:
https://androidfilehost.com/?w=files&flid=318235
.\fastboot flash recovery twrp.img
.\fastboot boot twrp.img
Yes I have unlocked my device using XiaoMiToolV2, I see a little unlocked padlock when booting my phone now.
I tried downloading twrp from the above url (thanks for that!)
I renamed it to recovery.img then:
[email protected] twrp % fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 3.746s]
Writing 'recovery' OKAY [ 1.123s]
Finished. Total time: 4.874s
[email protected] twrp % fastboot boot recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 3.733s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
[email protected] twrp % fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp % fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.046s]
Finished. Total time: 0.047s
[email protected] twrp % fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
[email protected] twrp % adb reboot bootloader
[email protected] twrp % fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp %
So your command to boot the image is incorrect, so I tried some other reboot commands but still when I did the reboot recovery it comes up with MIUIRecovery 5.0.... I should be seeing twrp here right instead?
supagu said:
Yes I have unlocked my device using XiaoMiToolV2, I see a little unlocked padlock when booting my phone now.
I tried downloading twrp from the above url (thanks for that!)
I renamed it to recovery.img then:
[email protected] twrp % fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 3.746s]
Writing 'recovery' OKAY [ 1.123s]
Finished. Total time: 4.874s
[email protected] twrp % fastboot boot recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 3.733s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
[email protected] twrp % fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp % fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.046s]
Finished. Total time: 0.047s
[email protected] twrp % fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
[email protected] twrp % adb reboot bootloader
[email protected] twrp % fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
[email protected] twrp %
So your command to boot the image is incorrect, so I tried some other reboot commands but still when I did the reboot recovery it comes up with MIUIRecovery 5.0.... I should be seeing twrp here right instead?
Click to expand...
Click to collapse
After flashing TWRP press volume+and power button
MIUI is automatically replacing TWRP with MIUI Recovery. So to fix this after flashing the recovery, you will need to flash the vbmeta image with the flag --disable-verity:
Code:
fastboot flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
This is the vbmeta image: https://forum.xda-developers.com/attachments/vbmeta_redmi9-img.5449805/
Also use this recovery: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/
Thanks guys!
Sergi, your combination of vbmeta and recovery has worked!
Proper url is here:
[RECOVERY][TWRP][UNOFFICIAL] TWRP recovery 3.6.1_11-0
TWRP recovery 3.6.1 for lancelot (redmi 9 | lancelot/galahad) I am not responsible for your brick devices. The recovery is fully working and has been tested. If you encounter a problem, write here, maybe they will help you. Before you accuse me...
forum.xda-developers.com
(you had a typo in your post)
supagu said:
Thanks guys!
Sergi, your combination of vbmeta and recovery has worked!
Proper url is here:
[RECOVERY][TWRP][UNOFFICIAL] TWRP recovery 3.6.1_11-0
TWRP recovery 3.6.1 for lancelot (redmi 9 | lancelot/galahad) I am not responsible for your brick devices. The recovery is fully working and has been tested. If you encounter a problem, write here, maybe they will help you. Before you accuse me...
forum.xda-developers.com
(you had a typo in your post)
Click to expand...
Click to collapse
No problem , and ahh I will correct the link . So glad it worked.