Related
Here above,
LG V20 TOT File v10i for F800K (KT Mobile)
Use it for root exploit and Development
Download (file is compressed, download and simply unzip it)
Mirror
support me if you want, and pay me a beer
wolfgart said:
Here above,
LG V20 TOT File v10i for F800K (KT Mobile)
Use it for root exploit and Development
Download (file is compressed, download and simply unzip it)
Mirror
support me if you want, and pay me a beer
Click to expand...
Click to collapse
thanks , do you have the dll file?
hkfriends said:
thanks , do you have the dll file?
Click to expand...
Click to collapse
Hey bro,
You don't need any DLL file.
To flash it you simply have to use same LGUP version used for LG G5 and follow same steps like you flash for KDZ files.
Just tried and it works perfectly
Also, LGUP can take dz file for upgrade (data stays intact).
is it possible to insert SuperSu directly into the restore file to have a pre rooted stock rom, while we wait for TWRP??
Amd4life said:
is it possible to insert SuperSu directly into the restore file to have a pre rooted stock rom, while we wait for TWRP??
Click to expand...
Click to collapse
That's what @tungkick did.
He made prerooted .tot for G5 and .dz for G Pad X 8.0
Both are T-Mobile version with unlocked bootloader with missing fastboot commands.
Amd4life said:
is it possible to insert SuperSu directly into the restore file to have a pre rooted stock rom, while we wait for TWRP??
Click to expand...
Click to collapse
i hope yes
but locked bootloader state could avoid boot unsigned code ...
wolfgart said:
i hope yes
but locked bootloader state could avoid boot unsigned code ...
Click to expand...
Click to collapse
Actually, locked bootloader does not matter anymore.
You have to do reverse engineering with hex editor to retrieve keys in order to bypass the bootloader. This is how Samsung Tab A6 can be rooted and TWRP installed even the bootloader is tight locked (and you have to patch the kernel to change SE Linux policy).
mingkee said:
Actually, locked bootloader does not matter anymore.
You have to do reverse engineering with hex editor to retrieve keys in order to bypass the bootloader. This is how Samsung Tab A6 can be rooted and TWRP installed even the bootloader is tight locked (and you have to patch the kernel to change SE Linux policy).
Click to expand...
Click to collapse
Great to know
@tungkick can help all of us
mingkee said:
Actually, locked bootloader does not matter anymore.
You have to do reverse engineering with hex editor to retrieve keys in order to bypass the bootloader. This is how Samsung Tab A6 can be rooted and TWRP installed even the bootloader is tight locked (and you have to patch the kernel to change SE Linux policy).
Click to expand...
Click to collapse
It would be great to bring all our computers together to crack the code like mining bit coins. How neat would that be.
Are you guys optimistic for root on the V20? Or will it be a similar story to that of the Note 7 with 99.9% stable root?
Thanks for your efforts.
Hi i got few Questions can i flash this on V20 F800L ?
and how much bloatware this firmware got can you please post some screen shots of the bloatware please
Thank you
iemwatiem said:
Hi i got few Questions can i flash this on V20 F800L ?
and how much bloatware this firmware got can you please post some screen shots of the bloatware please
Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/v20/development/lg-v20-f800l-t3487554
Be quiet with downgranding FW ...
wolfgart said:
http://forum.xda-developers.com/v20/development/lg-v20-f800l-t3487554
Be quiet with downgranding FW ...
Click to expand...
Click to collapse
Thanks for the reply i am asking this because i have the LG V20 F800L and their are some carrier bloatware i cant remove its so annoying and its also in Korean Language .
Thats why i want to know if it possible to flash the F800K on my F800L to try any luck with bloatware ?
iemwatiem said:
Thanks for the reply i am asking this because i have the LG V20 F800L and their are some carrier bloatware i cant remove its so annoying and its also in Korean Language .
Thats why i want to know if it possible to flash the F800K on my F800L to try any luck with bloatware ?
Click to expand...
Click to collapse
F800K is the phone from Korean Telcom so you are going to have the same issue. I have the F800K this is how I know.
wolfgart said:
Hey bro,
You don't need any DLL file.
To flash it you simply have to use same LGUP version used for LG G5 and follow same steps like you flash for KDZ files.
Just tried and it works perfectly
Click to expand...
Click to collapse
Wolf, could you please upload the LGUP you are using. All the ones I have found will not go past 9-10% when trying to flash the Tmobile .tot.
f800S?
wolfgart said:
Hey bro,
You don't need any DLL file.
To flash it you simply have to use same LGUP version used for LG G5 and follow same steps like you flash for KDZ files.
Just tried and it works perfectly
Click to expand...
Click to collapse
HOW?? Did you flash the extracted .bin files? Were you able to convert the .tot to .kdz? Please share. THX.
Boot Loop
Hey, My phone kept telling me that I had my jack connected. I wipe the system and now it's stuck in a bootloop and keeps going back to TWRP. ANY HELP PLEASE!!!!
Hi
Has anyone used this successfully on the F800K ?
Does it flash perfectly??
Could anyone post a new download link? Thanks!
Hello, i would to ask about how to downgrade to the earlier version of the stock ROM
I already download the correct country code, variant and everything else but when i click start in Odin
It says that cm.bin fail and the process is canceled, how to fix this issue?
Thanks a lot
SM-A750GN with XID country code, here is the firmware that i use https://www.sammobile.com/firmwares/galaxy-a7/SM-A750GN/XID/download/A750GNDXU1ARIE/241618/
and this is my device firmware now A750GNDXU2ASB4
or is it not possible to downgrade? any help around this as to not void my warranty if possible
There could be a couple of things:
1. You could be using an outdated version of Odin
2. You need to re-download the firmware, try searching updato for your firmware
3. Maybe the current/latest version of the firmware installed on your phone locks your boot loader to the current version (binary version matches the boot loader)and that is why you can't downgrade
What you could try (definitely at your OWN risk) because if things go wrong you can end up with an expensive paper weight:
1. Unpack the firmware with 7zip, remove the file (cm.bin) then repack to tar with 7zip
2. You can try to flash just the AP and CSC
rubenswing said:
There could be a couple of things:
1. You could be using an outdated version of Odin
2. You need to re-download the firmware, try searching updato for your firmware
3. Maybe the current/latest version of the firmware installed on your phone locks your boot loader to the current version (binary version matches the boot loader)and that is why you can't downgrade
What you could try (definitely at your OWN risk) because if things go wrong you can end up with an expensive paper weight:
1. Unpack the firmware with 7zip, remove the file (cm.bin) then repack to tar with 7zip
2. You can try to flash just the AP and CSC
Click to expand...
Click to collapse
Does it works for gn user? Any one try it?
I've tried to downgrade my SM-A750GN via odin software, but fails cm.bin and parameter.bin.
AP and CSC only to flash, it's not work at all.
How about flashing the oreo firmware with TWRP, does any one have tried it?
fr4n.4rdi said:
I've tried to downgrade my SM-A750GN via odin software, but fails cm.bin and parameter.bin.
AP and CSC only to flash, it's not work at all.
How about flashing the oreo firmware with TWRP, does any one have tried it?
Click to expand...
Click to collapse
You can't downgrade because the bootloader is protected by Rollback Prevention, the only way (maybe) to use Oreo is to flash TWRP and wipe system data and use any custom Oreo ROM.
If you want to know about Rollback Prevention then there is a attached pdf from the Samsung Technical documentation
rubenswing said:
You can't downgrade because the bootloader is protected by Rollback Prevention, the only way (maybe) to use Oreo is to flash TWRP and wipe system data and use any custom Oreo ROM.
If you want to know about Rollback Prevention then there is a attached pdf from the Samsung Technical documentation
Click to expand...
Click to collapse
Can you please give me a link to download any oreo custom rom for my sm-a750 gn.
Thank you for reply..
fr4n.4rdi said:
Can you please give me a link to download any oreo custom rom for my sm-a750 gn.
Thank you for reply..
Click to expand...
Click to collapse
AFAIK there is no Oreo custom ROM for this phone on THIS forum
rubenswing said:
You can't downgrade because the bootloader is protected by Rollback Prevention, the only way (maybe) to use Oreo is to flash TWRP and wipe system data and use any custom Oreo ROM.
If you want to know about Rollback Prevention then there is a attached pdf from the Samsung Technical documentation
Click to expand...
Click to collapse
Is there anyway to disable the Rollback Prevention bro? So i can downgrade my sm-a750gn.
fr4n.4rdi said:
Is there anyway to disable the Rollback Prevention bro? So i can downgrade my sm-a750gn.
Click to expand...
Click to collapse
Not that I know of
I have Samsung s8 plus SM-G995U1 USA unlocked.
I dont have oem unlock option, so trying to root with rooted firmware with odin and getting check fail: device 6 binary 5
Flashing firm: G955USQS5BRB1_ODIN_SAMFAIL_V5_Bootloader.7z
My baseband- G955U1UES6DSG1
Please tell me whts the issue and why i am getting this error. I am currently on pie update
srajnish209 said:
I have Samsung s8 plus SM-G995U1 USA unlocked.
I dont have oem unlock option, so trying to root with rooted firmware with odin and getting check fail: device 6 binary 5
Flashing firm: G955USQS5BRB1_ODIN_SAMFAIL_V5_Bootloader.7z
My baseband- G955U1UES6DSG1
Please tell me whts the issue and why i am getting this error. I am currently on pie update
Click to expand...
Click to collapse
USA ( U and U1 ) don't have the ability to have the bootloader unlocked.
You are also try to down grade you firmware. You will need a version 6 ( bootloader version ). Bootloader version is the 5th number from the right of firmware ( baseband ).
spawnlives said:
USA ( U and U1 ) don't have the ability to have the bootloader unlocked.
You are also try to down grade you firmware. You will need a version 6 ( bootloader version ). Bootloader version is the 5th number from the right of firmware ( baseband ).
Click to expand...
Click to collapse
Please tell me bro how to root this phone in bootloader 6.
Do i need to downgrade to root it??
srajnish209 said:
Please tell me bro how to root this phone in bootloader 6.
Do i need to downgrade to root it??
Click to expand...
Click to collapse
I don't have a Snapdragon variant
Having not to have the bootloader unlock will limit you to rooting solutions.
You can not down grade you bootloader version number.
Have a look at the s8+ rom section under jrkruse threads and may be ask you question there.
https://forum.xda-developers.com/galaxy-s8+/development
Hello,
We have a big issue. We have a custom application that was installed on Samsung Galaxy A6 phones. After upgrading Android the application won't install anymore.
I need to downgrade operating system from Android 10 to Android 8 on these phones, as they came original.
The big issue is I cannot downgrade the bootloader in order to install stock firmware of Android 8 from sammobile.com
Can anybody help me?
Thank you
Doesn't the stock firmware contain bootloader?
Tab E said:
Doesn't the stock firmware contain bootloader?
Click to expand...
Click to collapse
Yes, contain bootloader but I cannot revert from a higher bootloader version to a previous bootloader version using Odin
Oh yes you will get SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2." error
Extract the andorid 8 firmware with 7 zip. Delete all files ending with
".bin" repack the firmware to ".tar and flash it with odin
Tab E said:
Extract the andorid 8 firmware with 7 zip. Delete all files ending with
".bin" repack the firmware to ".tar and flash it with odin
Click to expand...
Click to collapse
the stock files have extension .tar.md5(5 files: BL, AP, CP, CSC)
I tried what you said, but when I repack with .tar extension ODIN do not read the files. Anyway, I did not found system.bin, image.bin, recovery.bin or files like this. Are just two .bin files(modem.bin and another one)
robertanisoiu said:
the stock files have extension .tar.md5(5 files: BL, AP, CP, CSC)
I tried what you said, but when I repack with .tar extension ODIN do not read the files. Anyway, I did not found system.bin, image.bin, recovery.bin or files like this. Are just two .bin files(modem.bin and another one)
Click to expand...
Click to collapse
Delte the BL
This is the bootloader file.
Tab E said:
Delte the BL
This is the bootloader file.
Click to expand...
Click to collapse
And I load in Odin only AP, CP and CSC files wihout any modification?
robertanisoiu said:
And I load in Odin only AP, CP and CSC files wihout any modification?
Click to expand...
Click to collapse
Yes
Tab E said:
Yes
Click to expand...
Click to collapse
I tried but, unfortunately, I receive the error: "kernel rev check fail device 6 binary 2(boot)". The actual bootloader is 5, the Android 8 bootloader version is 2.
I was trying to flash my phone but It was not successful so I did some investigation and found two model numbers,can someone please help me out
mathias1111 said:
I was trying to flash my phone but It was not successful so I did some investigation and found two model numbers,can someone please help me out
Click to expand...
Click to collapse
You flashed a firmware that was not for your model number.
Droidriven said:
You flashed a firmware that was not for your model number.
Click to expand...
Click to collapse
That's how I bought the phone, and everytime I factory set it I always see magisk on the phone,
So which of the numbers am I sopos to use
Look into Android's system file called "build.prop" in /system and /vendor for entries
ro.product.model
ro.product.brand
Click to expand...
Click to collapse
The values to be found in "build.prop" in /vendor should be the right ones.
mathias1111 said:
That's how I bought the phone, and everytime I factory set it I always see magisk on the phone,
So which of the numbers am I sopos to use
Click to expand...
Click to collapse
I'm assuming you bought the device used and the previous owner probably flashed a firmware from a similar device in it's series so that the device could be modified using Magisk.
xXx yYy said:
Look into Android's system file called "build.prop" in /system and /vendor for entries
The values to be found in "build.prop" in /vendor should be the right ones.
Click to expand...
Click to collapse
Not necessarily, if the device has been flashed with a firmware from a different model, the build.prop will show the model number of the different firmware. I had a SPH D710 that had been flashed with SCH R760X firmware, the build.prop showed SCH R760X but behind the battery it showed the correct model number SPH D710. I also had a SCH S968C that was flashed with SCH I535, it showed SCH I535 in build.prop even though the device was actually SCH S968C.
Droidriven said:
I'm assuming you bought the device used and the previous owner probably flashed a firmware from a similar device in it's series so that the device could be modified using Magisk.
Click to expand...
Click to collapse
Yes you are right, I want to flash it with a new firmware but it's not working should I unlock bootloader before the flashing it?
mathias1111 said:
Yes you are right, I want to flash it with a new firmware but it's not working should I unlock bootloader before the flashing it?
Click to expand...
Click to collapse
If you are flashing a stock firmware file, you "shouldn't" have to unlock the bootloader. If you can verify which firmware you need you should be able to flash it is Odin as long as the binary of the correct firmware is equal to or higher than the currently installed firmware. You may have to use a modified version of Odin, it can flash without some of the restrictions that interfere with standard Odin.
I tried flashing the firmware today and I had an error message "secure check fail BOOTLOADER "