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.
Related
Okay, here it is as promised. You need Clockworkmod Recovery installed but you don't need to be rooted to flash the zip.
I have created a flashable zip file to replace the stock apns-conf.xml with one that has settings for Simple Mobile. What I have done is made an apns-conf.xml file that has settings for virtually every gsm carrier worldwide with the main TMO settings changed to Simple Mobile settings. I wanted to have it backup the current one also but the Edify scripting language used by Clockworkmod Recovery doesn't have support for moving or copying a file. So if you want to back up the file first there are two ways. If you are rooted just use 'Root Explorer' and copy the file and then paste it back to the same directory (change to R/W first). The backup will show as apns-conf-copy.xml. The other way (root not required) is to connect to the phone by ADB and issue the following adb command:
> adb pull /system/etc/apns-conf.xml apns-conf-backup.xml
[Make sure the directory you are issuing the adb command from is not read only and you have full modify permissions if you are using Windows.]
To restore the file you can just use Root Explorer to delete the new one and then rename the copy back to apns-conf.xml. If you copied the original to your computer using adb then just change the backup to apn-conf.xml and use 7-zip to replace it with the one in my zip file and flash the zip package again. That will restore your original file.
I made two flashable zip packages. Both are flashed using Clockworkmod Recovery. Put the desired file on your internal or external sd card and flash it, then reboot. Afer rebooting go into Settings, Wireless & networks, Mobile network settings, Access Point Names. Click the menu button and then select "Reset to default." Then select the radio button for Simple Mobile to turn the selection green. T-Mobile will still show but the change to Simple Mobile should be persistent even if you shutoff or reboot the phone. If you change the sim you might need to select the Simple Mobile apn again (only first time). This apn setting is for internet and mms with Simple Mobile.
apns-4-simple.zip: Worldwide apn settings with Simple Mobile instead of TMO.
Download Link: http://www.mediafire.com/?8rovq05g7is2txs
MD5 checksum: 4db59ceeae1d80f14ca2d44ef04e61ed
apns-4-GB-stock.zip Restores the stock Gingerbread G2X file which has no settings for any carrier. TMO, Wind and Videotron are set elsewhere in the rom.
Download Link: http://www.mediafire.com/?lcxlg23tsk6cc46
MD5 checksum: bb7ef684edb88a69e831a20828a4ca4a
I tested this myself with an old T-Mobile sim I have. It worked and the change was persistent after rebooting and shutting off the phone.
This should fix your data connectivity problems.
Please note: If you have a stock rom this will prevent future OTA or LG Updater updates. Use the "apns-4-GB-stock.zip" to restore the file to stock GB T-Mobile G2X and then OTA and LG Updater updates will work. If you have a stock Froyo rom use one of the methods above to backup your original file so you can restore it later if you want to get an OTA or LG Updater update.
Enjoy!
THANK YOU
Hi jboxer,
Thank you very very much.. Its been quite a while I did adb and stuff the last time I did it was with HD2 last year I need to refresh my skills..
Anyways the phone is not with me and I will go home in the evening and try this fix and let you know..
Thank you very much for such detailed steps and description.
I will let u know how it goes as soon as I try it..
anush.isaac said:
Hi jboxer,
Thank you very very much.. Its been quite a while I did adb and stuff the last time I did it was with HD2 last year I need to refresh my skills..
Anyways the phone is not with me and I will go home in the evening and try this fix and let you know..
Thank you very much for such detailed steps and description.
I will let u know how it goes as soon as I try it..
Click to expand...
Click to collapse
It would have been nice to get some feedback after making the effort to fix this problem for you Simple Mobile users. anush.isaac, you said you would let us know as soon as you tried it out and we have been waiting four days now for your update.
question: What is APN? What does it do, and why does it need to be fixed. Sorry noob question. Im slowly learning about the android system. Some feedback would be nice. One more question: This works on T-Mobile???
*edit I just googled it.......can someone explain it to me in english, lol. I felt like I was reading in a different language.
Have the Same Problem
Hey all,
I was reading up and I have the same problem with my G2x.
I would like to try to use the solution that you provided but I have never done any rooting or modifying to my phone. I am not sure how to install the clockwork mod that you mentioned.
I only have access to a mac and in my experience that usually stops most attempts to modify my phone or other phones.
where can i find simple instructions on how to apply the flashable zip package and perform the Adb (not sure what this is)
Thanks in advance,
RR
Originally Posted by oceandographer
Well the settings from their site were correct. The android configuration is what was needed. It's not obvious how you activate the APN though. The technical support rep helped me figure it out but even he was like, "You have to get the green dot on that new APN. Try to drag it or just touch it.." Well you have to touch the radial button where the green dot should go, however, that is not good enough. You have to hold it down for awhile. Just the button. Then you get the green activation dot. There you have it.
Thanks for the help. You were correct, as was my assumption.
g2x activation at simple mobile.
Simple Mobile website--> Enter in Android config on a new APN--> Save and hold down the radial button long enough for it to turn green. From there, internet, gps, mms, etc. all work.
Ocean .. you are AWESOME. it worked like a charm , i kept searching around until i found your post, i'm gonna post this in another thread on here about the same issue if you don't mind. i'm sure many people are experiencing this issue
glad i didn't have to root ..why? my name says it all
ps. just make sure you do the drag first a couple of times "it wont actually drag the dot" but just do it a few times then hold like Ocean said until it turns green , i held it for 15 seconds at least
Sorry
jboxer said:
It would have been nice to get some feedback after making the effort to fix this problem for you Simple Mobile users. anush.isaac, you said you would let us know as soon as you tried it out and we have been waiting four days now for your update.
Click to expand...
Click to collapse
Hi jboxer,
I really apologize for not being able to get back to you quickly. I was help up at work for the past few days and could not try anything.
I have not Rooted a G2X before and I am a little concerned on how to do it. I did read the Instructions on this form but it is a little confusing. Let me confirm this with you, To apply your fix I know I need to Root the phone but is there another way without rooting the phone as I am afraid I might brick the phone.
Also In order to root the phone I followed this link http://forum.xda-developers.com/showthread.php?t=1255214 . So I just need to install the CLOCKWORK MOD RECOVERY and flash the root zip??
The phone is my Girlfriend's so I don't have access to it all the time.. I once again apologize for the late reply..
anush.isaac said:
Hi jboxer,
I really apologize for not being able to get back to you quickly. I was help up at work for the past few days and could not try anything.
I have not Rooted a G2X before and I am a little concerned on how to do it. I did read the Instructions on this form but it is a little confusing. Let me confirm this with you, To apply your fix I know I need to Root the phone but is there another way without rooting the phone as I am afraid I might brick the phone.
Also In order to root the phone I followed this link http://forum.xda-developers.com/showthread.php?t=1255214 . So I just need to install the CLOCKWORK MOD RECOVERY and flash the root zip??
The phone is my Girlfriend's so I don't have access to it all the time.. I once again apologize for the late reply..
Click to expand...
Click to collapse
No, you DO NOT need do root the phone to apply this. I stated that in my original thread and in others. You just need to install Clockworkmod recovery, boot into Clockworkmod and flash the APN zip and follow the instructions to restore to default apn settings. That's it. If you want to root then you can also flash the root zip at the same time or another time. The choice is yours and solely up to you.
Thanks
All day I've been trying to get the correct APN set up..and I come across your easy flash zip. It worked fine on my G2x and I have data! Thanks
dokjon said:
All day I've been trying to get the correct APN set up..and I come across your easy flash zip. It worked fine on my G2x and I have data! Thanks
Click to expand...
Click to collapse
Glad to help. Please click me a Thank You.
I've installed the zip and have followed the instructions over and over again, but somehow it keeps dropping out. i just upgraded to GB today (should have stayed with FY). the apn just keeps resetting to TMO over and over, my phone is completely screwed on data now thanks to GB. either way, anything you think i can do about the anp issue?
it just keeps failing or saying the connection timed out.
blink6966 said:
I've installed the zip and have followed the instructions over and over again, but somehow it keeps dropping out. i just upgraded to GB today (should have stayed with FY). the apn just keeps resetting to TMO over and over, my phone is completely screwed on data now thanks to GB. either way, anything you think i can do about the anp issue?
it just keeps failing or saying the connection timed out.
Click to expand...
Click to collapse
If you install my APN zip file the problem should go away. Once this is installed the APN has the same status as the TMO one so the phone should not want to switch back to TMO any more.
Im gonna give you guys another solution that does not involve flashing anything. I had this exact problem and here is what i did to fix. Blv me after you read this you wont believe it. Plus with the described methods in this forum about this issue, if you ever have to reset your phone, you will be back to the same problem again...having to flash that xml file.. read on..
First you need to get an unlock code for SIM unlock. I paid $2.80 on ebay for unlock code from unlock_fusion. Really cheap. You will not be able to create and save a new APN without the phone being unlocked. Now the default APN in the LG G2x is "T-MOBILE US" and you cannot delete it. Even if you root or unlock it cannot be removed. If you create the simple mobile APN as described in a matter of minutes it switches back to the tmobile APN which is a real pain in the a$$. The simple solution is to create another APN and name it exactly as your default APN which is "T-MOBILE US". Viola! Dont worry, it will allow you to save it with the same name but inside that APN you have the simple mobile configuration. It works without flashing anything. I added one thing extra to the simple mobile config APN type: default,mms,ota,agps
Thats it. you dont really have to add that but I did.
Note: This problem shows up after updating to android 2.3.3. before that, a simple unlock and adding the simple mobile APN worked fine.
Note:
to unlock requires that you put a sim card from a different carrier other than t-mobile for this phone. Also using the simplemobile sim card wont bring up the screen that asks for the sim unlock code. Use an AT&T sim card.. just borrow one from a friend. For those of you that dont know, simple mobile is what is called an MVNO (mobile virtual network operator) of t-mobile. They resell t-mobile's network which is why your 3G and 4G still works on simple mobile or any t-mobile phone that is used on simple mobile. You can also use a sim card from h2owireless as they are an MVNO of AT&T. So with that said, insert a different sim card and turn on the phone and you will see the screen come up asking for the unlock code. Do not enter anything that is not a real unlock code as too many tries will lock you out.
{
"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"
}
THANKS!
(I don't know, or can't find the "thank you" ikon on the page)
Found a fix that worked for me.
Nothing listed here fixed this issue for me. I eventually ran across APN Manager on the market. It works with root access and gives you full control over the APNs. I just made a backup then deleted the T-Mobile default one and now only Simple is there and always active.
simple
txnr70 said:
Nothing listed here fixed this issue for me. I eventually ran across APN Manager on the market. It works with root access and gives you full control over the APNs. I just made a backup then deleted the T-Mobile default one and now only Simple is there and always active.
Click to expand...
Click to collapse
John,
Funny its only you with that problem. Ive helped so many friends with this phone and the same problem and its resolved with what i posted. No root access needed. Only unlock code required and its cheap enough. Did you get unlock code for your phone? because you cant do what I posted (see picture link in my post) with out unlocking first. Please post exactly what changes you made because i dont think there is a root solution for the G2x/android 2.3.3. Post exactly what you did in the app you installed. thanks
pcdocta said:
John,
Funny its only you with that problem. Ive helped so many friends with this phone and the same problem and its resolved with what i posted. No root access needed. Only unlock code required and its cheap enough. Did you get unlock code for your phone? because you cant do what I posted (see picture link in my post) with out unlocking first. Please post exactly what changes you made because i dont think there is a root solution for the G2x/android 2.3.3. Post exactly what you did in the app you installed. thanks
Click to expand...
Click to collapse
No root solution? Look at my signature.
exactly my point.
Sent using XDA App
pcdocta said:
exactly my point.
Sent using XDA App
Click to expand...
Click to collapse
What is your point? The root solution is linked in my signature. GB stock is easily rootable.
blink6966 said:
I've installed the zip and have followed the instructions over and over again, but somehow it keeps dropping out. i just upgraded to GB today (should have stayed with FY). the apn just keeps resetting to TMO over and over, my phone is completely screwed on data now thanks to GB. either way, anything you think i can do about the anp issue?
it just keeps failing or saying the connection timed out.
Click to expand...
Click to collapse
I have discovered this is a framework issue also. I can make you a new framework and build.prop that should fix this issue once and for all. What rom are you using? I need your framework-res.apk file and your build.prop. I can fix them and make a flashable zip for you to install.
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
Below, not only will you find step by step instructions on how to root your device but also a FAQ section in post #2 that will guide you through the problems most of us encountered in the beginning. It is highly recommended that you read through all of it. Basic knowledge of ADB is required and if you don't have it then you should definitely read the FAQ section for ADB set up. Make sure you have all the files downloaded.
Update 10/25/2016: Attached at the end of this thread is a modified debloat script for knox removal and a few other apps. This will make your root experience a heck of a lot smoother than before. Just flash the zip using FlashFire without changing any settings. You may notice a reboot or two. There are few bloatware apps that will still be there (amazon shopping, amazon videos, amazon photos, etc) that you'll have to remove manually. Happy flashing and don't forget to hit that Thanks button down below!
Disclaimer:
This root method is NOT for beginners. It is NOT easy. If you don't get it then DON'T do it. Especially if you're worried about voiding the warranty and blah blah blah. Simply put, don't do it if you don't have the slightest idea of what you're doing. I'm tired of complaints. This guide is not for the faint of heart. Do this at your own risk!
Package Disabler Pro is required to get this rooting method working. Yes, it costs money ($.99) but it's the way I acheived this work around at the moment.
Be prepared to lose data (LTE) connection but don't be scared as it's an easy fix.
Make sure you don't have Secure startup set up before you start the process. Having this set up causes issues.
Must have ADB set up and installed system-wide.
This root method should be used with PE1 firmware for both the GS7 and the GS7 Edge. Although this root method might work with the latest firmware, users have been reporting issues dealing with APN's on the newest update. Look at post 2 FAQ's returning to stock for flashing PE1 firmware through Odin.
Do not update to PJ2 if you want to keep service with your root. Phone calls and text messages won't come through after rooting on PJ2.
Files you will need:
Odin by Princecomsy: http://www.filedropper.com/princecomsyodin
G935A: http://www.filedropper.com/samsungg935xqcrootedboot (S7 Edge)
G930A: http://d-h.st/o3hm (S7)
SuperSU: https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
Click on the BLUE "download" links. Extract everything into a folder easy to locate.
Here we go:
After downloading and getting set up Package Disabler Pro, you'll need to disable the following three packages:
samsung dm phone interface
samsung dm service
securityLogAgent.
Use the search box to easily find these packages.
Power off your device and boot into download/bootloader mode by pressing and holding the volume down, home, and the power button. Press volume up to get into bootloader.
Open PrinceComsy odin and flash the engineer boot.img by clicking AP and navigating to the file for your model. Click start and your device should reboot by itself.
Enable developer options by going to Settings>About Device and tapping Build Number till it shows Developer mode has been turned on. You will now have Developer options under the settings menu.
Enable USB debugging in the Developer options settings.
Extract the SuperSU zip and run the root.bat file. Your phone will reboot if the script is successfully ran.
Next, we'll get LTE data back:
Method A: BuildProp Editor (easiest method)
Open Build.Prop with BuildProp Editor and change the following settings:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
Make sure you grant root permissions when it asks. You may have to try this twice. Reboot and LTE should stick.
Method B: Manual activation (also if you're not able to make any calls)
Enable the three packages disabled in step 1. Go into the phone dialer and type in ##72786# and your phone should reboot and begin the activation process. After the 5th retry, it will manually activate itself. It should say "writing to device". Don't click done yet. Press the home button and disable the three packages once again. Reboot.
Alternatively, after renabling the three packages and dialing ##72786#, you can go into Settings>Activate this device and manually try to activate it yourself. It still must say "writing to device". Don't click done. Disable the packages once again. Reboot. Voice and LTE should stick.
Download S7_or_S7Edge_Fixes_V15.zip to your internal or external storage and install install FlashFire from the playstore.
Open FlashFire and let it acquire root access. Click the + button at the bottom right corner then click on Flash ZIP or OTA. Navigate and select the S7_or_S7Edge_Fixes_V15.zip. file. Leave the options alone and click the check in the top right. Scroll down to the bottom and click flash. Your phone will reboot and flash the zip. This can take a while.
Go to Settings>Lock screen and security>Other security settings>Security policy updates and turn off "Automatic updates" and "Wi-Fi only". Reboot. This seems to be the culprit of the 7 day soft brick.
Open back up Package Disabler Pro and search for "software update". Disable both packages (com.sec.android.soagent and com.wssyncmldm)
Enjoy your rooted device with minimal to almost no lag.
???
Profit.
As always, be sure to donate to the people who actually helped achieved root: @Princecosmy, @br3w3r, and @Chainfire
For the bounty donate to [email protected] PayPal
Shout out to @psouza4, @izzibew26, @mhill1986, @LeftyGR, @Soooperstar, and to all of you who are contributing in making this root method easier everyday. Thanks for the feedback.
Originally, it started getting interesting at post #185:
http://forum.xda-developers.com/att-galaxy-s7/how-to/bounty-att-s7-root-exploit-t3341274/page4
I'm also keeping track of the Sprint Galaxy S7 (SM-G930P) version:
http://forum.xda-developers.com/sprint-galaxy-s7/how-to/sm-g930p-root-t3410604
FAQ's:
My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Download BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Credit goes out to: @guaneet for this fix
Can I install Xposed?
A: Yep. Here's how to do it:
fnztakedown said:
Alright. Here is a DB link of the two files I had installed to get xposed working. To flash this you will need flashfire.
Process is simple. Download both files and install the apk.
Open flashfire> select flash new file> find the xposed zip, flash. Give it a solid 5-7 minutes during boot up.
Ensure you do not have any major packages disabled and ensure you have BACKED UP YOUR ROM VIA FLASHFIRE. Please be aware, this was successful for me on the 935T and I do have random reboots at time. I cannot confirm this is the cause yet. I would also suggest finding the uninstall zip in the event you have issues you can flashfire back.
{
"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"
}
https://www.dropbox.com/sh/0yabdfx6ao69dpd/AAAnu-9Jv8W9stjjuG1Nq5jba?dl=0
Click to expand...
Click to collapse
Credit goes out to: @fnztakedown for these instructions
I'm having issues with ADB. Any help?
A: Easiest way to install ADB and its subsequent drivers would be to get it from here:
http://forum.xda-developers.com/showthread.php?t=2588979
It's SO easy to install and it takes most if not all of the hassle out of it.
Credit to @Snoop05 for this easy ADB installer.
How do I enable USB debugging?
A: Go to Settings>About device and tap Build number until it shows Developer options has been enabled.
I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. If you keep on getting stuck at the LTE splash screen you may have to factory reset your device. As soon as your phone restart quickly press the volume up + home + power button and let it boot into recovery. Wipe data/factory reset and cache partition.
I'd like to unroot and return to factory stock. How would I go about this?
A: Head on over to @psouza4's post HERE and follow his steps in the return to stock section. The steps are easy and he's posted mostly all the firmware.
[*]Does this method trip Knox?
A: No, it doesn't. And flashing back to stock will allow Knox to work again, as long as you didn't flash files from other sources (there are some that will trip Knox, so be careful).
[*]Does Samsung Pay work?
A: No, sorry. They can detect the rooted boot environment through a driver, so you can't even hide root from the app using RootCloak.
[*]Does Android Pay work?
A: It does, but you have to make a change that disables root and then reboot your phone. You can toggle this back/forth without flashing, but you either get root or Android Pay at any one time.
[*]What happens if I brick my phone?
A: As long as there are stock images to flash back to, it's almost impossible to do this no matter how badly the process goes. Check that we have stock images; if we do, then we can always flash them over the device using the unroot method in this guide. That practically guarantees a return-to-stock experience for a phone as long as it doesn't have any serious physical damage preventing it from powering on.
[*]I installed the ADB system-wide on my Windows computer/laptop, but I see "'adb' is not recognized as an internal or external command, operable program or batch file".
A: Your user profile path can't contain a space. That means if your Windows user is 'Somebody Nice' and thus your Windows user path is 'C:\Users\Somebody Nice', the install will fail. You can create another user on your computer (if prompted for a Microsoft login, choose to make only a local account) and enter a short, single-word name for your user. Sign into and use that user profile instead. Also, the path where you extract the SuperSU package can't contain a space, so try extracting them to somewhere simple like perhaps C:\S7Root.
More answers to FAQ's to come.
PF2 will not activate for me.
mrboost said:
PF2 will not activate for me.
Click to expand...
Click to collapse
Like to make calls and what not? Try going into the dialer and type ##72786#
I sure miss root. I read Samsung will be releasing factory unlocked phones that support all US Carriers however that doesn't necessarily the bootloader will be unlocked.
Awesome. Cant wait.
Sent from my SM-G935P using XDA-Developers mobile app
mrboost said:
PF2 will not activate for me.
Click to expand...
Click to collapse
Got mine finally activated by going through the system settings and clicking "Activate Device". Alternatively, after the 5th retry, this will automatically happen.
any update on what does and doesnt work? i have a PF2 s7 edge and im anxious to use this but wont if it breaks my samsung pay or gear 2 usability
rhyme187 said:
any update on what does and doesnt work? i have a PF2 s7 edge and im anxious to use this but wont if it breaks my samsung pay or gear 2 usability
Click to expand...
Click to collapse
Breaks Sam Pay. Root will always break it.
LeftyGR said:
Breaks Sam Pay. Root will always break it.
Click to expand...
Click to collapse
This is correct.
Sorry, I've been away and just got back to my computer. So far it seems that I am having issues activating the device after flashing the engineer boot.img through odin. It seems that after the 5th retry it will activate and write to device but will then restart and the whole activation process will start back over. I'm trying to see if I can use disabler pro to stop the reactivation process and I'll see where it goes from there.
My S7 is unlocked and with the activation problem, I feel I already know the answer, shouldn't affect me, right?
Since it's a matter of punching in APN info
TehPirate_ said:
My S7 is unlocked and with the activation problem, I feel I already know the answer, shouldn't affect me, right?
Since it's a matter of punching in APN info
Click to expand...
Click to collapse
Try it and let us know. And if it works, let us know the APN info would you?
I figured it was something to do with the APN info too but when I hit up my friend about the APN info (who isn't rooted) he told me the information was grayed out so I couldn't get a hold of the info.
My S7 edge SM-G935v is working great But running very HOT!!! Any Fixes?
colormedroid said:
Try it and let us know. And if it works, let us know the APN info would you?
I figured it was something to do with the APN info too but when I hit up my friend about the APN info (who isn't rooted) he told me the information was grayed out so I couldn't get a hold of the info.
Click to expand...
Click to collapse
Well the APN info would be for Cricket. Wouldn't be relevant.
melona380 said:
My S7 edge SM-G935v is working great But running very HOT!!! Any Fixes?
Click to expand...
Click to collapse
Unfortunately no, I only have the G935P and mine does not run hot after doing the above mentioned. Good luck to you and let us know if you figure anything out.
TehPirate_ said:
Well the APN info would be for Cricket. Wouldn't be relevant.
Click to expand...
Click to collapse
True! Thanks anyways! I was just hoping that ppl wouldn't have to spend money on package disable pro and it thus it would be a free solution.
Still getting reboots. It connects to LTE and does fine for a few minutes. Then it'll reboot randomly. I disabled the DM service as suggested. I also disabled System Update and Software Update. Thoughts?
EDIT: Also, it says Samsung in the top left corner and not Sprint. Just an observation.
sirslipzalot said:
Still getting reboots. It connects to LTE and does fine for a few minutes. Then it'll reboot randomly. I disabled the DM service as suggested. I also disabled System Update and Software Update. Thoughts?
EDIT: Also, it says Samsung in the top left corner and not Sprint. Just an observation.
Click to expand...
Click to collapse
What software version are you on? Did you disable the DM service AFTER your phone was activated? And just to make sure, your phone is the Sprint version?
colormedroid said:
What software version are you on? Did you disable the DM service AFTER your phone was activated? And just to make sure, your phone is the Sprint version?
Click to expand...
Click to collapse
I'm on PD3. I did disable DM AFTER activation. And yes, I'm on the G935P.
sirslipzalot said:
I'm on PD3. I did disable DM AFTER activation. And yes, I'm on the G935P.
Click to expand...
Click to collapse
Hmm.... I had issues with it rebooting on me randomly too at the beginning. It wasn't until I got home and after a few wipes that I didn't notice it afterwards. Might want to try a wipe or two and try it again.
Sent from my SM-G935P using Tapatalk
Hi guys
I know the creator of Newflasher has been removed, and so has his tutorial and useful information in the crossdevice section....
But does anyone have a good tutorial and also a confirmed working version of newflasher so that I can flash my XZP to a generic Australian version?
Really much appreciated!
Cheers
Hi!
I just flashed my XZP, read here
I used the tutorial here, except put all the *.sin files in the directory and flashed. This one kinda explains much more than yours Lorehaze
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16''
cheetah2k said:
I used the tutorial here, except put all the *.sin files in the directory and flashed. This one kinda explains much more than yours Lorehaze
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16''
Click to expand...
Click to collapse
not good to flash *.ta files sir
cheetah2k said:
Hi guys
I know the creator of Newflasher has been removed, and so has his tutorial and useful information in the crossdevice section....
But does anyone have a good tutorial and also a confirmed working version of newflasher so that I can flash my XZP to a generic Australian version?
Really much appreciated!
Cheers
Click to expand...
Click to collapse
I have both version stored on my mega account, linking below.
I recommend using the older version. I don't trust the most recent after he got banned.
Here's the older version.
Here's the most recent.
Thanks for your help guys. Flashing mine went smooth and easy
cheetah2k said:
Thanks for your help guys. Flashing mine went smooth and easy
Click to expand...
Click to collapse
did u exclude all .ta files??
Lorehaze said:
did u exclude all .ta files??
Click to expand...
Click to collapse
Yes
Do not use any of the *.ta files. Only copy the *sin files across (except for the userdata - but this made no difference anyways as my userdata was corrupt after the flash).
My aim was to change from Vodafone Australia, to Australian Generic (sony shop) firmware so that I would get all the latest updates quick, instead of waiting for carrier updates (which take ages).
I did not change countries.
So I used newflasher to do all the *.sin files from the Australian Generic firmware to the phone. After the first boot post flashing, I got the "your password is correct, but your user data is corrupt - Reset Phone" warning. I let it reset the phone, then before doing anything else, I powered it off and went to Sony Companion and then did a software recovery (full wipe and full 1.5gb flash) so that if there was anything I missed in the flashing, it would be picked up in the official Sony Companion flash.
Worked a charm. I used to do the a similar method with flashtool on the older Sony phones, especially where some user compiled FTF files had others userdata on them.
Cheers
cheetah2k said:
Yes
Do not use any of the *.ta files. Only copy the *sin files across (except for the userdata - but this made no difference anyways as my userdata was corrupt after the flash).
My aim was to change from Vodafone Australia, to Australian Generic (sony shop) firmware so that I would get all the latest updates quick, instead of waiting for carrier updates (which take ages).
I did not change countries.
So I used newflasher to do all the *.sin files from the Australian Generic firmware to the phone. After the first boot post flashing, I got the "your password is correct, but your user data is corrupt - Reset Phone" warning. I let it reset the phone, then before doing anything else, I powered it off and went to Sony Companion and then did a software recovery (full wipe and full 1.5gb flash) so that if there was anything I missed in the flashing, it would be picked up in the official Sony Companion flash.
Worked a charm. I used to do the a similar method with flashtool on the older Sony phones, especially where some user compiled FTF files had others userdata on them.
Cheers
Click to expand...
Click to collapse
Thanks for that dude, going to try that tonight to unbrand my Telstra XZP. Just a question though - Where you said to not use any of the *.ta files, and ONLY the *.sin files across - You mentioned you used all of the *.sin except userdata, but if I were to copy the userdata file over as well, would that matter or do anything bad?
Edit: Also - There's a *.ta file in the boot folder for the FW, do I exclude this also?
Guessing that excluding the *.ta files will ensure the TA partition will be left intact to not affect DRM, etc.
Thanks man.
laes443 said:
Thanks for that dude, going to try that tonight to unbrand my Telstra XZP. Just a question though - Where you said to not use any of the *.ta files, and ONLY the *.sin files across - You mentioned you used all of the *.sin except userdata, but if I were to copy the userdata file over as well, would that matter or do anything bad?
Edit: Also - There's a *.ta file in the boot folder for the FW, do I exclude this also?
Guessing that excluding the *.ta files will ensure the TA partition will be left intact to not affect DRM, etc.
Thanks man.
Click to expand...
Click to collapse
cheetah2k said:
Yes
Do not use any of the *.ta files. Only copy the *sin files across (except for the userdata - but this made no difference anyways as my userdata was corrupt after the flash).
My aim was to change from Vodafone Australia, to Australian Generic (sony shop) firmware so that I would get all the latest updates quick, instead of waiting for carrier updates (which take ages).
I did not change countries.
So I used newflasher to do all the *.sin files from the Australian Generic firmware to the phone. After the first boot post flashing, I got the "your password is correct, but your user data is corrupt - Reset Phone" warning. I let it reset the phone, then before doing anything else, I powered it off and went to Sony Companion and then did a software recovery (full wipe and full 1.5gb flash) so that if there was anything I missed in the flashing, it would be picked up in the official Sony Companion flash.
Worked a charm. I used to do the a similar method with flashtool on the older Sony phones, especially where some user compiled FTF files had others userdata on them.
Cheers
Click to expand...
Click to collapse
Hey I just followed your instructions, excluded all TA files including the one in the BOOT folde r- Worked perfectly as you said, just restored in Xperia Companion! Thanks mate!
laes443 said:
Hey I just followed your instructions, excluded all TA files including the one in the BOOT folde r- Worked perfectly as you said, just restored in Xperia Companion! Thanks mate!
Click to expand...
Click to collapse
Good news! enjoy
I'm currently developing a tool for XZP. I will integrate a working flasher and some other tools. What is still missing for me at the moment, is a working hack for the DRM. I've been biting my teeth for days. I am currently trying to understand the process better. I just look at the respective files in IDA and my head smokes. If someone finds a usable approach, let me know. I would integrate the whole thing into the tool.
What I can safely say is that previous versions of the DRM fix do not run, but still have an effect. Without DRM fix the Google camera runs almost without problems and the system camera makes green pictures. With the DRM fix the Google Camera makes green pictures. So the approach does not have to be wrong.
{
"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"
}
sToRm// said:
I'm currently developing a tool for XZP.
Click to expand...
Click to collapse
You will make many people happy with your tool considering we desperately need a safe and reliable one!
I'm sure most would love to ditch NewFlasher as it's... not very safe considering who it comes from.
It would be amazing if you could release it asap when you feel it's stable.
I just picked up a new XZP Pink and I don't wanna use NewFlasher on it.
Keep up the good work :good::good:
This is android app, right?
Windows
Realy? Probably it will use new flasher? Or still newflasher?
** USE THIS AT YOUR OWN RISK.
** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS.
** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE.
** BACKUP YOUR WORKING MODEMST1/2 AND PERSIST PARTITION IMAGES WITH BEFORE CONTINUING. THESE PARTITIONS ARE DEVICE UNIQUE, SO IF SOMETHING HAPPENS TO THESE PARTITIONS DURING THE CONVERSION, AND YOU DON'T HAVE A BACKUP, NOT EVEN MSM DOWNLOAD TOOL CAN SAVE YOU. YOU'LL HAVE TO SEND YOUR DEVICE BACK TO ONEPLUS FOR REPAIR. If YOUR PHONE IS ALREADY ROOTED, I RECOMMEND USING PARTITIONS BACKUP AND RESTORE TO DO THIS. JUST REMEMBER TO COPY YOUR BACKUPS OFF YOUR PHONE BEFORE YOU GET STARTED.
** BE SURE TO HAVE MSM DOWNLOAD TOOL AT THE READY FOR IF SOMETHING DOES HAPPEN. FOR THE T-MOBILE ONEPLUS 9, YOU CAN GET IT HERE: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
THIS METHOD REQUIRES AN UNLOCKED SIM AND BOOTLOADER
If you don't wish to unlock either, craznazn has released a MSM conversion package you can use to acomplish the same thing without requiring ether to be unlocked. Just download the package from their post, and follow the steps on their 8T MSM Conversion guide, as the steps should mostly be identical.
* I've successfully done this ONCE on my own personal T-Mobile OnePlus 9
* The script used here is just the same one made by craznazn to convert the T-Mobile OnePlus 9 Pro to EU firmware. I just swapped EU OnePlus 9 Pro images for the Global OnePlus 9 images and wrote a bash script for non-Windows users to use. You can just download my conversion package and follow their steps if you want. Just for convenience I'll also be writing the steps on how to use it here as well.
* You can drag and drop my bash script into craznazn's conversion package to use their package on non-Windows systems. You can download the bash script by itself here: https://gist.github.com/Lomeli12/73825a287d3cf60414e244aece9b6bdf
* This package will install Global Firmware 11.2.2.2. You'll need to use Oxygen Updater to update it to the current version (or at least until System Update can do it for you).
* Use the latest platform tools, either from https://developer.android.com/studio/releases/platform-tools or through your package manager of choice (apt, brew, scoop, etc). DO NOT USE MINIMAL ADB, it has not been updated for years.
* If you're having issues with either adb or fastboot detecting your device, consider installing the Universal ADB Driver.
* Have any issues? Describe the steps you take, copy the script's output log, and take screenshots. Include the output of fastboot --version in your post.
Now with all that out of the way...
Steps to convert your T-Mobile OnePlus 9 to the Global (or other) firmware
Unlock your bootloader and SIM. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
Global 11.2.2.2
MD5: 14e0c5e41df26bacbc11fe7e69a63c0e
SHA256: 10801f12c50e2d9a7e8085d113ac4a90ab312018beb84a10fa4c1a0f84fc95eb
Google Drive: https://drive.google.com/file/d/1h7Hpbde40wLYynUIo83TTIoERhA_04nS/view
AndroidFileHost: https://www.androidfilehost.com/?fid=2188818919693806454
Spoiler: If you want to use a newer or different region firmware, delete all the *.img files from my conversion package and do the following:
Download and unzip the firmware you want from the OxygenOS Repo thread. You'll specifically want to extract the payload.bin file.
Install Python 3 and Python Protobuf. Figure out how to do this on your own system.
Download cyxx's extract android ota payload script from GitHub: https://github.com/cyxx/extract_android_ota_payload/
Place the payload.bin you extracted earlier into the same directory as the extract_android_ota_payload.py script.
Run the extraction script and wait. This step usually takes a while to complete
Bash:
python3 extract_android_ota_payload.py payload.bin tmp/
Open up the tmp folder the script created and copy all the image files from there over to where flash_all scripts are located.
Boot to bootloader
From adb:
Bash:
adb reboot bootloader
From fastboot/bootloader:
Bash:
fastboot reboot bootloader
Execute either flash_all.bat or flash_all.sh from the unzipped conversion package.
Reboot into recovery and wipe everything
Once fully booted and setup, use Oxygen Updaterto update your phone to the latest version the app provides. Oxygen Updater will provide steps on how to use the full OTA zip.
After you've updated using Oxygen Updater, go into Settings -> System -> System Updates and check for new updates, as Oxygen Updater usually takes a few days to have the absolute latest OTA available. If there is another update available, go ahead and let the System Updater do its thing.
Do a regular system reboot, NOT into recovery, bootloader, or fastbootd.
NOTE: The following steps (8-10) may or may not be optional, we haven't 100% figured it out yet
Repeat step 3 to get back into the bootloader.
Flash the T-Mobile modem included in the conversion package
Bash:
fastboot flash modem NON-HLOS.bin
After each full OTA you take in the future, repeat steps 8 and 9 again.
Fixing SafetyNet by installing Magisk
When I first did this on my own phone, my phone would fail SafetyNet, specifically with a CTS Profile Mismatch. Once I installed Magisk and enabled MagiskHide, however, SafetyNet was passed once more. No MagiskHidePropConfig or UniversalSafetyNetFix required. Here are the steps I did.
Make sure you've updated your phone to the absolute latest version of OxygenOS you can. See step 6 of the conversion steps on how to do so.
Copy the boot.img from the conversion package onto your phone.
Install Magisk Manager onto your phone.
Open Magisk Manager and patch boot.img
Tap Install
Select Select and Patch a file and tap Let's Go
Choose the boot.img file we copied over and hit okay
Once the patch is finished, copy the patched boot.img back onto your PC. Magisk Manager usually puts it in your phone's downloads folder as magisk_patched-<current magisk version>_<random string of characters>.img. The logs in Magisk Manager will tell you exactly what it named the patch image as.
Boot to your bootloader. See step 3 of the conversion steps for this.
Boot your phone using the patched boot.img
Bash:
fastboot boot magisk_patched-<current magisk version>_<random string of characters>.img
Once your phone has booted up, open Magisk Manager once more
Go into Magisk Manager settings and enable MagiskHide.
Back out of the settings and install Magisk via Direct Install
Reboot your phone normally. You should now have Magisk and pass SafetyNet.
Issues so far:
Using EdXposed Hide on the Google Play Store or Google Play Services can cause a soft brick requiring resetting your device via recovery. No issues with LSPosed so far.
Google Phone dialer doesn't display option for Visual Voice Mail. The T-Mobile Visual Voicemail app can be used though.
What appears to work:
Everything else
Edit 1 (5/17/2021):
Fixed some wording that I felt was awkward after the fact.
Made a note that flashing the T-Mobile modem may be optional, still up in the air on that.
Included download mirror for AndroidFileHost.
Listed EdXposed softbrick reported by @Josh McGrath.
Edit 2 (5/19/2021):
Added note about VVM missing from Google Dialer, but T-Mobile VVM app being a good alternative.
Adjusted phrasing in modem flashing steps
Edit 3 (6/7/2021):
Added link to craznazn's MSM conversion tool, which is a good alternative for those who don't want to unlock their bootloader.
Excellent. I've been waiting for this. For partition backup, using the MSM readback functionality (password is usually oneplus) is also an option.
If the OP9 is anything like the OP8T, a direct Euro conversion would be better for quicker updates.
Getting to Euro from Global in a GUI-based approach is also possible. Just set the device ID to OnePlus 9 (EU) in Oxygen Updater and follow the rest of the main guide. You might need to enable advanced settings and ignore device mismatch warnings though. Assuming you are already rooted at this point, you can keep root after the local upgrade, but before rebooting, by flashing Magisk to the inactive slot. Modem still needs to be reflashed.
Modem in general is going to be a pain. Somebody will need to extract it from each T-Mobile OTA if you want fixes and new carrier aggregation combos.
Note: I have not tested this and this is not advice. Follow at your own risk.
He said the TMobile modem files were in the download. Are those 2 files not the correct ones or something?
Or are you just talking about updating the modem every time Tmo sends out an update. (which is usually every 3 months )
Talking about modems in OTAs.
That will be a pain to get any updated modem images, but 1) we just need one person who's willing to stay on the T-Mobile firmware and dump it. Just need to find this willing person and 2) like @Josh McGrath said, expecting T-Mobile OTAs to come frequently, especially those with substantially changes to the modem.img, might be giving T-Mobile too much credit.
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Jg1234 said:
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Click to expand...
Click to collapse
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Lomeli12 said:
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Click to expand...
Click to collapse
I know they have trouble with the pro version, so far I haven't had any issues. I will report back after the weekend and test it more while I travel, but don't think that will make a difference. Maybe others can test too!
I was about to do this but I've been using Minimal ADB of course but I downloaded platform tools from the link, unzipped it and ADB.exe won't work. It immediately closed.
Anyone had this issue?
And I didn't read that sentence correctly. Any specifics on what adb error ya got
No prob on the misreading my post bro.
There are no errors, it just simply will not stay open. It opens and immediately closed down. I've downloaded it twice already. Any idea? Win 10
Again, sorry. Completely misread the sentence. Without getting logs or anything more specific than "adb.exe isn't working", we can't really help you.
Not a problem. And yes I totally understand that. I was hoping it was a known easy fix that someone knew but I guess not. But thanks for your help anyhow and will ask again if I can't get it working and get the logs.
Just to test things out and see if adb is working, verify that you don't have minimal adb installed anymore and run
Bash:
adb devices > log.txt
and copy whatever got piped into log.txt.
Minimal ADB is too old. Follow directions.
You may need to set PATH for ADB or put everything in the same folder.
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Josh McGrath said:
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Click to expand...
Click to collapse
Good that you've resolved your issue. I've only tried with LSPosed without issue or triggering SafetyNet, but I'll make a note of it for EdXposed.
After replacing the flash, does the VVM voicemail in the dialer work?
After replacing the flash, does the VVM voicemail in the dialer work?
iSkyJIE said:
After replacing the flash, does the VVM voicemail in the dialer work?
Click to expand...
Click to collapse
Can confirm Visual Voicemail does work, so does the Dialer.. Although, i don't recognize the dialer as the oneplus stock one... someone else may be of better use for an answer for that, as I have never used the stock dialer. Although, one slight issue with the conversion.. And it doesn't seem as if anyone else is having this problem.. After I updated to 11.2.4.4 via oxygen updater, I can't get OTA to work.. It starts for two seconds and says Update Failed.. I'm not sure what I could have done wrong, I followed the steps 100% and the only thing I could think of that could have caused it is that when I rooted before this process (while still on the T-Mobile ROM), I accidentally flashed the boot.img from the EU version instead of boot it. I tried to flash the boot img that was in the ZIP package from the download above, and still didn't fix it. Hoping I or someone could figure this one out.