Related
Hello friends I am on the latest Russian 4.3 firmware and am flashing the PIT and the old bootloader and then a stock 4.2.2 indian Firmware to check if the warranty bit can be reinstated !!!!!!!! Because here in India the service centers dont know or dont bother to check the hidden counter.......
I know I am taking a risk but opening this thread so that I can post my observations and maybe we can work something out.....fingers crossed!!!!!
UPDATE 1 : Was Unable to flash the MG1 bootloader getting failed on odin and unsupported !!!!!
UPDATE 2 : Flashed UBUBMH1 4.2.2 successfully no IMEI loss all working fine so yes we can downgrade to 4.2.2
The bootloader though remains unchanged and shows device status as custom!!!!!
UPDATE 3 : Flashed the leaked 4.3 and device status says official binary also official only warranty bit says 1
UPDATE 4 : Device is able to check for OTA updates and not given an error saying your device has been modified
**********************************************************************************
STEPS TO REVERT I9500 TO 4.2.2 WITH OFFICIAL STATUS
**********************************************************************************
1) Download South African FW 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html
2) Go to recovery wipe data factory reset and wipe cache and then flash the firmware that you downloaded above
NOTE : If you are on the russian 4.3 and having issues flashing this FW then first flash the leaked 4.3 from here
http://forum.xda-developers.com/showthread.php?t=2488155
3) After flashing leaked 4.3 go to settings and check device status it should say official
4)now go to download mode and flash the 4.2.2 rom you downloaded
5) NOTE : IF YOU ARE STILL HAVING TROUBLE GOING BACK TO 4.2.2 YOU CAN DOWNLOAD THE
ATTACHED PIT FILE AND FLASH IT ALONG WITH THE 4.2.2 ROM
IN ODIN SELECT THE PIT FILE IN PIT SECTION AND SELECT THE FW IN PDA SECTION
AS A LAST RESORT IF NOTHING WORKS THEN FOLLOW THE STEPS FROM STEP 1 AGAIN USING ODIN
1.85 attached below!!!!!!
PLEASE EXTRACT THE ODIN AND PIT FILES BEFORE USING.
Trying other things now!!!!!!!
I will be posting detailed steps with links soon!!!!!!!
Hey,
When I was in 4.2.2, root and kernels and Cwm were already flashed so my binary and system were custom. But when I flashed 4.3 leak all become official and warranty bit: 0, I was happy that I kept my warranty.
But now, my warranty bit is 1 because I flashed cf root. And downgrading to 4.2.2 and flashing again 4.3 didn't change anything. I really want to know how to remove that knox bootloader.
Envoyé de mon GT-I9500 en utilisant Tapatalk
speed s said:
Hey,
When I was in 4.2.2, root and kernels and Cwm were already flashed so my binary and system were custom. But when I flashed 4.3 leak all become official and warranty bit: 0, I was happy that I kept my warranty.
But now, my warranty bit is 1 because I flashed cf root. And downgrading to 4.2.2 and flashing again 4.3 didn't change anything. I really want to know how to remove that knox bootloader.
Envoyé de mon GT-I9500 en utilisant Tapatalk
Click to expand...
Click to collapse
Well as the title states right now there is no way to do that its been three hrs i have tried all sorts of crazy things to go back to the old bootloader but it just refuses to flash so we will have to wait.....I created this thread so that at least we can have the binary and status official because most of the places that will be ok like in india if i go to the svc center and it says official all will be ok!!!!
hey @hypergamer1231,
what is the procedure to revert back to 4.2.2, am currently CF-Rooted on 4.3?
can you please tell me what all things are required ?(will be thankful if you provide the links)
and after that again upgrading to 4.3 will i be able to use Knox container app???
i don't have any problem with bit 1, just want to use container app !
Thanks in advance
nish983 said:
hey @hypergamer1231,
what is the procedure to revert back to 4.2.2, am currently CF-Rooted on 4.3?
can you please tell me what all things are required ?(will be thankful if you provide the links)
and after that again upgrading to 4.3 will i be able to use Knox container app???
i don't have any problem with bit 1, just want to use container app !
Thanks in advance
Click to expand...
Click to collapse
Sure mate OP updated with detailed steps let me know if it works and also if you dont root after gaining official status knox should work as well!!!!!!!
hypergamer1231 said:
Hello friends I am on the latest Russian 4.3 firmware and am flashing the PIT and the old bootloader and then a stock 4.2.2 indian Firmware to check if the warranty bit can be reinstated !!!!!!!! Because here in India the service centers dont know or dont bother to check the hidden counter.......
I know I am taking a risk but opening this thread so that I can post my observations and maybe we can work something out.....fingers crossed!!!!!
UPDATE 1 : Was Unable to flash the MG1 bootloader getting failed on odin and unsupported !!!!!
UPDATE 2 : Flashed UBUBMH1 4.2.2 successfully no IMEI loss all working fine so yes we can downgrade to 4.2.2
The bootloader though remains unchanged and shows device status as custom!!!!!
UPDATE 3 : Flashed the leaked 4.3 and device status says official binary also official only warranty bit says 1
UPDATE 4 : Device is able to check for OTA updates and not given an error saying your device has been modified
**********************************************************************************
STEPS TO REVERT I9500 TO 4.2.2 WITH OFFICIAL STATUS
**********************************************************************************
1) Download South African FW 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html
2) Go to recovery wipe data factory reset and wipe cache and then flash the firmware that you downloaded above
NOTE : If you are on the russian 4.3 and having issues flashing this FW then first flash the leaked 4.3 from here
http://forum.xda-developers.com/showthread.php?t=2488155
3) After flashing leaked 4.3 go to settings and check device status it should say official
4)now go to download mode and flash the 4.2.2 rom you downloaded
5) NOTE : IF YOU ARE STILL HAVING TROUBLE GOING BACK TO 4.2.2 YOU CAN DOWNLOAD THE
ATTACHED PIT FILE AND FLASH IT ALONG WITH THE 4.2.2 ROM
IN ODIN SELECT THE PIT FILE IN PIT SECTION AND SELECT THE FW IN PDA SECTION
AS A LAST RESORT IF NOTHING WORKS THEN FOLLOW THE STEPS FROM STEP 1 AGAIN USING ODIN
1.85 attached below!!!!!!
PLEASE EXTRACT THE ODIN AND PIT FILES BEFORE USING.
Trying other things now!!!!!!!
I will be posting detailed steps with links soon!!!!!!!
Click to expand...
Click to collapse
Thks 4 this tutorial, Perfect in My S4 TTT Region.
Congrats Bro
Just got the official 4.3 OTA update (INS). Not going to update coz of warranty bit. It should be 0 when I update, but as soon as I root it would become 1. Will be waiting for AOSP or MIUI for i9500, say a month or so. Then will use it and update to 4.3 next yr (or maybe 4.4 then?) When warranty anyway would expire.
Edit - this is similar to Knox on i9505, hence even downgrading your official software doesn't remove the boot loader, and in fact triggers it.
yashvchauhan said:
Just got the official 4.3 OTA update (INS). Not going to update coz of warranty bit. It should be 0 when I update, but as soon as I root it would become 1. Will be waiting for AOSP or MIUI for i9500, say a month or so. Then will use it and update to 4.3 next yr (or maybe 4.4 then?) When warranty anyway would expire.
Edit - this is similar to Knox on i9505, hence even downgrading your official software doesn't remove the boot loader, and in fact triggers it.
Click to expand...
Click to collapse
well thanks for the headsup abt the indian fw dloading it now!!! Also in india most of the svc centers wont trouble you because they hardly even check!!!!
sorry wrong thread post edited
hypergamer1231 said:
well thanks for the headsup abt the indian fw dloading it now!!! Also in india most of the svc centers wont trouble you because they hardly even check!!!!
Click to expand...
Click to collapse
in india we dont have locked bootloader. is it is safe to flash the 4.3 without bootloder provided in pre rooted thread.
thanks
mateen5997 said:
in we dont have locked bootloader. is it is safe to flash the 4.3 without bootloder provided in pre rooted thread.
thanks
Click to expand...
Click to collapse
i am not sure but thats a very good idea i would have tried that but i am already on the new bootloader if you can try that would be great make sure you have a nandroid backup and efs backup!!!!!! Do it at your own risk at the most u will have basic issues try and revert if poss
thank you,it works like a charme even if a had the russian 4.3, no need to go back to the indian version ,just used odin 1.85 with the.PIT and the south african 4.2.2
My experience:
My GT-I9505 was a Hongkong version with its stock firmware version I9505ZHUAME3, then OTA to ZHUDMI1.
After flashed the CWM recovery, the KNOX warranty set to 0x1. As you know, ZHUDMI1 cannot be fully rooted now.
Then I tried to flash the phone by ODIN with I9505ZHUBMF4 (includes PIT, PHONE, MODEM, CSC). The phone showed "OFFICIAL" and can OTA again, but I disabled auto upgrade.
And rooted the phone with CF-Auto-Root-jflte-jfltexx-gti9505. Now its status is "CUSTOM". Anyway, maybe I lost the warranty, but I can use this phone with fully rooted now.
I have nothing useful to add except that I find it funny that my country's firmware is allowing for downgrades :lol:. Congrats on finding the exploit BTW .
Anakha56 said:
I have nothing useful to add except that I find it funny that my country's firmware is allowing for downgrades :lol:. Congrats on finding the exploit BTW .
Click to expand...
Click to collapse
What about the warranty bit
Sent from my GT-I9500 using Tapatalk
hypergamer1231 said:
What about the warranty bit
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I learnt from the S2 days never, ever flash the latest leaks until a work around has been found. So yeah I have not gone the 4.3 route just yet but its nice to know that the firmware I already have could downgrade me should the need arise .
My experience:
So I have a I9500, and its on the russian 4.3, and I root it, it says both binary and status official except the Warranty Bit is 1, and Knox won't work on my phone, It goes " Your device is not authorised to enter knox mode". It shows the same thing after I unroot it ( Flash the 4.3 rom again). Just wonder is there any way that I can use Knox again??
Frigedaeg said:
So I have a I9500, and its on the russian 4.3, and I root it, it says both binary and status official except the Warranty Bit is 1, and Knox won't work on my phone, It goes " Your device is not authorised to enter knox mode". It shows the same thing after I unroot it ( Flash the 4.3 rom again). Just wonder is there any way that I can use Knox again??
Click to expand...
Click to collapse
Install the stock ROM via odin. It's solve the problem, try another ROM from another country.
Sent from my GT-I9500 using Tapatalk
Braulio00 said:
Install the stock ROM via odin. It's solve the problem, try another ROM from another country.
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Well, I tried to install the 4.3 Russian Stock rom again, it still wont work, still says Your device is not authorised to enter knox mode
Frigedaeg said:
Well, I tried to install the 4.3 Russian Stock rom again, it still wont work, still says Your device is not authorised to enter knox mode
Click to expand...
Click to collapse
Same thing happened to me knox won't ever work till warranty bit is reset or motherboard is replaced
Sent from my GT-I9500 using Tapatalk
Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
See PIT files flashing .
http://forum.xda-developers.com/showthread.php?t=2363703
Hi JJEgan,
Forgot to include that in my original post.
I've tried a few PIT files with no success. It fails at re-partitioning with Odin, and fails to transfer the pit with Heimdall.
Cheers
artois7 said:
Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
Click to expand...
Click to collapse
I've been facing the same thing these days. I was able to install a STOCK ROM here that worked. Well, it's a 4.0.4 android version and it's not recognizing my SIM card, hahaha but it worked until I figure out how to get back to my Gnabo rom OR any other one that can work properly and be rooted after. I can't tell that the same rom i used will work for you cause of the region, but If you would like to try, I can post here and you can flash it and see what happens. Although there is PIT files for 4.0.4 that might me suitable for the rom I've used. =D
vitortakeda said:
I've been facing the same thing these days. I was able to install a STOCK ROM here that worked. Well, it's a 4.0.4 android version and it's not recognizing my SIM card, hahaha but it worked until I figure out how to get back to my Gnabo rom OR any other one that can work properly and be rooted after. I can't tell that the same rom i used will work for you cause of the region, but If you would like to try, I can post here and you can flash it and see what happens. Although there is PIT files for 4.0.4 that might me suitable for the rom I've used. =D
Click to expand...
Click to collapse
What were your symptoms? worth a shot. Thanks.
I have a problem on /efs stuff, well so far I wasn't able to solve it, but as I said, the only rom that was able to be installed was the 4.0.4.
That is the rom i've used.
http://eusouandroid.com/tutorial-rom-original-galaxy-note-10-1-gt-n8000-android-4-0-4/
artois7 said:
Hi all,
I was asked to look at a Galaxy Note 10.1 GT-N8000 by a colleague. It had been upgraded to 4.4.2, all was fine for a few days until it crashed. It's now in a bootloop spinning on the Samsung screen.
I can access Download mode, but no recovery.
Download screen says:
ODIN MODE
Product Name: GT-N8000
Current Binary: Samsung Official
System Status: Official
RP SWREV: A2
I've tried multiple versions of Odin, multiple official firmwares and multiple recoverys (custom/stock). Generally I get a NAND write Start.. FAILED message for most things. One bootloader file gave me "invalid magic string", and by manually packing files to .tar.md5 format, I can get a blue download bar appear on the tablet but nothing ever happens.
Heimdall is able to read the pit file from the device, but not flash anything (unable to confirm end of file transfer)
This seems to either be failed eMMC, or the bootloader is locked and I just haven't hit the correct software yet. I've been on this for days and don't seem to be getting anywhere.. Where do I go from here? And am I correct in thinking that I cannot access ADB from download mode; the device would need to boot to enable USB debugging?
Thanks in advance.
Click to expand...
Click to collapse
I found the solutions from another forum.. It's must repair with Z3X box flasher..
forum*gsmhosting.com/vbb/f672/n8000-logo-only-done-via-z3x-jtag-direct-emmc-step-step-inside-1959278/
Can anyone in the UK do this for me? Happy to pay obviously!
derekcfoley2 said:
Can anyone in the UK do this for me? Happy to pay obviously!
Click to expand...
Click to collapse
Local mobile repair shop that carries the tool .
Sent from my SM-N930F using XDA-Developers mobile app
My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Try to connect with smart switch.
On windows pc or laptop
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
It will flash stock firmware and solve all binary problem
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Intall smart connect or smart switch in pc
Sent from my [device_name] using XDA-Developers Legacy app
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Flash latest stock firmware for your region and enable OEM unlock in developer settings to avoid FRP in future. Also try to remember your google account password :silly:
Solved. I flash the latest firmware with an old version of odin
frp lock
marcoar said:
Solved. I flash the latest firmware with an old version of odin
Click to expand...
Click to collapse
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
kira31390 said:
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
Click to expand...
Click to collapse
Odin 3.12.5
Firmware: fxxu2drb6
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Matty1993 said:
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Click to expand...
Click to collapse
after the combination file flash, the phone normally starts with the combination firmware
marcoar said:
after the combination file flash, the phone normally starts with the combination firmware
Click to expand...
Click to collapse
Thanks so much for the reply i appreciate it i might try my combination file with the G930FXXU2DRB6 firmware you used as i need to test my hardware and fix imei but cant get the factory binary to boot on G930FXXU2DRBE firmware my thinking that it wouldnt boot was as its FA60 is android 6.0 MM where as my U2DRBE firmware is FA70 7.0 nougat is your device nougat or marshmallow ? Just trying to work out whats going wrong where for it to not boot on my device as ive lost my imei number flashing a custom rom and dont have access to my TWRP back up for another 3 weeks
Thanks
Hello. I have a similar problem. I have the latest firmware on it: G930FXXS2DRDI There are no ways to lift the Google lock. I have tried everything possible: Bluetooth does not work, Talkback, Realterm, etc. Please for help
My Android Version is: 7.0 (Nougat)
Frp g930fxxu2ara1
Hello my friend, i have this problem too. Have you a fix? this security patch for FRP is incredible....
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
ATRAC3, do you have the combination files and firmware for the SAMSUNG S7 SM-G930FD please and thank you for your wonderful tutorial here.
my odin(tried on v3.12.5/v3.12.7/v3.13.1 ) keep failing while flashing HOME_CSC but will success with CSC, and still required to login google account, what is the issue here ? (are we supposed to insert the pit file by ATRAC3 ? )
flashing at the lastest FW G930FXXS2DRCE
phone version:SM-G930F
ATRAC3 said:
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
Click to expand...
Click to collapse
Hi mate ive used the G930FXXU2DRBE XSA Firmware and also G930FXXU2DRB6 firmware with the G930FXXU2ARA2 combination rom however it will not boot past the samsung logo the nad passes and is provisioned in top left corner and when plugged into the computer comes online with ADB bypass flasher but it just sits there even if i do a cache wipe and factory reset it comes up with a tango console error or something like that when reset then reboots back to samsung logo and when re installing firmware HOME-CSC will fail every time the only thing ive been able to put it down to is that (1) the firmware is FA_70 which is nougat OS and the combination rom is FA_60 MM or (2) my knox warranty bit is tripped and will not allow a samsung factory binary to be run on it, may i ask what would be the difference with the firmware you have listed to the firmware im already using with the combination rom ? Need to sort my imei number out with the factory nad asap dont have access to my TWRP backup for another week and a half, if it helps my device is not FRP locked and is oem unlocked.
Thanks
Matthew
P.S to all those whom have a bit 2 bootloader on S7 all the loopholes have been patched the only way is to use the combination files ive been through absolutely everything and tried everything this new bootloader update is impenetrable i can google unlock samsung S8 and S9 no dramas and with S9 the OEM lock option dissapears for a week if tampered with but still 15 minutes and its done this **** but got me goin loco holmes !!!!! Maybe they figured this out also as there is only bit 1 bootloaders for both the S8 and the S9 however with S8 i found a stock firmware that allows another way to unlock the device without the need to flash any combination rom.
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
LEVY P said:
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
Click to expand...
Click to collapse
If it gets stuck on the console error and wont reboot to download mode then hold the power button volume down button and power button for 40 seconds and it will re boot to download mode for stock firmware re installation in short basically no theres way to remove the FRP unless you can get the combination rom to boot which from what ive seen some will boot the binary but then it also depends if HOME_CSC will flash to keep usb debugging enabled to use adb bypass program im now using the new G930FXXU2ERE2 8.0 OREO so I've given up on the binary 2 nougat FRP unlocking for now might be best to wait a while for someone to receive a factory binary on the nougat or oreo when sent off and returned so it can be dumped and built into a flashable rom until then not much can be done and i may have to wait another week and a half for my EFS backup :'(
We will be waiting from u for the new combination file when out bro, our hope are hinged on u!
No one is coming up with any method about the bootloader binary 2 for the Samsung S7 G930FD...?
Sent from my SM-G930F using Xposed Modules
FRP can be done so easy from any GSM tool by combination, anyone need it it will be my pleasure to help
DM verity failed
Frp locked
Bricked
Unlocked bootloader.
Odin different errors! If everything goes fine it stucks at something for minutes /hours then give fail message!
Smart switch is useless
Adb sideload /fastboot , the only commands that responds is the one used to get connected devices. When I try to flash there it reboot to recovery instantly.
Recovery is damaged or blocked!!
I cannot instal TWRP because the phone is locked.
I can flash only a stock firmware for my region . Is region matter? (no need to unlock??)
Please browse the pictures . Everything is portrayed. Simply I cannot flash! My mother's device. Not only me. But also the technicians!
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
[RESOLVED]Thank you.
The issue :I used frija to give me the last firmware for my region and the firmware was downgraded , B:4 .it is the last for my region , security level 4 . While the frimware I need to replace , is B6 ,its SWREV is B6 ,K1 S2. So level 6. I tried low level B for 10 days it is why I got Fail messages all the time. But did not give up. I'm a newbie thou. Learned many things in this processe .I used all possible tricks trying to solve the issue.
I thought it is obligatory to flash a firmware from same region if the bootloader is locked , and FRP is locked. I read it from a blog but no! The value of B , stands for security level and bootloader matters. Also the phone version SM-J710F matters ,That 's it. If you flashed ROM with higher B , and failed then adjust the technical stuffs, USB , ports and so on . Or try a Combination frimware create one or get it from the net , use pit files too...goodluck . Dear reader