Related
Hi Fellow Users!
I just bought LG v10 yesterday with international warranty even though i live in UAE, the problem is i am following all the steps from "step by step guide to root for tmo" but unfortunately i am not able to boot into phone recovery which is odd for me as i am a long time user of android, is that possible my phone doesn't have one? I tried everything adb, manually but nothing worked, i once booted my phone into recovery via adb but i saw green android picture with no command written on it and fastboot didn't worked there so there is that.
1) i tried dirty_cow but stuck at getenforce "permissive didn't appeared which is must needed, i think its related to my bootloader"
2) should i follow LGUP procedure even i am not sure my bootloader is unlocked?
P.S my phone is TMO although its unlocked to use any network.
Please advise, thank you
Unfortunately flashing KDZ file bricked my phone, :crying:
Now its just off it doesn't turn on tried everything any advise?
Update: Went to LG TechServe and handed over my phone to re-flash the original firmware, bad thing they don't cover international warranties as i live in UAE and the model i have is TMO with international warranty so there's that.
Reason to share the story, may people learn from this.
Have you tried with Kingroot app or kingoroot app? These apps can root many devices.
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
Code:
adb devices
adb reboot bootloader
fastboot getvar all
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
Code:
fastboot oem unlock
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
TootyRooty said:
This is a problem, and it's doing my nut. I have a Vodafone Smart Mini 7, which I desperately want to root, to get all of Google's bloatware and the stuff the original network provider put on it.
I've already unlocked it to all networks, but the bootloader is being a PITA. I've done the usual with adb and fastboot, namely put it into USB Debugging, and then done this;
When I get to the section on the bootloader, it advises me that it's Secure.
I tried to use
and when I confirm on the phone that I want to unlock it, I get told that Remote Unlock is not allowed.
I assume that the fact that fastboot getvar all says that the bootloader is secure, means I need some sort of key to get it off. My old network provider don't know where to get it from, my tech team don't know where to get it from and I'm screwed.
Anyone got any ideas on whether I can get round the "secure" part of this, like some way of finding the key for it? Thanks
Click to expand...
Click to collapse
I have the exact same issue I read some threads and nothing solid has come out of it some say they managed to get root but others say they bricked the phone
Any news on this topic? I too have one i desperately would like to root because it is permanently full and you cant do anything wih it. The Google apps and the apps installed by my service provider take up all the onboard storage space. I downloaded only Whatsapp and Facebook Lite and bam,the phone is completely full and useless as it cant do updates,runs extremely slow and does all sorts of random stuff like restarting on its own etc. driving me utterly insane.
I'm using samsung A10,i try to root my phone but not sure the step are correct or not. But now my bootloader is unlocked and my data was erase, how to lock the bootloader and recover my data's back.Please help me
Even if you manage to re-lock the bootloader the data are unrecoverably wiped.
So I've been having this issue for a while now. I would like to unlock the bootloader on my Samsung and I'm struggling severely. I've done so much research and attempts and phone calls and in the end, my hands always turn up empty. Could someone please give me some advice or a guide to what I'm supposed to do because it seems like this specific phone under the Tracfone carrier is a ghost when it comes to this and rooting. Once I get a lead I'm suppose to enable oem unlock, well my phone doesn't have one. I've waited more than a week with developer options on and I've even tried adb and fastboot. Still nothing, I really need an expert's help but I can't seem to find anyone. Not even XDA is helpful with this phone. Yeah they have the A10 or A10s but not the A10e under the Tracfone carrier with the model number SM-S102DL. Help would be much appreciated. Thank you
visit here
My A10 phone still in unlock bootloader condition, can i still recover the lost files?
Samsung A02s(SM-A025F)
I do these steps any body help
1.I unlock oem through developer option
2.I unlock bootloader successfully
3.I downloaded firmware and patch AP with magisk to root
4.I flash Patched AP
5.After getting my phone rooted successfully I want to install TWRP Recovery
6.I downloaded unofficial version of TWRP from xdaforums....
7.I followed the steps guided here
The steps are as follows
1.reboot to boot loader and flash vbmeta_disable.tar
2.Put TWRP tar in AP and flash
3.Reboot to recovery
4.Disable encryption
Go to Advanced >Terminal : type "multidisabler"
5.Go back to wipe>Format Data>type "yes"
6.Reboot system
This is my first experience to root and flash TWRP.... but after that when I reboot my phone got lock .... only official binaries allowed to be installed....and stuck there
I got frightened so I locked my bootloader
But nothing happens...
I downloaded stock firmware and flash.....now my phone works perfectly But I want to root my phone I searched and found a correct way to root but now oem unlock option is not found in developer options....
I watched hundreds of videos on yt and searched a lot on Google but
found no proper solution.....someone tell me to wait 7 days....
In about phone> phone status>uptime
Uptime should be equal to 7days... then oem unlock option will appear but ...... I want another solution date change and WiFi connect is not solution ... If any body knows any other solution please guide me ... I'll be very thankful.....
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
bmwdroid said:
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
Click to expand...
Click to collapse
Thanks for reply...
This bypass method doesn't work in my device
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Mahmoudm.kamal said:
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Click to expand...
Click to collapse
Keep us updated.. I'd like to get my OEM unlock to come out of hiding.. this is frustrsting.. i see all these tutorials for the A02s root, twrp and ROMs and whatnot and I'm itching to get flashing!
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Noobiu said:
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Click to expand...
Click to collapse
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Mahmoudm.kamal said:
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Click to expand...
Click to collapse
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Swyen said:
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Click to expand...
Click to collapse
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Mahmoudm.kamal said:
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Click to expand...
Click to collapse
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
ewrecc said:
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Click to expand...
Click to collapse
STOP TRYING TO UNLOCK A US DEVICE ITS NOT POSSIBLE
Swyen said:
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
Click to expand...
Click to collapse
Which tool did you use?
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.