Related
Hi guys, I searched around the forum before posting this so I apologize but I recently installed a new rom and possibly a wrong kernel with it. Afterwards, if I try to turn it on, it just shows the logo and then turns right off. I can't even go into recovery since it does the same. The only thing I can do is boot it into fastboot but I'm not sure where to go from here. I tried using a guide with no success.
Any words of wisdom?
reflash your recovery via fastboot, then boot into recovery and do a clean install
fastboot flash [recovery].img
I tried reflashing recovery but all it does is show the old rom logo that was used and then shuts down.
Hi,
Read carefully and try this guide:
forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
which rom did you flash? You need the correct twrp file for your bootloader.
That's the first place I tried. Anytime I hook-up my phone to the PC it shows up as OnePlus Android bootloader interface under Android phone and I can't seem to update the drivers..
matze19999 said:
which rom did you flash? You need the correct twrp file for your bootloader.
Click to expand...
Click to collapse
I used the Freedom Rom 2.0
Arken2121 said:
I used the Freedom Rom 2.0
Click to expand...
Click to collapse
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
matze19999 said:
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
Click to expand...
Click to collapse
Thank you so much, I guess I installed the wrong TWRP and I can FINALLY get into recovery. Thank you so much.
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
dg89 said:
Hey guys,
i had CM13 on my phone an i wanted to try a new rom. So i did all the steps like it is written in the thread. After i used the wipe function my phone is always starting in twrp and i cant install a new rom and i also can't update my twrp.
Is my phone now ****ed up or can i do anything to save?
Thx
Click to expand...
Click to collapse
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
tiklmypikl said:
You should be able to boot to bootloader if it's the same problem I have. You can then either flash the stock recovery or this version of TWRP which should fix the problem; https://forum.xda-developers.com/showpost.php?p=70296158&postcount=79
Click to expand...
Click to collapse
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
dg89 said:
thank you but its not working. i can't install the new version twrp and i also tried to install cm13 again and it is not working
Click to expand...
Click to collapse
What verison of TWRP are you on?
tiklmypikl said:
What verison of TWRP are you on?
Click to expand...
Click to collapse
right now it is on v2.8.7.0 and i tried to install the new version but it's not working
Hi guys!
I can root my Galaxy S9 (SM-G960F Exynos variant, build no.: G960FXXU2BRGA, latest build from sammobile). When I want to flash a custom ROM like LineageOS or Resurrektion Remix through TWRP, it remains on the ''Samsung Galaxy s9'' logo after wiping cache and data and rebooting to system.
Before installing any ROM, I wipe the cache, install the ROM, and wipe cache, and then reboot to system. No matter what ROM I flash, it always remains on the logo. I am also able to flash the stock ROM through Odin and install the TWRP in downloading mode and root the device again, but can't flash any custom ROM.
Am I doing something wrong? I appreciate your help!
Thanks in advance!
Update you twrp recovery
I am on the latest build, which is 3.2.3-0.
Vmb265 said:
Update you twrp recovery
Click to expand...
Click to collapse
Ardiswan said:
Hi guys!
I can root my Galaxy S9 (SM-G960F Exynos variant, build no.: G960FXXU2BRGA, latest build from sammobile). When I want to flash a custom ROM like LineageOS or Resurrektion Remix through TWRP, it remains on the ''Samsung Galaxy s9'' logo after wiping cache and data and rebooting to system.
Before installing any ROM, I wipe the cache, install the ROM, and wipe cache, and then reboot to system. No matter what ROM I flash, it always remains on the logo. I am also able to flash the stock ROM through Odin and install the TWRP in downloading mode and root the device again, but can't flash any custom ROM.
Am I doing something wrong? I appreciate your help!
Thanks in advance!
Click to expand...
Click to collapse
Had the same issue. Flash bre5 firmware via twrp.
https://androidfilehost.com/?w=files&flid=272468
I'm having the same issue. I think it's because I'm not on the correct firmware version though. I keep reading that I need to be on BRE5; which I'm currently downloading from updato.com.
---------- Post added at 04:59 PM ---------- Previous post was at 04:56 PM ----------
passion8059 said:
Had the same issue. Flash bre5 firmware via twrp.
https://androidfilehost.com/?w=files&flid=272468
Click to expand...
Click to collapse
How do I flash that via twrp?
Download file from link and reboot to twrp and flash. Phone should boot. If not clean flash.
passion8059 said:
Download file from link and reboot to twrp and flash. Phone should boot. If not clean flash.
Click to expand...
Click to collapse
It doesn't allow me to select the file from the install menu. The download ends with .tar not .zip, so it isn't displaying in the TWRP Install Menu's file explorer. Choosing Install image doesn't make a difference either.
IMissMSN said:
It doesn't allow me to select the file from the install menu. The download ends with .tar not .zip, so it isn't displaying in the TWRP Install Menu's file explorer. Choosing Install image doesn't make a difference either.
Click to expand...
Click to collapse
Flash this before flashing ROM
https://mega.nz/#!PbJAUAxJ!RI7jiQDm7WpeYMZvmURAWsiDMShEt0UPp5YCarvxuDo
Vmb265 said:
Flash this before flashing ROM
https://mega.nz/#!PbJAUAxJ!RI7jiQDm7WpeYMZvmURAWsiDMShEt0UPp5YCarvxuDo
Click to expand...
Click to collapse
Nice, this worked right away; didn't need to reflash the ROM. Thanks very much to you both.
Worked beautifully! Thank you all guys for taking time a responding!
Vmb265 said:
Flash this before flashing ROM
https://mega.nz/#!PbJAUAxJ!RI7jiQDm7WpeYMZvmURAWsiDMShEt0UPp5YCarvxuDo
Click to expand...
Click to collapse
May I ask in this thread for my own problem?
SM-G960F/DS,
After installing TWRP lastest version, backing up, wipe data, cache, dalvik I installed LineageOS, opengapps and addonsu, rebooted to system and now the screen stucks with the samsung galaxy s9 logo. I am not able to turn off the device since more than 30 minutes. Now I'm waiting for the battery to get empty and then try to reboot into TWRP
Do a battery pull power off by pressing and holding the volume down and power keys at the same time for 10 seconds or until the phone boots up. Between the restart hold the keys to get into TWRP recovery and it'll boot into that. Once there follow the instructions above.
IMissMSN said:
Do a battery pull power off by pressing and holding the volume down and power keys at the same time for 10 seconds or until the phone boots up. Between the restart hold the keys to get into TWRP recovery and it'll boot into that. Once there follow the instructions above.
Click to expand...
Click to collapse
Thanks, well I tried those key combinations with no success
...however, I found the following key combination to restart the phone: POWER + VOLUME DOWN + "homebutton" (at the bottom of the touchscreen, where you would find the home button in older phones)
pressing this combination several seconds restarted the phone. After that I FIRST had to go into download-mode, and after that I could finally enter recovery !!! hurray. Trying to enter recovery at once was not possible. However, now I will try to install.
chrisL17 said:
May I ask in this thread for my own problem?
SM-G960F/DS,
After installing TWRP lastest version, backing up, wipe data, cache, dalvik I installed LineageOS, opengapps and addonsu, rebooted to system and now the screen stucks with the samsung galaxy s9 logo. I am not able to turn off the device since more than 30 minutes. Now I'm waiting for the battery to get empty and then try to reboot into TWRP
Click to expand...
Click to collapse
Flash the file in twrp as los needs BRE5 vendor to boot
https://mega.nz/#!PbJAUAxJ!RI7jiQDm7WpeYMZvmURAWsiDMShEt0UPp5YCarvxuDo
Any issues then flash lineage zip again and reboot
ASHLEY117 said:
Flash the file in twrp as los needs BRE5 vendor to boot
https://mega.nz/#!PbJAUAxJ!RI7jiQDm7WpeYMZvmURAWsiDMShEt0UPp5YCarvxuDo
Any issues then flash lineage zip again and reboot
Click to expand...
Click to collapse
Thanks, I will try this later! Really great that kind of fast replies in this forum :good:
ASHLEY117 said:
Flash the file in twrp as los needs BRE5 vendor to boot
https://mega.nz/#!PbJAUAxJ!RI7jiQDm7WpeYMZvmURAWsiDMShEt0UPp5YCarvxuDo
Any issues then flash lineage zip again and reboot
Click to expand...
Click to collapse
Yes, this works!!!!
Thank you very mich
chrisL17 said:
Yes, this works!!!!
Thank you very mich
Click to expand...
Click to collapse
Nice one, certain ROMs need certain vendors and no worries mate
U guys are awesome, thanks for all the help!
This is really frustrating.
Shouldn't this be added to the lineageOS installation wiki or something?
Vmb265 said:
Flash this before flashing ROM
https://mega.nz/#!PbJAUAxJ!RI7jiQDm7WpeYMZvmURAWsiDMShEt0UPp5YCarvxuDo
Click to expand...
Click to collapse
Hi,
I am having the same problem as the OP (although I am not trying to flash a ROM). Before I flash this random link out of the internet, can you tell me what it is and why it is needed? To educate?
Thanks!
Samsung Galaxy S9 (SM-G960F) New Zealand
Hi, I'm new here, new to flashing ROMs, and I'm lost...
Today I flashed TWRP using Odin, then booted to system.
I then rebooted to TWRP, copied a no-verity zip to the internal storage, and installed.
Booted successfully to system again. Nice.
I'm on my way to LineageOS .
I rebooted again, as a test, yet it resulted in a BRICKED STATE!! Only official released binaries are allowed to be flashed.
Now I can only get into download mode, not recovery. Nice... I'm so disappointed.
I will post my results here, after flashing a stock ROM. I assume this will take me back to square one.
But what had I done wrong here, that I can alter next time I attempt to simply install TWRP?!
Luther
LutherChelm said:
Samsung Galaxy S9 (SM-G960F) New Zealand
Hi, I'm new here, new to flashing ROMs, and I'm lost...
Today I flashed TWRP using Odin, then booted to system.
I then rebooted to TWRP, copied a no-verity zip to the internal storage, and installed.
Booted successfully to system again. Nice.
I'm on my way to LineageOS .
I rebooted again, as a test, yet it resulted in a BRICKED STATE!! Only official released binaries are allowed to be flashed.
Now I can only get into download mode, not recovery. Nice... I'm so disappointed.
I will post my results here, after flashing a stock ROM. I assume this will take me back to square one.
But what had I done wrong here, that I can alter next time I attempt to simply install TWRP?!
Luther
Click to expand...
Click to collapse
sorry I only know for stock firmware
leap_ahead said:
flash stock rom with odin ,
go to software update
and check for update …
flash twrp,...
keep read only
format data type YES
reboot to recovery
keep read only
copy the patch
flash patch
reboot to system
go to software update
and check for update …that's fix the problem !
Click to expand...
Click to collapse
Thank you for the clear reply!
But what is the patch you speak of? LineageOS?
Luther
LutherChelm said:
Thank you for the clear reply!
But what is the patch you speak of? LineageOS?
Luther
Click to expand...
Click to collapse
no-verity-opt-encrypt-samsung-1.0.zip
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.