Database Info

[Leak][Canada] i337m VLUFNC1 Kit Kat - Multicarrier package, Now with 100% less pit!

Through a well executed chain of private messages I managed to get a hold of a shiny new leak for us S4 users, Don't know if it will help you AT&T users much, But I'd love it if it did. For now, this is for Canadian users only, and can be used (Confirmed with Bell, and Telus) with any carrier
Included in this package are a few things:
1) BL, AP, CP, and CSC files for Odin
2) Odin v3.09 to be used for flashing (Not confirmed to work with any other version, So why not have the latest? )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions for Flashing
Root: Latest version of CF Auto root HERE (Seriously, go buy that guy a beer. http://www.chainfire.eu/ )
As far as flashing the package goes, all files need to be put in their respective shots as per the screenshot, you may need to flash 2-3 times in odin to get the whole package in there, like with most custom -> stock transitions.
The updated bootloader is the only real bummer here, overall a very nice package, fully rootable, works with Wanam Xposed for any of those curious, with very little as far as incompatible modules I can see.
One key change I'm missing personally is the lack of adaptive auto brightness... Can no longer increment -5/+5 on your auto brightness setting
Anyway, enough about it for now, here is the package link. Screenshots will be posted in a few minutes.
https://mega.co.nz/#!h8pTnCZS!t2-PiSb5W9ZyNp7fct7WD_Pg_dnc-eZqtMvpsuKv_9Q <-- Now with 100% less pit file!
I know some people were doubting the legitimacy of this in the Canadian thread, but I just finally got permission to post the leak from my source, since it's not carrier specific, and doesn't tie back to any one specific person. Heh.

downloading right now, will install it asap.
Thanks a lot 0mega1

Interested in trying this out...wondering if anyone has noticed any bugs or general performance issues? Also is it responsive on the S4?
Thanks,
0mega1 said:
Through a well executed chain of private messages I managed to get a hold of a shiny new leak for us S4 users, Don't know if it will help you AT&T users much, But I'd love it if it did. For now, this is for Canadian users only, and can be used (Confirmed with Bell, and Telus) with any carrier
Included in this package are a few things:
1) BL, AP, CP, and CSC files for Odin
2) The appropriate PIT file for the Canadian 16gb model
3) CF Auto Root package for Odin(Latest version as of posting) -- HUGE Thank you to chainfire for all of his work. http://www.chainfire.eu/
4) Odin v3.09 to be used for flashing (Not confirmed to work with any other version, So why not have the latest? )
Instructions for Flashing
As far as flashing the package goes, all files need to be put in their respective shots as per the screenshot, you may need to flash 2-3 times in odin to get the whole package in there, like with most custom -> stock transitions.
The updated bootloader is the only real bummer here, overall a very nice package, fully rootable, works with Wanam Xposed for any of those curious, with very little as far as incompatible modules I can see.
One key change I'm missing personally is the lack of adaptive auto brightness... Can no longer increment -5/+5 on your auto brightness setting
Anyway, enough about it for now, here is the package link. Screenshots will be posted in a few minutes.
https://mega.co.nz/#!ghpAhaaK!eXjKiZvQy9aUvy54AhXXAl14DJGVrot1msb6XOUlhgw
I know some people were doubting the legitimacy of this in the Canadian thread, but I just finally got permission to post the leak from my source, since it's not carrier specific, and doesn't tie back to any one specific person. Heh.
Click to expand...
Click to collapse

dahlungril said:
Interested in trying this out...wondering if anyone has noticed any bugs or general performance issues? Also is it responsive on the S4?
Thanks,
Click to expand...
Click to collapse
Up until I hear otherwise it is literally running on two phones, aside from whatever there is internally.
I've had zero issues since I flashed it yesterday, and battery has been great.

Very nice. Thanks for uploading. Can someone please provide and upload a system dump of this ROM? Having trouble with my ext4.img extract tools since 4.3.
Thanks.

I noticed that the pit file isn't in the package anywhere!

dont use pit files unless you NEED a pit file.
quick way to bork your phone
always check the post count of the Uploader.
less than 200 ? I would not follow his instructions. And i would only flash his leak, if my post count was higher and I knew what to do without reading some "new guy's" instructions

TRusselo said:
dont use pit files unless you NEED a pit file.
quick way to bork your phone
always check the post count of the Uploader.
less than 200 ? I would not follow his instructions. And i would only flash his leak, if my post count was higher and I knew what to do without reading some "new guy's" instructions
Click to expand...
Click to collapse
OP probably took the files and infos from here: http://true-android.blogspot.ca/2014/03/i337mvlufnc1-android-442-kitkat.html

I don't care where he got it, my point is only experts should be flashing leaked firmware.
Or to put it simply if you need instructions, don't flash it.
Sent from my SGH-I337M using Tapatalk

I've installed this using Odin. Can't get the modem file to stick. I'm stuck on MK6 for baseband. Wifi doesn't work as a result.
Did a complete wipe of System, Cache, Dalvik and Data.
I've tried reflashing the modem file a few times but it's not sticking. I'm attempting a reflash of the entire ROM right now to see if that does the trick.
Edit: It stuck after a second flash. Wifi works now.

Relayers said:
OP probably took the files and infos from here: http://true-android.blogspot.ca/2014/03/i337mvlufnc1-android-442-kitkat.html
Click to expand...
Click to collapse
That's my ****ing screenshot. Are you for real? I can submit the full resolution one if you'd like.
I've leaked a full early release before...
http://forum.xda-developers.com/showthread.php?t=868829
That was the official went-to-public build for the Telus Fascinate... Same deal.

TRusselo said:
dont use pit files unless you NEED a pit file.
quick way to bork your phone
always check the post count of the Uploader.
less than 200 ? I would not follow his instructions. And i would only flash his leak, if my post count was higher and I knew what to do without reading some "new guy's" instructions
Click to expand...
Click to collapse
I fail to see how my post count indicated the quality of what the release. This isn't the first time I've posted a leak here, might be the last though... Apparently the content doesn't matter so much as who is doing the work nowadays.

Hey, I'm thankful for the leak.

So where is the .pit file in the package? Or can we flash this without the .pit?
Thanks!

aiton said:
So where is the .pit file in the package? Or can we flash this without the .pit?
Thanks!
Click to expand...
Click to collapse
You don't need the .pit file. The OP should remove that from the instructions. Otherwise it's running smoothly.

TLS2000 said:
You don't need the .pit file. The OP should remove that from the instructions. Otherwise it's running smoothly.
Click to expand...
Click to collapse
Oh, ok, thanks. And just another question, if we're not using the .pit file, we should also uncheck the repartition box? (because .pit files will only need to be used if a firmware update needs to change your partition layout). Or how did you do it?
Thanks for the info!

modem.bin
Is it possible to pull the modem.bin file from here? I am running another kitkat rom but with MK6 would like to try this one......

aiton said:
Oh, ok, thanks. And just another question, if we're not using the .pit file, we should also uncheck the repartition box? (because .pit files will only need to be used if a firmware update needs to change your partition layout). Or how did you do it?
Thanks for the info!
Click to expand...
Click to collapse
It fails for me Re-Partition checked or unchecked. Any suggestions?

thank you very much!
works great on I337M Telcel Mexico

ChantalCaron13 said:
It fails for me Re-Partition checked or unchecked. Any suggestions?
Click to expand...
Click to collapse
where does it fails ?

HTC One E8 Lollipop Leaked? - RUU Link added

Please read this before you proceed:
1. The phone heats up a LOT
2. The battery consumption exceeds the charging speed, so using the device while it is charging will also drain battery (at idle state, it takes around 11 hours to charge)
3. You cannot install apps. You just can't. Don't be a smartass and say that you'll use ADB. That also won't work
4. It can get frustratingly sluggish
5. There isn't an RUU for the stable version out yet. I am trying to get one. Please refrain from trying this until I can upload a stable RUU file for you to fall back on (if a downgrade even works at all!)
6. This is a test version and logs a lot of stuff.
Once again, use it with caution! You have been warned.
So, after I read a few posts in the Lollipop update thread, I checked the ir-file.com website myself and found that they in fact do have an E8 lollipop leak (it is called M8 Ace by developers). Also, there's a bunch of other RUU on the website that isn't anywhere else. The OTA file that they are hosting seems to be the same one that I posted a few days ago to this forum.
What's the catch? It is paid. So, if anyone is a member on the website, would it be possible for you to try the RUU or at least mirror it?
The screenshot from the website is here: (LINK)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There's an Lollipop ROM out there guys. Let's go get it..
BTW.. Has anyone heard of or used this website? Its it possible that they could be fraud?
EDIT: Seems this thread is updated with the link: Thread | LINK to RUU

Even if I download this , how do I flash it, thru stock recovery ??

I'm as clueless.. In fact the first attempt I had at downloading this, I ended up with a corrupt archive. Now I'm downloading again.

Anyway the main thing here is that this is the first time we have seen indian RUUs for e8 or even m8 for that matter.
If not the lollipop I would definitely like to know if the other kit Kat Indian RUUs work or not.
If they do work, these are a real catch!!

Well, someone only posted the link to the Lollipop ones. And sadly, the archive posted seems to be corrupt.. :/

buggerman said:
Well, someone only posted the link to the Lollipop ones. And sadly, the archive posted seems to be corrupt.. :/
Click to expand...
Click to collapse
If I'm not mistaken HTC RUUs are encrypted so probably that archive is not corrupted at all.

Interesting.. In that case, how do you use it?

crystal_ball said:
If I'm not mistaken HTC RUUs are encrypted so probably that archive is not corrupted at all.
Click to expand...
Click to collapse
But those are .exe files. This is a zip, that just won't extract.. If there is some software to use these with, that would be an entirely different matter..

buggerman said:
But those are .exe files. This is a zip, that just won't extract.. If there is some software to use these with, that would be an entirely different matter..
Click to expand...
Click to collapse
Maybe these .zip are actually .exe files .
try renaming extensions and flash again, just guessing here.
BUT to flash any RUU, .zip or .exe, dont we need to be s-off ???

Ahh !! I remember these zip RUUs from the days when i had wildfire s. To flash this, u need to rename the zip file to OPAJIMG.zip and place in your sdcard. Then boot into boot loader, and it will automatically detect the zip file and start extracting it, and show you the status on top right (a coloured bar).
In the case of wildfire s, there was no internal memory. I'd suggest you place the zip file in both, internal and external sd.
And yeah, these files can't be extracted simply (AFAIK). Even you can't open boot.img or system.img, either by iso managers or winrar.
If the zip is really currupt, it would show in the bootloader. And even if it's a bogus file ( like made from another device's ruu or fake rubbish files), the extraction would stop!!
Hope I helped
Offtopic: I got a DOA for my E8 and got it replaced with one M8 EYE. You should be happy that there exists a page for E8 and a group of enthusiasts M8 eye is hopeless in terms of support

Kartik1807 said:
Ahh !! I remember these zip RUUs from the days when i had wildfire s. To flash this, u need to rename the zip file to OPAJIMG.zip and place in your sdcard. Then boot into boot loader, and it will automatically detect the zip file and start extracting it, and show you the status on top right (a coloured bar).
In the case of wildfire s, there was no internal memory. I'd suggest you place the zip file in both, internal and external sd.
And yeah, these files can't be extracted simply (AFAIK). Even you can't open boot.img or system.img, either by iso managers or winrar.
If the zip is really currupt, it would show in the bootloader. And even if it's a bogus file ( like made from another device's ruu or fake rubbish files), the extraction would stop!!
Hope I helped
Offtopic: I got a DOA for my E8 and got it replaced with one M8 EYE. You should be happy that there exists a page for E8 and a group of enthusiasts M8 eye is hopeless in terms of support
Click to expand...
Click to collapse
Thanks for the info dude.. Will check it out.
I thought the M8 Eye had decent support. It doesn't?

I can confirm that the image shared is legit. Just follow Kartik's instructions and you will have lollipop..
However, this is a test build, I think. I'd really like to shift back to KitKat..

buggerman said:
I can confirm that the image shared is legit. Just follow Kartik's instructions and you will have lollipop..
However, this is a test build, I think. I'd really like to shift back to KitKat..
Click to expand...
Click to collapse
is there's something wrong with it? or it's just unsuited to be daily driver?

I found out that after installing and configuring it you cannot install packages from Google play store... Others please confirm.

Please read the first post for details and warnings regarding this.

buggerman said:
Please read the first post for details and warnings regarding this.
Click to expand...
Click to collapse
Good warning and it does not look like a worthwhile test. Going to wait for the stable version, as HTC normally does a good job with these things

buggerman said:
Please read the first post for details and warnings regarding this.
Click to expand...
Click to collapse
thanks dude... This makes me wonder how long before we get an official update. hopefully in 2-3 weeks.

buggerman said:
Please read the first post for details and warnings regarding this.
Click to expand...
Click to collapse
The damage is already done ...
FYI, Your reply is after that ....

Well , I guess we have established that we just have to wait for the lollipop update from htc.
Meanwhile why dont we concentrate on getting the KK Indian ruu which is just above the loliipop ruu in ir-file.com .
I dont know how all the other e8 variants get RUUs but there are never for indian htc devices atleast for the m7 , m7 dual sim 802d, m8 etc.. , i'm talking about indian htc mobiles here.
We have FTFs for sony and tar.md5 for samsung so that when ever phone is soft bricked we can always use the corresponding stock fw to un-brick the device.
I googled with the below name but i could find the link only on ir-file which is possible to download only thru a paid account.
Code:
0pajimg_m8_ace_dwgl_k44_sense60_htc_asia_india_1.26.720.6_radio_1.12.30.0109_nv_nv_india_2.14_09b_release_420051_combined_signed.zip
So i would request indian users to find link for indian ruus.

iamsuperuser said:
Well , I guess we have established that we just have to wait for the lollipop update from htc.
Meanwhile why dont we concentrate on getting the KK Indian ruu which is just above the loliipop ruu in ir-file.com .
I dont know how all the other e8 variants get RUUs but there are never for indian htc devices atleast for the m7 , m7 dual sim 802d, m8 etc.. , i'm talking about indian htc mobiles here.
We have FTFs for sony and tar.md5 for samsung so that when ever phone is soft bricked we can always use the corresponding stock fw to un-brick the device.
I googled with the below name but i could find the link only on ir-file which is possible to download only thru a paid account.
Code:
0pajimg_m8_ace_dwgl_k44_sense60_htc_asia_india_1.26.720.6_radio_1.12.30.0109_nv_nv_india_2.14_09b_release_420051_combined_signed.zip
So i would request indian users to find link for indian ruus.
Click to expand...
Click to collapse
I am going to the service centre tomorrow.. Will try to get the file so that I can share it with you guys..

(SOLVED) Help Restore Lost IMEI & Serial No (SM-G920FD)

Hi, can someone guide me as to how I can restore my lost IMEI - Serial No back to stock? using SM-G920FD (duos)
Kindly refer below to the details of my problem and actions done.
How the issue happened
1. I'm currently on stock firmware of SM-G920FD (COH8). (Local copy of COH8 flashed via ODIN)
2. I received an OTA update (COI9) and installed it. Phone works perfectly fine.
3. After doing some tests on some kernel (arters97's kernels), I have decided to revert back to stock firmware since the kernel uses Note 5 gpu driver (not knowing that someone has prepared a flashable zip for S6 flat/edge) :crying:
4. I use my local copy of COH8 and flashed via ODIN. The flash failed thru sboot.bin - that tells me the bootloader is outdated on my phone *ugh.
5. I downloaded COI9 firmware from samfirmware site and flashed it via odin.
6. It is now stucked at first samsung logo. After going to recovery it says cannot mount /efs
Fixes I made
1. I dont know much stuff with efs thingy, that's why I didn't do a backup for it.
2. First fix, (this is the worst step I ever made - that costs me into this big trouble) I installed a "something" application that requires me to format the efs partition. Well done to myself, the app successfully wipe it all without backing up efs .
3. Now the phone is stucked to samsung first logo. Period. Even Reflashing stock via odin failed. Realizing the efs files are all messed up.
4. Now, after searching thru forums, Ive come into this adb command by running this, .
/system/xbin/su
mke2fs /dev/block/sda3
mount -t ext4 /dev/block/sda3
After doing this, Ive been able boot into device, I have a working WIFI, a valid ip address.
a. no bluetooth address
b. no imei for both sim 1 and sim 2
c. Incorrect Serial Number
d. No network of course
After deep searching thru xda, Ive come across with nv_data.bin editing thru Hex Editor. It could probably return my IMEI and Serial No back to normal(i still have the imei no & serial at the back of my phone ).
Perhaps, the only way to fix this will be on a repair shop to fix my imei. I doubt my samsung warranty would help since Im constantly flashing stuffs on my phone.
Can someone share me their full EFS folder zipped with Galaxy S6 SM-G920FD / G920F (probably a single sim will do) so I could compare and edit my own imei that would be a great help and I'll give a feedback asap.
Hoping someone can help me on this. Thank you

Anyone?
37 views of galaxy s6 owner and no one dares to share their efs

There is loads of information on the forums to recover lost IMEI. Did you try flashing a modem and bootloader update. This should generate the efs folder with nv_data.bin. You still may not have the correct IMEI and serial in the nv_data.bin, but at least you can edit it.
Search the forums I have seen loads and loads of tutorials for this problem.
Not many people are quick to give out there IMEI.

bahmonkeys said:
There is loads of information on the forums to recover lost IMEI. Did you try flashing a modem and bootloader update. This should generate the efs folder with nv_data.bin. You still may not have the correct IMEI and serial in the nv_data.bin, but at least you can edit it.
Search the forums I have seen loads and loads of tutorials for this problem.
Not many people are quick to give out there IMEI.
Click to expand...
Click to collapse
No, modem and bootloader flashing does nothing.
I do already have a pre-generated-stock nv_data.bin from my efs folder.
Can you give me an example of a working thread that requires editing of nv_data via editor that works?
The problem is that their issue has worked specifically on their device, none of the Galaxy S6 users were able to do that afaik. Almost a week since i started searching for answers but to no avail.
For example this, the thread below says that I should goto this address [offset] 00188008 but in my Galaxy S6 nv_data.bin, the file is only up to 000FFFF0 offset?? That's why I need help from others to at least share their fixes or comparison of this thread below with their nv_data.bin file. If there is similarity. Forget sharing your imei to me, but maybe you can consider how am I supposed to do that fix on the other thread.
Thanks
http://forum.xda-developers.com/showthread.php?t=881162

Or if someone can find their IMEI code in nv_data.bin, kindly share to me the offset (location) of the IMEI in hex editor. That would be a good start. Thanks

batuzai04123 said:
No, modem and bootloader flashing does nothing.
I do already have a pre-generated-stock nv_data.bin from my efs folder.
Can you give me an example of a working thread that requires editing of nv_data via editor that works?
The problem is that their issue has worked specifically on their device, none of the Galaxy S6 users were able to do that afaik. Almost a week since i started searching for answers but to no avail.
For example this, the thread below says that I should goto this address [offset] 00188008 but in my Galaxy S6 nv_data.bin, the file is only up to 000FFFF0 offset?? That's why I need help from others to at least share their fixes or comparison of this thread below with their nv_data.bin file. If there is similarity. Forget sharing your imei to me, but maybe you can consider how am I supposed to do that fix on the other thread.
Thanks
http://forum.xda-developers.com/showthread.php?t=881162
Click to expand...
Click to collapse
I can't remember exactly the offset location but I have seen it on my phone a few weeks back. I do remember seeing a few tutorials on YouTube. I will take a look tomorrow and if you haven't it solved by then I will help you fix it....

Thanks, hoping you could help me on that.
Something is weird on how efs is generated. I backed up the messed up nv data from efs folder. Then I deleted the contents of whole efs folder then reboot.
When phone booted, to my surprise I notice that it still generated the contents of efs. Then I compared the Newly generated nv_data to my backedup nv_data. No difference -_-. Still incorrect imei was given to me. 350000000000006 format both for sim 1 and sim 2.
Phone Info app says that my imei info (www.imei.info) was from an apple device rofl.
Since its giving me same and same imei and no product code/serial code
I suspect that my IMEI was generated from embedded hardware/chip??? But i think its not possible to mess any of the hardwareparts from flashing custom roms/zips/stock firmwares alone?

Hmm I think there's no chance for it to recover? since it is always giving me Generic Imei
One user says that it could be the hardware is somewhat corrupted or cant be modified blah blah
http://forum.xda-developers.com/showpost.php?p=30292696&postcount=185

Forget the EFS
Forget the NV
〔You should try to write cert〕!!!!!!!
Only in this way your phone will be working properly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 12:41 PM ---------- Previous post was at 12:39 PM ----------
batuzai04123 said:
Anyone?
37 views of galaxy s6 owner and no one dares to share their efs
Click to expand...
Click to collapse
This is my modified IMEI case success

china chenli said:
Forget the EFS
Forget the NV
〔You should try to write cert〕!!!!!!!
Only in this way your phone will be working properly
---------- Post added at 12:41 PM ---------- Previous post was at 12:39 PM ----------
This is my modified IMEI case success
Click to expand...
Click to collapse
You showed your edited IMEI on your phone, but you didn't share how ?
I think this is what Im looking for, but HOW???
1. What is that cert file? Can it be installed via phones system files?
2. Does it need third party app and a toolbox hardware to buy and install? It smells like its for technician part already :|
3. Since it needs key cert, how can I generate this? Thru the 3rd party also?
But FYI, Im not into modifying IMEI as it illegal, what I wanted to do is to restore my device's IMEI found at the back of my phone.

batuzai04123 said:
I think this is what Im looking for, but HOW???
1. What is that cert file? Can it be found via phones system files?
2. Does it need third party app and a toolbox hardware?
3. Since it needs key cert, how can I generate this? Thru the 3rd party also?
But FYI, Im not into modifying IMEI as it illegal, what I wanted to do is to restore my device's IMEI found at the back of my phone.
Click to expand...
Click to collapse
You have now lost the IMEI
If you still have flash the firmware is invalid
I think no way to restore the original IMEI
If change IMEI is illegal in your country, it would be a sad thing

ugh. Based from your pictures, you used 3rd party hardware tool and app something like octopus box and the likes.
You're telling me to give this to technician, as it is the only way to fix my issue?

china chenli said:
You have now lost the IMEI
If you still have flash the firmware is invalid
I think no way to restore the original IMEI
If change IMEI is illegal in your country, it would be a sad thing
Click to expand...
Click to collapse
Perhaps were not on the same page
What I wanted to do is to change my IMEI to stock IMEI (printed on my phone) so that it can connect legally to my network provider. If your way is good, maybe you can help me how to change my IMEI
Changing IMEI i.e., frying someones IMEI to hacked/stolen/blocklisted phones are definitely illegal.
Back to my issue, did you send your phone to technician/ did you have the box tool to flash cert files to your phone?
Hope you can help me thanks

batuzai04123 said:
ugh. Based from your pictures, you used 3rd party hardware tool and app something like octopus box and the likes.
You're telling me to give this to technician, as it is the only way to fix my issue?
Click to expand...
Click to collapse
Yes the octopus can do it
------------------------------------------------------------------
My English really bad, I speak a little bit more simple
If you don't have a backup EFS and your mobile phone and lost IMEI.
The solution is to use the BOX to write a new IMEI so that you will get a new IMEI
You write a new IMEI may and other mobile phone to repeat After doing this You will forfeit the warranty In addition to Will not affect the normal use of your phone
Samsung CERT is unique And only CERT must be the truth

china chenli said:
Yes the octopus can do it
------------------------------------------------------------------
My English really bad, I speak a little bit more simple
If you don't have a backup EFS and your mobile phone and lost IMEI.
The solution is to use the BOX to write a new IMEI so that you will get a new IMEI
You write a new IMEI may and other mobile phone to repeat After doing this You will forfeit the warranty In addition to Will not affect the normal use of your phone
Samsung CERT is unique And only CERT must be the truth
Click to expand...
Click to collapse
I get it. But this cant be done without using the box tools? Am I right?

batuzai04123 said:
I get it. But this cant be done without using the box tools? Am I right?
Click to expand...
Click to collapse
Yes, you need a BOX and a clean CERT

Well still thank you for the replies, only repair via technician is the only way . Requesting for mod to close the thread. No way the imei can be reverted back via EFS - NV way, flashing stock modem, backing and restoring efs, mke2fs thingy, flashing stock firmware and so on.
There is part on the chip of the phone that literally erases the phone info for my s6.
If any can give other ways before I let go HAHAHA, but please refrain from efs,nv_data,flashing stock stuff, as the firmware doesn't have to do with restoring efs. Only the hardware device stores efs info for our phone.

batuzai04123 said:
Well still thank you for the replies, only repair via technician is the only way . Requesting for mod to close the thread. No way the imei can be reverted back via EFS - NV way, flashing stock modem, backing and restoring efs, mke2fs thingy, flashing stock firmware and so on.
There is part on the chip of the phone that literally erases the phone info for my s6.
If any can give other ways before I let go HAHAHA, but please refrain from efs,nv_data,flashing stuffs, as the firmware doesn't have to do with restoring efs. Only the hardware device stores efs info for our phone.
Click to expand...
Click to collapse
If your phone is KNOX 0 x0
Then you can look for samsung to solve for you
I wish you good luck, my friend

Thanks , haha but my knox is 0x1 already

Tried to bring it to a legit 3rd party technician and they assigned a new IMEI for my phone and its working fine now.
imo I brought it first to Samsung and tells me that my warranty is void, but they can fix it via hardware replacement and would cost me at around $350. Lol no way!!!
For those who tried to do anything when all methods do not work, frustrations etc. This is the quickest way to restore it.
But thanks for the info I got from XDA members, now Ive learned that the first rule should be applied whenever possible before its too late.
To all other Explorers/newbies/Risk taker out there. Remember this one word.
BACKUP!!!!
Thanks.
To Mod:
Requesting for mod to close this thread thank you

Confusion about FW, flashing tools and process

Hi guys
I am sorry that my post is maybe very short but the original one was messed up by the system
So now I try it again and with a short version...
At first:
Thanks for help (a "flashing triple-noob") on xda :laugh:. I found so many informations (also before with other problems) and this was way beyond "help"-all of you get a great "thumbs up"!
And so far-the only experience in flashing was on my Xperia Z1 (de-brand) and it was quite easy but now it seems....uhmmmm....
So now go to my questions:
(hint: I want to use the stock FW no custom)
1.)
Anybody know the differences between the firmware version (no, I dont mean fingerprint ) of "Customized Hong Kong" and "CE1" for XZP Premium G8142?
Depends on the answer of this question maybe the next two dont need an answer
2.)
Question for newflasher:
I found and read many informations about flashing the FW but I getting more confused with more information!?
If I use newflasher the normal guide for that was veryyyy easy. And also at the moment newflasher is the only application for the XZ so > no other choice
But on the other side some user mentioned the following things:
-newflasher doesnt do a "full flash", something/files will be incomplete (means what? somebody have issues after flash?)
-delete parts of the files (like "things dont need" or "the partion folder")
-create partition folder (?)
So what is right and what is wrong?
Do I need to follow the easy tutorial or do I need to customize depends what happens during the flash?
3.)
Question for flashtool:
I know that currently flashtool doesnt support the XZP (still right?) even if its mentioned under "supported devices".
Also found (the generally) information that it isnt necessary to unlock the bootloader for flash a stock rom.
Now in flashtool description everybody can read: "...can only be used by Xperia™ devices having an unlocked boot loader..."???
But for unlock it needs to save the DRM keys before...and for this needs root.
But for root it needs to unlock the BL before...and this will erase the DRM keys before can save them.
So even if flashtool works on XZP the keys will be always lost?
Uhmm what I get wrong?
So thats my questions and I hope I can get some answers.
Because for the decision about the next device the XZP always comes back after compare with others (even it has a hybrid sim tray).
Thanks for help

Launch Flashtool/XperiFirm and download the fw you want. Either Nougat or Oreo.
Go into the fw folder, copy all the newflasher files and simply drop them into the fw folder, connect your phone in flashmode and doubleclick newflasher.exe
Wait until it has completed flashing and that's it!
IF you want to upgrade your fw later on without losing data, then you would have to delete some files yes, but for now just let everything be.
Sonie-User said:
Anybody know the differences between the firmware version (no, I dont mean fingerprint ) of "Customized Hong Kong" and "CE1" for XZP Premium G8142?
Click to expand...
Click to collapse
There's not really any difference, just go with what you want and it will be fine.
Sonie-User said:
-newflasher doesnt do a "full flash", something/files will be incomplete (means what? somebody have issues after flash?)
Click to expand...
Click to collapse
It does a proper flash if you leave the files intact.
Sonie-User said:
-delete parts of the files (like "things dont need" or "the partion folder")
Click to expand...
Click to collapse
Only delete certain files if you want to upgrade your fw without losing data.
Sonie-User said:
-create partition folder (?)
Click to expand...
Click to collapse
Just rightclick the rar file and extract into a folder "partition"
Sonie-User said:
So what is right and what is wrong?
Click to expand...
Click to collapse
You don't need to do anything.
Sonie-User said:
Uhmm what I get wrong?
Click to expand...
Click to collapse
You can flash without unlocking bootloader, don't worry.

Hi, thanks for reply.
I see your first post-its good that you dont see the first (messed up) post (because contains much more text )
FartyParty said:
Launch Flashtool/XperiFirm and download the fw you want. Either Nougat or Oreo.
Go into the fw folder, copy all the newflasher files and simply drop them into the fw folder, connect your phone in flashmode and doubleclick newflasher.exe
Wait until it has completed flashing and that's it!
IF you want to upgrade your fw later on without losing data, then you would have to delete some files yes, but for now just let everything be.
Click to expand...
Click to collapse
Sounds good and exactly the things I found first. Later (after tons of information from xda) the questions comes up. But now - seems the way it works :good:
There's not really any difference, just go with what you want and it will be fine.
Click to expand...
Click to collapse
Nice to know-so I can buy a randomly choosed XZP and the FW I want (at the moment all devices here dont have any google content in the FW) can be flashed afterwards
It does a proper flash if you leave the files intact.
Click to expand...
Click to collapse
Ok. I only getting confused about the written post on xda (maybe I can find it in my vistited sites to show you)
You can flash without unlocking bootloader, don't worry.
Click to expand...
Click to collapse
...also in Flashtool?

Sonie-User said:
...also in Flashtool?
Click to expand...
Click to collapse
No you use newflasher, Flashtool doesn't work with XZP.

So with newflasher you are meant to extract the partition.zip and put the contents in a partition folder in the same directory as the other files downloaded through XperiFirm right? If that's the case then how did I manage to update from Nougat to Oreo when I deleted the partition.zip file without extracting it and flashed the update?

LMV600TM Restore/Ugrade Guide a12

This restore process is intended for the Tmob V60 (lmv600tm) model and you must WIPE your data so back it up if you want to keep it!
This process will restore the lmv600tm to the state directly after the ota upgrade to the a12 v30b build. I’ve dumped all the required partitions from a MY personal lmv600tm. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently unable to boot or who just can’t access Tmob ota services and wishes to upgrade their lmv600tm to the a12 build. I have only tried this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from a Android 10 rom but I haven’t tried it.
This process will not fix your erased or damage imei number problem.
Steps
Download “Lmv600tm v30b Restore Partitions.7z” file from ???? and unzip. Remember the unzipped restore directory path.
Download “DriverBootandFirehose.zip” file from here and unzip. Remember the unzipped location.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose from where you unzipped “DriverBootandFirehose.zip”.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.
When complete phone reboots as I recall.

Thanks for shareing
I have a LG V600AM , Can I use this backup file to upgrade my phone?

As per the op this is for the T-Mobile model. I haven’t tested on the AT&T model.

zhh said:
Thanks for shareing
I have a LG V600AM , Can I use this backup file to upgrade my phone?
Click to expand...
Click to collapse
We still need A12 Att modems in order to work or somebody on Att model that makes that same dump the full A12 system :/ sadly I don't know no one

krissrmx said:
We still need A12 Att modems in order to work or somebody on Att model that makes that same dump the full A12 system :/ sadly I don't know no one
Click to expand...
Click to collapse
The AT&T version has 30a as of now.I'll make a LUNS copy,and upload it some where if you want it?

surgemanx said:
The AT&T version has 30a as of now.I'll make a LUNS copy,and upload it some where if you want it?
Click to expand...
Click to collapse
Sure

I want backup imei and everything file partitions network need.
How to backup? And partition name ?

Userdata.bin is missing in the archive.

dprast said:
I want backup imei and everything file partitions network need.
How to backup? And partition name ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Partition Manager and backup those yellow ones and you should be good

krissrmx said:
View attachment 5627813
Download Partition Manager and backup those yellow ones and you should be good
Click to expand...
Click to collapse
Edit: Partition Backup

krissrmx said:
View attachment 5627813
Download Partition Manager and backup those yellow ones and you should be good
Click to expand...
Click to collapse
thanks your info.. i've subcribe unlocktool and backup all my ufs data for safety before unlocking and customized my phone but i've problem . my phone in android 12. May security path since ubl fingerprint not working how to fix them? and how to disable anti rollback?

very good , i updated it on verizon .thanks so much ...

thienton1689 said:
very good , i updated it on verizon .thanks so much ...
Click to expand...
Click to collapse
You're welcome

TheLoonyRebel said:
Userdata.bin is missing in the archive.
Click to expand...
Click to collapse
You won't need userdata on a reflash.

zhh said:
Thanks for shareing
I have a LG V600AM , Can I use this backup file to upgrade my phone?
Click to expand...
Click to collapse
Did you manage to do this?

I can confirm that a LGV600Am -> LGV600TM works*. It is possible to crossflash a ATT (A10) to T-Mobile (A12) LG v60!* Yay and TY. As stated elsewhere good luck with 5G. It is suspected T-Mo is blacklisting LG now? My FingerPrint reader is broken. I had to use a weird hidden menu trick on the stock Att A10 when bootloader unlocked. This guide worked perfect except the firehose! Someone is handing out the prog__ufs_firehose_sm8250_ddr.elf and not correct file named prog__ufs_firehose_sm8250_lge.elf! I kept getting QFIL errors! I attached the proper version. Its getting hard to find for free!
Still learning about treble generation. Thanks for the dump! Hopefully there is a newer june/july update.
PS: Welp unlocked bootloader causes failed update & lg switch key attestation/ key deleted error. I would appreciate any help w/ 5G would be nice but not needed.
*= Broken 5G and No Fingerprint registration.

Bug725 said:
I can confirm that a LGV600Am -> LGV600TM works*. It is possible to crossflash a ATT (A10) to T-Mobile (A12) LG v60!* Yay and TY. As stated elsewhere good luck with 5G. It is suspected T-Mo is blacklisting LG now? My FingerPrint reader is broken. I had to use a weird hidden menu trick on the stock Att A10 when bootloader unlocked. This guide worked perfect except the firehose! Someone is handing out the prog__ufs_firehose_sm8250_ddr.elf and not correct file named prog__ufs_firehose_sm8250_lge.elf! I kept getting QFIL errors! I attached the proper version. Its getting hard to find for free!
Still learning about treble generation. Thanks for the dump! Hopefully there is a newer june/july update.
PS: Welp unlocked bootloader causes failed update & lg switch key attestation/ key deleted error. I would appreciate any help w/ 5G would be nice but not needed.
*= Broken 5G and No Fingerprint registration.
Click to expand...
Click to collapse
I update my T-Mobile version from A11 to A12 and encounter the same problem.
Using the .elf file from https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ (probably the same as you provided because both files share the same name) and updated the system successfully.
The bootloader unlock state is perserved (unlocked). However, I also find that the fingerprinter is broken (Enrollment was not completed: Fingerprint enrollment time limit reached).
Edit:
Fingerprint can be fixed by following the guide in https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/

Thanks above for this and to OP for the original walkthrough this saved my bootlooped device! Took me a couple tries to get QFIL to start the process but it worked for me.
Also if you're a v60 neophyte like me you can follow the first 4 steps from the bootloader unlock thread to get QFIL setup to run the OP's restore process.

showgood163 said:
I update my T-Mobile version from A11 to A12 and encounter the same problem.
Using the .elf file from https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ (probably the same as you provided because both files share the same name) and updated the system successfully.
The bootloader unlock state is perserved (unlocked). However, I also find that the fingerprinter is broken (Enrollment was not completed: Fingerprint enrollment time limit reached).
Edit:
Fingerprint can be fixed by following the guide in https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/
Click to expand...
Click to collapse
Yeah the FP doesnt work period (or random) on custom roms. 4got that part. I was able to get it working prior with a different post about accessing testing/service menu on Stock ROM. Ty anyway. I cannot type on laptop anymore b/c touch phone. Seems hit & miss. Im going to do a full kdz restore. I will be able to download the latest update. I may link it when I do.
My thinking is the a/b schemes. So I am super grateful for the flash files. I did some minor prodding and the files were initially for EA series. I saw build props & stuff that said so. My thinking is there is a Vendor &or Product partition update thats needed. Most likely a full up to date Vendor from US carriers.
Unfortunately an unlocked boot-loader deletes Google Certs. This is because the (unlock magic) Engineering or Test BL thats around is not signed or more likely not matching the rest of the boot chain.
I dont really know of a better way to access 5G info other than the *#INFO or phone util app.
I choose NR/LTE, then menu select band. Now interesting things happen here. Selecting US gets LTE but if I select Auto then I get LTE+...
jeez all of this b/c my replacement Note10+ was locked and unlock dude died from COVID (or is being held by Samsung all Umbrella Corp style). Apparently nobody else has the keys or license.
lastly sorry about length & incompleteness of dialer codes. I said yeh lets update Corvus using updater. When it was done it said done & slot switched! My other partition was full stock! Now I got bootloops. Im experimenting w/ dualboot...

Bug725 said:
Yeah the FP doesnt work period (or random) on custom roms. 4got that part. I was able to get it working prior with a different post about accessing testing/service menu on Stock ROM. Ty anyway. I cannot type on laptop anymore b/c touch phone. Seems hit & miss. Im going to do a full kdz restore. I will be able to download the latest update. I may link it when I do.
My thinking is the a/b schemes. So I am super grateful for the flash files. I did some minor prodding and the files were initially for EA series. I saw build props & stuff that said so. My thinking is there is a Vendor &or Product partition update thats needed. Most likely a full up to date Vendor from US carriers.
Unfortunately an unlocked boot-loader deletes Google Certs. This is because the (unlock magic) Engineering or Test BL thats around is not signed or more likely not matching the rest of the boot chain.
I dont really know of a better way to access 5G info other than the *#INFO or phone util app.
I choose NR/LTE, then menu select band. Now interesting things happen here. Selecting US gets LTE but if I select Auto then I get LTE+...
jeez all of this b/c my replacement Note10+ was locked and unlock dude died from COVID (or is being held by Samsung all Umbrella Corp style). Apparently nobody else has the keys or license.
lastly sorry about length & incompleteness of dialer codes. I said yeh lets update Corvus using updater. When it was done it said done & slot switched! My other partition was full stock! Now I got bootloops. Im experimenting w/ dualboot...
Click to expand...
Click to collapse
I also found that OTA updates fails w/ unlocked bootloader (didn't test on locked bootloader). Because of that I even don't have the chance to change the slot. I thought that it was the R/O system partition that caused the problem.
'unlocked boot-loader deletes Google Certs', I don't know the consequence of deleted Google Certs, willing to explain more?
I currently don't have a 5G SIM so I can't have a test on 5G problem.