Develop Bugs

Phone will only boot to recovery after flashing TWRP?

Hey all, so this is a strange issue. I've tried this 3 times, on 8.0, 8.1 Jan security patch, and 8.1 March security patch. Booting to TWRP via fastboot works just fine, but after flashing it via ZIP within TWRP and rebooting, the phone will only boot to TWRP. Even flashing a stock boot.img and/or dirty flashing the stock image did not fix the issue and every time I had to do a clean install of the stock image. Any ideas why this is going on?

Have you tried installing Magisk after it boots back into TWRP?

sliding_billy said:
Have you tried installing Magisk after it boots back into TWRP?
Click to expand...
Click to collapse
Absolutely. It will patch the Boot Img.

Mikkey81 said:
Absolutely. It will patch the Boot Img.
Click to expand...
Click to collapse
hooligan33_3 said:
Hey all, so this is a strange issue. I've tried this 3 times, on 8.0, 8.1 Jan security patch, and 8.1 March security patch. Booting to TWRP via fastboot works just fine, but after flashing it via ZIP within TWRP and rebooting, the phone will only boot to TWRP. Even flashing a stock boot.img and/or dirty flashing the stock image did not fix the issue and every time I had to do a clean install of the stock image. Any ideas why this is going on?
Click to expand...
Click to collapse
Sorry, I meant to quote you when I suggested installing Magisk since it will patch boot.img.

Hello, this happened to me too after I uninstalled Magisk. I just reinstalled it and wiped the phone (just to be sure) and it works now.

stepedes said:
Hello, this happened to me too after I uninstalled Magisk. I just reinstalled it and wiped the phone (just to be sure) and it works now.
Click to expand...
Click to collapse
Are you trying to flash Magisk in fastboot or through TWRP?

In TWRP.
I'm a noob in all this, glad I didn't brick it. ?

it just happened to me now, I read one of the posts saying flash Magisk again and it worked.
aside: can someone tell me briefly who phones now having slot A and B? everytime i reboot twrp, i see option to decide which slot. I did choose slot B once and the phone never booted up. i'm little bit confused. and everytime twrp boots in, it asks me to draw my security pattern for decryption, is that OK? thx

mohawahba said:
it just happened to me now, I read one of the posts saying flash Magisk again and it worked.
aside: can someone tell me briefly who phones now having slot A and B? everytime i reboot twrp, i see option to decide which slot. I did choose slot B once and the phone never booted up. i'm little bit confused. and everytime twrp boots in, it asks me to draw my security pattern for decryption, is that OK? thx
Click to expand...
Click to collapse
Are you using twrp-pixel-installer-marlin-3.2.3-1.zip and twrp-3.2.3-1-marlin.img on your Pixel XL?
twrp should not be giving you an option to choose
a slot nor draw a security pattern for decryption.
look at this guide: [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76

Homeboy76 said:
Are you using twrp-pixel-installer-marlin-3.2.3-1.zip and twrp-3.2.3-1-marlin.img on your Pixel XL?
twrp should not be giving you an option to choose
a slot nor draw a security pattern for decryption.
look at this guide: [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
Click to expand...
Click to collapse
I am actually sailfish .. will look into the link. Thanks

mohawahba said:
I am actually sailfish .. will look into the link. Thanks
Click to expand...
Click to collapse
Try the Pixel forum
TWRP for sailfish
- twrp-pixel-installer-sailfish-3.2.3-1.zip
- twrp-3.2.3-1-sailfish.img

custom roms do not boot up

hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that

logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.

so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D

cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers

Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.

NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms

daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?

well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..

daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.

NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards

Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.

yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway

daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.

NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/

daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?

NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way

daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.

I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?

Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers

Bootloop flashing miui 12 closed beta

hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)

Use fox twrp to flash.

haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I used TWRP. Also tried orangefox

haovh_85 said:
Use fox twrp to flash.
Click to expand...
Click to collapse
I also tried flashing the firmware first

-iwl- said:
hi, i am having aproblem right now trying to flash miui 12. first time i just formatted the phone in twrp. used adb push to push the zip on the phone. and flashed it. it was successful but after booting into the system it had a password for some reason and there was no setup screen. so i tried to reflash by formatting again and repeating the process. now i boot into system and it just goes into bootloop at the MI boot screen.
Its super weird that it worked the first time. then it doesnt work anymore no matter what (adb sideload, multiple recoveries) and it seems the rom isnt installing correctly because afterwards i cannot flash magisk (cannot mount system partition)
Click to expand...
Click to collapse
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.

paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed

paradise220 said:
Wait for some days,when some one success.
I have also flashed the rom first day.
I struggle for 1 hour with my laptop than i booted into LOS 17.1 after destroying my whole 100 gb internal data of my phone.
Click to expand...
Click to collapse
i have no idea what to do now

-iwl- said:
did you encounter the same issue? this person has it correctly installed:
https://www.youtube.com/watch?v=x5HJgH8QrMs
also. sometimes it says no os instlaled after i flashed
Click to expand...
Click to collapse
when i flashed miui 12 beta it showed on operating software installed before reboot.

paradise220 said:
when i flashed miui 12 beta it showed on operating software installed before reboot.
Click to expand...
Click to collapse
it seems they released a broken rom. i tested again with lineage os and it worked perfectly. so its xiaomi at fault here

Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta

Use chinese twrp

JrAdams said:
Ive installed It yesterday (dont know where but i Saw someone saying that It need Magisk, i flashed It and It worked).
But i turned back to oficial miui 11, my sim card was not working with this beta
Click to expand...
Click to collapse
Gapps or any google related services doesnt seem to be working with this beta. lots of bugs encountered too, i might just go back to havoc os

Yunus Ceyhan said:
Use chinese twrp
Click to expand...
Click to collapse
Got it working already. just had to flash magisk along with the rom

Android 10 stock doesn't boot

So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?

Madalin32 said:
So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?
Click to expand...
Click to collapse
U format ur datapartion?

joke19 said:
U format ur datapartion?
Click to expand...
Click to collapse
Yes, I do all my wipes and what is necessary to boot but still, stock android 10 doesn't do it. With Treble I can boot but with Pixel Experience and android 10 roms I can't...

Maybe you could have asked this question directly in the thread of the ROM you're trying to boot...

Tanguy_ASM said:
Maybe you could have asked this question directly in the thread of the ROM you're trying to boot...
Click to expand...
Click to collapse
It's not only one specific rom, all Stock android 10 roms don't boot

Madalin32 said:
It's not only one specific rom, all Stock android 10 roms don't boot
Click to expand...
Click to collapse
flash using pit file,and check re-partition

DarkVallen22 said:
flash using pit file,and check re-partition
Click to expand...
Click to collapse
Didn't think of this, might try tommorow.

You using f2fs for /data?
Make sure all the partitions are in ext4, if that didn't help it is probably your TWRP not flashing correctly, try Anajaser1211's TWRP.

Mohamedkam000 said:
You using f2fs for /data?
Make sure all the partitions are in ext4, if that didn't help it is probably your TWRP not flashing correctly, try Anajaser1211's TWRP.
Click to expand...
Click to collapse
I can't acces the link.. it is deleted

I would be interested to hear if you managed to fix this issue as I have exactly the same problem. I have a UK spec Galaxy S7 Exynos and started experimenting with custom ROMs a year ago. Both Lineage 16 and Pixel Experience 9 worked fine with no issues, however whenever I try to flash an Android 10 based ROM (I've tried both Lineage 17 and Pixel Experience 10) they will not boot and get stuck on the startup screen.

Have you updated your boot partition with the latest stock version before trying Android 10 versions?

I have 4 Galaxy Exynos phones (G930W8) and ran 16 (Android 9) on all of them with no problems. But when I started to try 17 (Andoid 10), 3 would boot but one did not and still will not boot any 17.1 ROM. Out of curiosity I tried Ivan's 18 on that one phone and it boots fine. All of the 18 ROMs (Android 11) seem to boot with no problems. I have no idea why and did try every 10 ROM that I could find. Maybe a slight hardware variation?
I did update to the latest stock version and even ran the PIT file to reset partitions with no improvement.

RickBH said:
I have 4 Galaxy Exynos phones (G930W8) and ran 16 (Android 9) on all of them with no problems. But when I started to try 17 (Andoid 10), 3 would boot but one did not and still will not boot any 17.1 ROM. Out of curiosity I tried Ivan's 18 on that one phone and it boots fine. All of the 18 ROMs (Android 11) seem to boot with no problems. I have no idea why and did try every 10 ROM that I could find. Maybe a slight hardware variation?
I did update to the latest stock version and even ran the PIT file to reset partitions with no improvement.
Click to expand...
Click to collapse
My phone was updated to the latest stock version of Samsung's software. I tried the above advice and you are exactly right! Lineage 18 boots with no issues at all as does Lineage 16 - it seems to be certain phones that are not compatible with Android 10 as I am using exactly the same procedure in TWRP when installing the new ROM. Thanks very much for your help, I will see how I get on with Android 11 as this is just a spare phone anyway!

Madalin32 said:
So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?
Click to expand...
Click to collapse
I also have same problem ! Did you find any fix ? Pls tell !!! :-(
Exact Same issue

Madalin32 said:
So I have this issue with my S7 that it doesn't boot on stock android 10 but on OneUI 2 boots just fine, did anyone have this issue?
Click to expand...
Click to collapse
Since when was there an official stock Android 10 update for the Galaxy S7?
EDIT: Nvm, misunderstood the post.

Question twrp

Hello, tell me please, is there a working TWRP for the realme s21 device?

leon2299 said:
Hello, tell me please, is there a working TWRP for the realme s21 device?
Click to expand...
Click to collapse
Yes, and here is the source.
It is not fully tested, but i have installed RealmeUI2 .ozip firmware with it (and i externally needed to flash rui2 recovery in order to boot), i currently use rui2 and my phone is rooted.
The twrp is for android 10 only, afaik there is no one for android 11 yet.

MrMiyamo said:
Yes, and here is the source.
It is not fully tested, but i have installed RealmeUI2 .ozip firmware with it (and i externally needed to flash rui2 recovery in order to boot), i currently use rui2 and my phone is rooted.
The twrp is for android 10 only, afaik there is no one for android 11 yet.
Click to expand...
Click to collapse
thanks, is it possible to somehow collect it into a recovery file

leon2299 said:
thanks, is it possible to somehow collect it into a recovery file
Click to expand...
Click to collapse
I am poor at building recovery from source, so you can get in touch* with him.
*(check his github overview)

ok, I'll think of something

hello, there are tvrp samples, I need to check, fastboot stopped working for me, and twrp needs to be checked, there is a result, I need to check

leon2299 said:
hello, there are tvrp samples, I need to check, fastboot stopped working for me, and twrp needs to be checked, there is a result, I need to check
Click to expand...
Click to collapse
You can use
dd if=/path/to/TWRP.img of=/dev/block/platform/bootdevice/by-name/recovery
Than run "reboot recovery" to check, if it boots congrats, else you can just reboot device by holding 3 key for 10 seconds, the recovery will become stock after reboot, to keep recovery there is a magisk module.
Note that, there is 2 branch in this recovery, android 10 one works, but 11 is not working

MrMiyamo said:
You can use
dd if=/path/to/TWRP.img of=/dev/block/platform/bootdevice/by-name/recovery
Than run "reboot recovery" to check, if it boots congrats, else you can just reboot device by holding 3 key for 10 seconds, the recovery will become stock after reboot, to keep recovery there is a magisk module.
Note that, there is 2 branch in this recovery, android 10 one works, but 11 is not working
Click to expand...
Click to collapse
the fastboot worked, it was necessary to flash Android 10 of the latest version 53, went into the fastboot by holding the power button and the minus adjustment button, tried to flash the samples, as a result, the TWRP splash screen hangs and nothing, the phone does not respond to the buttons, to the tapas too, but already at least something, there is a twrp screensaver
these three created recovery, the twrp screensaver hangs, they need to be brought to mind

can I flash these through MTK clint?
leon2299 said:
hello, there are tvrp samples, I need to check, fastboot stopped working for me, and twrp needs to be checked, there is a result, I need to check
Click to expand...
Click to collapse
and which one should I flash

Zartazor said:
can I flash these through MTK clint?
and which one should I flash
Click to expand...
Click to collapse
Yes, twrp 10 I found worked for Android 10
I am working on the fastboot issue for 11, as I did the same trick on my android 10 USB serial error, just trying to remember exact line of code I used lol
But basically it involves using magisk, magisk, module magisk props config, and having that insert the serial number where it's needed without actually inserting to build.prop.
I'm back home tonight where I will be able to work in it more

I have flashed the TWRP from android 10 and updated it to android 11 GSI
TWRP is working just fine

But is fastboot still working that is the question

smiley.raver said:
But is fastboot still working that is the question
Click to expand...
Click to collapse
Yes it does