Related
Hi,
I am using samsung galaxy S5 SM-G900R7, i am able to root this phone then started trying flashing of custom boot.img contating custom zImage. ODIN is showing successful flashing , but when i am restarting its always going in download mode with error message "couldn't do normal boot" . In download mode there is a line "QUALOCM SECUREBOOT : ENABLE". I doubt this is beacuse of locked bootloader.
I want to know is it really beacuse of locked bootloader?
I downloaded kernel for my phone model from samsung official website mentioned below and built in same way they have given instruction, so i ahve less doubt on custom zImage.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
if yes then i have second question is it unlockable or not, i am not getting any unlocking method for samsung galaxy S5. whatever info i am getting regarding unlocking is upto galaxy S3 but not helpful for galaxy S5. PLease help me to come to a final conclusion on flashing custom zImage to phone.
arvind3023 said:
Hi,
I am using samsung galaxy S5 SM-G900R7, i am able to root this phone then started trying flashing of custom boot.img contating custom zImage. ODIN is showing successful flashing , but when i am restarting its always going in download mode with error message "couldn't do normal boot" . In download mode there is a line "QUALOCM SECUREBOOT : ENABLE". I doubt this is beacuse of locked bootloader.
I want to know is it really beacuse of locked bootloader?
I downloaded kernel for my phone model from samsung official website mentioned below and built in same way they have given instruction, so i ahve less doubt on custom zImage.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=900r7
if yes then i have second question is it unlockable or not, i am not getting any unlocking method for samsung galaxy S5. whatever info i am getting regarding unlocking is upto galaxy S3 but not helpful for galaxy S5. PLease help me to come to a final conclusion on flashing custom zImage to phone.
Click to expand...
Click to collapse
As far as I'm aware most Samsung devices if not all have unlocked bootloaders, as for a soloution I haven't seen anything really but some say you need to re-flash stock then try from scrath or make a backup after reflashing stock and a custom recovery then format and restore to get it working.
TechMinerUK said:
As far as I'm aware most Samsung devices if not all have unlocked bootloaders, as for a soloution I haven't seen anything really but some say you need to re-flash stock then try from scrath or make a backup after reflashing stock and a custom recovery then format and restore to get it working.
Click to expand...
Click to collapse
Thanks a lot for your reply,
I searched regarding this and i found latest samsungs are coming with KNOX security in which SECUREBOOT is there, which doesn't allow phone to boot with any boot image if chacksum value doesn't match. so i feel even if bootloader is not locked here but same thng KNOX security is doing. Help me if you have any idea how to disable it in samsung galaxy S5. Getting way how to disable in previous series but not finding method how to do for galaxy S5.
arvind3023 said:
Thanks a lot for your reply,
I searched regarding this and i found latest samsungs are coming with KNOX security in which SECUREBOOT is there, which doesn't allow phone to boot with any boot image if chacksum value doesn't match. so i feel even if bootloader is not locked here but same thng KNOX security is doing. Help me if you have any idea how to disable it in samsung galaxy S5. Getting way how to disable in previous series but not finding method how to do for galaxy S5.
Click to expand...
Click to collapse
Looks like getting rid of KNOX is a difficult task but not impossible: http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
TechMinerUK said:
Looks like getting rid of KNOX is a difficult task but not impossible: http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html
Click to expand...
Click to collapse
Thanks for your reply,
I think your post brought me closer to soltution. Tommorw i have to try this. The only problem now i have that i am not getting firmware for my phone model SM-900R7, I am getting firmware for model number SM-900R6 which is very close to this not not exactly for SM-900R7. I have to search more to get it, i hope i will be able to find it.
Thanks again for your valuable post.
arvind3023 said:
Thanks for your reply,
I think your post brought me closer to soltution. Tommorw i have to try this. The only problem now i have that i am not getting firmware for my phone model SM-900R7, I am getting firmware for model number SM-900R6 which is very close to this not not exactly for SM-900R7. I have to search more to get it, i hope i will be able to find it.
Thanks again for your valuable post.
Click to expand...
Click to collapse
No problem, good luck with removing KNOX
TechMinerUK said:
No problem, good luck with removing KNOX
Click to expand...
Click to collapse
Hi,
Yesterday night you posted a link, that link was good but still my requirement is different.Yesterday i was not able to go through whole link you provided to me, today i was reading the whole article. its looks like they are trying to save warrany of phone even after flashing custom ROM. They are deleting bootloader contents of flashing ROM, even i will flash custom ROM with deleted bootloader contents, In phone bootloader will remain same with KNOX SECUREBOOT feature. My target is to flash with KNOX disabled bootloader so it will not stop booting with custom zImage.
TechMinerUK said:
No problem, good luck with removing KNOX
Click to expand...
Click to collapse
Actaully that link was removing KNOX from firmware which you are going to flash not from phone if you have already KNOX is there. That is for if your mobile is not having KNOX and you dont want KNOX when you are going to flash with recent updated firmware so you can delete KNOX contents from firmware and can flash.
arvind3023 said:
Actaully that link was removing KNOX from firmware which you are going to flash not from phone if you have already KNOX is there. That is for if your mobile is not having KNOX and you dont want KNOX when you are going to flash with recent updated firmware so you can delete KNOX contents from firmware and can flash.
Click to expand...
Click to collapse
Hmm, it appears it not possible due to it having a locked bootloader/KNOX not being removable
http://forum.xda-developers.com/verizon-galaxy-s5/help/g900r7-problem-t2877527
TechMinerUK said:
Hmm, it appears it not possible due to it having a locked bootloader/KNOX not being removable
http://forum.xda-developers.com/verizon-galaxy-s5/help/g900r7-problem-t2877527
Click to expand...
Click to collapse
Thats my problem is i am not getting concrete answer either some good link or something official from samsung to come to conclusion of NO, searching searching trying this and that with a hope that its possible.
arvind3023 said:
Thats my problem is i am not getting concrete answer either some good link or something official from samsung to come to conclusion of NO, searching searching trying this and that with a hope that its possible.
Click to expand...
Click to collapse
I would pressume their will be some method of doing it and if it's not released yet it will be soon...
I guess it's just best to bide time and wait untill a concrete method has been developed
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
NeoDJW said:
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
Click to expand...
Click to collapse
It's not possible since I bought it second hand.
Even if I had a warranty, in my country (Serbia) warranty for smartphones doesn't mean much, I think I could write PhD thesis easier than to make seller replace/fix smartphone with warranty
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Erik1805 said:
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Click to expand...
Click to collapse
Thanks but this will not fix my problem.
Have you tried this: http://pangu.in/frp.error.html
Bright.Light said:
Have you tried this: http://pangu.in/frp.error.html
Click to expand...
Click to collapse
No I didn't but the fact is it will not work.
There is currently no way to fix that. The only way would be to unlock FRP by some box, but it isn't released yet.
What I am asking here is true that Galaxy S7 could be hard bricked that easy? By steps I wrote in my first post.
My questions are partially answered in this article
But I still don't understand what's the problem with dm-variety if I flashed stock rom?
Is there are any other parts of the NAND that are not original/signed and that's why dm-verity fails?
If that's the case can they be backed up then reflashed with the Odin if I get into same problem with new phone?
Thanks
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
harshang2007 said:
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
Click to expand...
Click to collapse
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
mss1988 said:
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
Click to expand...
Click to collapse
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
harshang2007 said:
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
Click to expand...
Click to collapse
I don't have the phone anymore to confirm or to deny this. But the whole procedure in Kies and Smart Switch is the same. There are other people with the same problem too in this thread too, and they still didn't found the way to unbrick their devices.
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
I went through this procedure: http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 which gives a link to downloading the factory binary (of either version). It reinstated my IMEI which had been turned to a string of zeroes. I will say that when you reboot after flashing the factory binary it's pretty different looking so be prepared for that. I then went to Sammobile and downloaded the appropriate stock ROM for my s7 and flashed that with Odin. I flashed TWRP, formatted internal data when given the opportunity, flashed the no-verity-opt-encrypt.zip, and I was able to use my s7 again. At any rate, you might follow the guide at the link I gave you and see if it helps. As always, no guarantee is given or implied. It's just what I did.
Thanks man, but I can't flash the Factory binary, my FRP is unfortunately ON.
E pa brate nemoj se više onda igrati sa telefonom, nije to za svakoga,...
Mod Edit: Please post in English only:
Well, the brothers do not come then play with the phone, it's not for everyone
now phone detect usb ? i mean adb devices
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
wild guess....
Install dm-verity and force encryption disabler
Wipe Cache
install custom kernel
chandarakk said:
now phone detect usb ? i mean adb devices
Click to expand...
Click to collapse
There's no adb/fastboot access from Samsung recovery or Samsung download mode, as far as I know.
Just get your phone into downloadmode and then flash the stock firmware witch you can find on sammobile. I got also this problem, and then everything will be fine ?
did you try use Kies or Smart swticher to factory restore the phone ?
because as far as i know , even FRP is on , you can still flash stock firmware.
and , try local shop to find any place have z3x box or Octopus box .
I have a Samsung Galaxy Note 3 SM-N900V from Verizon and I have been trying to change it to the DarkLord ROM that is a Modded Mix between Note 7 & Edge ROM.
I at first had problems rooting the phone with Odin (it always failed) so I search and search and found a tool called ArabicTool which took care of it and finally I rooted my phone, after that I tried adding TWRP so I could change the ROM but every time I added the recovery tool I got the message saying that the “System software not authorized by Verizon Wireless has been found on your phone” and then had to do an emergency restoration using Kies3 and the cycle began again with other methods but always the same result.
I would like to know if anyone has a way to change the ROM on a SM-N900V from Verizon, I have seem some guides that claim the process works with the SM-N900V but every time I try to do them I get the message of software not authorized when I install the recovery app TWRP and then I have to do an emergency restore in Kies3.
Please help anyone it would be really appreciated.
anrabaro said:
I have a Samsung Galaxy Note 3 SM-N900V from Verizon and I have been trying to change it to the DarkLord ROM that is a Modded Mix between Note 7 & Edge ROM.
I at first had problems rooting the phone with Odin (it always failed) so I search and search and found a tool called ArabicTool which took care of it and finally I rooted my phone, after that I tried adding TWRP so I could change the ROM but every time I added the recovery tool I got the message saying that the “System software not authorized by Verizon Wireless has been found on your phone†and then had to do an emergency restoration using Kies3 and the cycle began again with other methods but always the same result.
I would like to know if anyone has a way to change the ROM on a SM-N900V from Verizon, I have seem some guides that claim the process works with the SM-N900V but every time I try to do them I get the message of software not authorized when I install the recovery app TWRP and then I have to do an emergency restore in Kies3.
Please help anyone it would be really appreciated.
Click to expand...
Click to collapse
Greetings and welcome to xda. I am not sure the rom you mentioned is compatible with your device and I think your bootloader may also be locked. This thread here
http://forum.xda-developers.com/showthread.php?t=2517610
should help you with a custom recovery and I found this rom which is a s7 port for your device
http://forum.xda-developers.com/ver...ent/rom-aryamod-port-s7edge-portv6-5-t3506144
Good Luck
Sawdoctor
This ROm
sawdoctor said:
Greetings and welcome to xda. I am not sure the rom you mentioned is compatible with your device and I think your bootloader may also be locked. This thread here
http://forum.xda-developers.com/showthread.php?t=2517610
should help you with a custom recovery and I found this rom which is a s7 port for your device
http://forum.xda-developers.com/ver...ent/rom-aryamod-port-s7edge-portv6-5-t3506144
Good Luck
Sawdoctor
Click to expand...
Click to collapse
This is teh ROM i was trying to use but the main problem I'm having is trying to install a recovery tool everytime I do the phone gets stock on the software not authorized screen.
How do I know if teh bootloader is locked and if it is is there a way i can unblocke it?
http://forum.xda-developers.com/galaxy-note-3/development/darklord-s7-edge-port-6-0-1-mm-t3382954
anrabaro said:
This is teh ROM i was trying to use but the main problem I'm having is trying to install a recovery tool everytime I do the phone gets stock on the software not authorized screen.
How do I know if teh bootloader is locked and if it is is there a way i can unblocke it?
http://forum.xda-developers.com/galaxy-note-3/development/darklord-s7-edge-port-6-0-1-mm-t3382954
Click to expand...
Click to collapse
That rom may not be compatible with your device, the verizon variant is different to the other note 3's. I'm pretty sure the verizon note 3 is locked bootloader but if you ask your questions here
http://forum.xda-developers.com/verizon-galaxy-note-3/help
the experts there will be able to confirm this for you
Good Luck
Sawdoctor
Finally found how to install the ROM
So I finally found the solution on how to change the ROM on my SM-900V Verizon Wireless Note 3.
>>>>1) First Step How to Root the phone:
Activate USB debugging, download ArabicTool.exe.
I follow this youtube Vid to do it:
https://www.youtube.com/watch?v=GtuOPhSlymg
>>>>2) Unblock boot loader:
I follow this link:
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
>>>>3) Install TWRP (Using Flashly):
Download Flashly from the Android Play Store then download a recovery img using Flashly I picked TWRP.
>>>>4) Install the ROM:
I follow this link:
http://forum.xda-developers.com/galaxy-note-3/development/darklord-s7-edge-port-6-0-1-mm-t3382954
and
https://www.youtube.com/watch?v=-i6DsGKTsJc
So happy
I found this phone (Samsung Galaxy A8 au SCV32) and the owner didn't try to contact me so I will try to unlock it. It is currently stuck with FRP (Verify Google account). I tried the RootJunky method with the OTG cable but the file explorer just won't launch so I was thinking of downgrading the Android version, not sure if that would help.
The problem is that I can only find the Android 5.1.1 stock rom for this model. I was wondering if it would be safe to flash a different Galaxy A8 model rom like SM-A810F, SM-A810Y or SM-A810S. I guess the hardware is exactly the same and if something goes wrong I could still go into recovery mode and flash the stock rom. What do you think?
Hi. Anyone. Please help me please.
I installed a custom recovery and rooted my friend's j7 Prime, and everything went good.
now, the next day, his phone will not boot because of "Custom binary blocked by FRP lock".
I can only imagine that he flip the Oem switch at the developer options, and now his phone won't boot.
I am searching for a week now for the solution to found out that the only solution is to reflash the stock ROM via ODIN.
but the problem is: I CANNOT FIND MY FIRMWARE.!!
I am searching the firmware for 2 days now, I really cant find the right
firmware for the phone. please help me please.
I am from the Philippines and I need the firmware for all networks since the phone is open line.
thanks in advance for the help.
me too...
Hi we have a same problem.
email me if you found a solution.... [email protected]
check updato.com
jamsubzero said:
Hi. Anyone. Please help me please.
I installed a custom recovery and rooted my friend's j7 Prime, and everything went good.
now, the next day, his phone will not boot because of "Custom binary blocked by FRP lock".
I can only imagine that he flip the Oem switch at the developer options, and now his phone won't boot.
I am searching for a week now for the solution to found out that the only solution is to reflash the stock ROM via ODIN.
but the problem is: I CANNOT FIND MY FIRMWARE.!!
I am searching the firmware for 2 days now, I really cant find the right
firmware for the phone. please help me please.
I am from the Philippines and I need the firmware for all networks since the phone is open line.
thanks in advance for the help.
Click to expand...
Click to collapse
Bro nakakuha ka ba ng stock rom?
help me guys.. my samsung galaxy j7 prime SM-G610Y baseband version(G610YZTU2ARJ3). I intalled so many firmware but even one are not much with my phone.. help me guys..
email me --- [email protected]
Hi,
Try this one combinefile.com<<index.php?a=downloads&b=folder&id=19962 I've tested it a couple of times 100% working I use Odin to flash it. My phone is Galaxy J7 Prime SM-G610Y Baseband: G610YZTU2ARJ3. I'm also from PH am sure it will work on you guys :fingers-crossed:
Note: Use https and replace << with / to go into that link or just search the baseband in google and look for the combinefile website.
AikaDroid said:
Hi,
Try this one combinefile.com<<index.php?a=downloads&b=folder&id=19962 I've tested it a couple of times 100% working I use Odin to flash it. My phone is Galaxy J7 Prime SM-G610Y Baseband: G610YZTU2ARJ3. I'm also from PH am sure it will work on you guys :fingers-crossed:
Note: Use https and replace << with / to go into that link or just search the baseband in google and look for the combinefile website.
Click to expand...
Click to collapse
Im looking for this rom. I accidentally deleted my system via twrp. I need to flash stock via oden. Can you please uodate the link? Thanks in advanced