hello every one
i have a d6503 z2 phone its on android 4.4.4
of course i have it rooted and boot loader unlocked
i tryed pc companion but i can't while its unlocked bootloader
i tryed downloading a stock ftf and flashing it but always a problem of can't open the bundle
what am i doing wrong i have the latest flash tool and i created the ftf throw the downloaded files of the stock lolipop folder
and always same problem can;t open bundle flash operation stopped
please help me i can't get that freaking update !
Flash stock Indian 4.4.2 ftf and recheck.
Hi,
You mentioned you are rooted , so i assume you have recovery.
Search for the tread for a prerooted LP Firmware zip and flash over your current Firmware.
I did it, and its working great.
Hello
I flashed the latest firmware available for my S6 edge (SM-G925F) : G925FXXU3DPDP (XEF).
I've never used Android 5.1.1 on my phone and I asks to you if downgrade is possible at this point (latest BL I think) and if yes, how ?
Thanks you for your further replies
Bye.
I Think Once u Flashed The latest Firmware U can't Go back
Because Of bootloader
Bt U can try Download Android LP And boot loader And put Ur phone in Download Mode Flash with odin
i updated on 6.02...
didn´t like it...
flashed back to 5.1.1 stock without problems (odin)
Hello poci,
You were running with which firmware ?
It's easy to go back to lollipop?
I'm reading some comments off people wich say No, ando some less who say Yes.
i made an OTA update from 5.1.1 to 6.0.2... but i didn´t like the battery drain on 6.0.2......(or 6.0.1 i don´t know anymore)
after clean install of 6.0.2....there was no change at all...
then i went back to 5.1.1 by flashing a stock 5.1.1. firmware with odin...no trouble or anything else...
If flash fails, is my device will be hardbricked ???
if you have the right firmware...i would say "no"
so why should it fail?
i used this firmware for my o2 edge
G925FXXU3QOLD_G925FTEF3QOL1_G925FXXU3QOJB_HOME.tar
Beceause newest bootloaders blocks downgrade, you was in which firmware on Marshmallow ?
don´t know exactly...60.1 then
when 6.0.2 blocks downgrade...
Edit: You can follow the solution of @ashyx through the following link to fix the problem can not flash twrp or boot via Odin. I think it will work
Link: https://forum.xda-developers.com/sa...g-sm-a520f-2017-kernel-source-t3557622/page31
Hello everyone,
After I updated the latest firmware, I was unable to flash BOOT or TWRP via Odin. It just returned the result that ONLY OFFICIAL BINARIES ARE ALLOWED TO BE FLASHED (RECOVERY / BOOT). I think samsung locked the bootloader. Today, I have found a way to fix this problem because knox 0x1 but can not root is not pleasant at all!
I only tested on my A520F, not tested on any other device. I am not responsible for any errors on your device.
1. Go to http://updato.com and download 2 firmware updates with your CSC.
+ Latest firmware 7.0 (November security).
+ Latest firmware 6.0 (MM).
2. Backup your important data
3. Reboot to download mode.
4. Add AP, CP, CSC of firmware 7.0 (November security) to the corresponding slot in Odin.
5. Add BL file of lastest firmware 6.0 (MM) to BL slot in Odin.
6. Start and wait a moment.
7. Setup and after that, you can flash TWRP or BOOT via Odin without bootloader errors.
Enjoy!
Sorry for my english...
Original info from this thread maybe?
https://forum.xda-developers.com/sa...g-sm-a520f-2017-kernel-source-t3557622/page31
.
Hi ahyx, i searched google about not being able to flash twrp or boot after security update in November and know the information is that maybe samsung has locked the bootloader. So, I just tried replacing the BL file of the old firmware that I saved on my laptop and it worked. I do not notice that you have found the solution first. Sorry for it as an act of plagiarism. I will link to your topic as a good faith (sorry for my english)
Oh man, thank you very much !! helped me here too! I had my a5 17 with this 'softbrick' but thank God I was able to install twrp, and so doing root haha I just can not downgrade to the MM.
this one are 100% work?
i need to download lates MM version and lates Nougat version? then i flash only BL of MM and CP,CSC and AP of nougat version? tia
kobejor said:
i need to download lates MM version and lates Nougat version? then i flash only BL of MM and CP,CSC and AP of nougat version? tia
Click to expand...
Click to collapse
Vou need to download the latest Nougat 7.0 firmware (A520FXXU2BQK4) and fw plus MarshMallow 6.0.1 (A520FXXU2AQG4).
I, as a Brazilian, downloaded the fw of Brazil.
And then in AP, CP and CSC you put the respective AP, CP and CSC files of the Nougat rom
and in BL the Marshmallow rom file.
It works, man!
At first I had some problems, the smart was out of system because before finishing the process I got some errors (old usb port, bad contact, etc.). Try to keep all the smart USB drivers on your PC, turn on the debug and also the OEM mode and restore your a5. Today I have been able to downgrade and I am using the stock rom 6.0.1
guys can someone please upload MM boot loader so we don't have to download the ROM completely (approx 2.1 GO )
THANKS GUYS
When i try to flash it says: SW REV CHECK FAIL DEVICE 2 BINARY 1
T-Rex said:
guys can someone please upload MM boot loader so we don't have to download the ROM completely (approx 2.1 GO )
THANKS GUYS
Click to expand...
Click to collapse
http://www.mediafire.com/file/8173e...911830_QB14224310_REV00_user_low_ship.tar.md5
BL MM (6.0.1) - From ZTO Brazil
caiquess95 said:
Vou need to download the latest Nougat 7.0 firmware (A520FXXU2BQK4) and fw plus MarshMallow 6.0.1 (A520FXXU2AQG4).
I, as a Brazilian, downloaded the fw of Brazil.
And then in AP, CP and CSC you put the respective AP, CP and CSC files of the Nougat rom
and in BL the Marshmallow rom file.
It works, man!
At first I had some problems, the smart was out of system because before finishing the process I got some errors (old usb port, bad contact, etc.). Try to keep all the smart USB drivers on your PC, turn on the debug and also the OEM mode and restore your a5. Today I have been able to downgrade and I am using the stock rom 6.0.1
Click to expand...
Click to collapse
I'm also Brazilian, and it worked for me! Thank you!
It turned out people were stuck with my A7 2017 using the rom of India nougat, I could not install nor the recovery much less to do the root, with your help here I got I'm from Brazil, I just installed via odin the file BL zto android 6, I entered the download mode and installed recovery and did the root, now only joy.
Download ROM quickly in Android Duniya site.
same problem hahaha, now it's root after the December patch
thangluong said:
Edit: You can follow the solution of @ashyx through the following link to fix the problem can not flash twrp or boot via Odin. I think it will work
Link: https://forum.xda-developers.com/sa...g-sm-a520f-2017-kernel-source-t3557622/page31
Hello everyone,
After I updated the latest firmware, I was unable to flash BOOT or TWRP via Odin. It just returned the result that ONLY OFFICIAL BINARIES ARE ALLOWED TO BE FLASHED (RECOVERY / BOOT). I think samsung locked the bootloader. Today, I have found a way to fix this problem because knox 0x1 but can not root is not pleasant at all!
I only tested on my A520F, not tested on any other device. I am not responsible for any errors on your device.
1. Go to http://updato.com and download 2 firmware updates with your CSC.
+ Latest firmware 7.0 (November security).
+ Latest firmware 6.0 (MM).
2. Backup your important data
3. Reboot to download mode.
4. Add AP, CP, CSC of firmware 7.0 (November security) to the corresponding slot in Odin.
5. Add BL file of lastest firmware 6.0 (MM) to BL slot in Odin.
6. Start and wait a moment.
7. Setup and after that, you can flash TWRP or BOOT via Odin without bootloader errors.
Enjoy!
Sorry for my english...
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------
I try this with the Android 6.0.1 BL but I recived the next error: SV REV. CHECK FAIL. DEVICE: 3. BINARY: 1
please help me.. my Phone is A5 2017 (SM-A520F)
RubenDGuerreroG said:
--------------------------------------------------------------------------------------------------------------------------------------
I try this with the Android 6.0.1 BL but I recived the next error: SV REV. CHECK FAIL. DEVICE: 3. BINARY: 1
please help me.. my Phone is A5 2017 (SM-A520F)
Click to expand...
Click to collapse
OK two things.
1. You can't have downloaded the boot image specified as it's a rev. 2 binary not 1.
2. Your device has been updated to rev. 3, so you're probably out of luck for downgrading.
ashyx said:
OK two things.
1. You can't have downloaded the boot image specified as it's a rev. 2 binary not 1.
2. Your device has been updated to rev. 3, so you're probably out of luck for downgrading.
Click to expand...
Click to collapse
Same problem here...
I can't root anymore
ashyx said:
OK two things.
1. You can't have downloaded the boot image specified as it's a rev. 2 binary not 1.
2. Your device has been updated to rev. 3, so you're probably out of luck for downgrading.
Click to expand...
Click to collapse
I just bought the A520F/DS (Malaysia) which still has MM 6.0.1. Can I use the procedure - Flash latest Nougat (Rev. 3 or later) in AP, CP, CSC) leaving BL blank - then do root? (Would I be correct to assume the bootloader will be unaltered, i.e. still be MM 6.0.1?) Thanks.
Just dropping by to leave some info, I successfully flashed TWRP on my single sim A520F with December bootloader updated to january after porting 7.1.1, and another one, same single sim, with January bootloader. Although, i have a friend with Duos that can't flash anything too since november patch.
So i think this issue is more like a bug, i don't see why samsung would lock only duos devices and not single too. N8 issue is actually the dissappearing oem unlock toggle, csc related. Some countries have it, some countries don't. But in our situation, this is more like a frp lock stuck on, no matter why oem toggle says. I surely hope i am right and future updates will bring duos users the freedom back.
Regards
Sent from my SM-A730F using Tapatalk
Has anyone tried updating to January Security Patch using the same trick? Say, Odin combination of rev 2 BL (from MM) + rev 4 January nougat update (AP+CP+CSC) and had their phones rooted after flashing?
Update: Done using this trick and had my device rooted successfully.
@ashyx
Hi
Is it possible to skip updating bootloader when flashing, to avoid rooting problems?
e.g. Can we update to android O with an unlocked bootloader of Android N or MM?
I removed frp and after restarting I got to recovery screen with a message stating "DM-VERITY verification Failed: , googling around I figured I needed to reflash the rom (ODIN), thing is I already tried many times and i always get a FAIL while flashing the SYSTEM part, I've tried downloading from different sources, so maybe I am downloading the wrong firmware, is this possible if boot and rec are flashing fine?, so i went to search and I always ended p with same firmware version.
then I found some others:
USA (Anritsu) AIO Official Frimware SM-J120AZ J120AZTUS5ARA1 Android 6.0.1 Marshmallow 05-Feb-18 Download
USA (Anritsu) AIO Official Frimware SM-J120AZ J120AZTUU3AQH2 Android 6.0.1 Marshmallow 10-Sep-17 Download
USA (Anritsu) AIO Official Frimware SM-J120AZ J120AZTUS3AQE1 Android 6.0.1 Marshmallow 13-Jun-17 Download
USA (Anritsu) AIO Official Frimware SM-J120AZ J120AZTUS2AQB2 Android 6.0.1 Marshmallow 15-Mar-17 Download
USA (Anritsu) AIO Official Frimware SM-J120AZ J120AZTUU2APJ2 Android 6.0.1 Marshmallow 10-Nov-16 Download
USA (Anritsu) AIO Official Frimware SM-J120AZ J120AZTUU1APD2 Android 6.0.1 Marshmallow 29-May-16
Which one should i get, or HOW Can i Know which one i Need?
it is a cricket device but seems like all of those are cricket
model under battery says SM-j120AZ-UD
i know it had android 6.01 but then again all of those files are 6.01
under the sticker there has some numbers:
170224 which must be a date, and REV 03 to the right of the barcode.
made in vietnam if that helps at all.
Please Help.
nevermind, I got it , thank you, had wrong firmware