Develop Bugs

[Q] Phone boots only to recovery

Hey there,
I have installed a new rom,
and after installing everything (I did full wipe) and trying to reboot the system,
the phone is showing the htc logo, but then it just goes right back to recovery mode,
every single time.
Something that may cause the problem - the only way i was able to update to 6.0.4.7 recovery was to install it every time again with fastboot
then to boot into recovery
then it showed me the 5.X.X.X version again
So I do "Reboot system now"
and only then it opens the 6.0.4.7 recovery
maybe because of this everytime I do "reboot system now" it keeps booting my phone into the recovery mode.
how can i fix it?
thank you all very much for reading!

arnon124 said:
Hey there,
I have installed a new rom,
and after installing everything (I did full wipe) and trying to reboot the system,
the phone is showing the htc logo, but then it just goes right back to recovery mode,
every single time.
Something that may cause the problem - the only way i was able to update to 6.0.4.7 recovery was to install it every time again with fastboot
then to boot into recovery
then it showed me the 5.X.X.X version again
So I do "Reboot system now"
and only then it opens the 6.0.4.7 recovery
maybe because of this everytime I do "reboot system now" it keeps booting my phone into the recovery mode.
how can i fix it?
thank you all very much for reading!
Click to expand...
Click to collapse
are you flashed the boot.img from the rom.zip???

Thant said:
are you flashed the boot.img from the rom.zip???
Click to expand...
Click to collapse
well I was sure I did, but now when I try to reflash it it says:
sending 'boot'....
FAILED <command write failed <unknown error>>
finished.
what should I do?

arnon124 said:
well I was sure I did, but now when I try to reflash it it says:
sending 'boot'....
FAILED <command write failed <unknown error>>
finished.
what should I do?
Click to expand...
Click to collapse
which is the output of fastboot devices command? is any device listed?
if no device is listes, it might be a fastboot/driver issue on the pc, so you might try to download it/them again...

arnon124 said:
well I was sure I did, but now when I try to reflash it it says:
sending 'boot'....
FAILED <command write failed <unknown error>>
finished.
what should I do?
Click to expand...
Click to collapse
wWitch recovery youy use and witch ROM? Kitkat roms have problem and recovery have problem with drivers and for this you receive problem to flash boot.img now you must to fix the problem with the drivers to flash the boot.img

C1905 - "Error mounting /data"

Hey folks,
I've just unlocked my bootloader and flashed the newest PhilZ Recovery. I've been following THIS tutorial.
Fastboot didn't encounter any issues, so I thought everything went fine. But after flashing the recovery image, my phone got stuck while booting. The Sony logo shows up, the screen turns black and that's where it gets stuck.
Trying to erase userdata, factory reset etc didn't help. While resetting it shows up the following message
Code:
"Error mounting/formatting /data"
So I tried to mount it manually in the recovery, but it shows the same error. Seems like a permission problem?!
Since I don't have a ROM on my SD-card yet I tried to install one via fastboot.
Code:
fastboot update ArchiDroid_V3.0.1.1-nicki.zip
But..
Code:
Archive does not contain 'android-info.txt'
Archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now I'm stuck. I don't think installing a new ROM will work if I can't even mount /data. So first thing is to fix this and then I'll be able to install a new ROM. Am I right?
By the way : fastboot has no problem detecting my device, but adb can't find it?! D:
I appreciate any kind of help! Thanks in advice!
Gruß aus Deutschland,
furi ;D

furiify said:
Hey folks,
I've just unlocked my bootloader and flashed the newest PhilZ Recovery. I've been following THIS tutorial.
Fastboot didn't encounter any issues, so I thought everything went fine. But after flashing the recovery image, my phone got stuck while booting. The Sony logo shows up, the screen turns black and that's where it gets stuck.
Trying to erase userdata, factory reset etc didn't help. While resetting it shows up the following message
Code:
"Error mounting/formatting /data"
So I tried to mount it manually in the recovery, but it shows the same error. Seems like a permission problem?!
Since I don't have a ROM on my SD-card yet I tried to install one via fastboot.
Code:
fastboot update ArchiDroid_V3.0.1.1-nicki.zip
But..
Code:
Archive does not contain 'android-info.txt'
Archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Now I'm stuck. I don't think installing a new ROM will work if I can't even mount /data. So first thing is to fix this and then I'll be able to install a new ROM. Am I right?
By the way : fastboot has no problem detecting my device, but adb can't find it?! D:
I appreciate any kind of help! Thanks in advice!
Gruß aus Deutschland,
furi ;D
Click to expand...
Click to collapse
have you try to flash any rom except that? because when i try to flash archidroid i've same problem like you can't mount but when i try to install any rom like cm my device can mount normally.

Nicklas Van Dam said:
have you try to flash any rom except that? because when i try to flash archidroid i've same problem like you can't mount but when i try to install any rom like cm my device can mount normally.
Click to expand...
Click to collapse
I did. Tried 3 different ROMs and everyone gave me the same outcome.
But it seems like I fixed it by returning to stock using FlashTool and a stock ROM. I went all over again and now it's installing the ROM. I hope it's working now.
E: Yup, it's working fine now. But thanks anyway!

TWRP Freeze - close call?

Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler

pootler said:
Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler
Click to expand...
Click to collapse
Ok so quick update
I decided to use a different recovery
I was installing lineages 17, so used their recovery.
Everything worked fine?

HI,
I obtained a nokia 6.1 recently.
I had the bootloader unlocked.
I then went to flash the latest ( official) lineage 17
I did all the usual stuff ( i am not a stranger to installing custom roms ), and then tried to temporarily boot into twrp, in order to flash the lineage zip.
I was using the twrp as recommended on lineage site for this device ( nokia 6.1 TA 1050 )
For some reason, after using fastboot boot twrp.img, ( I renamed the image) the phone just booted back to android one screen.?
I could use power/vol up, to get out and back to existing installation, but nothing else.
I then tried temporarily booting the lineage recovery. ( according to the lineage installation instructions)
This involves using a combination of ''fastboot flash boot'' and hardware keys to get there
This worked fine - and I was able to sideolad the lineage zip.
Problem is, if I want to flash images , and do other stuff the lineage recovery cant, i need twrp ( even temporarily).
After installing lineage 17, I tried again to get into twrp, with the same (non) results.
I was wonderinfg if I was getting confused about slots.
I believed that booting twrp temporarily would boot to the right slot? - maybe not.
I then decided to do fastboot flash boot_a, ( etc, ) and then fastboot flash boot_b, ( etc ) to make sure it would boot off either slot. With hindsight, this was dumb
That got me twrp., but lost me the ability to boot into the lineage installation.
After a bit of a panic, I managed to get back to my lineage install.
I have tried since to temporarily boot twrp ( not to both slots ), and am still getting the same results- it boots to the android one screen, and just sits there.
But - if I try to get to recovery using the hardware buttons, I can get to Lineage recovery - which I find strange, because I thought official lineage packages did not install their recovery by default?
Makes me wonder when I thought I had booted lineage recovery temporarily, that maybe I hadn't, and I just booted into a pre installed recovery using the hardware method.
I am probably doing something stupid ( quite common for me ), can anyone enlighten me ?
Many Thanks
pootler

O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler

pootler said:
O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler
Click to expand...
Click to collapse
Yes - it appears that if you cannot boot into twrp temporarily , then this worked for me!
--at your own risk---
fastboot flash recovery <filename>.img
This will FAIL - but ignore and then right after,
fastboot boot <filename> .img
Voila - boots into TWRP temporarily.
Cheers
pootler

I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?

MigueTK said:
I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?
Click to expand...
Click to collapse
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck

pootler said:
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck
Click to expand...
Click to collapse
Thanks for the reply, I still haven't figured it out and am running a manually patched boot image for magisk without a recovery, fastbootd is "enough". Another weird thing is If I installed a custom Rom certain pixel features would be lost such as the OCR and lens integration into the recents menu, pixel stand standby and wallpapers. I love the features of a custom Rom but the overview copy and paste functions are a must have for me.

Well, I use Raghu Varma's unofficial TWRP. It works like a charm, I've had no issues with it so far. Just be careful to choose the correct one between the build for Android 10 and the one for Android 11 -- I think that got me into trouble once, can't remember clearly.

Recovery boots to black screen, can't flash on OP 5T

I have an old OP5T that is still on an older version of LOS, so I thought I'd start from scratch and first flash the Lineage Recovery instead of TWRP (an equally old version, but still working at this point).
USB debugging is active and OEM unlock enabled.
However, when I flash the image with
fastboot flash recovery lineage-17.1-20201229-recovery-dumpling.img
I get this output:
Sending 'recovery' (26685 KB) OKAY [ 0.698s]
Writing 'recovery' OKAY [ 0.252s]
Finished. Total time: 0.951s
First thing I found weird is how it took less than a second. Is it supposed to be that fast? It obviously did something:
When I try to boot to recovery now, I only get a black screen and a solid white notification LED (after the boot splash).
Same thing when I use the TWRP image instead: terminal shows it's finished in a second, but recovery wont boot afterward.
fastboot boot leads to the same black screen.
I tried it from two different computers, one with Fedora and the other with Windows; same thing happens on both.
The installed OS still works just fine, it's an old version though (and OTA updates don't work for some other reason).
Anyone have an idea what's wrong? What else could I try to get a working recovery?

Hi Mike
I had this very same issue. Regardless of what recovery (codeworkx, blu_spark, LOS etc.) I tried (I was on TWRP 3.2.x before) it always ended up with the solid white led. Eventually I got at least stock recovery from here working again (I was copying the recovery.img to internal storage, then booting to bootloader and went from there to recovery). This then allowed me to get adb sideload back so I could upgrade my old LOS 15.1 to OOS 10.0.1 (via 5.1.3, then 5.1.4, 5.1.7, 9.0.11 and finally 10.0.1). Once I was on the latest OOS I went back to fastboot bootloader and then flashed recovery with a more recent TWRP image (I took twrp-3.3.1-x_blu_spark_v9.101_treble-op5_op5t.img). Not sure if all those steps are actually required (I think you need at least 5.1.3 and 5.1.4 to get around this treble/vendor partition issue if you are on a version that didn't have the vendor partition yet) but this is how I got to a working TWRP recovery again. Hopefully this is of any help to you.
Cheers

Question HELP, device stuck in bootloop, tried every method.

Hi everyone,
maybe someone here might help me. I was on bliss rom and my phone suddenly froze yesterday.
And oh boy did that started a very long day of messing with miflash tool and twrp.
The situation right now is like this,
I have full access to TWRP, and fastboot and mi flash tool.
I tried flashing stock rom with mi flash, got success with no error and yet still stuck in frozen POCO logo.
Tried flashing with TWRP couple of ROMs with correct fw and still got POCO logo stuck.
Tried sideloading with adb some ROMs and same results, stuck on POCO logo.
Also tried to use flash_all bat without mi flash tool, and it boots me to MIUI recovery...
I can always come back to fastboot and boot to TWRP and tried miflashtool many time , I always result in success (0) but nothing works...
Is there anything I'm missing?
Of course I waited at least half an hour every time on POCO logo beacuse I know It can take some time for first boot but nothing happens, If I had to guess is there a possibility that the Storage it self in the phone is broken?

kmo1997 said:
Hi everyone,
maybe someone here might help me. I was on bliss rom and my phone suddenly froze yesterday.
And oh boy did that started a very long day of messing with miflash tool and twrp.
The situation right now is like this,
I have full access to TWRP, and fastboot and mi flash tool.
I tried flashing stock rom with mi flash, got success with no error and yet still stuck in frozen POCO logo.
Tried flashing with TWRP couple of ROMs with correct fw and still got POCO logo stuck.
Tried sideloading with adb some ROMs and same results, stuck on POCO logo.
Also tried to use flash_all bat without mi flash tool, and it boots me to MIUI recovery...
I can always come back to fastboot and boot to TWRP and tried miflashtool many time , I always result in success (0) but nothing works...
Is there anything I'm missing?
Of course I waited at least half an hour every time on POCO logo beacuse I know It can take some time for first boot but nothing happens, If I had to guess is there a possibility that the Storage it self in the phone is broken?
Click to expand...
Click to collapse
Did you format the data partition at all while doing this? If not, then try running "fastboot -w" while in bootloader mode.

DarthJabba9 said:
Did you format the data partition at all while doing this? If not, then try running "fastboot -w" while in bootloader mode.
Click to expand...
Click to collapse
yes i tried. it gives me an error :
Erasing 'userdata' OKAY [ 0.032s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\Moti\Desktop\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata

kmo1997 said:
yes i tried. it gives me an error :
Erasing 'userdata' OKAY [ 0.032s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\Moti\Desktop\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Click to expand...
Click to collapse
Hmmm ... that shouldn't happen. You may have a hardware problem.
Try booting to recovery and formatting data from there. If that doesn't work either, then I have no other suggestions.

DarthJabba9 said:
Hmmm ... that shouldn't happen. You may have a hardware problem.
Try booting to recovery and formatting data from there. If that doesn't work either, then I have no other suggestions.
Click to expand...
Click to collapse
i tried , no luck.
is there any way to fing out if it is truely hardware problem?

Hi,
just a thought,
I have been in a situation were Miui stock would not complete it`s installation, I don`t use MIflash tool, i found a tip that involved moving the ADB flies from Miflash and put them into the Miui fastboot stock rom folder and move the re-named folder to my C: Drive.
After some panicking i tried my old faithful a "Xiaomi.eu Fastboot rom", i installed it from fastboot, it completed as it should and i carried on where i left off, flashing custom roms,
its worth a try

i do the same

johnr64 said:
Hi,
just a thought,
I have been in a situation were Miui stock would not complete it`s installation, I don`t use MIflash tool, i found a tip that involved moving the ADB flies from Miflash and put them into the Miui fastboot stock rom folder and move the re-named folder to my C: Drive.
After some panicking i tried my old faithful a "Xiaomi.eu Fastboot rom", i installed it from fastboot, it completed as it should and i carried on where i left off, flashing custom roms,
its worth a try
Click to expand...
Click to collapse
thanks for the answer, in my situation miui stock completes the installation successfully with a beautiful green success in miflashtool and yet I'm still stuck at the POCO logo till botting itself to MIUI recovery.
regardless I tried your advice and no luck

I have tried a couple more things, I flashed with locking the bootloader the oldest MIUI ROM I found on the archive, of course no luck, still stuck on POCO logo and as always somehow, I'm able to boot into fastboot so unlocked the bootloader again and tried a xieomi.eu rom without mi flash tool with the .bat file and flash_all.
same result, no luck
I'm starting to think it might really be a hardware issue, yet I'm baffled at how the phone was working perfectly fine and suddenly froze while i was using it and started bootlooping which started this whole mess.

kmo1997 said:
.... I'm starting to think it might really be a hardware issue, yet I'm baffled at how the phone was working perfectly fine and suddenly froze while i was using it and started bootlooping which started this whole mess.
Click to expand...
Click to collapse
That is often how hardware problems manifest themselves.

kmo1997 said:
thanks for the answer, in my situation miui stock completes the installation successfully with a beautiful green success in miflashtool and yet I'm still stuck at the POCO logo till botting itself to MIUI recovery.
regardless I tried your advice and no luck
Click to expand...
Click to collapse
If possible try gsi builds to boot bro it may boot directly to system

Try flashing different Fastboot stock Roms using miflash, don't use just one version, try only without locking the bootloader, probably it is a boot partition error, you just need to find the right one, also use a different miflash version (older ones seem to be more stable)

I have just read one of your recent comments, it seems like e miflash problem, flashing with lock must lock the bootloader, try using known versions especially older ones

Have you tried turning it off and on again?

Jk.
First of, which twrp Version are you using? You should try the latest skkk versions. https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/alioth/
Are you sure that you have full twrp storage access? If you boot into twrp, how big is your internal storage, as seen from twrp? Does it show 0?
I had this error once, couldnt flash anything anymore because twrp couldnt handle some encryption and needed to reformat the internal storage to ext2, then back to ext4 again. Then the storage was readable and writable again.
Encryption can be a weird, just like A/B partitioning.

Make sure to use the latest version of MIUI for your specific region.
A.k.a. the exact version of MIUI that your phone shipped with, but use the latest version of it.
And don't download from a weird third party website.
I think the official site is mi.com (but you'll have to google the exact link).
Otherwise, my go-to for MIUI ROMs is xiaomifirmwareupdater.com