Related
Hi All,
Have s6 SM-G920F international model. now my brother accidentally try wrong attempts in pin to unlock the phone. so phone got locked. and i give to guy who unlock the phone and after that i am not able to get official update . so have decided to install official stock firmware. details are below. when phone is return back to me have below version.
Old firmware :-
G920FXXU1AOCY 5.0.2 Lollipop, Initial release on 3/29/2015 for EE only.
New firmware which i try using ODIN :-
G920FXXU3QOJF Galaxy S6 SM-G920F 5.1.1 Stock Firmware -- This firmware is officially released on November 2015 for EE UK Galaxy S6 alone.Build date: October 12, 2015.
Got success in above firmware , PASS is result in ODIN.
But when phone reboot after this ,after erasing screen appear then it hang on logo screen. have waited around 20 mins but nothing happen. Have tried recovery mode also via wipe cache / factory reset , no change in result.
Have again try to install G920FXXU1AOCY but got sof rev fail in ODIN .
Have tried samsung switch for software update it's successful but when phone reboot it again stop there at logo screen.
In recovery mode -- G920FXXU3QOJF this show on top.
I don't whether phone was root or not as guy says he just unlock the phone. got this from UK .
Can anyone please help which firmware will now work on this case ? how to solve this issue.
Please help me as i mess up with my phone which work great before .
Tons of thanks to all.
Is there any firmware which work on all unlock or root phone for this model ? the above step from 5.0.2 have installed 5.1 is correct step ? i am working this phone from india,before doing this firmware update my sim card work properly. as phone was already unlock or rooted (not sure here whether it's rooted or not but sure as it's unlocked phone) as i can see EE apps in phone. please help me . it's hurt me on my decision to do this upgrade and create mess. :crying:
Can anyone pls help.. Thanks
dbarot87 said:
Can anyone pls help.. Thanks
Click to expand...
Click to collapse
have you solved this yet?
this helped me:
http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395
Hello,
this is the very first time here at XDA Developers Forum that I do not find clear information about rooting a smartphone. I am talking about this Nokia 3 updated with OREO 8.0. Only a lot of confusion reading your posts, sirs. Nobody that is telling if rooting this model is possibile or not. So... can anyone says if it is possibile and how to do that, in a clear and simple manner?
Thanks and regards!
jimgordon said:
Hello,
this is the very first time here at XDA Developers Forum that I do not find clear information about rooting a smartphone. I am talking about this Nokia 3 updated with OREO 8.0. Only a lot of confusion reading your posts, sirs. Nobody that is telling if rooting this model is possibile or not. So... can anyone says if it is possibile and how to do that, in a clear and simple manner?
Thanks and regards!
Click to expand...
Click to collapse
here you go
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
this thread should be on Q&A.
Hello,
thanks for your reply. I already read this thread.
So since I am on OREO, it seems I have firstly to downgrade to Nougat. Can someone please tell me how to do that, posting links to the official 7.0 rom, the software and a short guide? Somewhere I read you have to use OST, somewhere else SP Flash Tool...
Thanks in advance and regards
Cosimo
Hello again...
I am trying to downgrade my Nokia 3 8.0 to Nougat, in order to unlock the bootloader.
I have searched a lot for an official 7.0 rom... nothing official... I tryed to follow this guide:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Managed to install and get a working copy of OST. Connected and start flashing the rom NE1-147I-ind-0-00WW-B02.nb0 (the one I thought it was the earlier one, since nobody wrote "7, 8, or another number" in the file name). OST got stuck at "Reflash service bootloader..."
Can anyone please write a clear guide on how to proceed to root a Nokia 3 OREO that was never ever unlocked before (i mean with bootload never unlocked)? I am going crazy, really...
jimgordon said:
Hello again...
I am trying to downgrade my Nokia 3 8.0 to Nougat, in order to unlock the bootloader.
I have searched a lot for an official 7.0 rom... nothing official... I tryed to follow this guide:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Managed to install and get a working copy of OST. Connected and start flashing the rom NE1-147I-ind-0-00WW-B02.nb0 (the one I thought it was the earlier one, since nobody wrote "7, 8, or another number" in the file name). OST got stuck at "Reflash service bootloader..."
Can anyone please write a clear guide on how to proceed to root a Nokia 3 OREO that was never ever unlocked before (i mean with bootload never unlocked)? I am going crazy, really...
Click to expand...
Click to collapse
flash UAE version of nb0 if IND doesn't flash, that's Android 7.0 May 2017 Security Patch, unlock and lock bootloader there and apply OTA updates from notification up to latest update. Then follow guide.
SkaboXD said:
flash UAE version of nb0 if IND doesn't flash, that's Android 7.0 May 2017 Security Patch, unlock and lock bootloader there and apply OTA updates from notification up to latest update. Then follow guide.
Click to expand...
Click to collapse
Hi, thanks again for your precious support. Can you give me a link to download the UAE version of the firmware? At this address: https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg I can only find the IND one.
Regards
jimgordon said:
Hi, thanks again for your precious support. Can you give me a link to download the UAE version of the firmware? At this address: https://mega.nz/#F!1ENgnThL!FyL9uYCC3Dq-16elThKAPg I can only find the IND one.
Regards
Click to expand...
Click to collapse
oh they deleted it it was before. I have it on PC, but PC can't turn on.
I have found the file elsewhere... NE1-147C-UAE-0-00WW-B01.nb0
I have tried to upload using OST, and got the same result: stuck at "Reflash service bootloader..."
Is there someone that can help me?
jimgordon said:
I have found the file elsewhere... NE1-147C-UAE-0-00WW-B01.nb0
I have tried to upload using OST, and got the same result: stuck at "Reflash service bootloader..."
Is there someone that can help me?
Click to expand...
Click to collapse
which ost la version you have?
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
jimgordon said:
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
Click to expand...
Click to collapse
you need to unlock bootloader first, and you can PM code i will send you key, use only OTA through notification, don't use OST LA for this guide.
Can you tell the way you downgraded ur Nokia 3
jimgordon said:
I finally managed to downgrade to Nougat 7.0.
Now, in order to get root, do I have to unlock bootloader first? Can I obtain the code only via a request to the_laser (that didn't answer me) or can I use an online tool ?
Click to expand...
Click to collapse
Hi,
can u tell me the method in which you downgraded Nokia 3 from 8.0 to 7, also were u able to unlock the boot loader and root the device. Waiting for your reply as one of my friend also wanna do the same.
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
solamente said:
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
Click to expand...
Click to collapse
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
DeadRatGames said:
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
Click to expand...
Click to collapse
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
solamente said:
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
Click to expand...
Click to collapse
Do I really need to wait 168 hours lol?
DeadRatGames said:
Do I really need to wait 168 hours lol?
Click to expand...
Click to collapse
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
solamente said:
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
Click to expand...
Click to collapse
How do I downgrade though?
DeadRatGames said:
How do I downgrade though?
Click to expand...
Click to collapse
At this time its impossible to downgrade from a binary 3 towards 2 or from 2 to 1.
You can only upgrade, Samsung has blocked the downgrading from a higher to a lower binary, therefore it is useless to try it with Odin, it won't succeed.
Maybe someone else knows a way around to downgrade, but I don't.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
BlackMesa123 said:
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
Click to expand...
Click to collapse
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
DeadRatGames said:
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
Click to expand...
Click to collapse
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
BlackMesa123 said:
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
Click to expand...
Click to collapse
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Reformat system.
DeadRatGames said:
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Click to expand...
Click to collapse
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
solamente said:
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
Click to expand...
Click to collapse
Ok. Thanks
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
same questions
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
amazing. youre the man. cheers.
samalderon said:
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
Click to expand...
Click to collapse
omg youre the best. thanks so much.
So I just got my new ATT samsung J7 2018 and after searching i have not found a root or bootloader unlock method for the devices. Is there any work being on this device ? Could some one maybe point me in the right direction to get root on this device ?
ramious2012 said:
So I just got my new ATT samsung J7 2018 and after searching i have not found a root or bootloader unlock method for the devices. Is there any work being on this device ? Could some one maybe point me in the right direction to get root on this device ?
Click to expand...
Click to collapse
I have been searching for this for 1week now...and its all cause in " Dev Option " the ( OEM is Hidden ). Atleast im stuck in this part with this phone cause the rest i know with Odin.
I just got this phone a few days ago and I'm already looking for a root as well. I found one post on a root for this phone, but I kinda doubt it's legit. If you search 'Samsung galaxy SM-J737A root' on google, it should be the first search results. I'm keeping an eye on these forums for now.
ramious2012 said:
So I just got my new ATT samsung J7 2018 and after searching i have not found a root or bootloader unlock method for the devices. Is there any work being on this device ? Could some one maybe point me in the right direction to get root on this device ?
Click to expand...
Click to collapse
I have serach it just like that before and try afew of this Tricks but still wont show me the OEM option in Dev. That one with setting the date to 10 to 7 days before wont work cause i dont have that " Manual Software Update " option. I aint working atm so im like full searching away.:laugh:
anybody had any luck with this?
bigTINY779 said:
anybody had any luck with this?
Click to expand...
Click to collapse
Still of this moment No luck. Saw today with a so called Box Z3x something that works good ( the hack version that dosent use the actuall box ) but this Devi e Model Version wont showup.....
If you see KG STATUS: checking or if it's not there after the wait time then you shouldn't need to use the OEM unlock option
Original recovery post for the J7 2017
https://forum.xda-developers.com/ga...fm-g-gm-x-samsung-galaxy-j7-pro-t3835629/amp/
https://mega.nz/file/fFFSxALD#1nOVnhF0k6vojg19bK60YCSugHH4LPULdmhYx-wHhP0 here is the J7 2017 recovery that should work since the 2018 model is the exact same but minor screen differences (I do not take credit for this recovery I'm just supplying the link)
It should flash without issues as the bootloader should already be unlocked
TheExploitedOne said:
If you see KG STATUS: checking or if it's not there after the wait time then you shouldn't need to use the OEM unlock option
Original recovery post for the J7 2017
https://forum.xda-developers.com/ga...fm-g-gm-x-samsung-galaxy-j7-pro-t3835629/amp/
https://mega.nz/file/fFFSxALD#1nOVnhF0k6vojg19bK60YCSugHH4LPULdmhYx-wHhP0 here is the J7 2017 recovery that should work since the 2018 model is the exact same but minor screen differences (I do not take credit for this recovery I'm just supplying the link)
It should flash without issues as the bootloader should already be unlocked
Click to expand...
Click to collapse
The file in that link doesn't work anymore. Do you have another one by any chance?
I have tried everything, I have flashed 4 different firmware versions in odin. Did all the updates, followed the guides and all that yet the OEM unlock option does not appear and kg status is still prenormal. You are probably wondering how I got here. I flashed a GSI rom that I did not like, I flashed back my firmware INCLUDING the bootloader. Flashing the bootloader reset it's state to locked. That in it self was no problem ill just wait 7 days and it will be unlockable again. But no KG state is still prenormal and oem is not unlockable. I just reflashed my firmware and I am going to start waiting *again* hoping that a miracle will happen. How hopeless is the situation with my phone, is it worth hoping it can fix this or will i have to just use the preloaded non rooted firmware? I had a hope to port lineage 18.1 to this phone but I am losing any hope of it happening.
Hi ...... I have stucked in the same situation did you find any solution ?????
Bazzazi said:
Hi ...... I have stucked in the same situation did you find any solution ?????
Click to expand...
Click to collapse
No there is absolutely no solution, trust me. EDL method does not work anymore due to the security patch from last year having an new system. Unfortunately there is no working leaked firehose file since then. Don't even try any of the methods on youtube, rewritting the storage with the file from the factory was the only method.
thanks for your reply bro !!!!
I think 7 days up time and internet connect should fix the problem
i'm gonna try it.....
Bazzazi said:
thanks for your reply bro !!!!
I think 7 days up time and internet connect should fix the problem
i'm gonna try it.....
Click to expand...
Click to collapse
Did you get it fixed?
I think we already have a solution here on XDA portal
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
hi, can you tell me the exact model and carrier? (csc)