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've looked for quite a while on anything that could help me root the phone, and have had no success with anything. I'm worrying at this point that the bootloader is just locked and have to ask, is there anything else I can do to root this phone? Willing to try pretty much anything, even at risk of bricking it.
Lavitz324 said:
I've looked for quite a while on anything that could help me root the phone, and have had no success with anything. I'm worrying at this point that the bootloader is just locked and have to ask, is there anything else I can do to root this phone? Willing to try pretty much anything, even at risk of bricking it.
Click to expand...
Click to collapse
I'm interested in this too but in all likelihood nobody with the knowledge is even working on it because this is a niche phone.
Locked bootloader..
Well i have this fone now...i bought it because it was a good deal so it seemed..Less than 100$ for fone and service activation plan...I have rooted just about every Samsung i have ever owned...So heres what i have come up with..There is no OEM option in Developer options...On any other samsung fone i always go right into developer options and disable OEM by turning it off...Then i either have used Kingroot apk or Kingoroot apk in the past and they have worked...sometimes u have to find the perfect version to match your android software specifically...Now i have always had huge success with Odin and flashing TWRP via Laptop or Computer via USB connection, but thats something each individual should personally take the time and educate theirselves on just in case... Sorry to say that the Samsung J3 Orbit with Total Wireless and Oreo 8.0 needs a serious look at...
Lavitz324 said:
I've looked for quite a while on anything that could help me root the phone, and have had no success with anything. I'm worrying at this point that the bootloader is just locked and have to ask, is there anything else I can do to root this phone? Willing to try pretty much anything, even at risk of bricking it.
Click to expand...
Click to collapse
Your phone is a 2018 model of the j3. When xda finally makes a J3 (2018) thread i will request for this thread to be moved. Any root methods shown in J3 (2017) are likely not to work anymore since samsung patched the methods used. The only way to root phones now is by buying the U variants of samsung's phones which are only available from samsung's website under unlocked phones. Unlocked phones from samsung have an unlocked bootloader by default.
thepcwiz101 said:
Your phone is a 2018 model of the j3. When xda finally makes a J3 (2018) thread i will request for this thread to be moved. Any root methods shown in J3 (2017) are likely not to work anymore since samsung patched the methods used. The only way to root phones now is by buying the U variants of samsung's phones which are only available from samsung's website under unlocked phones. Unlocked phones from samsung have an unlocked bootloader by default.
Click to expand...
Click to collapse
incorrect statement.
My s9+ is a U varient with no OEM unlock option and did not come from samsung. And my s9+ is still not rootable.
OuijaElite said:
incorrect statement.
My s9+ is a U varient with no OEM unlock option and did not come from samsung. And my s9+ is still not rootable.
Click to expand...
Click to collapse
strange. what is the model number.
thepcwiz101 said:
Your phone is a 2018 model of the j3. When xda finally makes a J3 (2018) thread i will request for this thread to be moved. Any root methods shown in J3 (2017) are likely not to work anymore since samsung patched the methods used. The only way to root phones now is by buying the U variants of samsung's phones which are only available from samsung's website under unlocked phones. Unlocked phones from samsung have an unlocked bootloader by default.
Click to expand...
Click to collapse
U models are normally U.S. models which are locked tight. I run a s8 as my everyday driver which is rooted. The s9 s10 and most other us snapdragon and in this case exynos all are locked tight. And they cannot be rooted as of right now. The sampwn and other samfail do not work anymore. The U model you are referring to is the U.S. sim unlocked model not bootloader. With the S series F is the European bootloader unlocked model I don't know the European letter for J series.
Until some one finds a way to push a rooted system img on stock permissive combination kernel root will not come just like s9 and s10 us models
If these where us snapdragon we could push a rooted system combination file with safestrap just like we do on the newer bootloader on s8 using EDL and Qualcomm 9008
Just had an idea, another thread on this forum a guy says he made a modified version of Odin that can flash mix matched models. So just flash a model version of the j3 orbit that can be rooted or at least oem unlock capable to be able to flash twrp and then be able to root through twrp.
If flashing a j3 with a model number different than sm-367vl would brick it, just extract the .img partitions like boot.img or whatever the partition may be with ubuntu to restore one by one until you find which one makes the phone boot.
I don't know much about phones when it comes to this depth of modification. But I had a lg zone 3 that used this method to turn an unrootable model number version into a different model number that was rootable. Before I flashed the .img partitions of the stock software the screen had lines all over it, so using screen mirroring I was able to root the different model number software then download partition backup and restore app them restore the partitions that were for the original model number.
So basically it took both model numbers and combined some partitions of each to make it work properly.
In my head I can totally see this working. Just depends on how close to the same hardware each model number of the galaxy j3 has i guess.
I wish I would have noticed/seen this a bit sooner.. any progress or luck? I have the j337u ...
I know chimera tool is able to remove Knox kglock oemlock rmm mdm , of which mine shows kglock on, oemlock: on, frplock off. Trying to flash anything gives the error insufficient payment somethin. So there's got to be a way around it. ALSO I found interesting, the FCC id has J337t instead of U ...wonder why that is ...
(Anyone know where I can get stock j260AZ/AIO -notpaid- (cricket) firmware,I've literally checked every where )
We need someone to take that new 0day exploit rootPoC mod it however and release it
Found this [Have not tried it yet]
Came across an article on androidbiits. Not sure it's actually viable. Unfortunately I cant post the direct link until I have enough posts under my belt.
I'm willing to pitch in if someone can point me in the right direction.
Yhuda
How now????You are find How to root this phone????Please add Develop for find How to root Samsung J3 Orbit?!??
For my kglock on, oem lock on j337u, which also has some new mdm / rmm on it from consumer , I used chimera tool to set KGLock to Complete.
This also switched the oem lock to off and show the toggle in Dev ops....
1st flash of magical patched img worked. But after.connectinf.the Wi-Fi , knox enrollment and instantly a sec. Msg popped up and locked up the entire device. No usb connection or.anything.
factory reset
Same Issue,.then locks up
So for try 3, flash the patched boot, let boot.
AS SOON AS ITboots to android, hit the Airplane Mode toggle to activate it to stop Knox Enrollmnt
So er.gont get
was able to unlock the boatloader with comb file that was compatible, flashed stock track phone, updated to 9 pie...
used a gig pressed power button ???
9 pie trac phone j3 orbit
patched AP file with majisk, ran with Odin : says noway fail, I was able to reflash with stock firmware, so it doesn't work on mine...
any other luck
thanks
I would really like to know if anyone has succeeded either rooting or SIM unlocking or flashing with a different firmware on this model.
I was able to access the OEM unlock in my J3 Orbit (SM-S367VL) via factory binary after flashing combination firmware.
That is as far as Ive gotten. I am assuming you would want to run ADB download mode to flash anything as factory binary seems to have some security measures against full bootloader unlock built in
Hi at all,
so I bought this samsung phone (Samsung Galaxy S7 SM-G930F) for my mom online, but there is an android account lock on it. Previous owner not reachable and so now I'm stuck with this phone.
I tried a lot of "FRP/Google Lock Bypass" videos, but it seems this phone has the newest android version so non of them work.
Types of bypasses I've tried:
- notification bypass
- SIM-Card insert/eject and power on/off
- specialized FRP software
none worked.
Now my next move would be to try to flash a custom ROM in order to flash an older android version, which would hopefully make one of the above mentioned FRP methods work.
BUT for some reason I cant't enter download mode, which is as I understood essential to flash anything on the phone.
The only mode I can enter is recovery mode. There I already tried factory reset, which did work, but did not solve my Android Lock /FRP problem.
Now ...... any clue what I can do to finaly make a use of my money that I spend on this phone?
Thansk in advance for every bit of help
schurika said:
Hi at all,
so I bought this samsung phone for my mom online, but there is an android account lock on it. Previous owner not reachable and so now I'm stuck with this phone.
Which phone do you have? If it is a Snapdragon version with updated software, you can't flash custom ROMs due to the locked bootloader.
Click to expand...
Click to collapse
Drunkpilot said:
schurika said:
Hi at all,
so I bought this samsung phone for my mom online, but there is an android account lock on it. Previous owner not reachable and so now I'm stuck with this phone.
Which phone do you have? If it is a Snapdragon version with updated software, you can't flash custom ROMs due to the locked bootloader.
Click to expand...
Click to collapse
Hi sorry forgot to add the info ==> Samsung Galaxy S7 SM-G930F
Click to expand...
Click to collapse
Hey i really need help with a galaxy s7 sm-g930f i got from a friend of my mother which is FRP locked and cant boot into recovery and bootloops on the Galaxy s7 screen with Custom binary locked by FRP standing in the top left corner since they somehow tampered with the phone. i already tried to get TWRP running (which wont work since the frp lock blocks it) and tried to flash the stock roms with the latest stock roms and some older versions since i cant really tell if it was updated to the latest android available for the s7 or not. even after sucessfully flashing through oding it just wont work i cant access the recovery menu or atleast it wont show up at all and it binary still is locked by frp
and before wasting money on sending it to samsung directly i now try to get help through this forum would really appriciate your answers