Hello everyone,
I've recently gotten a Samsung Galaxy™ Stratosphere™ II (Verizon), and can't find anything on rooting this sucker. The pertinent specs (as far as I can tell) are as follows:
Android: 4.0.4
OS Version: 3.0.8-1157001
Dalvik Version: 1.6.0
CPU: Snapdragon S4 (ARMv7 r4)
Hardware: Samsung Aegis2 r4
Anyone have any advice? I'd love to be able to root then make a CWM recovery for this thing, and any help would be greatly appreciated.
Thanks!
Holy mother of humanity, these threads get buried QUICKLY!
I have the same phone and have looked everyone trying to find a way to root it
fltbosn said:
I have the same phone and have looked everyone trying to find a way to root it
Click to expand...
Click to collapse
I mean, I know it's a relatively new phone and all, but surely someone with some development knowledge has one by now...
... I'd try to figure it out, but I think it might be a little over my head.
Okay, the problem with the available rooting procedures is that they all try to install things to /data/, which is inaccessible (not even read-only); I've been looking and trying to ask around, but can't find any alternative procedures.
How hard is it to root a phone from scratch? Is it possible to use exploit bases from other phones that use the same SoC and Android version? Any devs able to chime in?
What is it about this Verizon implementation of 4.0.4 that doesn't allow access to /data/, which is what every standard root procedure uses? Do any other Verizon phones use 4.0.4 that don'e have access to the /data/ folder?
(I really, REALLY hate to keep bumping my own thread)
I got this phone too. A root method would be great so I can remove the bloatware.
ShaneRitz said:
I got this phone too. A root method would be great so I can remove the bloatware.
Click to expand...
Click to collapse
I am from Bulgaria and I have bought this phone too and we still can not make it working even with Verizon Wireless SIM card.
The problem probably (not sure) is that it was never turned on or registered so in Bulgarian when I put Verizon Wireless SIM card it can't recognize its home network of Verizon to start the setup.
It seems that it need Verizon network to make first registration and activation of device or I am missing something? The only thing that pop up is Wizard of Verizon that want to set up my phone and account and I can't do it because no Verizon Network connectivity...
Any suggestions?
Trying and failing
WetLlama said:
Hello everyone,
I've recently gotten a Samsung Galaxy™ Stratosphere™ II (Verizon), and can't find anything on rooting this sucker. The pertinent specs (as far as I can tell) are as follows:
Android: 4.0.4
OS Version: 3.0.8-1157001
Dalvik Version: 1.6.0
CPU: Snapdragon S4 (ARMv7 r4)
Hardware: Samsung Aegis2 r4
Anyone have any advice? I'd love to be able to root then make a CWM recovery for this thing, and any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
I have been working through many of the methods, unfortunately with no success. The root exploits don't work (including debugfs which would work on nearly anything) as the file system is locked down HARD even in recovery mode. Even ODIN 3.07 flashing recoveries (CWM touch 6.01) fails check after NANDWRITE step (Same trying to flash an unlocked boot for the MSM8960 (SIII)). I have built the kernel from source successfully but with no way to get the initramfs built there's no way to flash the product. Damn VZW!!! Need some suggestions for moving forward, I'm about stumped.
So I feel your pain friend, I'm sure others are too. Short of an emulator to suck the code off the chip, (which I'm not above doing *if* I had the hardware and twiddling bits in the binary I don't know how we're going to get this thing unlocked yet.
TheHierophant said:
I have been working through many of the methods, unfortunately with no success. The root exploits don't work (including debugfs which would work on nearly anything) as the file system is locked down HARD even in recovery mode. Even ODIN 3.07 flashing recoveries (CWM touch 6.01) fails check after NANDWRITE step (Same trying to flash an unlocked boot for the MSM8960 (SIII)). I have built the kernel from source successfully but with no way to get the initramfs built there's no way to flash the product. Damn VZW!!! Need some suggestions for moving forward, I'm about stumped.
So I feel your pain friend, I'm sure others are too. Short of an emulator to suck the code off the chip, (which I'm not above doing *if* I had the hardware and twiddling bits in the binary I don't know how we're going to get this thing unlocked yet.
Click to expand...
Click to collapse
You're a much braver man than I, I'll tell you that much.
I've been considering attempting to flash a T-mobile Samsung Relay 4G recovery since the phones are almost identical (with the exception of the radios, of course), but I'm afraid of totally borking it because I have no backup. If you're up for it and haven't tried that one yet, maybe editing some settings in the build.prop of the Relay's stock ROM would work (I don't know really; I'm a hardware guy, not a developer... )?
http://forum.xda-developers.com/showthread.php?t=2117436
There's all of the stuff for it so far, and if you do decide to give it a shot, let me know and I'll try to provide whatever help I can.
Hidden Menu results
Okay, fell back and started looking at other approaches. So... following on Adam Outler's work on the SIII I snooped through the .apk's and found this little gem "HiddenMenu.apk" which I disassembled. Low and behold the following things popped out at me [which I put in activation strings]:
Code:
shell "am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://HIDDENMENUENABLE"
shell "am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://IOTHIDDENMENU"
shell "am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://UNLOCKKERNEL"
The first line brings up the Hidden menu screen: select the entry and select "enable"
The second line brings up the internal operation test menu which lets you look at all sorts of interesting and possibly dangerous goodies
The third line brings up the following message in a dialog box followed by another dialog asking for the unlock key code
"You have obtained the key for unlocking the bootloader to install custom OS. In order to unlock the bootloader, you must read and accept the following terms and conditions. By clicking on the “I Agree†button, you acknowledge and agree to the terms and conditions. If you change your mind, you may click on the “Cancel†button, which will stop the process.
1. The unlocking of the bootloader voids and invalidates the warranty of your device. As result of the unlocking, certain functions of your device may cease to function and physical injuries or material damage may occur, for example, due to the phone overheating. You take full responsibility for any and all consequences that may arise from the unlocking of the bootloader. Samsung will not be liable for any damages that such unlocking may cause, and you waive any rights in connection with the unlocking.
2. You will not be able to recover the device to its original state. Even if the device’s setting is restored, the warranty will remain voided and invalid.
3. As result of the unlocking, you may lose certain contents that you have stored on your device, for example, through the malfunction of the DRM functions.
4. You agree that your attempt to unauthorized kernel download from the default setting or without the authorization key will lead to blocking of the device, which may permanently disable the device. Samsung will not be responsible for any damages or injuries that result from such attempt. For downloading of custom kernel, you need to follow through a special installation process as set forth in the device manual.
5. You agree to comply with all applicable laws and regulations as well as any contractual obligations that you may have with your wireless carrier in using the unlocked devices. In particular, you will not operate the unlocked device on any wireless carrier’s network unless such wireless carrier approves of the operation of such unlocked device on its network.
6. You agree not to resell your unlocked devices to other parties without first explaining the content of the terms and conditions herein.
"
Click to expand...
Click to collapse
I found the following part inside the constructor for SecureBootMenu:
Code:
.line 24
const-string v0, "oMEdqNRWh9CCSQb0JWI8FEbq//5jD61LPUAYB8V8ErpudvLLUXAFm+qPJZtPNeZo"
iput-object v0, p0, Lcom/android/hiddenmenu/SecureBootMenu;->SBOOT_KEY:Ljava/lang/String;
Well, I tried that key and got a message "HIDDENMENU stopped" and a boot into loader still gives the "QUALCOMM SECUREBOOT: ENABLE". So I'm not quite there yet, but there may be something close. I'll keep looking around. If anyone has suggestions or more wisdom LMK.
TheHierophant said:
Okay, fell back and started looking at other approaches. So... following on Adam Outler's work on the SIII I snooped through the .apk's and found this little gem "HiddenMenu.apk" which I disassembled. Low and behold the following things popped out at me [which I put in activation strings]:
Code:
shell "am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://HIDDENMENUENABLE"
shell "am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://IOTHIDDENMENU"
shell "am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://UNLOCKKERNEL"
The first line brings up the Hidden menu screen: select the entry and select "enable"
The second line brings up the internal operation test menu which lets you look at all sorts of interesting and possibly dangerous goodies
The third line brings up the following message in a dialog box followed by another dialog asking for the unlock key code
I found the following part inside the constructor for SecureBootMenu:
Code:
.line 24
const-string v0, "oMEdqNRWh9CCSQb0JWI8FEbq//5jD61LPUAYB8V8ErpudvLLUXAFm+qPJZtPNeZo"
iput-object v0, p0, Lcom/android/hiddenmenu/SecureBootMenu;->SBOOT_KEY:Ljava/lang/String;
Well, I tried that key and got a message "HIDDENMENU stopped" and a boot into loader still gives the "QUALCOMM SECUREBOOT: ENABLE". So I'm not quite there yet, but there may be something close. I'll keep looking around. If anyone has suggestions or more wisdom LMK.
Click to expand...
Click to collapse
Wow man, that's awesome; I'd mucked around with some of the dialer codes, but never got to that point. I wish I could help at all, but you've blown way past my usefulness at this point -- unless you want a tester.
What about trying various decode methods on that key? It looks like it could be maybe base64.
Here's two ideas that may help you root:
1) Borrow a page from the kindle fire and instead of trying to access /data directly, get around it with a symlink http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
2) You said Odin wouldn't let you flash custom bootloaders. See if you can flash custom system images. Get a copy of the stock system image from Kies or samfirmware.com, mount it under Linux, add the superuser apk and su manually and fix permissions, and then repackage it as a .tar.md5 and try to flash it. Here's an (old) guide to do that http://forum.xda-developers.com/showthread.php?t=1081239 I'm sure there's newer ones though.
Thanks for the suggestions...
Nardholio said:
Here's two ideas that may help you root:
1) Borrow a page from the kindle fire and instead of trying to access /data directly, get around it with a symlink http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/
2) You said Odin wouldn't let you flash custom bootloaders. See if you can flash custom system images. Get a copy of the stock system image from Kies or samfirmware.com, mount it under Linux, add the superuser apk and su manually and fix permissions, and then repackage it as a .tar.md5 and try to flash it. Here's an (old) guide to do that http://forum.xda-developers.com/showthread.php?t=1081239 I'm sure there's newer ones though.
Click to expand...
Click to collapse
I'll give these a try, have been busy with other things, but have a couple evenings free to experiment. Thank you for the ideas.
Did you get anywhere?
I dissassembled the HiddenMenu.apk and found the same code. When I entered it I got an error saying that the application stopped working.
I ran the string through base64 --decode, but it was full on non-printable characters. I'm wondering if it's encrypted.
I've also tried various methods that symlink data but keep getting permission denied errors. I haven't found a copy of a stock firmware to mess with.
I also have a stratosphere two, and i'm more then happy to help out in anyway possible, even if it means sending my phones to one of you guys trusted hands.
You guys suck. To get the stock firmware for your phone if it's not on sammobile or samfirmware you can trick Kies into downloading it and then intercept the file from your Windows temp folder while it's flashing to your phone (3-4 minute window)
http://forum.xda-developers.com/showthread.php?t=2088809
Then you can transfer it to a linux box to convert it to a mountable file system to root it, before repackaging it as an odin tar. From there you should be able to flash it.
Sent from my SGH-T699 using xda premium
apparently the sch i415 does not support kies
i just checked for a software update on my wife's Stratosphere II SCH-i415 and there is one. I live in NC the update was under settings/about device/ software update. its form Verizon size 506.6 MB. is there a way to pull it before it installs? maybe a root method. I installed it. could not wait. well its jellybean went from 4.0.4 to 4.1.2 baseband 1415vrlj2 to i415vrbma3 kernel was 3.0.8-1157001 to 3.0.31-947060
Related
I have been reading in forums about rooting and unlocking phones. I have a Samsung Galaxy S2 . Model # is SGH-S959G.. It is Android version 2.3.6 and has Gingerbread UDL12.
I want to unlock the phone as it shows in my settings that Network Lock is "ON" and SP Lock is "ON". Subset lock is off as well as CP lock..
I understand that I may have to root the phone. I see from most of the threads I have read in various places, they were posted back from 2010 and up to about 2013. I am not seeing anything that appears to be current in threads that tell how to do this. I am wondering if there have been updates or changes, or even if this phone can be rooted or unlocked.
I purchased the phone at full price from Walmart. Used Straight Talk as the provider, but now I want to simply change to another provider using this phone instead of the phone they want to provide. When I bought the phone, unlocked and a lot of other things meant nothing to me because I was totally unfamiliar with phones. I still do not use the phone too much. I am 63 and not savvy to most of this, but did want to make sure I know all the facts ( as much as there are any ) before doing anything, as I am on limited income now and sure can not afford to really mess up my phone. Can you tell me if there are more updated posts or news on how to root or unlock this phone.
First, welcome to the XDA forums. There is a dedicated thread for your device, you can find it here. In the first post you'll find very specific information for your phone, so my recommendation would be to check there and see if it answers any other questions you might have.
To unlock you don't necessarily have to root your phone, but if you DO want to root the procedure is much easier than it used to be. Just download the Framaroot app from this thread and use the Aragorn exploit when prompted. Then reboot and you'll be rooted.
But again, you don't have to root just to unlock.
Here is a link to an old app that used to work for unlocking the i777/959... https://app.box.com/s/mu8xp28np9y7f9r9psqswljhhlhkfx3q. In order to install the app you may need to go to System Settings > Security > and check "Unknown Sources". This will allow the app to install, bypassing the "Play Store-only" check. If you're uncomfortable leaving "Unknown Sources" checked after you've installed the app, simply uncheck it it afterwards.
Because these devices are older and out of the warranty time-frame it's perfectly legitimate to unlock them, so see if that app will work. No guarantees, though! If you have any other questions please feel free to ask here, but you may find better answers from those users who actually have your device, as I have a tendency to over complicate things!
jmccoll said:
I have been reading in forums about rooting and unlocking phones. I have a Samsung Galaxy S2 . Model # is SGH-S959G.. It is Android version 2.3.6 and has Gingerbread UDL12.
I want to unlock the phone as it shows in my settings that Network Lock is "ON" and SP Lock is "ON". Subset lock is off as well as CP lock..
I purchased the phone at full price from Walmart. Used Straight Talk as the provider
Click to expand...
Click to collapse
SteveMurphy said:
First, welcome to the XDA forums.
You don't have to root just to unlock.
Here is a link to an old app that used to work for unlocking the i777/959... . In order to install the app you may need to go to System Settings > Security > and check "Unknown Sources". This will allow the app to install, bypassing the "Play Store-only" check. If you're uncomfortable leaving "Unknown Sources" checked after you've installed the app, simply uncheck it it afterwards.
Because these devices are older and out of the warranty time-frame it's perfectly legitimate to unlock them, so see if that app will work. No guarantees, though!
Click to expand...
Click to collapse
Thank you Steve. I did use the link and downloaded the old app you provided link for, but it did not work after following instructions. It gave me a message about Root Access Denied, Please check your ROM is rooted. .. Does this mean I would have to root my phone?
Probably, but it isn't a big deal if you decide to do it. In every sense rooting is actually beneficial, as it gives the user compete control over their devices and what's installed. You can root and never install a custom ROM, so the only thing that would be detrimental would be if you had to return it for a warranty issue (of which there is a way to unroot/return to stock). But because these devices are out of warranty due to age, there's no reason not to root.
So my advice would be to download Framaroot from my previous post and use the Aragorn exploit, then reboot and run the Sim Unlock. That should work.
Finally got tired of the Pixel 2 XL after the third one. Now I have this super rugged handset that I can actually hold on to! Great loud audio too!
The Sonim XP8 comes with a seemingly near stock Android 7.1.1 ROM. OEM unlocking is available in the developer options. I have it enabled. Does anyone know how to use the ADB/Fastboot tools to unlock it? The standard commands do not work. My unit is personal and not under any "enterprise" restrictions. Thanks for any help fellow hackers ... some TWRP would be awesome.
ctradio said:
Does anyone know how to use the ADB/Fastboot tools to unlock it? The standard commands do not work. My unit is personal and not under any "enterprise" restrictions. Thanks for any help fellow hackers ... some TWRP would be awesome.
Click to expand...
Click to collapse
(Im)patiently waiting for this too. I don't care if it is single touch or long drawn out process involving a cauldron, hermetic circle, and a full moon. Root is sorely needed...
Phuhque said:
(Im)patiently waiting for this too. I don't care if it is single touch or long drawn out process involving a cauldron, hermetic circle, and a full moon. Root is sorely needed...
Click to expand...
Click to collapse
Good luck! Still nothing. It looks like we might be able to sign up as a developer on their page .... fwiw. I find the interface on that device to be awful and am in the early stages of fighting AT&T for my money back. That device and another one with the same stupid issues and an admitted software problem that I'd have to wait for the carrier to decide to release. Awesone idea for a device, absolutely rushed to market with god awful software that was new in '16 or so.
ctradio said:
I find the interface on that device to be awful and am in the early stages of fighting AT&T for my money back. .
Click to expand...
Click to collapse
I am on T-Mobile and found the factory unlocked version with no bloatware (obtainable directly from the) to be rather refreshing, even if it did set me back an extra $100. I suggest do getting the refund, then turning around and getting the "clean" version. It may be more expensive, but considering how much it costs for monthly insurance, the overall price becomes somewhat more competitive with the 3 year "comprehensive" warranty...
Phuhque said:
I am on T-Mobile and found the factory unlocked version with no bloatware (obtainable directly from the) to be rather refreshing, even if it did set me back an extra $100. I suggest do getting the refund, then turning around and getting the "clean" version. It may be more expensive, but considering how much it costs for monthly insurance, the overall price becomes somewhat more competitive with the 3 year "comprehensive" warranty...
Click to expand...
Click to collapse
I was told there was no carrier unlocked variant of this thing. Didyou get it from Sonim? Also, any problems at all with it? I had two with touch issues along the right side of the screen (it perceives a light constant touch in various areas and it gets worse the longer the screen is on). The units would eventually start selecting things on its own and even deleting contacts. Also, the speaker phone is useless and the UI is horribly laggy at times (my mind operates fast and it screws with me). I presented them with a "laundry list" of the issues.
ctradio said:
I was told there was no carrier unlocked variant of this thing. Didyou get it from Sonim? Also, any problems at all with it? I had two with touch issues along the right side of the screen (it perceives a light constant touch in various areas and it gets worse the longer the screen is on). The units would eventually start selecting things on its own and even deleting contacts. Also, the speaker phone is useless and the UI is horribly laggy at times (my mind operates fast and it screws with me). I presented them with a "laundry list" of the issues.
Click to expand...
Click to collapse
Someone flat out lied to you. Go here: https://store.sonimtech.com/products/sonim-xp8-blk-nam
Well, maybe not lied at the time you were told... I waited several months for them to post it on their store page. In response to your concerns....
No issues with it going all AI on me. Speaker PHONE portion leaves a bit to be desired, but for audio books, this thing is damned awesome and really loud. Not sure how to reference the lag. My previous phone was a Note 4 with issues.
My own complaints. The lock screen is a pain. The default music program is broken in my opinion. I am suffering through with Musicolet for my books.
What sold me on this is that is is one of the last phones made today that has a removable battery (really my only requirement in a new phone), has both gps an glonass, and in a pinch I can use is an a hurled object to an opponents head. Someone complained about the camera, but it seems fine to me. Wouldn't matter much as I am partially colorblind and won't see any difference.
I have only had mine for a week, and am still tweaking the settings to how I want them. Honestly, I like it.
I would really love to see some support for this phone. Especially since the monsters at Telus have disabled the 2nd sim slot for no good reason. I have tried everything but without Root I am out of luck getting the dual sim feature to function. Is there anything I can provide to assist someone more knowledgeable in getting a root solution for this phone? Please let me know.
mertin said:
I would really love to see some support for this phone. Especially since the monsters at Telus have disabled the 2nd sim slot for no good reason. I have tried everything but without Root I am out of luck getting the dual sim feature to function. Is there anything I can provide to assist someone more knowledgeable in getting a root solution for this phone? Please let me know.
Click to expand...
Click to collapse
Hello,
I just bought this phone. I use 2 sim cards at the same time but it does not work properly: I can receive and make calls, but I can not send or review sms / mms on 1 operator. I use the xp8800 in France, it is a Att model unlocked. to have the 2 sim cards at the same time I rebooted several times, cut the data, without really understanding how I did . is there a way to restart the network part of Android ?
Thanks
Pascal S
I take it we are still coming up snake-eyes when it comes to someone being able to root the XP8. I am rather surprised with the fact it is on 7.1.1. Is this still an unbeatable task to overcome?
The thread is closed, this is the tested version of the firmware
Unlock fastboot
Step 1, open the developer mode
Go to “Settings” → “About Phone” and click “Version Number” 7 times to open Developer mode.
Step 2, open oemlock
Go to “Settings” → “Other Settings” → “Developer Mode” and open the OEM to unlock;
3 START mode
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
Firmware update soon.. ??
In May, I sent of another email to Sonim Tech support asking about firmware. I did get a response back. Granted it was rather vague, but it was an answer. Further granted, is is now mid June and no updates in sight including one that allows the viewing of PDF's. grrrr.
The support guy did mention that AT&T is going to be one of the first providers to get the update. That sucks for me because I got my unit direct. He also said the month of May was a non-official time frame.
So still waiting and no success story yet posted of anyone unlocking this little beastie.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1259507?make=Sonim&model=XP8XP8800
No idea how to update manually, though...
Phuhque said:
In May, I sent of another email to Sonim Tech support asking about firmware. I did get a response back. Granted it was rather vague, but it was an answer. Further granted, is is now mid June and no updates in sight including one that allows the viewing of PDF's. grrrr.
The support guy did mention that AT&T is going to be one of the first providers to get the update. That sucks for me because I got my unit direct. He also said the month of May was a non-official time frame.
So still waiting and no success story yet posted of anyone unlocking this little beastie.
Click to expand...
Click to collapse
No idea how to update manually, though...[/QUOTE]
Thanks for the news , but no working to ATT from France , until in OTA .
Wait and see if dual sim working clean ....
Has anyone seen this video? There's a part in the video where as the guy turns it on, and there is a prompt to re-lock the bootloader(which, of course, implies that the bootloader is unlocked); I don't know how this really helps, but it might give someone more experienced than I something to grab at. I should mention that it is mentioned as a pre-production model of the Sonim XP8, so it probably won't apply to models that most people have, but it's something to look at.
Sonim XP8
I know that Verizon is now selling the Sonim XP8. Does anybody happen to know if it is possible to use both SIM card slots with this device after it is unlocked?
Being able to use BOTH AT&T AND Verizon would be a huge benefit to me.
is there any root yet ive tried about every root apps i cant even find working drivers for this phone
Thecctech said:
is there any root yet ive tried about every root apps i cant even find working drivers for this phone
Click to expand...
Click to collapse
Drivers are not an issue.. It's using Qualcomm reference designs from the S660 dev kit where most generic Qualcomm drivers should work with minimal modification.
This is a good thing! Most of the root apps are using a collection of known exploits where only vulnerable devices would fall victim. You would have to use an exploit that's more recent then the security patch level installed but you also have to remember - if you can do it that easily then an attacker can do it just as easily too! I personally believe that the association between root and device/firmware level vulnerabilities is the reason why most see root in a negative context today.
As far as I'm concerned - we only have 2 "correct" ways to achieve root.
1. Obtain (or compile) either a Debug or Engineering firmware variant from AT&T that includes the native su packages for adb root. This is usually not an option for us individuals.
2. Unlock the bootloader and use a patched boot image.. Works great! To unlock the bootloader takes a bit of work though and flashing still requires EDL so with that I have not been able to make a public instruction set yet.
Could be in the next few days.. Could be in the next few months.. I'm honestly not sure. Mostly just a matter of collecting images, testing, and finding time.
Enjoy!
XP8 Android Root Theory - DEBUG or Magisk over EDL
EDL is a must since Fastboot cannot be unlocked initially from standard "user" builds.
One option is flash a userdebug image (below) allowing for adb root, fastboot unlocking, and other useful features.
or
Without unlocking the bootloader - Similar flashing methods remain valid when standard magisk powered root is desired. This method allows preservation of all current system data aside from boot.img. All is covered since Magisk works with AVB and we have EDL as a flashing alternative. Please see Android Boot Flow > LOCKED Devices with Custom Root of Trust for more information.
Recommend method ..
It's up to you.. If you want OTA updates and your planning to use root apps then go with Magisk. As of today we have current debug images available and I personally prefer isolated adb root access only however future availability of updated Debug images cannot be guaranteed.
Disclaimer
-Devices with locked bootloaders will display a custom OS warning at boot
-Tested on AT&T branded devices only - please provide system dump for validation on other builds
-I have not identified any JTAG procedures and I can not help if you hard brick your device!
-This guide only touches boot_a and should be relatively safe since boot_b remains unmodified. I'm pretty sure this is enough to restore the original boot.img to boot_a under a failure scenario.. But I'm not really qualified enough to say definitively either.
-Take great caution - this is raw emmc access and critical system data! You are proceeding at your own risk!
Magisk Root
Step 1 - Pull Boot.img
We need to pull the boot.img in order to feed it to magisk later for patching. It's also good to keep on hand for if/when you need to restore for any reason.
1. Create an XML file with the data below
Code:
<?xml version="1.0"?>
<data>
<program start_sector="262144" sparse="false" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="boot_a" filename="boot.img" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="512"/>
</data>
2. Boot to EDL mode and load firehose programmer
Code:
QSaharaServer.exe -p \\.\COM<#> -s 13:prog_emmc_ufs_firehose_Sdm660_ddr.elf
3. Backup boot.img using the following command
Code:
fh_loader.exe --convertprogram2read --port=\\.\COM<#> --sendxml=<xmlfile.xml> --lun=0 --memoryname=emmc --noprompt --reset
Or visit the XP8 carrier firmware thread for full system backup steps.
https://forum.xda-developers.com/showpost.php?p=80465045&postcount=6
Step 2 - Magisk Patch
1. ADB push boot.img /storage/self/primary/Download/
2. Install Magisk Manager and apply patch to boot.img
2a. Download from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2b. Extract and run adb install magisk.apk
2c. Open Magisk app and apply patch to boot.img
3. ADB pull /storage/self/primary/Download/magisk_patched.img
Step 3 - Restore
1. Change the filename attribute in the XML to reflect newly created magisk_patched.img as shown below
Code:
<?xml version="1.0"?>
<data>
<program start_sector="262144" sparse="false" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="boot_a" filename="magisk_patched.img" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="512"/>
</data>
2. Boot back into EDL mode and load firehose programmer
Code:
QSaharaServer.exe -p \\.\COM<#> -s 13:prog_emmc_ufs_firehose_Sdm660_ddr.elf
3. Apply magisk_patched.img using the following command
Code:
fh_loader.exe --port=\\.\COM<#> --sendxml=<xmlfile.xml> --lun=0 --memoryname=emmc --noprompt --reset
USERDEBUG Flash
Step 1 - Backup
1. Boot to EDL mode and load firehose programmer
2. Generate rawprogram0.xml - Run GPTConsole <COM Number>
Example: GPTConsole 19
3. Initiate backup
Code:
fh_loader.exe --port=\\.\COM<#> --convertprogram2read --sendxml=rawprogram0.xml --lun=0 --memoryname=emmc --noprompt --reset
4. Wipe all partitions
Code:
fh_loader.exe --port=\\.\COM<#> --convertprogram2read --sendxml=erase.xml --lun=0 --memoryname=emmc --noprompt --reset
5. Restore new image
Code:
fh_loader.exe --port=\\.\COM<#> --sendxml=rawprogram0.xml --lun=0 --memoryname=emmc --noprompt --reset --search_path=<extracted image file directory>
// rawprogram0_unsparse.xml for some images
Images and OTA Files
Full 8.1 System Image
XP8A_ATT_user_8A.0.5-11-8.1.0-10.54.00
XP8A_ATT-user-8A.0.5-10-8.1.0-10.49.00
USERDEBUG Images
XP8A_ATT_userdebug_8A.0.5-11-8.1.0-10.54.00
XP8A_ACG-userdebug-8A.0.0-00-7.1.1-32.00.12
XP8A_USC-userdebug-8A.0.0-00-7.1.1-34.00.10
(ATT 7.1 pending upload. Please check back or use other links available further in thread.)
OTA Updates
XP8_ATT_user_N10.01.75-O10.49.00
XP8_ATT_user_O10.49.00-O10.54.00
XP8_TEL_user_N12.00.24-O12.23.00
Flash Tools - programmer (elf) file provided by eleotk!
XP8 Drivers
Firmware Carrier Codes
Code:
None = 0,
ATT = 10
Bell = 11
Telus = 12
Sasktel = 13
Harris = 14
Verizon = 15
Ecom = 16
NAM = 17
Rogers = 18
T_Mobile = 19
EU_Generic = 20
MSI = 21
CISCO = 22
NAM_Public_Safety = 23
Vodafone_Global = 24
Orange = 25
Southern_Linc = 26
OPTIO = 27
India = 28
SPRINT = 29
JVCK = 30
AUS = 31
ACG = 32
CSPIRE = 33
USC = 34
SB = 35
Multi = 99
Automatic OTA without AT&T service:
Purchase a blank AT&T SIM card ($5)
Start online prepaid activation - complete pages 1 & 2
**SIM Card is now partially active without funding - do not complete page 3 (payment)***
*#*#368378#*#* > Clear UI > Check for updates in settings
XP5s
Sprint Image: XP5SA.0.2-03-7.1.2-29.03.00
Works the same. Tested with unmodified Sprint firmware. Like most other apps, the Magisk manager app is unusable since the XP5s has no touch screen - I had to patch the boot image on another device. You can plug in a USB mouse however the cursor does not seem to invoke in-app tap's.
Need to use the appropriate Firehose loader (prog_emmc_firehose_8920.mbn) and replace the boot image location according to the XP5s GPT (start_sector="790528").
Great, thanks alot for instructions, @smokeyou!
In order to be able to boot into patched boot image, does it require to have unlocked bootloader? Assuming I can upgrade my phone to build 8A.0.5-10-8.1.0-10.49.00, but have my bootloader locked, can I still use your instructions? Can you clarify it?
-albertr
albert.r said:
Great, thanks alot for instructions, @smokeyou!
In order to be able to boot into patched boot image, does it require to have unlocked bootloader? Assuming I can upgrade my phone to build 8A.0.5-10-8.1.0-10.49.00, but have my bootloader locked, can I still use your instructions? Can you clarify it?
-albertr
Click to expand...
Click to collapse
Untested but should not be a problem. Bootloader unlocking only allows Fastboot flashing where this method uses EDL only.
Basically the same outcome though just without the option to use TWRP or custom recovery (easily).
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
tcl trackfone
Hello i was wondering if you ever got your phone rooted?
me to i have that problem on my tcl lx
to
Temporary mtk- root. Use init.d for always root
Sonjouten said:
Temporary mtk- root. Use init.d for always root
Click to expand...
Click to collapse
I can't possibly express how much I would love for you to elaborate on the 'use init.d for always root' part. Anyone else who knows, please jump in. Start by pretending I am an idiot. Then stop pretending and explain it to me as if I were an adult who needs a full-time minder. First one to help me achieve "always root" on this terrible, wretched, little excuse for an electronic device gets my undying gratitude and um, maybe some Google Play money? I am open to ideas here on that score. To reiterate, need help rooting my Tracfone TCL LX A502DL that has a castrated recovery (seriously, you can't flash anything from adb, the option is flat-out missing) and apparently no fastboot access AT ALL. I could do another seriously in parentheses, but you need to take my word for it w/o a bunch of examples. The bright spot is the vulnerability the device has to the mtk-su exploit. Get a # in like no time at all. Time elapsed from executing the file to getting the prompt is too short for my flesh computer to register (unless you -v, then about 1.5 seconds.) So how do I turn a root prompt into full root?
I can't possibly express how much I would love for you to elaborate....
Click to expand...
Click to collapse
WHAT HE SAID
+1
X2
etc
Thank you, H
Did he get that?
So did he earn that Google Play Store money or was he just full of it?
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
I never did get her to root. Alas she is a broken phone now RIP. Sorry for the disappointments. But I move on more hopeful. ?
As posted by Viva La Android in another thread about the tcl a501dl:
The TCL A1 (A501DL) cannot be bootloader unlocked. Although the OEM Unlocking option can be enabled in the Developer Options menu, fastboot mode has been made inaccessible by TCL. Because the bootloader cannot be unlocked, it simply is not possible to flash a custom recovery or a patched boot image for systemless root support. System-wide root is not possible due to TCL's secure boot chain configuration and dm-verity. Until an exploit is found to bootloader unlock this device, rooting is not possible.
Click to expand...
Click to collapse
levone1 said:
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
Click to expand...
Click to collapse
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
fliproc said:
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
Click to expand...
Click to collapse
Sorry, I honestly don't remember now - I just happened to have tje phone for a short time at that moment, so I was messing around with it... I remember there was nothimg special about it. I jist followed the instructions from the mtk-root thread and it worked.
Amazing Temp Root for MediaTek ARMv8 [2020-08-24] | XDA ...
Braadleyah said:
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
Click to expand...
Click to collapse
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
$cronos_ said:
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
Click to expand...
Click to collapse
unlock bootloader and root with https://github.com/bkerler/mtkclient
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
UPDATE: After hearing from some members regarding the Hydra Tool, and doing a little bit of research on the method, it appears that I was completely wrong on my.statement. Members here on XDA as well as Hovatek have confirmed that the A509DL bootloader can indeed be exploited with the Hydra Tool method, opening the door to systemless root with Magisk. Thanks guys for the info and guidance. I have one of these devices and look forward to unlocking & rooting soon. Thanks @PrivyetCyka for the info.
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Viva La Android said:
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
Click to expand...
Click to collapse
I sure would like to give it a whirl, but I haven't had that phone in over a year
Anyway, I decided to stop buying devices made deliberately less functional by their manufacturers.
PrivyetCyka said:
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Click to expand...
Click to collapse
I stand corrected on my statement. I was incorrect. Out of curiosity, does the Hydra tool require the dongle in order to unlock the bootloader?
@PrivyetCyka send me the Magisk packed boot image and I will unpack it and disable secure boot. I can then pack it back up and link it to you. Are you referring to only secure boot or also AVB 2.0/dm-verity?
I didn't use hydra tool I used MTKClient from GitHub and did an entire system read back to have a backup then just renamed boot.bin to boot.img used magisk to patch it and then used the same MTKClient tool to reflash it... I have a twrp I made for it also but I don't know how functional it is as far as flashing things and backups , the only thing I tried to flash was the magisk zip just to see what would happen and that tripped the secureboot , I used the mediatek secureboot tool and it says it's disabled but it's still not booting past the secureboot fail screen.. when I get home I'll get the files and upload them tonight
hello. first of all i don't speak english and i use google translate and i'm sorry for that.
I have an asus-me302kl tablet. I wanted to install twrp but now it's locked. I installed firmware with rawdate but it has no function. I need help unlocking the bootloader. recovery mode does not turn on either. I am wondering if there is a pat file or some other method to unlock the bootloader. Thanks in advance. I hope I was able to explain myself.
please help
civan34 said:
please help
Click to expand...
Click to collapse
This low-end tablet is heavily outdated ( 7 years old ), means you won't find a TWRP suitable to it.
jwoegerbauer said:
This low-end tablet is heavily outdated ( 7 years old ), means you won't find a TWRP suitable to it.
Click to expand...
Click to collapse
First of all, thanks for the answer. this tablet is a customer tablet. and it's my fault that it's locked. For this I need to unlock the bootloader. is there no tool to flash the software? I managed to install the .rawdata firmware. and the device has root permission but I couldn't go further. Now I'm waiting like this.
@civan34
My suggestion:
Re-flash tablet's Stock ROM ( is a ZIP-file ) to bring tablet back to its initial state ( what includes flashing the Stock Recovery ).
When that's done you can start to unlock tablet's bootloader by means of Fastboot, if it's not denied by OEM/Carrier.
If tablet's bootloader got successfully unlocked you can try to flash LineageOS v15 ( Android 8 Oreo ) onto tablet.
jwoegerbauer said:
@civan34
My suggestion:
Re-flash tablet's Stock ROM ( is a ZIP-file ) to bring tablet back to its initial state ( what includes flashing the Stock Recovery ).
When that's done you can start to unlock tablet's bootloader by means of Fastboot, if it's not denied by OEM/Carrier.
If tablet's bootloader got successfully unlocked you can try to flash LineageOS v15 ( Android 8 Oreo ) onto tablet.
Click to expand...
Click to collapse
I can't install the stock firmware. Doesn't allow flashing over fastboot. Doesn't allow flashing via recovery mode. Is there a program to install stock firmware?
@civan34
A Stock ROM gets flashed by means of ADB
Example command sequence:
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_ON_PC>
adb reboot
jwoegerbauer said:
@civan34
A Stock ROM gets flashed by means of ADB
Example command sequence:
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_ON_PC>
adb reboot
Click to expand...
Click to collapse
I am a little novice at the command line and do not know how to type the command you typed. Should I type as you wrote, or do I need to change the name of the zip on the computer?
my command
(adb sideload stock.zip) and I get read error for this command.Since I don't speak English, I didn't understand exactly how to write the command. I don't want to overwhelm you, sorry for that
I'm in the same boat.
I picked up 4 of these from an auction. I can't unlock any of them, because the Asus tool, (ME302KL_UnlockTool_Instructions) zip file, no longer works. TWRP is available 3.2, link is below. I have rolled back to the stock ROM on 2 of the machines, no joy. Any suggestions or guidance, would be greatly appreciated. Thanks.
https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Link to Asus Unlock file
https://drive.google.com/file/d/1mzntnfm5OlHbKd1cYkd1YEFs6CYeKqmn/view?usp=sharing
jbone899 said:
I picked up 4 of these from an auction. I can't unlock any of them, because the Asus tool, (ME302KL_UnlockTool_Instructions) zip file, no longer works. TWRP is available 3.2, link is below. I have rolled back to the stock ROM on 2 of the machines, no joy. Any suggestions or guidance, would be greatly appreciated. Thanks.
https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Link to Asus Unlock file
https://drive.google.com/file/d/1mzntnfm5OlHbKd1cYkd1YEFs6CYeKqmn/view?usp=sharing
Click to expand...
Click to collapse
I contacted Asus a few times about this Bootloader issue, but today I took a different approach. It appears they Blacklisted the ME302KL from the servers, because it is EOL. I made it clear to them. that I can't access the Asus Cloud or any other Asus tool loaded on the machine and I can't do OTA updates either. I made it clear that I should be able to at a minimum be able to upgrade to 4.4.4 from 4.2.2 after resetting the device. They agreed and are escalating the issue up the food chain.
My hope is they remove it from the blacklist which will fix the "Network Error" message when trying to use the Unlock Tool for the bootloader. I will circle back around, once I hear back from them....
jbone899 said:
I contacted Asus a few times about this Bootloader issue, but today I took a different approach. It appears they Blacklisted the ME302KL from the servers, because it is EOL. I made it clear to them. that I can't access the Asus Cloud or any other Asus tool loaded on the machine and I can't do OTA updates either. I made it clear that I should be able to at a minimum be able to upgrade to 4.4.4 from 4.2.2 after resetting the device. They agreed and are escalating the issue up the food chain.
My hope is they remove it from the blacklist which will fix the "Network Error" message when trying to use the Unlock Tool for the bootloader. I will circle back around, once I hear back from them....
Click to expand...
Click to collapse
No joy. Asus says they are under contract with AT&T. The ME302KL has been black listed and Asus will not add it back to the unlock tool or provide any support AT ALL!. They keep telling me the unlock tool isn't theirs. But the amount of times Asus's name is used in the EULA, tells me otherwise. I'm waiting to hear back from AT&T on their position on the matter. Stay tuned...
Ok campers, i have a work around for the ME302KL AT&T bootloader issue. I just verified AT&T can unlock the devices, they just verified 3 devices for me. Only catch, you have to have an account with them.
So, If you like people actually being able to hear you on a call, you probably have a different service, like i do. Based on the call, there are really only 2 options. Option 1, Harassment. Someone you know, has them as their provider. A family member, a friend maybe your priest. So, my suggestion is to harass them into they adding the device, under their plan. They only need to do it long enough, for you to get it upgraded. Once AT&T unlocks it, upgrade the OS, add TWRP and create a custom recovery that never goes back to KitKat. then, have them cancel it off their account. At the most, you're looking at $25 for the month, if anything at all.
Option 2 - Go Prepaid for a couple of months. This one is tricky based on the T&C's on their website. You will need to create a new account, $30 for 5 5gb a month. No contract and what you don't use, rolls over to the next month. Make sure to read their T&C's ased on new prepaid accounts with BYOD. I told the agent I wanted to Only use broadband service, no phone for when im working in the field, until i'm still under contract with Verizon. She pitched services, i dodged and evaded. She told me a month to month prepaid plan was doable, to get it unlocked. They would be able to unlock it for free and so i could upgrade the OS. So, it's not too terrible, just annoying to jump through so many hoops. The first option, would be the easiest.
These are just suggestions. I take no responsibility if you brick the device once it's unlocked. It is AT&T and the device may be commiting suicide in lieu of being on their Network. :0)
I sent the message to AT&T with imei of my ME302KL but the answer is been "the manufacturer doesn't have an unlock code for this device".
Help me to unlock my device.
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.