Related
can anyone please tell me howndo i delete the demo content that comes preloaded with the titan? when i plug in my tutan to the charger i get this windows 7.5 commercial running as a screensaver. can anyone tell me how to fix this?
You would need to install a retail/OEM ROM onto your device.
This would be rather difficult to do without HSPL on your device or without a properly signed ROM for you to flash onto your device.
The real question is, why did you get a demo model phone? You should take it back to wherever you got it and get an actual retail/non-demo device.
i purchased it from a friend of mine who purchased it from someone else. well being fora demo device, will this phone face any problems? what are the differences? and i cant i flash one of those eternity ROMS?
thankyou so much helping though
Hi
i was in the same situataion as you are in, this is either a stolen phone from the store meant only for display and not for sale or the store guys gave your friend a pretty good deal on the phone. anyways
I flashed the eternity 1.09 ROM for europe.
Just start the phone in the bootloader mode and run the RUU.
Thats all i did and my phone was up and running a retail NON-Demo ROM. when i plugged it into Zune i received all the secessary updates.
Hope this works on your titan too and sloves the problem.
do a hard reset
when the device turns off and back on
take the battery out
turn on the device in bootloader mode
and install the oem rom
let it work till done
So I have the same problem, ended up with a demo phone from Amazon, and I've tried many times to get a retail OEM flashed on the phone. I followed this thread in particular, downloading the ROM that matches my Radio version, (16.23.03.17) but no matter which RUU tool l I use, I always end up with the same error: ERROR [294] Invalid Vender ID
The readme's troubleshooting section tells me to get a proper matching RUU for my phone, but unfortunately my internet scouring abilities turned up nothing.
plz hlp
Phone details:
PI39100
SPL-2.1.160015.3(133679)
Radio-16.23.03.17
Yeah, still stumped. From what I can tell, I have to wait for someone to make a custom rom and hope it doesn't have the same compatibility errors. Should I just take it into an AT&T store and see if they can install a new OEM on it?
they wont be able to help you at an at&t store, i work at one, and the only way is to flash a new custom rom. they will only have the capability of flashing the retail demo rom onto it.
EDIT
and if you take it into an at&t store they would probably realize that it was stolen from their floor display and confiscate it, another store here ran in to that once a while back
---------- Post added at 10:35 AM ---------- Previous post was at 10:29 AM ----------
in your situation aculem, id probably contact amazon and have them ship you a new phone. i actually ran in to the same thing when i got my titan from our store stock. the box was unmarked and looked just like any other titan box. but it had the demo content pre loaded on it. they probably just shipped you one thinking it was a retail device, not a demo, because the packaging is exactly the same
Unfortunately I have suffered the same situation with the Titan II. I bought this on ebay from this seller, and it was a demo. In the description of the lot that was not, and I realized it only after a day of use. Where are we now take the OEM firmware is not clear.
If you can send back for refund from either Amazon or ebay, do it. It is not worth your effort to try make it work. Unless you can flash OEM shipping firmware, you will be never able to get rid of the demo stuff and you will also not be able to upgrade to newer OS.
foxbat121 said:
If you can send back for refund from either Amazon or ebay, do it. It is not worth your effort to try make it work. Unless you can flash OEM shipping firmware, you will be never able to get rid of the demo stuff and you will also not be able to upgrade to newer OS.
Click to expand...
Click to collapse
Seller not accept return but I will try to decide this problem.
In most cases, these demo units are stolen goods. Also, if seller didn't clearly label the phone as demo unit, you have a very good case to ask refund from ebay. Ebay will get your money back from the seller even if he doesn't accept returns.
Sent from my SAMSUNG-SGH-I777 using XDA
The seller has agreed to take the phone back and return money or return part of money if I am agree to reflash OEM firmware. Therefore I have important question - after reflashing OEM firmware the demo phone will be identical usual absolutely on all functions (it can be updated, etc.)?
Correct. But make sure Who is going to pay if your flashing bricked the phone?
Sent from my GT-P7510 using XDA
foxbat121 said:
Correct. But make sure Who is going to pay if your flashing bricked the phone?
Click to expand...
Click to collapse
Nobody, seller will not be responsible for the phone when return part of money back he said. Correct it does mean that after succesfull reflashing the phone will be identical of not demo ?
Joutes said:
Nobody, seller will not be responsible for the phone when return part of money back he said. Correct it does mean that after succesfull reflashing the phone will be identical of not demo ?
Click to expand...
Click to collapse
If you can find the OEM firmware for that specific region of your phone, yes. I'd suggest you investigate the flashing procedure and whether or not you can find the firmware for your phone first.
foxbat121 said:
If you can find the OEM firmware for that specific region of your phone, yes. I'd suggest you investigate the flashing procedure and whether or not you can find the firmware for your phone first.
Click to expand...
Click to collapse
I was searching the firmware (USA) but not found. If somebody help me it will be great. Maybe it is possible to restore OEM state from backup of OEM firmware ?
Joutes said:
I was searching the firmware (USA) but not found. If somebody help me it will be great. Maybe it is possible to restore OEM state from backup of OEM firmware ?
Click to expand...
Click to collapse
Nope. Backups are keyed to individual phones. Also, backups contain sensitive personal data. So it is no advisible to share the backup files.
I am also a victim, and I cant return the phone, anyone was able to do anything with it, please help. thanks in advance
I know this phone is old and I am not sure why HTC website is not being able to download this: 404 Not Found
Code: NoSuchKey
Message: The specified key does not exist.
Key: application/RUU_HIMA_UL_L51_SENSE70_ATT_MR_Cingular_US_2.6.502.16_Radio_01.01_U11440601_72.02.50602A_F_release_438693_signed_2.exe
My friends HTC m10 died recently and he still has his M9 which I'm trying to fix. But I cannot find anywhere this firmware that this phone is on. I read that I can't upgrade to anything higher and in order to restore that RUU I have use the same one. Issue is I can't find it anywhere to download. Anyone able to help?
EDIT: was able to find it -> took me like 2 hours...
https://androidfilehost.com/?fid=24052804347847327
I guess the title says it all but a little info, a couple of months ago I went on to settings and ticked on the OEM unlock option but never went forward with any flashing, no custom recovery, no kernel, nothing, plain stock Samsung ROM. 3 days ago I went to pick up some newspapers for work and everything was fine, at lunch time I had to get something and upon swiping the phone on the terminal it came up with a message on my phone that this device cannot be used to pay in stores with google pay. I deleted and updated my card info since I lost it recently and the new had a different expiration date. Which I had already changed but figured it might have taken a few days to flag or something. Same result, can't pay in stores message. Got in contact with google pay support and they told me my phone had been flagged for being rooted,modified OS. I said that I'm not rooted then they said it appears I have an unlocked bootloader so google pay doesn't work on devices with unlocked bootloaders. I stated that an unlocked bootloader is perfectly legal and not a sign of a modified OS. The operator replied they can't do anything since it's policy and my only option is to relock the bootloader, so I told them it'd work if I had a modified OS but it wont if I have an unlocked bootloader with no modifications to cover the BL state and I laughed, said thank you and signed off from the support conversation.
I went back an relocked the OEM option and restarted for it to take effect and was then able to use gpay again.
I have a XEU Exynos with the April Security update.
TLR if you OEM unlock but don't flash magisk and magisk hide your google pay wont work. Relock,reboot and you're good to go.
crossmission said:
I guess the title says it all but a little info, a couple of months ago I went on to settings and ticked on the OEM unlock option but never went forward with any flashing, no custom recovery, no kernel, nothing, plain stock Samsung ROM. 3 days ago I went to pick up some newspapers for work and everything was fine, at lunch time I had to get something and upon swiping the phone on the terminal it came up with a message on my phone that this device cannot be used to pay in stores with google pay. I deleted and updated my card info since I lost it recently and the new had a different expiration date. Which I had already changed but figured it might have taken a few days to flag or something. Same result, can't pay in stores message. Got in contact with google pay support and they told me my phone had been flagged for being rooted,modified OS. I said that I'm not rooted then they said it appears I have an unlocked bootloader so google pay doesn't work on devices with unlocked bootloaders. I stated that an unlocked bootloader is perfectly legal and not a sign of a modified OS. The operator replied they can't do anything since it's policy and my only option is to relock the bootloader, so I told them it'd work if I had a modified OS but it wont if I have an unlocked bootloader with no modifications to cover the BL state and I laughed, said thank you and signed off from the support conversation.
I went back an relocked the OEM option and restarted for it to take effect and was then able to use gpay again.
I have a XEU Exynos with the April Security update.
TLR if you OEM unlock but don't flash magisk and magisk hide your google pay wont work. Relock,reboot and you're good to go.
Click to expand...
Click to collapse
This was changed a while ago, a unlocked bootloader will trip safety net, if you have no reason for the OEM unlock, don't use it
Ferbee said:
This was changed a while ago, a unlocked bootloader will trip safety net, if you have no reason for the OEM unlock, don't use it
Click to expand...
Click to collapse
Yes, I forgot to mention it triggers the CTS Profile to mismatch and thus fail the Safety Net status check even if the Safety Net Request flag itself isn't raised.
I honestly think they're just trying to cover their asses by removing functionality even though I fail to grasp that they are not aware that the people who are technically minded enough to root, and try to use the service with malicious intent, know how to bypass Safety Net checks. On the other hand it might be that if someone has an unlocked bootloader is more susceptible to remote attacks and potentially have a random apk root and take hold of their device and all their info.
It's been a long couple of days at work and while typing the original post I forgot half of what I wanted to mention hehehe!!!
Hi guys I have an issue I need your quick help plz......
I have just purchased s9+ I want to create secure folder but it's showing an error saying couldn't create secure folder contact service providers....... and the same issue while using samsung pass it says your phone has been rooted.....
But my phone is not rooted it running official firmware even I have just updated Oct security patch now....... I have checked in download mode for knox wranty void it says (0x0000) plz help me how can I solve this problem :crying:
Plz some one help me
You just purchased the phone? If that is the case simplest solution is see if you can exchange it for a different one (of same model).
Only time I have heard of those errors happening is if the phone has been (or was) rooted/modified. Have you tried to do anything to the phone at all (like trying to install the pie beta before it was a public beta that was on the forum here, or anything else you might have flashed to the phone) or any software modifications/flashing? If you have not then it is very well possible the previous owner may have done so (or at least tried to do).. This is why I suggest you return it for a replacement since you just purchased the phone.
You could try doing a factory data reset or flashing the proper firmware for the phone model/region. Outside of that there isn't anything I myself could suggest, especially if the newly purchased phone is covered by a warranty.
UPDATE: This phone is money down the drain unless I can unlock and root it. If you can help me do that successfully, I'll pay you $20. Just to end this frustration.
UPDATE: Cash offer rescinded. I fixed the problem by buying a different phone and giving up on this one.
Question: How do I fix the OEM Unlocking option not appearing on a Samsung A01 (SM-S111DL)?
Answer: By giving up on it and buying a different phone.
Maybe this is a better forum to post this. I have a Samsung A01, SM-S111DL. I want to root. I want Magisk on there.
I have been searching, and searching, and searching for any useful tutorials on how to root this specific device. In addition to searching, I have also been searching. And besides that, completely apart from that, I have been searching. So nobody better tell me I haven't tried figuring this one out for myself.
So far, I can't find anything that works. I just can't. Partly because tutorials keep telling me I need to turn on the OEM Unlocking option, and it ain't there. I know where it's supposed to be, between Bluetooth HCI and Running Services, and it's not there. And I tried the Date & Time trick, and it didn't help.
So, if I can't turn that option on, what can I do? I was thinking about trying Heimdall. It was unable to print the PIT, but I managed to download a PIT that supposedly corresponds exactly to my device. It's labeled A01Q_USA_TFN.pit. I also downloaded the full firmware with Frija, and extracted stuff. I took the boot.img from the downloaded firmware and patched it with Magisk. I was thinking of installing it, but then I said, no, I better wait until some experts weigh in on this. Best case, the flash would go just fine. But then there are two bad cases. One, Heimdall won't even be able to flash, and that will mean more anger and frustration. Two, it'll brick the device. And I'm not even sure which is worse anymore.
This point, I don't even know what the hell to do. Please, someone help.
Also, I'd like to have TWRP on this device. But I don't know whether there's a version out yet. Sure, there's one for some other model of A01, but would it work with mine? I just don't know, and I'm feeling too discouraged to try.
Please, someone help.
Did you search before posting? I see many, many threads regarding rooting the Galaxy A01, including one you posted 7 days ago on the same topic.
V0latyle said:
Did you search before posting? I see many, many threads regarding rooting the Galaxy A01.
Click to expand...
Click to collapse
Did you read before replying? I told you many, many times that I searched.
FailSafeNow said:
Did you read before replying? I told you many, many times that I searched.
Click to expand...
Click to collapse
My point is, creating a new post isn't always the best course of action when there's already discussions on the topic. Secondly, do not create multiple threads on the same topic.
If OEM Unlock is not available, you won't be able to unlock the bootloader, which will prevent you from flashing custom images (such as the patched boot image). You could try using Odin to flash an older firmware version and see if OEM Unlock becomes available.
Here's a couple things you can try. First, remove your SIM and turn off WiFi. Then, disable Automatic Date & Time, and set the time ahead by at least 1 week. If the OEM Unlock toggle does not appear, just wait a while.
Apparently, this has something to do with Knox.
If you want to check whether unlocking the bootloader will be possible at all, you can use ADB:
Code:
adb shell getprop ro.oem_unlock_supported
If this returns 0, unlocking the bootloader is not possible at all.
If this returns 1, then you just need to be able to access the OEM Unlock toggle, which will set get_unlock_ability to 1 and permit unlocking the bootloader, at which point you should be able to flash a patched boot image.
See this article for more information.
V0latyle said:
My point is, creating a new post isn't always the best course of action when there's already discussions on the topic. Secondly, do not create multiple threads on the same topic.
If OEM Unlock is not available, you won't be able to unlock the bootloader, which will prevent you from flashing custom images (such as the patched boot image). You could try using Odin to flash an older firmware version and see if OEM Unlock becomes available.
Here's a couple things you can try. First, remove your SIM and turn off WiFi. Then, disable Automatic Date & Time, and set the time ahead by at least 1 week. If the OEM Unlock toggle does not appear, just wait a while.
Apparently, this has something to do with Knox.
If you want to check whether unlocking the bootloader will be possible at all, you can use ADB:
Code:
adb shell getprop ro.oem_unlock_supported
If this returns 0, unlocking the bootloader is not possible at all.
If this returns 1, then you just need to be able to access the OEM Unlock toggle, which will set get_unlock_ability to 1 and permit unlocking the bootloader, at which point you should be able to flash a patched boot image.
See this article for more information.
Click to expand...
Click to collapse
Thank you. I've tried various tricks with the date, to no avail so far. But I will try the trick the way you said it, and try waiting. Incidentally, I have no sim. Just got this phone off eBay. Never planned on putting a sim in it. Just wanted it for usage as a wifi device.
So far, no OEM Unlocking option has appeared. But I'll wait on it, like you said. And yeah, I've read that these devices are made to have some kind of waiting period.
I also read that you had to be on Android 11 before you could get the unlocking option. So that's what I'm on. As for Odin, it gets stuck on the analyzing phase and never actually writes anything. Heimdall gives me an error of -12 when I try to use it. I've tried installing drivers on my computer with Zadig, but it hasn't changed anything so far. And it has a lot of options for drivers and stuff, so I don't know which are even the right ones. (I'm on Windows 10 Pro.)
I tried the ADB code about a week ago, having found that direction in one of the threads. And yes, it gave me a 1, so good news.
Is there no other way to set unlock ability to 1? I mean, if Samsung had this phone in its lab, would they be able to force it to do things, or would they have to manually remove the MMC and put it on a special reader?
Also, the reason I created my own thread was that I thought piggybacking on other people's threads was frowned upon.
Edit: I also checked the article. I've seen it before, because when I want something, I keep searching for it until I either find it or destroy my nervous system trying. I tried putting together the combination firmware. But two problems. First, it lies about which files I'm going to find when I extract the various archives. boot.img.lz4: fine. system.img.lz4: no such file exists. sboot.bin.lz4: no such file exists. I'm guessing they would want me to use aboot.img.lz4 instead of sboot.img.lz4, and super.img.lz4 instead of system.img.lz4, but since the guide was made for phones that call their images different things, I don't honestly know. Second problem: Odin can't flash crap. Neither can Heimdall. The experts say, "Use one of these patched versions of Odin." So I try. No dice. And I try Heimdall, but that's no good either. Like I said, Error -12. What do I do about this? "Install stuff with Zadig." So I try that. I install every damn thing that Zadig has an option to install. Nothing changes. Nothing gets better. The tutorials have failed me.
Next time I buy a phone, painless rooting and unlocking is going to be my first criterion.
The option to unlock still has not appeared. I need more help.
I'm just about ready to give up on this phone completely. Can nobody save this situation?
are there any variants to this device? how would you match firmwares? or substitute the firmware to be able to flash, so that other options such as oem unlock become available? have we checked if any of the android 10 firmwares for a01 sm-s111dl have the oem option available?
FailSafeNow said:
UPDATE: This phone is money down the drain unless I can unlock and root it. If you can help me do that successfully, I'll pay you $20. Just to end this frustration.
UPDATE: Cash offer rescinded. I fixed the problem by buying a different phone and giving up on this one.
Question: How do I fix the OEM Unlocking option not appearing on a Samsung A01 (SM-S111DL)?
Answer: By giving up on it and buying a different phone.
Maybe this is a better forum to post this. I have a Samsung A01, SM-S111DL. I want to root. I want Magisk on there.
I have been searching, and searching, and searching for any useful tutorials on how to root this specific device. In addition to searching, I have also been searching. And besides that, completely apart from that, I have been searching. So nobody better tell me I haven't tried figuring this one out for myself.
So far, I can't find anything that works. I just can't. Partly because tutorials keep telling me I need to turn on the OEM Unlocking option, and it ain't there. I know where it's supposed to be, between Bluetooth HCI and Running Services, and it's not there. And I tried the Date & Time trick, and it didn't help.
So, if I can't turn that option on, what can I do? I was thinking about trying Heimdall. It was unable to print the PIT, but I managed to download a PIT that supposedly corresponds exactly to my device. It's labeled A01Q_USA_TFN.pit. I also downloaded the full firmware with Frija, and extracted stuff. I took the boot.img from the downloaded firmware and patched it with Magisk. I was thinking of installing it, but then I said, no, I better wait until some experts weigh in on this. Best case, the flash would go just fine. But then there are two bad cases. One, Heimdall won't even be able to flash, and that will mean more anger and frustration. Two, it'll brick the device. And I'm not even sure which is worse anymore.
This point, I don't even know what the hell to do. Please, someone help.
Also, I'd like to have TWRP on this device. But I don't know whether there's a version out yet. Sure, there's one for some other model of A01, but would it work with mine? I just don't know, and I'm feeling too discouraged to try.
Please, someone help.
Click to expand...
Click to collapse
ADB Fastboot OEM unlock? https://www.getdroidtips.com/how-to...-on-Samsung-Galaxy-Phones-via-PC-ADB-Fastboot
so i found out how to do this if anyone still needs this information for this phone. You go to software status and click the kernel version several times to activate developer mode and once thats activated there will be a developer options under "about phone" on the main settings menu and instead of being between bt hci and services it was down at the bottom under the debugging sub menu. There is USB debugging and wireless debugging(over wifi) simply toggle usb debugging and/or wireless debugging and continue from there on youre pc of choice with process of choice! Hope this has helped anyone. I have the exact same phone as OP, same model number.