My samsung phone shows "samsung galaxy " and then just black screen . I INSTALLED CUSTOM ROOM and gapps using TWRP . When I rebooted this happend.
keni0 said:
My samsung phone shows "samsung galaxy " and then just black screen . I INSTALLED CUSTOM ROOM and gapps using TWRP . When I rebooted this happend.
Click to expand...
Click to collapse
Did you create a backup of your stock ROM before you flashed the custom ROM? If not, you should have. A prepared user always makes a backup via TWRP before making any kind of changes to the system and before flashing ROMs, that way they can restore the backup via TWRP if something goes wrong.
Can you boot into TWRP?
Droidriven said:
Did you create a backup of your stock ROM before you flashed the custom ROM? If not, you should have. A prepared user always makes a backup via TWRP before making any kind of changes to the system and before flashing ROMs, that way they can restore the backup via TWRP if something goes wrong.
Can you boot into TWRP?
Click to expand...
Click to collapse
I solve it by removing battery and then boot in recovery mode and flashed stock firmware , but I still can not install custom rom
keni0 said:
I solve it by removing battery and then boot in recovery mode and flashed stock firmware , but I still can not install custom rom
Click to expand...
Click to collapse
That is because you triggered Knox, you won't be able to flash anything custom now that Knox has been triggered. The firmware that you flashed, was it the same build number as what you had originally or is it a newer, updated firmware? If you flashed a newer firmware that has a bootloader that can't be unlocked, you will not be able to flash TWRP or custom ROMs.
Droidriven said:
That is because you triggered Knox, you won't be able to flash anything custom now that Knox has been triggered. The firmware that you flashed, was it the same build number as what you had originally or is it a newer, updated firmware? If you flashed a newer firmware that has a bootloader that can't be unlocked, you will not be able to flash TWRP or custom ROMs.
Click to expand...
Click to collapse
I do not know my old build number
Related
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
mertonv said:
Hi... im currently running
CROMi-X v5.2.2, which is based on rom 10.6.1.27.5 with twrp 2.5.0.0 and my bootloader says is the one that came with us10.6.1.15.3-20130416...
To install omni kitkat, im been asked to have the latest bootloader, to avoid screwing up im planning on insalling the latest stock from asus...
However, each time i install a stock through twrp or cwr, the new image not only updates the bootloader and deletes all my data, but rewrites my recovery, for which then i have too reupload using fastboot to upload the recovery...
Is there any way to make sure i dont loose the recovery after flashing a stock firmware... or a way to flash the recovery from the recovery before rebooting after flashing the stock?
Thanks everyone!
Click to expand...
Click to collapse
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
cmendonc2 said:
Flashing the stock ROM reverts the tablet back to stock, so the recovery must go. Luckily, the bootloader you are on is compatible with the KitKat recovery (10.6.1.15.3) so you shouldnt have to flash the stock ROM at all. If you were on 10.6.1.8, you would have had to upgrade.
Click to expand...
Click to collapse
Thanks, then guess i only need to flash the kitkat twrp...
Asked the same question about my bootloader at the omni thread to be sure, if they say that it works too, will go ahead and give it a try
Hey, I flashed twrp 3.0.0 via odin on my s6 g920f 6.0.1 rooted device (custom kernel) and now I can't boot into recovery, my phone works well, also download mode, just recovery gives me Recovery is not seandroid enforcing and stuck there.
I know this message is normal and not concerning but it's still not booting into recovery, I flashed the wrong version?
Try reflashing stock 6.01 ROM via Odin. ?
latest official TWRP (3.0.2-0) does not support 6.0 bootloader, so that's why you are stuck on boot.
until a new fixed version is released, you can try to use 2 alternatives :
1. @arter97 version , thread here , download page here
2. idlekernel version , download page here
roydok said:
Try reflashing stock 6.01 ROM via Odin. ��
Click to expand...
Click to collapse
IDK.. my phone works pretty good, it still starts and no problem at all. only recovery isn't booting.
I don't want to format it and flash stock again just because of it.
djcristi said:
i heard that you need to flash custom kernel , that stock kernel cannot boot TWRP, because of 6.0.1 bootloader.
. I am on the same case now, looking for solution because i don't want to use custom kernel, just TWRP and root it using Supersu.
Click to expand...
Click to collapse
Actually I am running SpaceX MM kernel(auto root)... so twrp should be fine.
i edited my previous post, you have there solution.
djcristi said:
i edited my previous post, you have there solution.
Click to expand...
Click to collapse
Yeah and it worked. Also flashed xposed, when I installed greenify module it caused bootloops so I flashed xposed uninstaller, I guess no xposed for me
Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
[R]ainbow[D]ash said:
Hello everybody! I have a problem: I wanted to install custom ROM via Safestrap 3.71. I made all the wipe. But at the end of the installation, I get an error: set_metadata_recursive some changes failed. And so in each ROM. After that, ROM does not load: black screen after the logo Samung Custom. How to deal with this?
Click to expand...
Click to collapse
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Was it a true custom ROM? Or was it a modified stock ROM?
If it was a custom ROM such as Cyanogenmod or LineageOS, that's the problem.
Safestrap is intended to be used with modified stock ROMs that are based on stock kernel, not CM, AOSP or Lineage based ROMs.
Typically, Safestrap is used on devices with locked bootloader, these devices can't use CM, AOSP or Lineage based ROMs, these ROMs are built to be flashed via custom recovery such as TWRP.
If you have an unlocked bootloader and you want to use custom ROMs then you'll have to flash TWRP then use TWRP to flash the ROM.
If your device does not have an unlocked bootloader but you want to use Safestrap then you need to install TouchWiz(TW)/stock based ROMs.
There is a difference.
Also, when using Safestrap, you have to leave the stock rom in one slot and place the new ROM in a different slot. You can't overwrite the existing stock ROM with the new ROM, that causes issues and the device won't boot.
You will probably have to flash your stock firmware via Odin and start over with root and flashing.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
[R]ainbow[D]ash said:
I was flashing the modified ROM on the stock kernel. I put in the recovery on slot-rom1. I tried to flash: CarHD, KushanROM, GOLDENEYE and Omega. And still it does not work out
Click to expand...
Click to collapse
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Do you still have your original stock ROM in one of the slots? Or did you overwrite it? If you overwrite it, you messed up. As stated earlier, you'll probably have to flash the original stock firmware via Odin.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
The stock slot remained intact. But if I take the kernel from OC3, then the device will also not boot up and the recovery will become non-working.
Send me the stock ROM for flashed the custom ROM through the Safestrap. And send me the version of the Safestrap for custom ROM
I understood what the problem is. I installed another ROM NB1 and it all worked for me.
Hi,
I need some help with my moto e4, it was rooted using flashtool and twrp custom recovery and all was well until asked to system update in which apparently something went wrong and my phone is now bricked and stuck on a bootloop on custom recovery with no OS anyone know what steps i can take to fix this problem? thanks in advance
azkarev said:
Hi,
I need some help with my moto e4, it was rooted using flashtool and twrp custom recovery and all was well until asked to system update in which apparently something went wrong and my phone is now bricked and stuck on a bootloop on custom recovery with no OS anyone know what steps i can take to fix this problem? thanks in advance
Click to expand...
Click to collapse
On most android devices, you can't apply stock OTA updates on rooted devices or devices that have TWRP installed, stock updates require an unmodified system partition(meaning no root) and must have stock recovery because stock recovery is what actually flashes the update, TWRP cannot flash stock updates.
Do a Google search for:
"Return to stock (your model number)"
Or, you can try restoring a nandroid backup of your stock ROM if you ever created one in TWRP at any time before the update. Or you can try flashing a custom ROM for your specific device via TWRP.
Sent from my LGL84VL using Tapatalk
I need help I cant speak very very good english sorry. I flashed twrp my J7 prime but if I try rebooting his bootlooping always can I flash custom rom or Stock rom ? (My j7 prime can goes downloading mode and twrp)
Eren but Türk said:
I need help I cant speak very very good english sorry. I flashed twrp my J7 prime but if I try rebooting his bootlooping always can I flash custom rom or Stock rom ? (My j7 prime can goes downloading mode and twrp)
Click to expand...
Click to collapse
If you can not into recovery or download mode, try to flash TWRP again.
Or flash back stock firmware if that does not work. Keep in mind to use Home_CSC to boot wipe your data.
Eren but Türk said:
I need help I cant speak very very good english sorry. I flashed twrp my J7 prime but if I try rebooting his bootlooping always can I flash custom rom or Stock rom ? (My j7 prime can goes downloading mode and twrp)
Click to expand...
Click to collapse
Just flash stock firmware through odin again then boot back into download mode then flash TWRP and untick "Auto-Reboot" option then when flashing is done, boot into recovery manually to verify if TWRP is installed properly then you could boot back up to OS from TWRP it shouldn't loop if all went well. Also make sure that before you flashed TWRP, you enabled OEM Unlock and USB Debugging option in developer options.
Eren but Türk said:
I need help I cant speak very very good english sorry. I flashed twrp my J7 prime but if I try rebooting his bootlooping always can I flash custom rom or Stock rom ? (My j7 prime can goes downloading mode and twrp)
Click to expand...
Click to collapse
It's fine , Flashing TWRP first time wipes your data thus you get bootloop. You just need to Flash a custom rom and evertything will he fine.
tytfusokhszxc said:
It's fine , Flashing TWRP first time wipes your data thus you get bootloop. You just need to Flash a custom rom and evertything will he fine.
Click to expand...
Click to collapse
Yes since TWRP needs internal storage and data wipe to properly work with these partitions when coming from stock ROM but flashing a custom ROM after a clean wipe of the partitions should work fine.
HERE IS THE SOLUTION :
after flashing twrp with odin open twrp and format data after then there is a bug for j7 devices sd card won't work so u need a pc to transfer no verify encryption file to.internal storage here is the file or you can flash magisk 22.1 to disable keneral encryption
(THIS PROBLEM OCCURS BCZ AFTER FLASHING YOUR KENERAL FORCE ENCRYPT YOU TO NOT BOOT IN ROM BCZ OF SECURITY FLASH THIS FILE TO COMPRAMIZE KENERAL SECURITY )
Just Flash the custom rom you have downloaded.
Same thing happened to me when i flash recovery for the first time stucked at the bootlogo.
Hello
All of members here want say one thing( but it's very unclear and confusing )( excuse me all of members post here I don't want say all of you say wrong)the summery of all massages upper than here want say the the stock kernel when installed can not accept the custom recovery .you should with one of this ways disable it:
1-disable dm-verity with file upper massages posted
2-root it
3- install custom kernel
4-install custom rom
AM.Ohadi said:
Yup do among 4 anything it works Hello
All of members here want say one thing( but it's very unclear and confusing )( excuse me all of members post here I don't want say all of you say wrong)the summery of all massages upper than here want say the the stock kernel when installed can not accept the custom recovery .you should with one of this ways disable it:
1-disable dm-verity with file upper massages posted
2-root it
3- install custom kernel
4-install custom rom
Click to expand...
Click to collapse