You tried to root or install twrp and now you have a bootloop. You can't access to recovery and you can't flash with odin because it says "Fail!". Now you have Both OEM and FAP lock right?.
The solution: Go the the options tab, make sure "Auto Reboot" IS ticked. 3) Press "start", but as soon as you do, hold down Vol down+Bix+Power on your phone. Odin will fail and your phone will reboot into download mode again. Now press "Start" in Odin again, and your phone should flash without a problem.
Hope it helps you!
you've forgot to mention: it's happen currently only on AQG5 firmware. on AQG5 bootloader if to be more precise.
So, you have to flash at least bootloader from AQF7 (last known custom friendly bootloader).
It seems knox flag is not enough for Samsung anymore. They decided to lock down all phones with custom recovery. There was mention about enhanced firmware security in update. So probably this is it. Probably, tricks with buttons while flashing is kind of bug. I believe Samsung originally wanted to prevent reflash permanently (well, except may be service center).
I'm not 100% sure about exact buttons manipulations, but after some, i was able to flash AQF7 bootloader. I'm not going to update for some time and will see where it will go in the future firmwares.
gastondh91 said:
You tried to root or install twrp and now you have a bootloop. You can't access to recovery and you can't flash with odin because it says "Fail!". Now you have Both OEM and FAP lock right?.
The solution: Go the the options tab, make sure "Auto Reboot" IS ticked. 3) Press "start", but as soon as you do, hold down Vol down+Bix+Power on your phone. Odin will fail and your phone will reboot into download mode again. Now press "Start" in Odin again, and your phone should flash without a problem.
Hope it helps you!
Click to expand...
Click to collapse
Thank you So Much ... You just saved my (Software Bricked) Phone :laugh::laugh::laugh::laugh::good::good::good:
That's correct
sorg said:
you've forgot to mention: it's happen currently only on AQG5 firmware. on AQG5 bootloader if to be more precise.
So, you have to flash at least bootloader from AQF7 (last known custom friendly bootloader).
It seems knox flag is not enough for Samsung anymore. They decided to lock down all phones with custom recovery. There was mention about enhanced firmware security in update. So probably this is it. Probably, tricks with buttons while flashing is kind of bug. I believe Samsung originally wanted to prevent reflash permanently (well, except may be service center).
I'm not 100% sure about exact buttons manipulations, but after some, i was able to flash AQF7 bootloader. I'm not going to update for some time and will see where it will go in the future firmwares.
Click to expand...
Click to collapse
Yep, I forgot that detail, thanks
sorg said:
you've forgot to mention: it's happen currently only on AQG5 firmware. on AQG5 bootloader if to be more precise.
So, you have to flash at least bootloader from AQF7 (last known custom friendly bootloader).
It seems knox flag is not enough for Samsung anymore. They decided to lock down all phones with custom recovery. There was mention about enhanced firmware security in update. So probably this is it. Probably, tricks with buttons while flashing is kind of bug. I believe Samsung originally wanted to prevent reflash permanently (well, except may be service center).
I'm not 100% sure about exact buttons manipulations, but after some, i was able to flash AQF7 bootloader. I'm not going to update for some time and will see where it will go in the future firmwares.
Click to expand...
Click to collapse
Hello! I ask for help. I have this problem. I tried to install trwp and hung on the boot screen with the samsung logo. The instruction helped me to set trwp again but the result is the same. I have samsung galaxy s8 +
Please explain how can I flash AQF7 bootloader to be able to boot in the system ?
plz help (
sorg said:
you've forgot to mention: it's happen currently only on AQG5 firmware. on AQG5 bootloader if to be more precise.
So, you have to flash at least bootloader from AQF7 (last known custom friendly bootloader).
It seems knox flag is not enough for Samsung anymore. They decided to lock down all phones with custom recovery. There was mention about enhanced firmware security in update. So probably this is it. Probably, tricks with buttons while flashing is kind of bug. I believe Samsung originally wanted to prevent reflash permanently (well, except may be service center).
I'm not 100% sure about exact buttons manipulations, but after some, i was able to flash AQF7 bootloader. I'm not going to update for some time and will see where it will go in the future firmwares.
Click to expand...
Click to collapse
Deleted.
nyanAttack said:
Hello! I ask for help. I have this problem. I tried to install trwp and hung on the boot screen with the samsung logo. The instruction helped me to set trwp again but the result is the same. I have samsung galaxy s8 +
Please explain how can I flash AQF7 bootloader to be able to boot in the system ?
plz help (
Click to expand...
Click to collapse
download AQF7 firmware and flash BL_* part from it.
I'm sorry for a necroposting. But it helped to me . Thx slot !
gastondh91 said:
You tried to root or install twrp and now you have a bootloop. You can't access to recovery and you can't flash with odin because it says "Fail!". Now you have Both OEM and FAP lock right?.
The solution: Go the the options tab, make sure "Auto Reboot" IS ticked. 3) Press "start", but as soon as you do, hold down Vol down+Bix+Power on your phone. Odin will fail and your phone will reboot into download mode again. Now press "Start" in Odin again, and your phone should flash without a problem.
Hope it helps you!
Click to expand...
Click to collapse
Thank you so much!!!
after 2 days with a brick instead of phone and diving into google and the XDA forum finally the solution!!!
:good::good::good::laugh::laugh:
thanks a lot !!!!
thx!
friend !! I thank you from the heart! you saved me from the soft brick
Please help the same thing happens on the new oreo os when installing twrp
Can you please help me fix it?
gastondh91 said:
You tried to root or install twrp and now you have a bootloop. You can't access to recovery and you can't flash with odin because it says "Fail!". Now you have Both OEM and FAP lock right?.
The solution: Go the the options tab, make sure "Auto Reboot" IS ticked. 3) Press "start", but as soon as you do, hold down Vol down+Bix+Power on your phone. Odin will fail and your phone will reboot into download mode again. Now press "Start" in Odin again, and your phone should flash without a problem.
Hope it helps you!
Click to expand...
Click to collapse
sorry friend, can you give me a spesific step by step ?
Related
I pulled a boneheaded move and ended up formatting my phone from within the TWRP menu. Now the stock operating system is gone.
I wanted to put on one of the Gummy Nightly builds, but I'm new to TWRP and selected the wrong options while wiping.
So now I have the Gummy ROM on my PC, the phone is connected to my PC and in TWRP (in the advanced adb sideload feature), but adb will not recognize my phone.
When I check device manager, SAMSUNG_Android_SCH-I535 is there, but with a yellow "cauton" symbol. When I look at properties, it tells me that "The drivers for this device are not installed (Code 28).
I went out to the Samsung page and got the exe to unpack drivers on my machine... I've tried "update driver" and pointing to the root of the directory containing the Samsung drivers, but my PC claims none of them are applicable.
So what I'm looking for here is:
(1) How do I get this ROM on my phone so that I can install the zip and have a working OS again?
(2) Assuming that using the ADB Sideload feature of TWRP is my best option, how do I get the device drivers for my galaxy s3 installed to my windows 8 PC and get adb to detect it?
Thanks in advance.
Ok, so it seems to have gotten worse.
I cannot get my windows installation to recognize the phone without it being able to boot an android OS, it seems.
I had it in TWRP 2.6.0.0, but as I was trying to reboot to see if I could get into download mode (my thought being to change out TWRP for Clockwork; I seem to remember Clockwork Recovery having a "mount as USB" option which TWRP seems to lack), it tried to root the file system.
After that, the screen went black and nothing happened... the phone was unresponsive. I would remove the battery and replace it to have it vibrate once and then not respond to any key presses.
I removed the battery, SD card, and SIM card, replacing only the battery and got it to turn on and show a Samsung Galaxy SIII logo... but it's just sitting there... I'm assuming it's frozen because there's no OS to boot on the internal storage.
Please help me recover my phone!
Ok, so I've found I can still get into download mode, but not into recovery.
Recovery seems to lead to a black screen with nothing on it.
Trying to boot normally leads to the statis Samsung Galaxy SIII logo.
Can I fix my phone from the download menu?
Please help me.
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
ThePagel said:
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
Click to expand...
Click to collapse
Thanks for the reply!
Sorry, I'm a little out of date on the flashing and stuff -- I was just over in the thread where the poster thought he half softbricked his phone and was asking about 4.1.2 vs. 4.3
I see this at the top of my screen sitting here in download mode:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
It seems my bootloader got relocked somehow -- is this why my phone just goes to black screen when I attempt to boot into recovery -- even if I have TWRP or CWR installed? Odin claims I just pushed philz custom CWR to my PDA section, but it still won't go into recovery.
What are my options here?
You are pre 4.3 I'll help you more in the morning if no one else does first.
ThePagel said:
You are pre 4.3 I'll help you more in the morning if no one else does first.
Click to expand...
Click to collapse
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
corrosivefrost said:
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
Click to expand...
Click to collapse
Once you in download mode, can your Odin see your phone?
buhohitr said:
Once you in download mode, can your Odin see your phone?
Click to expand...
Click to collapse
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
corrosivefrost said:
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
Click to expand...
Click to collapse
What stock version do you have on your phone right now?
buhohitr said:
What stock version do you have on your phone right now?
Click to expand...
Click to collapse
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
I'm really not sure what kind of state anything is in at this point -- other than Odin seemingly working and being able to get into download mode.
Again, short version of what happened:
(1) Accidentally did a full wipe (factory reset?) in TWRP -- this wiped the ROM I was going to install with TWRP off the phone.
(2) While trying to ADB sideload from TWRP and telling TWRP to reboot, TWRP tried to install supersu.
(3) After (2), I was unable to get back into recovery mode. I got into Odin and tried to flash philz customer clockwork recovery and it seemed successful. Reboot and attempt to enter recovery still fails. Samsung logo with recovery mode text appears, but then the screen goes black.
(4) Normal boot leaves the screen stuck on the Samsung Galaxy SIII logo indefinitely.
corrosivefrost said:
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
Click to expand...
Click to collapse
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
buhohitr said:
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
Click to expand...
Click to collapse
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
corrosivefrost said:
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
Click to expand...
Click to collapse
Yes, it's pre rooted stock image and yes flash with PDA.
buhohitr said:
Yes, it's pre rooted stock image and yes flash with PDA.
Click to expand...
Click to collapse
Standard auto-reboot and f_reset_time options? nothing else necessary?
corrosivefrost said:
Standard auto-reboot and f_reset_time options? nothing else necessary?
Click to expand...
Click to collapse
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
buhohitr said:
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
Click to expand...
Click to collapse
Alright, I'll give it a shot and report back.
Thank you!
corrosivefrost said:
Alright, I'll give it a shot and report back.
Thank you!
Click to expand...
Click to collapse
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
It did work! Hooray!
buhohitr said:
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Didn't need to go that far -- but now that I'm back up and running, signed into google play, and downloaded goo manager, can you point me in the right direction for getting it to install cwm recovery?
Thanks guys!
This guide is intended for the Samsung Galaxy Core Prime, but it may work on other devices if you have the same issue.
The problem: You can only boot into recovery, and bootloader/download mode.
What you need: Stock Recovery, Odin v3.10.6 (This is what I used at least), TWRP Recovery and TrapKernel.
Download those and when you are done boot your device into Bootloader/Download mode.
Guide for 'beginners'
Connect it to your computer.
You should already have TrapKernel flashed then good, if not then flash if by clicking BL(It doesn't make a difference from what I have noticed, if you choice BL or AP but in my case I choice BL) and selecting it TrapKernel. Hit start.
Your device will start normally. This Doesn't fix your problem yet. Turn your device off and boot back into Bootloader/Download mode.
Click BL again and select the stock recovery you downloaded.
Click start.
Your device is now booted normally, but yet again this is expected and doesn't fix the problem.
Turn your phone off. It will boot into recovery again, scroll down and click "Reboot into Bootloader"
Now hold your power, vol down, and home button until your device turns off and turns on.
It will prompt you, hit vol up.
Now go back into Odin and hit BL again, and find TWRP recovery.
Hit start and it will, once again start your device normally.
Your device is now fixed. Don't believe me? Power off and power it back on. It will boot normally.
For more experienced people that just want the basics of what to do:
Flash TrapKernel if you haven't already.
Flash Stock Recovery (By itself), then flash TWRP Recovery(By itself).
Your problem should be solved.
Have any problems or think I didn't explain this good enough? Tell me. I am open to constructive criticism.
Very important root necessity
very important root necessity before you try to root your phone you must go to the developers options and check the "device to allow OEM bootloader unlock"this way it can allow the bootloader to be unlocked and you can then gain root. Sincerely Bricked for days.
Your sir are a savior
I'm sorry if I come off as crazy. BUT THANK YOU SO FREAKING MUCH. I just got done typing out a lengthy reply in the rom's forum about the "Device reboots into recovery" issue. I wish I had read around for your reply. Jesus man, you saved my bacon. I will like your post. Both of them.
If samsung knox is tripped. But reverting back to stock firmware wil features such as andoird pay and samsung updates still be disabled as a result of knox tripped? or this only an issue on custom fw.
If the "KNOX WARRANTY VOID" has been tripped to 1, there is NO way to use Android Pay or Samsung Pay anymore on tripped device.
forumber2 said:
If the "KNOX WARRANTY VOID" has been tripped to 1, there is NO way to use Android Pay or Samsung Pay anymore on tripped device.
Click to expand...
Click to collapse
thanks for your response.
what about the ability to use the samsung update feature etc and apps which do not run on rooted devices. will reverting back to stock fw cure this ?
Driver15 said:
thanks for your response.
what about the ability to use the samsung update feature etc and apps which do not run on rooted devices. will reverting back to stock fw cure this ?
Click to expand...
Click to collapse
Yes, reverting back to stock fw will make it possible to get samsung updates and to use apps that doesn't work with root. Knox tripped won't effect anything except samsung pay or android pay and you loose your warranty (you won't be able to repair your phone in an official Samsung store) However you can still have a custom fw and use apps wich do not run on rooted devices, you can google methods on how to You can also get updates to the newest firmware if the development of the rom of your choice is still active
Jojobojo100 said:
Yes, reverting back to stock fw will make it possible to get samsung updates and to use apps that doesn't work with root. Knox tripped won't effect anything except samsung pay or android pay and you loose your warranty (you won't be able to repair your phone in an official Samsung store) However you can still have a custom fw and use apps wich do not run on rooted devices, you can google methods on how to You can also get updates to the newest firmware if the development of the rom of your choice is still active
Click to expand...
Click to collapse
Thanks this is exactly what I wanted to know.
one last thing can the s6 be rooted and run custom recovery from any official fw.
Sent from my SM-G920F using Tapatalk
Driver15 said:
Thanks this is exactly what I wanted to know.
one last thing can the s6 be rooted and run custom recovery from any official fw.
Click to expand...
Click to collapse
Yes, I would recommend arter97's TWRP recovery, works like a charm http://arter97.com/browse/exynos7420/recovery/twrp/
You can flash it with ODIN
Jojobojo100 said:
Yes, I would recommend arter97's TWRP recovery, works like a charm http://arter97.com/browse/exynos7420/recovery/twrp/
You can flash it with ODIN
Click to expand...
Click to collapse
guys i am new to samsung device. how to unlock bootloader to flash custom roms and will flashing recovery is sufficient?
Guide me to root or to unlock bootloader. i have g920i running 6.0.1 baseband version is G9201DVU3EPH4
sushobith said:
guys i am new to samsung device. how to unlock bootloader to flash custom roms and will flashing recovery is sufficient?
Guide me to root or to unlock bootloader. i have g920i running 6.0.1 baseband version is G9201DVU3EPH4
Click to expand...
Click to collapse
Installing a recovey is very useful so you can install custom roms and root your phone. Here are my instructions :
Unlock developer options in settings, go into about device and software info, tap on you buildnumber 7 times. Go into developer options and switch it on. Find USB debugging and switch it on.
You need to download ODIN and install it to your computer http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/ download the latest version of odin
You also need to download samsung usbdrivers http://www.samsung.com/us/support/owners/product/SM-G920AZKFATT go down to downloads and click install exe and accept. When the download is finished install the usbdrivers.
Custom recovery http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/ download the tar file and NOT a zipfile to your computer.
1. Switch your phone off
2. Press and hold down volume down + home button + power button at the same time.
3. Release the buttons when the warning comes up and press volume up.
4. Open ODIN and plug in your phone to your computer via an USB cable.
5. When ODIN has recognized your phone just click on AP and browse untill you find the recovery tar file you have downloaded.
6. Click on start. Let ODIN do it's job.
7. Your phone might boot into recovery or just restart itself and if it boots into recovery tap on Reboot and tap System.
Now you have a custom recovery installed and to boot into recovery switch off your phone. Press and hold down volume up + home button + power button at the same time until the samsung logo pops up and in the top left corner it will say in red "warning recovery not enforcing"
On xda you can find many different roms for galaxy s6 and hopefully you can find one that suits you. Follow the devolopers instructions on how to install them.
If you just want to root your phone download Super SU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
Boot into recovery and tap Install. Browse the file SuperSU-v2.78, it's probably in the Download folder. Tap the file and flash it. When it's done wipe dalvik and cache and reboot.
You won't loose any data when you do all this if everything goes smoothly. Good luck!
Jojobojo100 said:
Installing a recovey is very useful so you can install custom roms and root your phone. Here are my instructions :
Unlock developer options in settings, go into about device and software info, tap on you buildnumber 7 times. Go into developer options and switch it on. Find USB debugging and switch it on.
You need to download ODIN and install it to your computer http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/ download the latest version of odin
You also need to download samsung usbdrivers http://www.samsung.com/us/support/owners/product/SM-G920AZKFATT go down to downloads and click install exe and accept. When the download is finished install the usbdrivers.
Custom recovery http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/ download the tar file and NOT a zipfile to your computer.
1. Switch your phone off
2. Press and hold down volume down + home button + power button at the same time.
3. Release the buttons when the warning comes up and press volume up.
4. Open ODIN and plug in your phone to your computer via an USB cable.
5. When ODIN has recognized your phone just click on AP and browse untill you find the recovery tar file you have downloaded.
6. Click on start. Let ODIN do it's job.
7. Your phone might boot into recovery or just restart itself and if it boots into recovery tap on Reboot and tap System.
Now you have a custom recovery installed and to boot into recovery switch off your phone. Press and hold down volume up + home button + power button at the same time until the samsung logo pops up and in the top left corner it will say in red "warning recovery not enforcing"
On xda you can find many different roms for galaxy s6 and hopefully you can find one that suits you. Follow the devolopers instructions on how to install them.
If you just want to root your phone download Super SU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
Boot into recovery and tap Install. Browse the file SuperSU-v2.78, it's probably in the Download folder. Tap the file and flash it. When it's done wipe dalvik and cache and reboot.
You won't loose any data when you do all this if everything goes smoothly. Good luck!
Click to expand...
Click to collapse
Thankyou
Hi,
I have S8 Plus SM-G955F in Germany.
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery. However, it does not enter into recovery and reboots after few seconds into "installing updates" mode which then fails.
It does not boot up into Android.
All I can access to is Download Mode.
I flashed "BL_G955FXXU1AQF7_CL11544126_QB13847503_REV00_user_low_ship.tar" Bootloader and rebooted and now it is stuck in Samsung boot logo. If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
I now downloaded following stock firmware through SamFirm: "SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
but when trying to flash it in odin I get FAILED !!! Also if I try to flash TWRP recovery "twrp-3.1.0-1-dream2lte.img" I get FAILED in Odin I now also tried to flash "AP_G955FXXU1AQH3_CL12050265_QB14545623_REV00" firmware using this tutorial: https://www.youtube.com/watch?v=2y0ZZxcNVnE which also FAILED. I think I am completely bricked !!
Please help, phone is completeley useless now
Thanks!
tobyffm said:
SM-G955F_1_20171214140840_hlcm4r582t_fac.zip.enc4" (3332 MB)
Click to expand...
Click to collapse
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.
Maltonator said:
I had the same problem with downloading stock firmware. My problem was that I couldn't download from SamMobile because of server maintenance. So I downloaded from here. An with this tool there's the option to decrypt the file automatically. I forgot to tick this option and had a .enc4-file like you have there. The problem could decrypt this file and then I could unzip it and use it with odin.
So that's your problem: you are trying to use an encrypted file. But you have to use an decrypted file.
Click to expand...
Click to collapse
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.
tobyffm said:
Hi,
thank you! But its actually not my problem. Samfirm decrypted and I got the zip with the BL, AP, CSC, CP files in it. But ODIN fails everytime anyway and I have no idea what I could still do now.
Click to expand...
Click to collapse
But you flashed all four files at the same run together?
Maltonator said:
But you flashed all four files at the same run together?
Click to expand...
Click to collapse
Yes, like the howto video described.
tobyffm said:
Dont knwo what exactly happend, but my phone was just still running fine (bootloader is unlocked) and I rebooted but then was stuck at "Installing system updates" screen which appear before getting into recovery.
Click to expand...
Click to collapse
But this happens with my phone to if I press volume up.
tobyffm said:
If I press Vol up + Bixpy Button + Power nothing happends, it does not even start to load Recovery mode.
Click to expand...
Click to collapse
But you have to press Vol down
Maltonator said:
But this happens with my phone to if I press volume up.
But you have to press Vol down
Click to expand...
Click to collapse
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand
tobyffm said:
Usual behaviour was this: Vol up, bixpy and Power -> Recovery mode which fist starts with "Installing update..." then failed and then it goes into some black recovery mode where you can choose Apply update.zip etc. right? However, in my case this black screen with more commands did not show up, before it was rebooting again by itself.
Now I cannot even get into this "installing updates" mode before recovery, because "Vol up, bixpy and Power" does not bring any action.
Click to expand...
Click to collapse
But why do you boot in recovery mode?
tobyffm said:
Vol down, Bixpy and Power still works and brings me to Download Mode. But it doesnt help me, because once I tr to flash any firmware in Download Mode, it FAILS in Odin, so I am completely stuck, hope you understand
Click to expand...
Click to collapse
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.
Maltonator said:
But why do you boot in recovery mode?
Download mode is the only mode you need for restoring stock firmware.
Try this guide. (Spoiler "Flashing Standard Firmware:")
Yesterday I did it with this one too and it worked flawlessly. But I used Odin v3.12.3 not as said in the guide V3.12.7.
Click to expand...
Click to collapse
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
tobyffm said:
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.
Maltonator said:
Yes that's the only thing that comes on my mind too if you think everything else is right. Download another firmware file maybe from a different provider than SamMobile.
Or try using different USB-Port, USB-Cable and/or different PC.
Click to expand...
Click to collapse
Did already, did not help. I think maybe there is something realldy bricked, so flashing stock firmware wont be possible at all anymore?! Is this possible somehow?
btw: Just managed to load into TWRP, randomly it does load twrp, dont know how, because if I press the keys for loading into recovery, it actually does not do anything, but currently I see twrp.
Is see anything I can try from there? btw: formated data (incl. internal storage) earlier already, but it did not change anything.
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...
tobyffm said:
But any idea what I can try to flash from TWRP maybe? Is there a way to flash stock firmware from TWRP somehow?
I found a backup in twrp, I am currently trying to restore it...
Click to expand...
Click to collapse
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.
Maltonator said:
Google found this. But I don't know if this works. I only flashed custom ROMs via TWRP. Stock ROMs always via Odin.
Click to expand...
Click to collapse
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!
tobyffm said:
Puuuuh, I was able to fix phone with hat TWRP backup I found!
Thanks for your efforts anyway, much appreciated!
Click to expand...
Click to collapse
Glad it worked! :good:
tobyffm said:
it automatically loaded into recovery before, I was not able to boot into Android, it loaded recovery (but without black screen with more commands) automatically by default and rebooted, loaded recovery again and rebooted, loaded recovery againd and rebooted etc...all I could to to interrupt this was loading download mode.
However, thanks for the link, but it does describe what I did already. And yes, I also used Odin 3.12.3 already because in the video tutorial I linked some posts before they said also, I need to use that version.
However, it simply does not work. Odin FAILS everytime
I am not doing anything wrong, I am sure. The only thing could be that the Firmware I downloaded is still wrong, even I cannot imagine this.
Click to expand...
Click to collapse
My mistake, sorry - I posted in the wrong place- sorry. (I do hope you find a way to get t his fixed) good luck
I just ran into this thread: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
It looks like you're not the only one...
You know, you might want to try and remove the more current apps you installed and see if that is causing the loop, and if that does not work, just dirty flash over what you have. For me, a lot of time a dirty flash will solve the issue, as it overwrites the OEM software, and in that manner, takes my phone OS back to normal/new state, while leaving my data.
Is there anyone here facing same with my situation? today i bricked my J4 plus, Dunno if its hard bricked or soft brick, I can't enter to download mode and system restore anymore. Im just trying to get oreo back because i fell little laggy on my current os (pie). I went to samsung service center and they told to use JTAG to get it fix but its too expensive for me to pay hundreds buck for this.
Thank you
its not bricked. your battery is full drained. i had the same problem and how i fixed!!! i presed all 3 buttons and put usb cable to my pc and my phone. it goes like bootloop starts and shuts. you will wait with pressed buttons from 5 to 10 mins depend how low is your battery. and finaly will go to download mode and you can flash it then!!!
Bricked my J4+
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
FL0R1AN said:
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
Click to expand...
Click to collapse
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
rudi021 said:
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
Click to expand...
Click to collapse
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
FL0R1AN said:
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
Click to expand...
Click to collapse
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
rudi021 said:
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
Click to expand...
Click to collapse
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
FL0R1AN said:
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
Click to expand...
Click to collapse
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
rudi021 said:
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
Click to expand...
Click to collapse
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
FL0R1AN said:
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
Click to expand...
Click to collapse
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
rudi021 said:
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
Click to expand...
Click to collapse
Thanks. I will wait for the phone to be unbricked and then will try TWRP again.
Can i install gsi rom if the phone is in oneui?
FL0R1AN said:
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately .
Click to expand...
Click to collapse
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
ashyx said:
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
Click to expand...
Click to collapse
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
FL0R1AN said:
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
Click to expand...
Click to collapse
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
rudi021 said:
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
Click to expand...
Click to collapse
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
install twrp(in odin option uncheck Auto Reboot) ,format data reboot to recovery,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
rudi021 said:
install twrp,format data,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
Click to expand...
Click to collapse
Got it, Thanks.
FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
ashyx said:
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
Click to expand...
Click to collapse
Got it, Thanks