I'm trying to flash Wanamlite's rom but at every attempt it goes into the bootloader instead of actually flashing the rom itself. Sometimes it does it immediately other times it takes about a minute but the screen goes black and when clicking on any button the bootloader appears. I've tried with CWM and Philz's recoveries but it's all the same. Not sure what to do as I'd like to be able to flash custom roms. It hasn't been an issue before. Can anyone help?
Related
after installing a stock rom of MK9. Odin mode appears to have added WRITTEN PROTECTION =ENABLED section. which prevetns me from flash bootloaders or any other custom rom. whenever i attempt to isntall TWRP, it triggers a message at the "SAMSUNG GT-I9505" start screen which stops phone from booting. so i conclude that i managed to stuff up my phone by locking it up. while it does still work. but now i;m stuck on offical rom. anyone help ?
My stock Nexus 7 (4.4, kot49h)'s volume down button is not working. Not even in bootloader (4.23) . Because of that, everytime i reboot it goes in the bootloader, not in system. And from bootloader I'm only able to go to safe-mode. I tried flashing a newer version of bootloader, and re-flashing the stock ROM. I can only use safe-mode.
Any solutions? Should I take it to the service and wait or there is a faster method of solving this problem?
It's an AT&T S5. I messed with the build.prop to try to spoof another phone, and wound up having the Android UI appear tiny and crash whenever I booted to the home screen. I tried to fix this problem by flashing earlier stock firmware with Odin, but now my phone freezes every time it boots up. It will load until the Samsung logo animation, then freeze mid-animation, and the screen will go black with my led light in the corner blue. I have to pull the battery out.
Every soft brick solution I see is to flash stock firmware, but it doesn't seem to be working. I flash G900AUGU1ANCE 4.4.2, the AP, CP and CSC files, but the phone still boots up with the the CUSTOM appearing at initial boot with the unlocked padlock graphic. Usually that goes away after flashing older firmware. SO despite flashing older firmware, it still boots and freezes. I can boot into Recovery mode and Download mode, so the phone is not all the way gone. I try wiping data and cache in Recovery, but that doesn't fix anything. I am at my wit's end. Can anyone help fix this?
QUOTE=RageKage14;59207198]It's an AT&T S5. I messed with the build.prop to try to spoof another phone, and wound up having the Android UI appear tiny and crash whenever I booted to the home screen. I tried to fix this problem by flashing earlier stock firmware with Odin, but now my phone freezes every time it boots up. It will load until the Samsung logo animation, then freeze mid-animation, and the screen will go black with my led light in the corner blue. I have to pull the battery out.
Every soft brick solution I see is to flash stock firmware, but it doesn't seem to be working. I flash G900AUGU1ANCE 4.4.2, the AP, CP and CSC files, but the phone still boots up with the the CUSTOM appearing at initial boot with the unlocked padlock graphic. Usually that goes away after flashing older firmware. SO despite flashing older firmware, it still boots and freezes. I can boot into Recovery mode and Download mode, so the phone is not all the way gone. I try wiping data and cache in Recovery, but that doesn't fix anything. I am at my wit's end. Can anyone help fix this?[/QUOTE]
I'm having the same problem after installing and using the TWRP app on my ATT S5. I tried reflashing the stock rom using odin and it says successful but the phone never boots. It only makes it to the Samsung logo then the screen goes black. I've heard that if the phone is on lollipop which mine is you have to downgrade to kitkat first then flash the stock files.
If your fone boot in recovery perform a full vipe and format system and after go in download mode end use odin for flash all file bootloader, modem ,PIT file for partition find the pit file for ur device modell in xda
It seems every ROM I’ve tried installing never boot after “successfully” through TWRP. (Like even 10 mins of waiting)
My idea is that unlocking the bootloader (where it gives you warnings every time the thing boots) has something to do with it, seeing as the flashing guides don‘t mention this in depth.
Factory reset through TWRP after flash, that wipe after flashing that has the button on the finished page
Now it can’t boot into TWRP, or download mode, just stuck between the power screen and black (seemingly turned off)
Did you flash Magisk-v23.0.apk through TWRP?
burningcreation said:
Did you flash Magisk-v23.0.apk through TWRP?
Click to expand...
Click to collapse
No, I was following this and this which don’t list Magisk as a step
Would that have been important to do?
Also any ideas on how to get it to download mode? So far it just gets stuck on the Galaxy A20 screen with a warning about it being unlocked, no button combo gets past that, even though it does reboot
Hey! I guess you can see from the title that I am a toootal noob in terms of custom recoveryes, roms and rooting, but I was trying to flash pixel experience on the phone, because my warranty recently expired and wanted to try it out. So I searched and I found to flash a rom on any phone I need a custom recovery and found that TWRP is the most popular and supported the phone so I installed odin and the samsung usb drivers, turned on bootloader and usb debugging in the developer settings, booted into the bootloader, connected the phone to my pc and used odin(tried by running it with and without adminstrator) to flash the tar file, with auto reboot turned off, it says it's installed succesfully, but when I hold the power and volume down button to exit bootloader and hold the power and volume up button to boot into recovery mode , instead of showing the phone model and then powered by <whatever it is> it shows me the phone model and under it it says that i have an unofficial OS that may harm my phone or something like that and sends me back to bootloader this time with "<!>" in the upper left corner and something about vbmeta. If I understand it right vbmeta is verified boot which as the name suggest makes the phone boot into the official os and you turn it off when you turn on bootloader. The only way to get out of that is to flash the official firmware again. I would really appreciate it if someone helps me with this. If not I guess I will try to flash Orange Fox recovery.
Try flashing this first, then TWRP