I unlocked the bootloader and was going to install CM. Accidentally wiped the internal storage too using twrp. Tried to mount USB so that I could copy the CM and gapps zipps but it just wouldn't copy from the computer. Tried to reboot and now I'm stuck on the "warning bootloader unlocked" screen. It looks like there is no OS on the phone!
EDIT: I can't even switch it off. Every time I hold down the power button, it just reboots to the same screen. So, I don't see any way of being able to boot into recovery. ;(
EDIT 2: I've got my hands on the exact AsiaRetail firmware I was on earlier. Does that help in any way? I've been reading that it might.
EDIT3: I've managed to get the phone into fastboot. All that needed to be done was hold on to the volume down and power buttons for a bit after the screen turned off and then let go.
It turns out I only got the OTA update zip. Can't flash from that one right? Where can I get hold of lollipop firmware for XT1052 that I can flash using fastboot?
What can I do from here?
Please help!
Okay, I'm at my last straw here. Someone please help! This is where I'm stuck now.
C:\Users\Soumen\Downloads\XT1052_GHOST_RETASIA_5.1_LPA23.12-15.5_cid7_CFC.xml>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1431847344 bytes
error: cannot load 'system.img': Not enough space
soumen08 said:
Okay, I'm at my last straw here. Someone please help! This is where I'm stuck now.
C:\Users\Soumen\Downloads\XT1052_GHOST_RETASIA_5.1_LPA23.12-15.5_cid7_CFC.xml>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1431847344 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
I've got an xt1060 (Vzn US version) but have heard of and/or seen most of your "error" messages before. If you google all those things, you'll see everything from "you've got the wrong version of fastboot/mfastboot" to "OEM /system restores/installs can restore your /recovery partition to the system version" and more. Feel free to chase it down or you can just try to get the thing back to a working state and worry about things like custom recovery and root later. This might be important to you if you've gone to pains to root the phone, so if it's not rooted, it is probably less of a big deal than if it is.
I'm not sure you gave enough "context" before & after your error on /system flash (like whether you were following down a complete list as in one of the flash.xml files in that same folder), but it appears from your path that you've got a full factory image of 5.1 in the original .xml format. If that's so and you just want to restore and don't care about root or any data on the phone, then do something like this:
Download RSD Lite (version 6.2.4 would do) from somewhere and set it up. Get the phone back in fastboot. Make sure it shows up in a "fastboot devices" command. Run RSD (virus check the thing first) and open up the .xml file (or flashfile.xml from within if it wants that). Make sure the phone is attached in fastboot.
Run RSD on that and it should restore the everything. Meanwhile, don't forget that any data you had saved will be gone (from /sdcard/0 etc).
If that succeeds (should take 30 minutes or less) and another 5 for first boot then you can think about other stuff like custom recovery & root, but only if you've got an unlocked bootloader. I have no idea whether there's any current way to an unlocked bootloader. Mine is a DE model so it's unlocked and I'm not up on current 5.1-compatible methods.
----------------------
By the way: I jotted this reply down about 3 hours back, then had to go out to do some stuff for awhile and just am back now. If someone solved it or you've solved it, just disregard this reply. Cheers.
Well, I've got it back up now. Turns out the problem was that my system didn't have enough free RAM to load the entire thing to RAM, split it into parts and then transfer it (which is what it does on the inside). So, rebooting the system solved the problem.
Hi everyone and thanks for your time. I will get straight to the point:
All these tests were made on G925V 5.1.1 , rooted with eng boot. (Look at my profile for my post on how to downgrade from 7.0 ,and all below, to 5.1.1 and for for root turorial)
-The samsung downgrade mechanism relies on a flag set in the different partitions to determine its version.
- The phone looks for the flag "SYSMAGIC X" where X is the version. (Starting from 0, meaning SYSMAGIC 0= version 1)
-The following partitions have the flag:
*BOTA0 <----gets its files from sboot.bin (bootloader first partition)
* BOTA1 <-------gets its files from cm.bin (bootloader second partition)
*BOOT <----- from boot.img
*CACHE <-----from cache.img
*RECOVERY <----from recovery.img
*SYSTEM <------from system.img
*sdb <---- which is the bootloader as a whole I believe, don't quote me in this, just a deduction.
All these files can be accessed through a full tar or by dumping them using dd if of.
Bota0, bota1, boot, system,recovery,cache..etc can be found in :
/dev/block/platform/15570000.ufs/by-name
Putting any of these in a hex editor, you will find the line "SYSMAGIC 3" (in my case for 5.1.1, binary version 4).
If you dump /dev/block/sda18 , edit with hex editor and edit the SYSMAGIC to one version lower. Save then dd back to sda18, reboot the phone and guess what?
SYSTEM REV. CHECK FAIL. DEVICE:3 BINARY:2.
All this is assumption but the line is there and it seems to pass every check and just assumes thats the version.
Hope someone can take it further. I unfortunately bricked my s6 writing the wrong partiton back over the bootloader...and well...bad bootloader....no more download mode.
Be careful, devs please help. Anyone with a device willing to use as a ginny pig, pm me.
dragoodwael said:
Hi everyone and thanks for your time. I will get straight to the point:
All these tests were made on G925V 5.1.1 , rooted with eng boot. (Look at my profile for my post on how to downgrade from 7.0 ,and all below, to 5.1.1 and for for root turorial)
-The samsung downgrade mechanism relies on a flag set in the different partitions to determine its version.
- The phone looks for the flag "SYSMAGIC X" where X is the version. (Starting from 0, meaning SYSMAGIC 0= version 1)
-The following partitions have the flag:
*BOTA0 <----gets its files from sboot.bin (bootloader first partition)
* BOTA1 <-------gets its files from cm.bin (bootloader second partition)
*BOOT <----- from boot.img
*CACHE <-----from cache.img
*RECOVERY <----from recovery.img
*SYSTEM <------from system.img
*sdb <---- which is the bootloader as a whole I believe, don't quote me in this, just a deduction.
All these files can be accessed through a full tar or by dumping them using dd if of.
Bota0, bota1, boot, system,recovery,cache..etc can be found in :
/dev/block/platform/15570000.ufs/by-name
Putting any of these in a hex editor, you will find the line "SYSMAGIC 3" (in my case for 5.1.1, binary version 4).
If you dump /dev/block/sda18 , edit with hex editor and edit the SYSMAGIC to one version lower. Save then dd back to sda18, reboot the phone and guess what?
SYSTEM REV. CHECK FAIL. DEVICE:3 BINARY:2.
All this is assumption but the line is there and it seems to pass every check and just assumes thats the version.
Hope someone can take it further. I unfortunately bricked my s6 writing the wrong partiton back over the bootloader...and well...bad bootloader....no more download mode.
Be careful, devs please help. Anyone with a device willing to use as a ginny pig, pm me.
Click to expand...
Click to collapse
That is great news. What else do you know of the magic bytes at the footer of the system image?
I'm going to look into this.
All of those partitions, probably even the cache partition with it's metadata file from the CSC, have points that have access to the private signing key burned into the Trust Zone firmware.
Hi, I followed your tut on downgrading my SM-G925V to 5.1.1 and also got root which was great, but I guess its pretty worthless as its only temporary til reboot, has there been any further progress on permanent root on the G925v? Great work btw all involved!
My KFHD7 - Tate (PVT-08) has some trouble in the last time.
It stucks in a boot loop with the yellow Kindle logo.
I am able to reflash boot, bootloader and recovery via fastboot.
Then I normally was able to flash a system image after run recovery and can run this system once.
But after a reboot the bootloop exists again.
Now i'm able to start TWRP with the procedure described above.
The partitions cache, userdata and system always appear with 0kb. So I change the file system and change it back afterwards. Then the partition size is correct again and I can flash.
This time, however, I can no longer access the system partition.
If I try to change the file system I get the error message:
Code:
Failed to mount '/system' (Invalid argument)
Error changing file system.
A repair of the file system also fails:
Code:
Repairing system using e2fsck
/sbin/e2fsck -fp /dev/block/mmcblk0p11 process ended with ERROR: 8
Unable to repair system.
I suspect therefore (with my modest knowledge) problems with the partition table.
Maybe someone can upload me a flashable gpt.bin or something.
Or is a completely different method more suitable?
Many thanks in advance.
I have a working Tate. What exactly do you need? gpt.bin means nothing to me.
I can connect and provide a dd of something if you say precisely what you need.
In your position, I would first be asking how your partition table could have been altered. What do you suspect you may have done to change it? Unless you know you could have damaged it you may need to look elsewhere before possibly doing more damage by screwing around with the partition table.
Code:
Failed to mount '/system' (Invalid argument)
Error changing file system.
start by posting what you used as a command. No one can tell from the error what you did right/wrong
BTW how did you root the device, what version of Tate was it running before you did that?
First of all, thank you for someone's interest in the thread after such a long time.
Because of your question how to read out the gpt.bin I did some more research.
Now I actually managed to deblock the tablet!
For this I used the KFHD System.img Restore Tool. After that the problems with the system partition disappeared.
The thread is therefore solved for me and may help others in the same situation.
Thank you very much for your support!
Sylvan86 said:
First of all, thank you for someone's interest in the thread after such a long time.
Because of your question how to read out the gpt.bin I did some more research.
Now I actually managed to deblock the tablet!
For this I used the KFHD System.img Restore Tool. After that the problems with the system partition disappeared.
Thank you very much for your support!
Click to expand...
Click to collapse
I'm very pleased that my reply stimulated you to look again and got you a fixed tablet. The amount of support we get for these older tablets here seems less than minimal.
I have rooted mine but have not managed to install a recovery or fully regain control yet. I'll look at that tool you used. Do you know what Tate version you were running before , was it "up to date" ( ie sync'ed since 2014 ? ) . Mine has 7.5.1 and that seems to cut off a lot of options.
One thing I'm stuck on is booting into "recovery" mode. I have read that it is vol-up during boot but this does not seem to change anything for me, It just boots normally. If I do vol-down, I get "safe mode" but that's not much help.
Thanks for the link. I had looked at the before but was not sure if it applied to these devices, so did not want to risk it. It worked fine. One thing it forgets to tell you is to disable OTA updates. The first time I gave it wifi access it shot off without so much as a please and thank you and updated me back to 7.5.1 . So first thing to do is to kill updates:
Code:
su
cd /system/etc/security/
mv otacerts.zip otacerts.notazip
Hello!
Not sure if this has happened, but I think my data partition has shrunk. My device (s10e) used to show 107 GB, now it shows ~ 15.7 GB. Is there a way to un-shrink data partition and restore it? I have TWRP at the moment. Was about to install LOS17.1 but stopped.
Reason: I did the stupid thing even though you (topjohn)asked not to, "Never flash only an AP file, as Odin can shrink your /data file-system if you do." Someone in the forums had a thorough, detailed post, saying to flash tarred files to AP slot (did not mention by themselves or with other files as well).
Thanks!
goodflood said:
Hello!
Not sure if this has happened, but I think my data partition has shrunk. My device (s10e) used to show 107 GB, now it shows ~ 15.7 GB. Is there a way to un-shrink data partition and restore it? I have TWRP at the moment. Was about to install LOS17.1 but stopped.
Reason: I did the stupid thing even though you (topjohn)asked not to, "Never flash only an AP file, as Odin can shrink your /data file-system if you do." Someone in the forums had a thorough, detailed post, saying to flash tarred files to AP slot (did not mention by themselves or with other files as well).
Thanks!
Click to expand...
Click to collapse
Flashing Stock rom should fix it...
Sent from my moto g(7) play using Tapatalk
@PoochyX That did it; thank you so much!
I have a Samsung SM-T290, running Android 9. Whatever I do, Magisk seems to shrink my data partition from 32G to 8G. I think I scrupulously followed topjohnwu's directions (except that I put the stock AR module on the SD card and moved it between the device and my laptop via sneakernet rather than adb pull). I used Odin to flash BL, the patched AP, CP and CSC (not Home-CSC). Magisk was installed alright, and I achieved root, but my storage was reduced to 8GB.
The only way I've found so far to bring my storage up to 32GB was to factory reset, which removes Magisk and root. I tried extracting the PIT file from CSC in the stock ROM and doing a NAND erase and reformat, but as long as I'm using the patched AR with Magisk, I end up with 8GB.
What am I doing wrong?
Further to the above: Just to dot all the i's and cross all the t's, I repeated the process, using adb pull to transfer the patched AP file, as topjohnwu recommended. The same thing happened: my data partition was reduced to 8GB.
Also, I've noticed, that whenever I insert the patched AP into Odin, it accepts it almost immediately, while it takes quite a while reading the original AP tar. Could this indicate that Magisk is corrupting the AP tar file when it patches it?
pgurwitz said:
Further to the above: Just to dot all the i's and cross all the t's, I repeated the process, using adb pull to transfer the patched AP file, as topjohnwu recommended. The same thing happened: my data partition was reduced to 8GB.
Also, I've noticed, that whenever I insert the patched AP into Odin, it accepts it almost immediately, while it takes quite a while reading the original AP tar. Could this indicate that Magisk is corrupting the AP tar file when it patches it?
Click to expand...
Click to collapse
I think the speed difference is due to whether it's ending with n.n.tar.md5 or just n.n.tar. The time probably has to do with the unpacking of md5.
By the way: My capacity also shrunk from 32 to 16 GB on my Xcover 4s
Hi there
Thanks to all other guys here who have made helpful development to tame this beautiful =)
To crossflash models other than LG G8 please read post 3.
Before asking any question please read the troubleshooting section at the bottom of the page.
If you still need some specific help I would appreciate if you bring it up just in the thread instead of sending direct messages.
LG has made things difficult in flashing custom and even stock roms by this new OPID thing! It prevents us from crossflashing but we have been able to use TWRP and change the system and some other partitions to have a different rom. We had to make some changes into OP partition using HxD editor.
But now, through this tutorial, we're able to flash any rom without the need to change OPID in OP partition. Also, there is no need to root or unlock boot-loader.
I was successful to do this on some G8 (LMG820UM) but I AM NOT RESPONSIBLE FOR ANY HARM TO YOUR PHONE!
By continuing to read the following instructions you are actually accepting the risk.
IMPORTANT!
first, MAKE A FULL BACKUP OF ALL PARTITIONS; and I mean it!!!
at least, for your sake, make a backup of "modemst1, modemst2, fsg, fsc, ftm" partitions, for emergency.
Requirements
QPST and Qualcomm USB Driver (get)
LGE SM8150 Firehose (get)
LGUP 1.16.0.3 (get)
LGUP_Common.dll (get)
UI_Config.lgl (get)
LG Mobile Driver 4.4.2 (get)
Preparation
1. Install QPST and Qualcomm USB Driver.
2. Install LGUP.
3. Find the folder named "model" in the installation directory of LGUP, then Create a folder named "common" in the "model" folder.
4. Move "LGUP_Common.dll" and "UI_Config.lgl" into "common" folder. Change the attribute of "UI_Config.lgl" to read only.
5. Install LG Mobile Driver 4.4.2.
Steps
A)
1. Open QFIL.
2. Change "Storage Type" to UFS.
3. Select "Flat Build".
4. Browse for "LGE SM8150 Firehose" and pick it.
5. Now, connect the phone to PC and boot into EDL mode.
6. Open "Select Port" and select the phone, press OK.
7. In "Tools" open the "Partition Manager".
B)
!!!BE CAREFUL TO DO EXACTLY AS THE INSTRUCTIONS SAY OR YOU WILL BRICK THE PHONE!!!
1. Make a backup of and erase these 7 partitions: FTM, Modem_A, Modem_B, SID_A, SID_B, OP_A, OP_B.
1.1. You have to left-click on a partition then right-click on it and select "Manage Partition Data".
1.2. In the pop-up window, you have 4 choices: I. Erase (to erase data on the partition), II. Read Data (to dump or back up the partition), III. Load Image (to restore the partition), IV. Close (to close the window).
1.3. First dump/back up the partition by choosing "Read Data" then Erase it.
2. Close the "Partition Manager" window.
3. Wait for 5 seconds then press Vol- and Power until it restarts.
3.1. Immediately after rebooting, Release the Vol- and Power buttons and press Vol+ to get into Download Mode.
Note: Do not let the phone to begin to boot! If it begins to boot, it may regenerate the SID and FTM partitions data and so you need to redo the whole step B.
C)
1. Open LGUP.
2. Pick your favorite KDZ.
3. Select "PARTITION DL".
4. Press Start. And a pop-up window will appear. In this window you can select which partitions to be flashed.
5. Here, uncheck these partitions: SID_A and SID_B. It will make it able to bypass the OPID Mismatched Error.
6. If you are in Sprint or other platforms you will get the message whether to change the model or not. Of course you know what to do =)
after completing the process it will boot up in some minutes and before starting the customization it will do one restart. just be patient.
ERRORS, QUESTIONS, TROUBLESHOOTING
1. Can I crossflash V50, V60, G8X or other LG devices using this method?
I did it on V50. Maybe it'll work on your devices maybe won't. There's one way to find out; make backup and give it a try.
2. SN is gone, zero, etc.
Restore your original FTM.
3. I can't get into recovery.
Restore the original FTM.
4. I got NT-Code error.
It's been discussed many times in the thread and some solutions have been presented (such as this one, thanks to @animo214 and this, thanks to @kt-Froggy as well as this one, thanks to @StvOchi ). However, you can ignore it if the phone got network.
Note: You need to disable verity on the phone in advance otherwise changes in cust_path_mapping.cfg won't be saved.
5. IMEI is lost, zero, null etc.
Restore LUN5 partitions. If you have no backup it should be repaired using Octopus box. Go to 16.
6. I got "permanently locked" error.
This is because of IMPL lock and you have to restore LUN5 partitions. In case of having no backup you should use Octopus box.
7. All partitions are deleted accidentally.
Follow this instructions.
8. I need to get into PDM mode.
Unzip and restore the attached PDM to FTM partition. Remember, you need to restore your FTM to get into OS.
9. Can I use another phone's LUN5 backup?
NO.
10. Can I use another phone's FTM backup?
Yes. All partitions can be restored from another phone's backup except LUN5 partitions.
11. My phone is stuck in boot-loop.
Restore the original FTM and if it doesn't help redo the whole crossflash process and use a different KDZ this time.
12. Which KDZ is the best (for any matter of use)?
I do not know.
13. Can I crossflash from any source variant to Korean variant or vice versa?
Yes it is possible but you may get error on opening stock camera application because of hardware differences. There are some methods to solve the issue which you can search and find them.
14. Can I downgrade using this method?
Yes.
15. I erased partitions (ftm, op_a, op_b, modem_a, modem_b, sid_a, sid_b) but it still does not let me to crossflash.
Redo the whole process and this time make backup of and erase these partitions too, on both sides A and B: vendor, product, system, boot and userdata. Do not make backup of userdata partition.
16. How can I write IMEI?
A) Dump modem_a and create a copy of it. Then open it in UltraISO and remove IMEIPROT files from image folder. Save and restore it in place of modem_a and modem_b partitions.
B) Make backup of FTM and then flash or restore the PDM file (attached) into your ftm partition. Restart the phone; you'll get into PDM mode.
C) Open Tutty (attached). Select "Serial" in protocol and the proper port of your phone's modem driver. Click open. To test if you have selected the proper port number type "at" and hit enter it should respond"ok". Type the code at%imei=# (replace # with your IMEI) and hit enter. It doesn't matter you get "error" or "ok" after that, just check if IMEI is written via this code at%imei=?. If IMEI is written so you'll have the right MEID and ESN too.
D) Restore the original ftm and modem_a in place of modem_a and modem_b. Restart the phone.
I've already tested this method on V30, V50 and G8. Remember, if the phone has IMPL lock it'll throw "perm. locked" error even if you have written the IMEI.
17. I have lost GPT files of my LG G8, G8X, G8S, V50, etc. and Qfil partition manager does not show anything in the list.
You need to flash GPT files to your device with fh_loader (see this, part C). For that matter use KDZ_Tools to Extract DZ from a KDZ of your device. Then extract the DZ using -c at the end of extracting command. For example: unkdz -f FILE_NAME.kdz -c. It will extract all files besides all GPTs.
18. Which are the LUN5 partitions?
SM8150 has 7 physical partitions known as LUNs which are numbered from 0 to 6. Each LUN is split into several partitions. In Qfil Partition Manager you can see all partitions except those of LUN3 and LUN6 which are hidden. The number of LUNs are shown under the first column named LUN. Therefore, all partitions in front of number 5 are LUN5 partitions.
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
LG K31 Crossflashing:
To crossflash LG K31 go to this guide. Thanks to @Wish39.
LG Stylo 6 Crossflashing:
To crossflash LG Stylo 6 using LG K71 Android 12 firmware see this. Thanks to @Wish39.
LG V50 Crossflashing:
I had two LG V50 (LMV450) to which I flashed Korean Andorid 12 using the method mentioned in the first post. I cannot guarantee that it will work on every V50. After corssflashing I found out that one of them had the problem of draining battery due to not getting into deep sleep mode. To overcome the issue, I reflashed it via "Chip Erase" this time, and then again reflashed it but in the same way mentioned for crossflashing in the first post. Of course, I had created backup and at the end I restored LUN5 partitions.
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
great, thank you
netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
You didnt follow preparation correctly I guess?
netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
What OPID does it get assigned once you boot the device? OPEN_CA?
AsItLies said:
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
Click to expand...
Click to collapse
Like the a11 korean one?
cloud1250000 said:
You didnt follow preparation correctly I guess?
Click to expand...
Click to collapse
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
i got the same problem, just 3 options
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
AsItLies said:
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
How to make it?srry i cant understand
alright, G8x Sprint succesfully crossflashed to OPEN CA
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
Sebastian Thiago said:
i got the same problem, just 3 options
Click to expand...
Click to collapse
Azs5165 said:
How to make it?srry i cant understand
Click to expand...
Click to collapse
Follow preparation.
cloud1250000 said:
What OPID does it get assigned once you boot the device? OPEN_CA?
Click to expand...
Click to collapse
AsItLies said:
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Azs5165 said:
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Click to expand...
Click to collapse
Follow the steps in part C.
netmsm said:
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Click to expand...
Click to collapse
curious how the sprint v50 will react to this.. I`ll try this guide when korean A11 gets release.. I'll let you know..
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
cloud1250000 said:
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
Click to expand...
Click to collapse
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
netmsm said:
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
Click to expand...
Click to collapse
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
cloud1250000 said:
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
Click to expand...
Click to collapse
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
netmsm said:
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
Click to expand...
Click to collapse
can you check which mcfg is used? (field test > mcfg status)