Develop Bugs

[Q] stuck on htc quietly brilliant screen

Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.

You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium

Thanks sir, I'll try.

sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.

thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card

sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too

dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.

See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA

Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.

"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command

sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA

Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!

Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.

Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!

I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?

All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot

i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.

mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?

When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s

Nobody can help me?!! ((

[Q] Swapping Cyanogemod Recovery for TWRP or Philz?

Hi I've been trying to flash a new recovery image over the recovery that I'm currently using ("cyanogemod recovery" (I understand that this is purely for CM updating)) but I can find no way of doing it. Via fastboot this happens (using mac terminal) after typing "fastboot flash recovery recovery.img:
sending 'recovery' (11044 KB)...
OKAY [ 0.693s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.696s
Do I need to delete the cyanogemod recovery and run this command?
Cheers in advance! (if laymans terms could be used as much as poss that'd be appreciated too!!)

Xiaomi Mi 10 Lite - Recovery mode

Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10

stephane_p said:
Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10
Click to expand...
Click to collapse
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup

Spuffyffet said:
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup
Click to expand...
Click to collapse
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.

stephane_p said:
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.
Click to expand...
Click to collapse
However, it's still not working. I have the same issue.

stephane_p said:
However, it's still not working. I have the same issue.
Click to expand...
Click to collapse
well use "fastboot reboot recovery"

Spuffyffet said:
well use "fastboot reboot recovery"
Click to expand...
Click to collapse
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here

stephane_p said:
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here
Click to expand...
Click to collapse
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)

Spuffyffet said:
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)
Click to expand...
Click to collapse
I downloaded platform-tools zip file (r33.0.0 for windows) and extract it in C:\Android\platform-tools
Then, I retry
C:\Android\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (131072 KB) OKAY [ 5.415s]
Writing 'recovery' OKAY [ 0.586s]
Finished. Total time: 6.017s
C:\Android\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But, I still get the fastboot screen instead of recovery mode.
Thank you for your help.

Have you tried with another recovery image, like TWRP ?

mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
well i have and it worked for me

mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed

stephane_p said:
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using the wrong command bro, don't use boot. Use "fastboot flash recovery twrp_recovery.img". Why are you flashing recovery.img as boot bro?

OK guys I've found my mistake. I thought the model of my phone was Monet. But it's not. It's Toco... A stupid error showing that I have to be more rigorous.
I thank you again for your help. All the best for xda.
See you

Help! Redmi note 8 (2021) bricked (bootloop)

Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help

Try this
https://www.getdroidtips.com/twrp-recovery-redmi-note-8-2021-root/
I guess you have used a wrong recovery file, maybe one for another device

The problem is that the command 'flash recovery' does not work, because it says th partition does not exist....

Norah1838 said:
I am using a Redmi Note 8 (2021)
Click to expand...
Click to collapse
wrong forum ! , see Biloba forum
on some devices, boot+recovery are on the same partition, but not for Biloba
boot partition (+dtbo on some cases) is the kernel
i think you should look for official install of miui rom since it has IMG of most partitions ...

Question Help! Redmi note 8 (2021) bricked (bootloop)

Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help

Norah1838 said:
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
Click to expand...
Click to collapse
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

First off: don't go punching in commands you don't understand.
You literally flashed an incompatible image to your boot_a.
You could try and set the active partition to b using: fastboot --set-active=b.
Other option, if you have the firmware image for your boot partition, flash that image to boot_a.

you only need to flash the original boot.img from firmware lol it's so easy