Related
I was searching for a way to debrand my AT&T Samsung Focus S to receive the latest update and was at first surprised to find out that none of the registry editors work and secondly, that I could not find a simple way how to unbrand it.
So here is a simple way for anybody who was looking for the same thing.
Please note that this will unlock and debrand your phone (and I’ve also thrown in the 3G toggle tweak) but after you update to 7.10.8107.79 through Zune, you will no longer be able to use the ProvXML method of deploying registry settings (that we are using here).
All credit goes to Deathbyvegemite who told me what to do and Jaxbot and his WindowBreak Project which helped me figure out how to do it. This is really just a simple modification of his work, so I have to thank him and all the other people that have worked on this.
Okay, so to do this, please follow these steps:
1) Open your mobile browser and go to: http://www.kremese.sk/debrand_focus_s.zip
2) The file will be opened. Follow the instructions and tap on “debrandfocuss.xml”
3) Press Start
4) Navigate to Phone
5) Dial ##634#
6) Type *#9908#
7) Select DebrandFocusS
8) Press Save and Reboot
After that, connect to Zune and you will receive the 8107 update.
Thanks for the hack! I'm completing the Zune update to 8107 now, it should be complete in another minute or so.
I have some wifi issues with the Focus S -- as well as several other people I know and I'm hoping that even though this update does not say it fixes the wifi connection issue, I'm crossing my fingers that it does.
Thank you again, I always love having the latest OS version installed.
-John
jfreiman said:
Thanks for the hack! I'm completing the Zune update to 8107 now, it should be complete in another minute or so.
I have some wifi issues with the Focus S -- as well as several other people I know and I'm hoping that even though this update does not say it fixes the wifi connection issue, I'm crossing my fingers that it does.
Thank you again, I always love having the latest OS version installed.
-John
Click to expand...
Click to collapse
Well, it's been a couple hours since I completed the upgrade to 8107 and I just had the phone reboot during a phone call.
Thanks for the update, but I'll go back to my backup and wait patiently for the official update. Not that this one isn't official, but there maybe special tweaks that need to be done for the Focus S/i937 or AT&T.
-John
To be honest, I don't think it's related to the update, but I can of course understand that you want to be safe.
Doesn't seem to work for me. Not seeing any updates.
onesikpuppy said:
Doesn't seem to work for me. Not seeing any updates.
Click to expand...
Click to collapse
Do you have an unlocked device? If you have a registry editor you can check under this path:
HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo\MobileOperator
The string value should be "000-88". If it still says "ATT-US" then please try again and follow the instructions precisely.
Yes, unlocked. Do you know of a registry editor that works on Focus S?
onesikpuppy said:
Yes, unlocked. Do you know of a registry editor that works on Focus S?
Click to expand...
Click to collapse
There are a couple that work, but currently only in read-only mode.
This one is the most user friendly I think:
EDIT: Argh, can't post outside links. Please google "Registry Editor for Windows Phone 7 Beta Testing".
Got the registry editor working. It still says ATT. I've gone through the process 5 times now. Each time it tells me "debrandfocussProvisioning succeeded" but after the reboot it's back to ATT-US.
but does this just give the OS update? Does this also give you the firmware update?
is the focus s out there for anyone else but ATT?
Not sure about the firmware update, but my firmware version after the update is: 2103.11.10.1.
onesikpuppy said:
Got the registry editor working. It still says ATT. I've gone through the process 5 times now. Each time it tells me "debrandfocussProvisioning succeeded" but after the reboot it's back to ATT-US.
Click to expand...
Click to collapse
Can you please check which version of the Diagnosis tool you have?
ver.0923
Thanks
Well, that's the same as mine. Are you sure you are not on 8107 already?
One thing you can try is to pull out your sim card and see if it works then.
I'll try pulling the sim
Sent from my SGH-i937 using XDA Windows Phone 7 App
Sim pull didn't help
Sent using xda premium
I have the samme issue that onesikpuppy with the same parameters in his attached thumbnails.
I bought a demo phone, can anyone help me get it out of the mode it's in?
works wonderfully. thanks to op
whats the diffrent betwween this unlock to the windows break unlock?
can i use registry editor to edit some enteries?
thank you
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)
Ok, Ladies and Gentleman I need some deep thought processing here for some help with a Motorola Nexus 6. In brief here is what the problem is, a while back when flashing Pure Nexus rom, I experienced a loss of my IMEI. I can restore my IMEI but if and when I do, I lose any 4g and LTE connectivity. The phone functions in 3g with data and phone etc... just slow as molasses but if I restore my IMEI to the one that doesn't show up my IMEI correctly I get back LTE/4g and all works fine also. I've tried going all the way back to the original firmware which was saved to computer and restoring it. Same thing, I have IMEI but no LTE/4g. restore bad efs and get LTE/4g back. I've tried going through all the factory firmware's and flashing by ADB and or TWRP and nothing firmware wise will allow me to restore the IMEI and have LTE/4g signal. If I restore the bad efs and get OOOOOOOO for IMEI when using the *#06# on any firmware version, I regain LTE/4g functioning! I am using Pure Nexus 7.1 now and can still see the 00000000 as a IMEI, if I restore my efs and get IMEI back showing correctly, no LTE/4g signal! My phone can only function as it should as long as the IMEI doesn't show correctly! I have tried just flashing base bands and other segments of any rom and still the problem persist! I have even tried restoring an EFS from another nexus 6 and still no help. It's not the sims because I've tried AT&T sims and Verizon sims from other phones and it does the same thing! I've tried flashing with a sims in the phone and without. Any ideas??? It's like somehow a correlating segment of a file is not being recognized when the correct IMEI is present, like some thing some where in the efs, IMEI, and radio are not taking to each other so to speak, unless it shows the zero's! Brain waves come on and help me out here!!
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
jbaumert said:
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
Click to expand...
Click to collapse
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
TheWacoKid said:
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
Click to expand...
Click to collapse
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
jbaumert said:
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
Click to expand...
Click to collapse
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Dixon Butz said:
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Click to expand...
Click to collapse
Thanks! Ok, Itried that, restored my IMEI, "reset APN to default" Tried Carrier reset ##3282# and it says "NO Cellular Network" even though I am showing my network and 3G. So, I rebooted and same thing, went to PRL and tried to update and it says "update error" but it will refresh!
TheWacoKid said:
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Click to expand...
Click to collapse
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
admiralspeedy said:
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
Click to expand...
Click to collapse
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
TheWacoKid said:
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
Click to expand...
Click to collapse
You know some magic we don't? There is no way you've flashed a ROM with ADB...
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
dahawthorne said:
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
Click to expand...
Click to collapse
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
admiralspeedy said:
You know some magic we don't? There is no way you've flashed a ROM with ADB...
Click to expand...
Click to collapse
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
TheWacoKid said:
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Click to expand...
Click to collapse
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
admiralspeedy said:
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
Click to expand...
Click to collapse
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
rignfool said:
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
Click to expand...
Click to collapse
No, you can use ADB sideload to flash a ROM which requires you to be in the recovery. Standard ADB cannot be used to flash a ROM.
admiralspeedy said:
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
Click to expand...
Click to collapse
Amazing to any one with half a brain how you a Troll can think from typed response that someone is yelling, swinging, snarky and rude but your the one with an attitude that is all the above because like I said your a childish troll! I can't believe this site would even allow someone like you to be a member paid or otherwise! Your attitude is all your own and based on your own weak assumptions! Now go back to playing with your legos!
drmuruga said:
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
TheWacoKid said:
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
Click to expand...
Click to collapse
So was there a solution? The thread just ended. I also have this problem but I'm no where as technical as thewacokid.
But I do know how to follow steps
Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in QD1, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576350
Worked great..Thanks! But....
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
3rdRockfromSun said:
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
Click to expand...
Click to collapse
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
iBowToAndroid said:
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
Click to expand...
Click to collapse
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
3rdRockfromSun said:
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
Click to expand...
Click to collapse
https://www.att.com/deviceunlock/
Thanks in advance for any help, short version at top, details below.
-- Short version:
Please help me recover my data, and phone if possible.
I need the data, esp texts and notes, for both personal (some family members have passed on) and business.
I have a new Galaxy S21 and / or PC Smart Switch ready to receive data backup if we can evacuate it from the S5.
ODIN flash seems to pass but has 'Resizing Data' fail, and phone still won't boot past AT&T logo screen.
All web searches seem to say Factory Reset is my last option, but I don't want to lose the data.
Please share ANY advice on how I can recover the data.
-- More details:
Phone = SM-G900A Samsung Galaxy S5 AT&T
Use = pristine, never rooted, modded, or unfortunately backed up
Status = will not boot, passes screen 1 'Galaxy S5', screen 2 'Samsung script', then stops on screen 3 'AT&T globe logo'
More details = Used clean for ~7 years, then on day x, saw phone automatically complete a system update (green screen, sprockets, "your phone is updating"), which was surprising as it's years after it is no longer supported by AT&T. After that update, I continued to use the phone that day, but it then rebooted automatically and stuck on the AT&T globe logo.
Attempts to fix = soft reset, battery pull, can't get into SAFE MODE, can get into and out of recovery mode, found this firmware (THANKS @iBowToAndroid), used multiple ODIN (Odin3 v3.13.3_3B_PatcheD, Odin3 v3.14.1_3B_PatcheD) to flash it (my first Android flashing experience). On flashing process, ODIN on PC shows 'PASS' and log shows "<OSM> All threads completed. (succeed 1 / failed 0)", but phone shows 'Resizing Data' failed:
"
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Resizing Data...
Can't open dir '/data/user/0/com.sec.knox.bluetooth' (Permission denied)
E:failed the resizing-data
"
PFA screen shots
Martin2019 said:
Thanks in advance for any help, short version at top, details below.
Click to expand...
Click to collapse
Trying the "wipe cache partition" is the only thing I can think of
iBowToAndroid said:
Trying the "wipe cache partition" is the only thing I can think of
Click to expand...
Click to collapse
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
The string seems to indicate a 'user data' permission error?
Is there any way to debug the logic of the firmware or slog through the 'Recovery Logs' to determine and resolve the cause of the permission error?
When the problem began, I had an SD card and SIM card loaded.
I've since removed both in trying to address this, also per 'web advice'.
Any chance putting them back in helps somehow?
Any other options available via apply update from SD card or ADB?
Any way to setup the Android OS as a secondary drive to another machine to pull data out that way?
I've done similar things with Windows OS in PC environment, but I'm not seeing anyone trying that with Android.
If I am really stuck with factory reset, are there any data recovery programs I could try afterward that work with the G900A?
So far I've looked at Dr Fone, Tenorshare, EaseUS, FonePaw, and D-Back, and none seem to work with the AT&T model variant.
Maybe that's just because they don't have access to AT&T firmware available to install, but if I clear the stuck boot via FR, they then might be able to get some of my data back via drive scan - whatever data is not truly overwritten by the FR?
Martin2019 said:
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
Click to expand...
Click to collapse
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
iBowToAndroid said:
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
Click to expand...
Click to collapse
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Martin2019 said:
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Click to expand...
Click to collapse
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Totally agree, and totally on me for not having a backup.
I was just foolish enough to not know yet how easy it is to back up.
Give me 10 minutes of life again now in this phone, I use Smart Switch to backup, and I'm off to a new phone, or even FR on this one and reload.
Now where did I put my Delorean...
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Have you ever tried a 'combination key' approach to get data access?
As in...
Smart Switch on PC won't connect, but ODIN does show 'Added'.
I don't understand the granular details, but hoping you might...
Could we use both Smart Switch and ODIN in some combination sequence that would allow Smart Switch to pull the data off to a Smart Switch PC backup that I could then throw onto a new phone?
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
iBowToAndroid said:
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
Click to expand...
Click to collapse
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Martin2019 said:
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Click to expand...
Click to collapse
Any 3rd party software will require ADB to be enabled. Smart Switch is the only one that *might* work just over MTP, but I'm pretty sure MTP doesn't fully load until the device is booted. Even if it did, you would likely need to allow on the popup message. Does the phone show up as a device/drive when it's plugged in while sitting on the AT&T logo?
I think you're asking "does the phone show up as a device/drive" in something like a windows file explorer, and the answer is unfortunately no, or at least not that I've found yet - I've tried several times now, and I'm still trying any combinations I can.
For now...
I can get EaseUS to show 'MTP USB device' per the pic attached in my last, but can't really get it to connect past that point, as it asks for USB Debugging, which it appears I can't do due to stuck in boot loop.
Smart Switch seems to try to connect for awhile, then says it failed to connect, so I think I'm then left with 'Samsung Smart Switch Emergency Software Recovery' (PFA).
Do you have experience using it?
Do you know if it could work to reload the firmware / OS without wiping the data?
AT&T Advanced Technical Support guy says it gives you an option to choose whether or not using it resets the phone (wipes your data), so he thinks (hopes) that would work, but he didn't sound certain at all.
I understand your point on the pop up message user prompt for File Transfer Mode. I used that mode many times in the past, so I'm hoping it might default on the phone so we wouldn't need to answer the pop up prompt to reach that status , but I'm obv not sure about that.
Per the speculation in my last, do you know of any combination approach we might use to get the desired result, like maybe... use ADB somehow to change 1 parm value to reach MTP mode, then use that progress step to enable Smart Switch to connect so we could offload the data?
Thanks again for your help
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
2. But if the phone never shows up as a device/drive (would show up under "Portable Devices" in Windows Dev Man), then it's not loading fully - and it normally doesn't do that until it boots past the carrier splash screen.
3. Even if it did boot fully and showed up as a device/drive, the MTP pop-up prompt shows up every single time you connect the device. There's no way around that. So the device would show as empty, with no files or folders, until you tapped "Allow" on the popup.
4. No, there's nothing else you can do to turn on any other connection modes
iBowToAndroid said:
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
Click to expand...
Click to collapse
Device Manager does show an entry for the phone connected via USB cable:
Under 'Disk Drives' as
SAMSUNG MZMTE256HMHP-000MV
Under 'Universal Serial Bus Controllers' as
SAMSUNG Mobile USB Composite Device
Please tell me that helps us somehow?
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
77an said:
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
Click to expand...
Click to collapse
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
abokamel said:
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
Click to expand...
Click to collapse
Can you share the rom that you use?
Also, were you root?
oscarillo said:
Can you share the rom that you use?
Also, were you root?
Click to expand...
Click to collapse
no, it's stock, not rooted.
the current rom i use now is here
abokamel said:
no, it's stock, not rooted.
the current rom i use now is here
Click to expand...
Click to collapse
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
oscarillo said:
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
Click to expand...
Click to collapse
used the command line, i think it's making refurbish
This is a bit of an older thread, but just recently did the same crossflash from pie on att device to korean open Q.
Decided on the KR instead of EBW because KR, I thought, had more of the t-mo LTE bands I needed. Unfortunately, the different sites with firmware specs aren't always accurate (which LTE bands supported). One site has EBW supporting every LTE band of every LG phone! Def inaccurate.
So I tested both EBW and KR Q versions. Use LTE Discovery (from playstore) to view LTE bands in your current location. One thing to note about that, the LTE bands it shows u are going to be the nearest towers it's using. Which means that another tower, a little farther away, won't show up.
So to verify a particular band, that you think the phone might be capable of, but you aren't sure, you have to go into the svc menu and select 'field test' and enable only that LTE band you're searching for. Then use LTE Discovery and see if it's connected with that band. If it isn't connected with it (usually it will default to a 3G band if that one u selected isn't available), that means 2 things; 1) either that band isn't used in your area 2) Your device doesn't support that band (or both 1 and 2).
But in my case, I know band 71 works in my area (from previous testing), but I have to select enable for only that band for it to show up, because other nearby towers with band 66 will 'drown it out'.
Thus, the point here, the KR firmware Band 71 **DOES WORK**. And, btw, no site indicates it included in supported bands. The following screenshot shows it connected to 71 and the KR 409 at the bottom.
Cheers
abokamel said:
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Click to expand...
Click to collapse
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
<snip brevity>
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
AsItLies said:
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
Click to expand...
Click to collapse
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
advancedtekniqs said:
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
Click to expand...
Click to collapse
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
AsItLies said:
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
Click to expand...
Click to collapse
that's terrific and brilliant to be honest! thank you so much for information you shared.
So, just found something additional that works on open 409N. The 'buffer fix' can be a bit of a pain. Tried a magisk module supposedly for v40 Q but that didn't work. So did what I've done before and just copy the .so fix to the appropriate directory, but that didn't work, even the oem camera stopped working after that.
So, even though this says it's for 'custom roms' tried it, and boom, works in magisk and does what's needed to fix buffer.
cheers
abokamel said:
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
Click to expand...
Click to collapse
Try this website to find your seriel# by IMEI
So, interesting updates, for anyone using this Rom.
I went back to my AT&T rom, android 9. Then, just a few hours later... decided to go back to KR Open Don't ask, it's too confusing
But, the point, this time, when flashing the KR rom, I did part DL, and then after booting did Refurbish. Had read on tele that doing that fixes some of the issues crossflashing causes. Sure enough, my NT-code issue went away (couldn't fix that even with hexedit of ftm)!
So, that was cool. But now, my S/N disappeared! IMEI was still okay though. So tried the hexedit ftm and added S/N, boom, now it's fine also. But the funny thing was, with the refurbish and no NT-code problem, I looked at what was in the newer ftm at that address, and it had nothing, no info at that address at all.
One thing to be aware of, attesting to why this is difficult to deal with, these values (IMEI, S/N - and others) get propagated from one partition to another, I don't know the chain of events or criteria involved, but it adds to the difficulty of trying to fix issues. Which specific place it looks for something is confusing also, and if it's doing compares of 2 or more places is a mystery.
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
AsItLies said:
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Click to expand...
Click to collapse
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
fireblade20 said:
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
Click to expand...
Click to collapse
Mine is an AT&T, but afaik, Sprint should be the same. Yes, do the part DL, let it reboot as normal, then shut off and do refurb. Is S/N a big deal? no, everything works, and the S/N is still in the phone, just not displaying properly. It's an individual thing how much effort you put into fixing that. Some people have lost either / or IMEI or dual IMEI (some roms have that), when cross flashing. That's a problem because they get no cell signal, but that's on a different rom.
Look in this thread for how to LGUP / crossflash.
cheers
Thanks man!