I have been searching high and low across the internet for many days now and can't seem to find an answer to this issue.
Previously, Samsung devices could use a dialer code to enter the pre-configured menu of the CIDmanager to change the CSC using either of two codes containing "272". As of now, neither of these codes work anymore to enter this menu. Things like quickshortcutmaker don't work due to issues with permissions.
ODIN as well, does not work to flash other CSC firmware, and I have seen elsewhere on the xda forums that the new firmware must be flashed along with changing the CSC.
I have tried things like cheetah tool and magma tool, (chimera tool being much too expensive) and even an unlocking service that states explicitly that they are able to work with my CSC (TMK), yet the credits for the tools are impossible to get, and the unlocking service refuses to respond to my inquiries about payment, as their websites interactions with PayPal are totally broken.
What I need to know is how I can flash the stock XAA CSC firmware using TWRP because currently ODIN will not allow it.
I have stock firmware in two different compatible baseband, but these firmwares are naturally tarballs.
I can't flash tarballs with TWRP.
How can I make the 5 ODIN flashable firmware tarballs (CP, AP, CSC, BL, and the other one.... forget off the top of my head) into TWRP flushable ZIP files?
I have searched endlessly for days and all I come across are stupid answers that don't answer the questions that people have asked.
"Flash with odin" is NOT an answer when someone asks "how to flash these files with TWRP".
Edit: clearly I'm missing something, but I have no clue what that is.
Update: some patience and installing apps I've never used (whatsapp and telegram), which for some esoteric reason are the only means of support for the professional tools, i was able to find a company that sold credit for cheetah tool sim killer pro, through trial and error going through the official list of companies that are ALL supposed to sell the credit, and would sell less than $100 at a time, 10 being minimum for this company who's name I forget, and who's buying process is like pulling teeth by tieing a string and sinker to each one and waiting for gravity to do the trick. Seriously never seen a company that made it so hard for me to give them my money, as they all want it in crypto (for supposedly legal businesses...), and I was eventually able to pay with my debit card, but charged about 2 percent of the total as a special fee. I got 11 credits for the sim killer pro, and the CSC change was only 1 credit, which is only 89 cents, and also which somehow never got charged to my account after the csc change, so hey, In the end, totally worth the 0 i actually paid out to change the csc, but unfortunately did not actually carrier unlock the phone.
So I broke down and spent the $80 for a Samsung license for chimera tool.
(at this point, I've spent so much money to unlock this phone I could have bought a brand new unlocked one, but it's the PRINCIPLE that matters to me in that circumstance, soo.....)
The chimera tool is really awesome software, supports nearly any samsung ever made, including specifically my model, for flashing, imei, csc, etc.
Only to find that using it to flash ONLY this specific model still gives secure check failure for pit, aboot, modem, etc so I cannot flash any version of it at all on this phone, and fails at csc changes.
I eventually got a partial flashing by using the pit file that was already on the phone,and using that with my new firmware. It's sort of unlocked. It's very goofy. It was a10 before now its Android 11.
Related
Hi all, sorry for asking what has no doubt been asked before but I've been trawling through the forum and I'm struggling to find out what I want I know. I have an S6 Edge which I got from Carphonewarehouse on Vodafone (wish I'd stuck with Three) and I wanted to get the WIFI calling working because I'm often in areas where there is no signal (again, wish I'd stuck with Three!).
The phone doesn't have the WIFI calling option on it so from what I can gather, to get this working, I'll need to flash it with the Vodafone rom. I think I can just about bumble through this process with Odin but I can't work out if I'm going to lose functionality by doing it (specifically losing access to banking apps, losing fingerprint scanner, tripping Knox counter). I don't think I fully understand rooting and flashing and if they are one and the same thing or two separate things (I'm not interested in unlocking anything and tweaking registry type things, I literally just want the phone as it is now but with WIFI calling).
I'm a bit out of my depth on this tbh and from what I can see, if I trip Knox it can't be untripped. Can someone help point me in the right direction pretty please.
Thanks for any help.
Ok tripping knox will void samsung warrenty and samsung pay wont work, some banking apps may not work depends might have to google around and see if your will. Finger print scanner and everything else will work fine.
To flash and root are two different things. Rooting is to gain admin access on the software.
Flashing is done threw odin on a pc to change software, bootloaders, modems, recoverys things like that.
If u decide to flash a custom recovey like TWRP this can also do some of the things odin can the files are just in zip instead of tar for odin.
If ur looking to go to a new stock firmware then no need to root.
First ull have to make sure ur bootloader isnt locked cuz if it is i dont think you can flash other stock roms. I cant be totaly sure as mine is unlocked maybe someone else can chip in here.
If ur looking for wifi calling are there 3rd party apps in the play store that can do this for u?
Your also right about tripping knox once thats done no going back.
If all you want to do is flash the Vodafone firmware with odin, you will be fine and it will not trip knox, there are guides on here on how to do it. The phone was purchased from Carphonewarehouse like my own so the bootloader should be unlocked. Just make sure you read the guides fully and you should be good x
---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------
Just to add my first s6 edge was purchased from Ebay and was 02 branded and i flashed it to generic using Odin knox was not tripped, because its a stock firmware it will not trip knox
Thanks xstokerx and jadaress1, I really appreciate you both responding. Jadaress1, you are spot on in so much as I just want to put the standard Vodafone firmware on which, as I understand it, incorporates an extra question in the Phone Settings to be able to switch WIFI calling on/off. I will have a good read of the guides on how to do it tonight and take the plunge, wish me luck !! Thanks again.
Well .... last night was interesting ... EPIC FAIL!
I downloaded the most recent UK Vodafone Rom for my model from Sammobile then set about putting the phone in download mode. All seemed fine, Odin 3 loaded up the Rom fine and picked up the Com for the phone so I hit "Start" then, just as it was about complete everything (literally about 1/2 mm away from complete on the Odin and Phone status bars) it came up "FAIL".
I waited, waited some more, nothing! I tried to flash it again, another FAIL. I downloaded the 2nd latest Vodafone Rom (I resorted to paying for the fast download option on Sammobile because I was in a state of panic ) and tried flashing that, still a FAIL. I then took the executive decision to disconnect the phone and try to reboot it (I knew this was probably stupid but had run out of options) and then got an error message saying I needed to do an emergency recovery. I tried to load up Smart Switch and was told the device was not supported.
At this point I'd lost the will and resigned myself to the fact I was going to have to buy a new phone!! ... finally, after several hours of trying various things, I found a solution which was to extract the hidden.img file from the Rom and flash that individual file to the phone and much to my relief, the phone started working again but ... still on the old software (and *#1234# no longer works, I get an error message if I try to do that now).
All in all, this was not the smoothest software flash So ... does anyone know what was likely to have caused the flash to fail both times? I'm contemplating trying it again if I can find out why if failed and fix the problem (I must be a glutton for punishment!!)
Thanks in advance for any help, all gratefully received
I'm guessing as there has been no replies that there is no obvious reason why flashing the Vodafone rom failed. I'm a bit reluctant to give it another go given that I very nearly didn't get the phone working again after my previous attempt so I guess I will have to live without wifi calling for now
I own a registered (with Xperia Care [warranty]) Z5C E5823 phone. This phone was purchased from eBay US, but I believe the phone came from China as I had to manually switch from Chinese to English during the first initialization. Although at the time I got this phone (mid 2016), several build and android version updates existed, mine never updated. It is still stuck with Android 5.1.1, build 32.0.A.4.11, kernel 3.10.49-perf-g6b847e2. The phone, PC companion and everything else claims it's the latest update/version for the E5823.
I wanted to know what is happening and how to solve this. The phone is completely stock. Never rooted.
Thank you.
Thats why i payed extra 300$ to Sony
(my previous SONY was from alternative store, although the phone still was real and not fake replica it didnt get OTA updates so i had to used flashtool to update)
anyway you dont lose much.. wait for android 7 and update from flashtool
you can try use sony site to see if you supposed to get update
http://support.sonymobile.com/global-en/xperiaz5/software/
Superrman said:
wait for android 7 and update from flashtool
you can try use sony site to see if you supposed to get update
http://support.sonymobile.com/global-en/xperiaz5/software/
Click to expand...
Click to collapse
I've noticed something strange... I went to the link provided and inserted my IMEI number. The website claimed I have the latest version of everything, "as usual". But it showed the following message: "Your Xperia™ Z5 is up to date! 32.0.A.7.3.
That's not my build number and it also claims my phone as a Z5 and not Z5C. I don't know if this is relevant or not, but definitely strange.
Anyways, I believe that to use this flashtool I would have to root the phone. In this case I'm a bit concerned as the first android I ever tried to root was bricked instead. So I try to stand clear of doing that as I've been traumatized by my experience hahahahahaha. Well, unless there is a step-by-step-foolproof-recipe solution, I don't want to risk bricking my phone or voiding warranty (still in effect) if an update to marshmallow is not all that great.
l_abaurre said:
I've noticed something strange... I went to the link provided and inserted my IMEI number. The website claimed I have the latest version of everything, "as usual". But it showed the following message: "Your Xperia™ Z5 is up to date! 32.0.A.7.3.
That's not my build number and it also claims my phone as a Z5 and not Z5C. I don't know if this is relevant or not, but definitely strange.
Anyways, I believe that to use this flashtool I would have to root the phone. In this case I'm a bit concerned as the first android I ever tried to root was bricked instead. So I try to stand clear of doing that as I've been traumatized by my experience hahahahahaha. Well, unless there is a step-by-step-foolproof-recipe solution, I don't want to risk bricking my phone or voiding warranty (still in effect) if an update to marshmallow is not all that great.
Click to expand...
Click to collapse
As long as you are flashing an official ROM with flashtool, you don't need to root your phone.
I was sick of waiting for my Z5 compact to get the OTA for whatever firmware I initially had, so I just flashed unbranded Nordic with no problem without being rooted.
There are a few threads here on XDA that will explain what you need to do to use flashtool.
The wrong IMEI and Chinese first boot screen suggests your phone came from shady sources, otherwise there's no reason for the discrepancy. Did you check and see if the IMEI number matches the one on the box?
If I were you, I'd seek out the ebay seller and ask for an explanation and refund or replacement, fraudulent IMEI's are no joke, I mean what if the IMEI is reported stolen? You'd probably get tracked down and paid a visit by unpleasant people or something. Sure, you'd likely be able prove your innocence, but not worth the risk or hassle IMO. Then again, you have been using it for half a year already, chances are nobody's going to bother you, ever.
It's possible that the mismatch is the reason why you never got an OTA update notice. Like other members have suggested, you can use flashtool to flash the latest firmware, but it's certainly not as easy and painless as an OTA update. Going down the road, I don't think you'll ever get to update OTA with your device, so if you want to hang on to it and keep it up to date, learn how to download official firmware using xperifirm, convert to FTF and flash using Flashtool .
Next time, buy from credible and reputable vendors.
Thanks for the reply guys. Unfortunately, there was no suspicion at the time about the phone being "fake" or something like that. But after this IMEI situation and this problem as well (worth checking), I'm kinda suspicious. I don't have the box with me, I'll only be able to compare this in february, as I'm abroad. But I've registered my phone with Sony and I didn't have any problems. I even have the limited warranty available.
By the way, can this warranty be used to replace the phone in a case like this? Even considering the LED issue mentioned in the link above?
I guess I'll have to educate myself about flashing firmware with flashtool. I don't mind the extra hassle, as long as I don't brick the phone.
l_abaurre said:
Thanks for the reply guys. Unfortunately, there was no suspicion at the time about the phone being "fake" or something like that. But after this IMEI situation and this problem as well (worth checking), I'm kinda suspicious. I don't have the box with me, I'll only be able to compare this in february, as I'm abroad. But I've registered my phone with Sony and I didn't have any problems. I even have the limited warranty available.
By the way, can this warranty be used to replace the phone in a case like this? Even considering the LED issue mentioned in the link above?
I guess I'll have to educate myself about flashing firmware with flashtool. I don't mind the extra hassle, as long as I don't brick the phone.
Click to expand...
Click to collapse
You can't go to Sony and ask them to replace it. Ok, you can always try, but based on normal warranty, they won't replace it.
In your case, it's up to the dealer/store to fix your problem with IMEI, maybe a faulty ROM and so on. Or you can flash the update yourself
--jenana-- said:
You can't go to Sony and ask them to replace it. Ok, you can always try, but based on normal warranty, they won't replace it.
In your case, it's up to the dealer/store to fix your problem with IMEI, maybe a faulty ROM and so on. Or you can flash the update yourself
Click to expand...
Click to collapse
It's been a while since I've bought the phone, so I don't believe the vendor will do much.
I've read about the process of flashing the firmware. The only thing I did not understand is about the selection of the firmware itself. I'm presented with a list of firmwares of various countries (market) and carriers (operator) in XperiFirm. How do I know which one to select? A natural choice would be to select one from my region/carrier, but I can't find any or both for my phone. The guides I found doesn't elaborate on this.
Another thing. Will a simple backup with Xperia Companion or Factory Reset (from the phone itself) revert to the original firmware? Do I need to create a backup firmware?
Ahh, so the weird LED color thingy was you too. Your phone is off the charts fishy.
Your vendor should definitely be held accountable, try negotiating first. If things go sour, threaten to sue and see if they change their tune.
You select the firmware from your region, and don't select the carrier branded firmware, they're for locked phones sold by carriers, one normally wouldn't want to use that.
If I'm not mistaken, what you're trying to ask is if you're currently on firmware version A and flash version B, could you revert back to version A using Xperia Companion or via the factory reset, correct? The answer is no. You can however use Flashtool to flash version A regardless of what version firmware is currently installed on your phone, but I'm not sure if it's advisable to retain user data when you downgrade firmware.
Usually there's no need to make a backup of the original firmware. The factory reset function is basically just a data wipe, firmware version doesn't change. You should always backup your personal files before attempting to flash a firmware just in case. Personally I use Sony's preinstalled Backup and Restore app, it works for me - don't backup apps though it's pointless, takes up too much time and free space and is basically redundant. If you want to make a backup of the entire phone including the firmware, you will need a custom recovery solution like TWRP, but in your case I don't think you'll need to go that far, it's more stuff to learn and potentially go wrong.
mhaha said:
You select the firmware from your region, and don't select the carrier branded firmware, they're for locked phones sold by carriers, one normally wouldn't want to use that.
Click to expand...
Click to collapse
By region you mean the region I live or the region of the original firmware? I matched the CDA of the one that shows on the cellphone with one on the list of available firmwares. Not surprisingly, it shows that it is from Hong Kong and "customized HK" as operator. Intuition says I should try and flash that one...
So, usually backing up your current firmware is not needed/common?
Depends on what you're doing, because you're just upgrading and not messing with custom ROMs or kernels or whatever, then yeah you don't need to backup the entire phone/firmware, just backup your data.
I suggest picking the region you're living in, although it doesn't really matter since you can always change your language and uninstall/disable any localized apps. For example if you're in Russia, then you'd probably prefer the default search engine set to Yandex and local Russian apps preinstalled; or if you're in China, then you'd want Baidu instead and Chinese specific apps... etc. Or another possibility, US-based firmware may have the DST setting enabled by default, but nothing you can't change afterwards.
mhaha said:
I suggest picking the region you're living in, although it doesn't really matter since you can always change your language and uninstall/disable any localized apps.
Click to expand...
Click to collapse
I live in Brazil but I travel to the US all the time. I didn't find any firmware from these locations for my phone. So judging from what have I read so far, I can pick whatever as long as it's not carrier locked or something like that.
So I guess I'll pick whichever firmware is the most recent from the list and cross my fingers...
Just to give an update to whomever it may concern. I've decided to flash an Australian firmware (I belive it was the most recent one) after some more reading.
Although flashtool failed to flash the first time, I just repeated the process step by step and it worked like a charm the second time.
Although my backup didn't do much (I've deleted EVERYTHING from my phone, as recommended) everything worked and the phone is up to date.
Now I'm waiting for the Nougat!
Hello!
Recent proud owner of new Z5 Compact, U.S. edition (E5803, CDA 1298-3109). Excited to start tweaking it, but I want to have a copy of the shipping stock firmware before I begin messing with anything. I've already successfully created a TA backup, so we're good there. But I am BEYOND frustrated at the fact that it is seemingly impossible to obtain a copy of an FTF for the exact firmware version that my phone was preloaded with from the factory.
My phone was apparently manufactured in spring 2016 and came stock with 32.2.A.0.224, "Customized US". Does anybody have an FTF for this for my exact CDA? I haven't managed to find a copy anywhere, and of course XperiFirm doesn't show it as available for download from Sony's servers. (I'm having a little trouble believing that it is unavailable from Sony direct, given that OTA updates for older versions are still distributed...my phone is prompting me to accept an OTA for 32.2.A.0.253, which can't be obtained via XperiFirm, either.) I know I can flash FTFs for other CDAs on my phone (even for E5823s) but my goal at this point is simply to get one that matches what I already have exactly. It boggles the mind that nobody bothered to make a backup of this when Sony was still distributing it and that it isn't available for download anywhere (at least that I can find).
Barring that, though, I had another thought: pull a bit-for-bit image of the boot and system partitions. I'm concerned that a standard TWRP backup would not suffice given the existence of dm-verity, but I'm wondering if this would work:
1. Unlock bootloader
2. Boot TWRP with fastboot
3. Access an ADB shell, and then use dd to clone the necessary partitions to an SD card or attached USB drive
Then if I ever wanted to go back to the original factory firmware, I boot TWRP, use dd to write the clones back to the partitions, restore the TA to re-lock, and Bob's your uncle. Anybody see a problem with this plan?
Thanks much!
-- Nathan
P.S. -- Is there some super secret stash of FTFs for the Z5 Compact somewhere that I just haven't stumbled upon yet? In addition to hunting down this particular firmware build, I would also be interested in obtaining copies of other Sony stock firmwares (other than the most recent) for this particular CDA. Again, frustratingly hard to come by...
Darn it, I meant to post this to the Q&A forum. I swear that was the one I was browsing...grr. Anyway, mods, feel free to move, and my apologies.
-- Nathan
So, I guess I'll just keep talking to myself here...
I can confirm (in case anyone who stumbles across this thread in the future cares) that a bit-for-bit backup of all partitions using 'dd' works just fine, and that restoring that backup in reverse also works fine and does not risk a brick. I was 99% sure this was probably the case but wanted to make sure. I made a backup of every partition except userdata and cache, and then downgraded to Lollipop, and restored back to the shipping firmware by booting off of TWRP, clearing userdata and cache, and restoring each partition I had previously backed up (including my TA backup w/ bootloader lock & DRM keys). Phone booted up and went through OBE setup, and all DRM keys were present and accounted for.
I can't, however, get the FOTA update from .224 to .253 to take. Phone downloads it, reboots, goes through some kind of firmware verification process, reboots, and .224 boots up again and the Sony Updater says there was some kind of failure and to try again. If you try again, it re-downloads the whole update again and does the same thing. Not a huge deal, but I thought it would prove interesting if it were still possible to get all the way to 7.1.1 from the shipping firmware incrementally, especially since Sony seems to have pulled the full versions of those updates from their servers.
I'm still on the hunt for archives of firmware releases; I've found a few here and there, but it would be nice to find some Customized US releases. I'm particularly interested in 32.0.A.6.209, which I believe was the one and only Lollipop release that ever shipped on the U.S. models (since they were so late to market here).
-- Nathan
Can you post the img files?
Hey, as you can imagine I ****ed up. If you could do me a favor and post those images that you got from your phone somewhere that would be incredibly useful for me. Thanks.
nlra said:
I'm still on the hunt for archives of firmware releases; I've found a few here and there, but it would be nice to find some Customized US releases. I'm particularly interested in 32.0.A.6.209, which I believe was the one and only Lollipop release that ever shipped on the U.S. models (since they were so late to market here).
Click to expand...
Click to collapse
You probably won't find much US firmware floating around because of the disabled fingerprint reader, and I daresay the relatively tiny US market share Sony enjoys.
On top of that, I don't think anyone has compiled a database of Z5C FTFs unfortunately, so it's difficult to locate a particular version, and extra hard to find a specific version + region combo.
Honestly, I don't think there's any advantage to using a US-based firmware other than potential warranty validity reasons (if they even check it).
By hanging on to US firmware, you're missing out on a really useful feature that your phone hardware supports but can't let you use because business.
Since it sounds like you're comfortable with flashing ROMs, and have an understanding of making proper backups, I suggest you flash another region's firmware to enjoy the full potential of your phone.
Hey, thanks for the response.
mhaha said:
[...]I don't think anyone has compiled a database of Z5C FTFs unfortunately, so it's difficult to locate a particular version, and extra hard to find a specific version + region combo.
Click to expand...
Click to collapse
I do find this especially sad and frustrating, especially given that we know that Sony is apparently willing to delete older firmwares from their server. (Bad on Sony, BTW!)
mhaha said:
Honestly, I don't think there's any advantage to using a US-based firmware other than potential warranty validity reasons (if they even check it).
By hanging on to US firmware, you're missing out on a really useful feature that your phone hardware supports but can't let you use because business.
Click to expand...
Click to collapse
I haven't had the chance to run tests yet myself to confirm or deny this, but if you read some of the "enabling fingerprint scanner on U.S. models" threads for both the Z5 and the X/XZ, there is some unfortunate evidence that points to there being some kind of difference when it comes to LTE reception in U.S. firmware vs. other regions...some people claim that non-U.S. firmwares simply show "less bars" in the status area but that the phone's radio is still seeing the same RX levels (making it just a cosmetic thing), while others say that for them, it is not simply cosmetic and it quantifiably impacts their phone's radio's performance. I'm not sure why there would be any difference at all, but it is something to keep in mind, and is a potential "cost" one should take into account when using international firmware on a U.S. model.
Also, there are as-yet-unknown and undocumented differences between functionality in the various firmwares from different regions, making it extremely difficult to determine which is the "best" one to use. Arguably the only thing that the U.S. firmware lacks is the fingerprint scanner and is otherwise fully functional. I happen to know from reading other threads that all German firmwares, including the generic carrier-unbranded one, for some reason have SIP/VoIP calling ripped out of the system phone app, which makes absolutely no sense to me. Who knows what other features are missing or crippled in that region or in others.
At least with the U.S. firmware, it appears to be possible to restore the files that are missing from it in order to resurrect the fingerprint scanner (after rooting, of course). Given the minefield presented by the uncertainties when it comes to firmwares for other regions, this might arguably be the best way to go if you are in the U.S. and want a working fingerprint scanner.
-- Nathan
DRHARNESS said:
Hey, as you can imagine I ****ed up. If you could do me a favor and post those images that you got from your phone somewhere that would be incredibly useful for me. Thanks.
Click to expand...
Click to collapse
Sorry, somehow I missed seeing this reply! You want the images for 32.2.A.0.224 that I pulled? Just to clarify, these were pulled as bit-for-bit rips from the phone's partitions (so they're big; even leaving out cache and userdata we're talking about 6GB here), and are not in FTF format nor flashable with Flashtool or Emma. To flash, you'd have to have your bootloader unlocked, put the image files on an SD card, put the SD card in the phone, boot TWRP over USB with fastboot, and then use dd to flash each partition from the command line.
If you're still interested, send me a PM and we'll work out a way to get these to you.
-- Nathan
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good:
Due to some facts in life, I bought an S22+ LDU (SM-S906B), thinking that it just needed to be flashed.
I flashed it but nothing really changed. After sometime I realized that my CSC was WWD when I had flashed an SER firmware. Later I realized that I had to check the repartition option in Odin and extract the PIT file from the CSC file to repartition my EFS partition to be able to access the devices IMEIs. It still didn't work.
Later I changed CSC using SamFw Tool, but my carrier id is still WWD, and I'm still unable to repartition the phone.
I'm not a developer, so I'm not sure that I need to repartition. I already have other data from the EFS partition (MAC addresses). Please, tell me if I'm in the right direction.
Some people say that I can repair IMEI, if I had U1 (I have U3), but there're services that repair U3 phones (I'm too broke for those).
Now I think that I should change my carrier id, I found some video using combination firmware, but currently there're no combination firmwares for U3.
Today I found some comment, saying that to flash CSC you need to have U1, which relates to the claim two lines up, so I feel that I'm on the right direction.
Should I downgrade my bootloader? Is there a way to do it without tripping Knox?
Don't think there's any free way of downgrading bootloader. Needs Samsung server access