In my view:
I have noticed a few of you are reverting to stock and getting hard brick , I believe this cannot be fixed this is after either rooting or after installing stock . This will only happen over ota as it affects ur system partition and modem . Pls do not update on stock ROMs unless you are sure of the software number matching new software , even a carrier software with a letter difference can destroy your phone. Therefore , either don't unlock your phone or don't update via OTA
I got hardbricked device when i was updating an security patch in stock rom, unlocked bootloader...
Any fixes or solution? Blank flash or QFIL files?
CypherPotato said:
Any fixes or solution? Blank flash or QFIL files?
Click to expand...
Click to collapse
If you can still get into fastboot, try flashing TWRP and some custom ROM.
If not, your device is bricked beyond repair.
BtbN said:
If you can still get into fastboot, try flashing TWRP and some custom ROM.
If not, your device is bricked beyond repair.
Click to expand...
Click to collapse
Nope not work.
Related
A friend tried to flash CWM ( http://forum.xda-developers.com/showthread.php?t=2201860 ) for s4 and it failed...and now the phone is stuck..it says: Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again
Phone model: i9505
Some help please? I don't know what to do
EDIT: i found that i can flash the firmware with odin..but i still have a question..im not really sure what firmware i had before..so is there any problem if i install firmware from other country or carrier?
You can find latest stock fw for your phone here.
wvw.sammobile.com/firmwares/checker/
I can't post external links so change wvw to www
waynevan2000 said:
You can find latest stock fw for your phone here.
wvw.sammobile.com/firmwares/checker/
I can't post external links so change wvw to www
Click to expand...
Click to collapse
thanks but.. the phone isnt starting that's why i have to flash a firmware..so i can't check what firmware i have..
The flashing process failed at half of it..:/......
Just pick one of the latest.
btw if the flashing of the recovery fails then just try the standard stuff
- different usb port
- different cable
Lennyz1988 said:
Just pick one of the latest.
btw if the flashing of the recovery fails then just try the standard stuff
- different usb port
- different cable
Click to expand...
Click to collapse
Finally worked to flash a firmware..i used europe firmware from here http://forum.xda-developers.com/showpost.php?p=41072392&postcount=2
Aaaaand when the phone started, a error keeped showing up: samsung keyboard stoped working...and i entered in recovery menu and did a factory reset, and that error is still showing.... some help?..maybe i should flash other firmware? which firmware? i really don't know what firmware it had before..
And one more thing..i cant even connect to wifi because it says something about security error something that the system blocked an unwanted action or something like that :/..something from knox :/
PS: i flashed just the AP file but the firmware had more files :/..
raulx222 said:
Finally worked to flash a firmware..i used europe firmware from here http://forum.xda-developers.com/showpost.php?p=41072392&postcount=2
Aaaaand when the phone started, a error keeped showing up: samsung keyboard stoped working...and i entered in recovery menu and did a factory reset, and that error is still showing.... some help?..maybe i should flash other firmware? which firmware? i really don't know what firmware it had before..
And one more thing..i cant even connect to wifi because it says something about security error something that the system blocked an unwanted action or something like that :/..something from knox :/
PS: i flashed just the AP file but the firmware had more files :/..
Click to expand...
Click to collapse
Why did you want to flash a custom recovery, to just flash a custom rom? If so, then just flash the custom recovery again and then flash the custom rom you want.
And why would you just flash the ap file if the firmware has more files? Makes no sense to me.
Lennyz1988 said:
Why did you want to flash a custom recovery, to just flash a custom rom? If so, then just flash the custom recovery again and then flash the custom rom you want.
And why would you just flash the ap file if the firmware has more files? Makes no sense to me.
Click to expand...
Click to collapse
Thanks! i managed it.. 2 S4 devices got Imperium v13 ROM
I need this fixed asap as I need my phone for school.. I have no idea what Happened honestly, I just restarted my phone and it started doing this. The only thing i recall doing is possibly disabling SuperSU on accident before I restarted my phone.
All I've done so far is download the stock firmware from SamMobile and attempted to flash it, but when i do i get an (auth) failed code from Odin, I've been searching for hours and haven't found anything that has helped..
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Can you help with a newer model?
*Detection* said:
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Click to expand...
Click to collapse
i don't have anything recovery installed, its jsut the normal android recovery. I thought about reflashing supersu but I'm not sure how without a recovery..
Have you tried the factory reset from normal recovery?
*Detection* said:
Have you tried the factory reset from normal recovery?
Click to expand...
Click to collapse
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
What about a SM-G900P?
TheAgonistxX said:
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
Click to expand...
Click to collapse
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
*Detection* said:
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
Click to expand...
Click to collapse
Tried flashing TWRP with the same end result.. This is dumb really frustrating -.- is there any way to install Supersu without a recovery?
CF Auto Root, but it'll likely fail too due to the bootloader
II have been working on mine same model and it is because once you screw up ,which i did,the locked boot loader wont let anything by. a relative pretty much started the problem by flashing a ROM and erasing everything. this one wont even go into recovery. still wont give up until I figure out a way just because.......
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
kociubin said:
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
Click to expand...
Click to collapse
In Odin flash an older firmware then reroot and wait for a root update from Chainfire and the TWRP team
I know a couple people that have done that.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F
When I first upgraded to the new firmware, I found the same thing that you did - I wanted to be able to flash custom roms and didn't know when or if TWRP and ROOT was going to be possible with this new firmware - so I used odin and reflashed July's Firmware and I was able to do so without any Issues - so then I decided to try to upgrade the AP/CSC/CP files from the latest update and replaced the bootloader with the bootloader from july's update and it worked.
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not an indication of future issues for rooting samsung phones....
mocsab said:
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not indication of future issues for rooting samsung phones....
Click to expand...
Click to collapse
No it isn't. Korean models had already been incompatible with official TWRP since firmware APG7 and I confirmed it working again when I replaced the kernel inside TWRP with one built from the latest source released by Samsung. So, someone needs to build a new TWRP recovery with BPH6 kernel source and everything will become fine again.
I didnt know that but it is very good news as far as I am concerned.
I have alwasy been fearful that Samsung was going to eventually lock down their international phones like they did to the US Variants - and when this originally happened to me, I started thinking that maybe my worst fears had come true. Thanks for the information....
I have the same question,but i soved it,i Flash the old BL and TWRP can working
BL version :BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Xlim said:
I have the same question,but i soved it,i Flash the old BL and TWRP can working
BL version :BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Click to expand...
Click to collapse
pls send related boot loader download link
same iussue .. some news??
by the way to use root now i put the old firmwere
FARSHOOD said:
pls send related boot loader download link
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24671318762848807
When flashing bootloader in Odin there is an options tab, there are checkboxes - Auto Reboot which is checked - Re-Partiion which is unchecked - and - F.Reset Time which is checked, I flashed new bootlaoder and modem and now my phone will not restart no matter the key combination I press. So Are those checkboxes suppose to be checked off or unchecked
I factory reseted my S5 but when it went for the restart it said:
Recovery booting...
SYS REV CHECK FAIL(K) : No version
Secure : SECURE VERSION failure (recovery.img)
then
SECURE FAIL: RECOVERY
with Start up Failed screen and a prompt text to use the software repair assistant.
As you can see i while back i tried to flash it to newer OS but i remember i just couldn't manage to install the custom recovery or root it so i dropped it. Now it's come back to bite me in the ass, what do i do? Please help me out.
UglyBastard said:
what do i do? Please help me out.
Click to expand...
Click to collapse
Those writings do not bode well.
I'd try to flash the latest stock factory service firmware for your SM-G900V.
You can download it here: https://androidfilehost.com/?fid=818070582850486654
bbsc said:
Those writings do not bode well.
I'd try to flash the latest stock factory service firmware for your SM-G900V.
You can download it here: .......
Click to expand...
Click to collapse
I am currently downloading the 5.0 lollipop from sammobile as that is what was originally on. I have my doubts as to whether it will work since i was most likely unable to root the device or install the custom recovery. Is it possible to flash it back to stock firmware without root?
UglyBastard said:
Is it possible to flash it back to stock firmware without root?
Click to expand...
Click to collapse
Rooting process changes system partition and/or boot (kernel) partition.
They both (and recovery partition too) will be reverted back to stock after flashing a stock firmware.
Which version of LP do you currently have?
bbsc said:
Rooting process changes system partition and/or boot (kernel) partition.
They both (and recovery partition too) will be reverted back to stock after flashing a stock firmware.
Which version of LP do you currently have?
Click to expand...
Click to collapse
I finally finished downloading the verizon 5.0 G900V firmware and flashed my phone with odin which surprisingly worked. But now it has so much bloatware crap it almost makes up two entire screens. Can i flash it to latest marshmallow stock rom and should i ? Since i don't believe i will be tinkering with it anymore. Anyway thanks for your help.
UglyBastard said:
Can i flash it to latest marshmallow stock rom and should i ?
Click to expand...
Click to collapse
You definitely can but I cannot say if you should.
It depends on many things.
I think it's a good idea to have the latest firmware if you're just a usual phone user and not interested in rooting and so on.