I just bought a Moto E 4G LTE that is prebranded US Cellular (no contract). (XT1526 with lollipop 5.0) I don't need to use this device as a phone and do not plan on activating a carrier at any point, but just want to use it connected to my home wifi.
The problem is that the device will not allow me to bypass or skip the activation screen, and gives me no home button or option to even connect to my wifi. My previous Moto E (KitKat) simply allowed me to skip the activation and use the device..this one just keeps calling USC to activate over and over and the only option I have is to call or power off.
I have been searching the web all night and still have not found a solution (which granted may be due to my lack of knowledge in this area in general, and hopefully the solution is obvious to someone more knowledgeable). I tried touching the corners + volume up, but it hasn't worked and I tried different combinations, perhaps I have the wrong corner-order?
Anyone who can help me get this thing to let me in would be greatly appreciated! Thank you in advance.
Anyone? Surely there is a way to get past this activation screen...I'm not completely tech-inept and can follow instructions if it's something I've never done. Would unlocking the phone get past it? Can I even unlock it without being able to get to the home screen? Please help!!
It might be a US Cellular-only thing, as both my Verizon Moto E2 and Moto-Unlocked E2 can skip through the setup process without a SIM by just hitting Next or Skip.
Unlock the bootloader and flash TWRP and then any ROM, I recommend SuperR's Stock ROMS
P0PETIN said:
Unlock the bootloader and flash TWRP and then any ROM, I recommend SuperR's Stock ROMS
Click to expand...
Click to collapse
Keep in mind that you cannot unlock the bootloader in 5.1 until you get into the settings, activate the Developer Options (by tapping Build Number a bunch of times), and tick "Allow OEM Unlock".
If you cannot get into the settings at least once, you will not be able to install TWRP or flash anything.
What you need to do if you are stuck on the activation screen is wait 5-10 minutes while the activation runs and fails. After some time you will have the option to connect to wifi. After that you can get into the settings menu.
harryspar said:
Keep in mind that you cannot unlock the bootloader in 5.1 until you get into the settings, activate the Developer Options (by tapping Build Number a bunch of times), and tick "Allow OEM Unlock".
If you cannot get into the settings at least once, you will not be able to install TWRP or flash anything.
What you need to do if you are stuck on the activation screen is wait 5-10 minutes while the activation runs and fails. After some time you will have the option to connect to wifi. After that you can get into the settings menu.
Click to expand...
Click to collapse
Old topic, but USC carrier activation can be bypassed by simply removing the SIM card during initial setup.
xtermmin said:
Old topic, but USC carrier activation can be bypassed by simply removing the SIM card during initial setup.
Click to expand...
Click to collapse
Good to know!
By the way I don't see a way in the menus to enable GSM/WCDMA. Do you know how to do that?
harryspar said:
Good to know!
By the way I don't see a way in the menus to enable GSM/WCDMA. Do you know how to do that?
Click to expand...
Click to collapse
Download "Network" or "4G Switch" from the Play Store. Open, scroll down a little and look for "LTE/CDMA auto". Change that to "LTE/GSM auto".
If that doesn't work, you might need to do the same workaround that is needed for the Verizon model:
http://forum.xda-developers.com/moto-e-2015/general/help-confirm-5-1-how-to-verizon-moto-e-t3264258
http://forum.xda-developers.com/moto-e-2015/general/how-to-verizon-moto-e-2015-gsm-network-t3098953
My daughter's put in her password incorrectly to many times and it erased all data and it says choose language then hit start so I do and it says phone activation please wait while we activate your new phone. This may take up to 5 minutes. Emergency calling will not be possible during the remainder of setup. It has been stuck on this page for a couple of hours. What do I do?
Ldkreitz said:
My daughter's put in her password incorrectly to many times and it erased all data and it says choose language then hit start so I do and it says phone activation please wait while we activate your new phone. This may take up to 5 minutes. Emergency calling will not be possible during the remainder of setup. It has been stuck on this page for a couple of hours. What do I do?
Click to expand...
Click to collapse
Turn off, remove the SIM, turn on.
@xtermmin. Thanks for the advice but didn't work at all. I use the phone overseas and had unlocked the sim tray to get to work with another carrier since I while ago (4 to 5 months ago) with this method (http://forum.xda-developers.com/moto-e-2015/general/how-to-verizon-moto-e-2015-gsm-network-t3098953).
As of the morning of today, upon turning the phone up, it didn't want to connect nor Wi-Fi neither GSM. I made a factory reset and right after the Verizon logo screen the phone get on the wizard screen for a few seconds (5 to 8 secs) and then leave me on the screen saying "Pleas wait, this may take a few minutes". When I read your comment thought that could be, but there is no change after been done.
NegiSensei01 said:
@xtermmin. Thanks for the advice but didn't work at all. I use the phone overseas and had unlocked the sim tray to get to work with another carrier since I while ago (4 to 5 months ago) with this method (http://forum.xda-developers.com/moto-e-2015/general/how-to-verizon-moto-e-2015-gsm-network-t3098953).
As of the morning of today, upon turning the phone up, it didn't want to connect nor Wi-Fi neither GSM. I made a factory reset and right after the Verizon logo screen the phone get on the wizard screen for a few seconds (5 to 8 secs) and then leave me on the screen saying "Pleas wait, this may take a few minutes". When I read your comment thought that could be, but there is no change after been done.
Click to expand...
Click to collapse
If removing the SIM doesn't allow you to get past the activation screen, then it sounds like something on your ROM might have corrupted or something. Have you tried reflashing the stock firmware?
xtermmin said:
If removing the SIM doesn't allow you to get past the activation screen, then it sounds like something on your ROM might have corrupted or something. Have you tried reflashing the stock firmware?
Click to expand...
Click to collapse
I'm trying getting it done with this guide (http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936), but can do anything after putting the phone on fastboot. BTW, I think before doing the factory reset the phone had an update (a security patch of may or april). IDK how it installed but well now I'm stuck there.
My screen present me this:
AP Fastboot Flash Mode (Secure) [in red]
BL: 80.0F (sha-e9687e2, 2015-04-27 14:23:53)
Baseband: <not found>
Product/Variant: surnia XT1528 8G P3
Serial Number: TA0050CZX1
CPU: MSM8916 ES1.0
eMMC: 8GB Micron RV=06 PV=12 TY=17
DRAM: 1024MB Elpida S8 SDRAM DIE=4Gb
Console [NULL]= null
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official
Transfer Mode: USB Connected
Now I got this
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
TA0050CZX1 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Dunno, you'd probably have better luck asking in one of the stock-flashing topics in the General forum.
try taking out the sim chip like i did on my moto E phone ..... once i did then it let pick a wi-fi network and then i was go on with setup of google account info and was then able to restore all app's and data of google servers
hopes this helps alot people like it did me
because i was going crazy about till i tried taking out my sim chip .. then it worked
please help with my moto e
My phone hungs up and I did a hard reset it works but sadly when I open it the phone asking me to enter a google account that was sync in the phone and I am so unlucky because this phone was given to me by my sister who are in heaven now please help me what to do I don't have computer
Moto E4 Easily bypass Verizon activation
Remove the phones sim card. Thats it. Its that easy. The phone then allows you to do the typical android / moto setup.
xtermmin said:
Old topic, but USC carrier activation can be bypassed by simply removing the SIM card during initial setup.
Click to expand...
Click to collapse
This solution worked for me on my Moto Z Droid. I removed the SIM card after starting the activation process (phone ON). The phone went immediately to the wifi log in screen and I was all set! Thanks!
Related
Was there ever a kitkat stock ROM and was it always 5.1 out of the box? Anyway to down grade or even 5.0 or 5.0.2?
cell2011 said:
Was there ever a kitkat stock ROM and was it always 5.1 out of the box? Anyway to down grade or even 5.0 or 5.0.2?
Click to expand...
Click to collapse
Launched with 5.0.2. Think there are some firmware images in the firmware topic in the General forum. Should be able to downgrade, but I haven't tried it.
I don't think downgrading would work. I updated my XT1521 to Marshmallow, and then tried to roll back to 5.1.1, and the flashing failed every time I tried.
NSDCars5 said:
I don't think downgrading would work. I updated my XT1521 to Marshmallow, and then tried to roll back to 5.1.1, and the flashing failed every time I tried.
Click to expand...
Click to collapse
MM -> LP fails, yeah, but LP -> LP might work.
Looking at Post #3 in this topic, the TC downgraded from XT1528 5.1 to 5.0(.2) to mess around with rooting: http://forum.xda-developers.com/moto-e-2015/general/root-t3194165
Additionally, people have downgraded the XT1527 from 5.1 to 5.0.2 in order to restore LTE Band 12 functionality (search "downgrade"): https://www.reddit.com/r/tmobile/comments/39j0qb/psa_motos_51_update_to_the_2015_moto_e_disables/
xtermmin said:
MM -> LP fails, yeah, but LP -> LP might work.
Looking at Post #3 in this topic, the TC downgraded from XT1528 5.1 to 5.0(.2) to mess around with rooting: http://forum.xda-developers.com/moto-e-2015/general/root-t3194165
Additionally, people have downgraded the XT1527 from 5.1 to 5.0.2 in order to restore LTE Band 12 functionality (search "downgrade"): https://www.reddit.com/r/tmobile/comments/39j0qb/psa_motos_51_update_to_the_2015_moto_e_disables/
Click to expand...
Click to collapse
Hm, maybe. Just in case, look out for any "FAILED" messages while flashing the old firmware - if any, retry that command, or flash back to the newer firmware.
Anyone go through device protection crap? I got a xt1528 from a ebay store that has tons of phones and clean esn. I got it on friday last week and still cant get in. Isnt it just a 72 hr hold or what? Also on the verizon model the message app makes it harder for the workaround and network dialer it dont work esp when youre trying to use this phone as gsm. Not sure how long to wait for the hold though. Do i still need the previous password or email that was synced before i got this phone? I hope not or else this is a brick. Ive factory reset Friday and changed password hoping that would work. Nothing so far
cell2011 said:
Anyone go through device protection crap? I got a xt1528 from a ebay store that has tons of phones and clean esn. I got it on friday last week and still cant get in. Isnt it just a 72 hr hold or what? Also on the verizon model the message app makes it harder for the workaround and network dialer it dont work esp when youre trying to use this phone as gsm. Not sure how long to wait for the hold though. Do i still need the previous password or email that was synced before i got this phone? I hope not or else this is a brick. Ive factory reset Friday and changed password hoping that would work. Nothing so far
Click to expand...
Click to collapse
"Device protection"? If it prompts you for a password on bootup even if you factory reset, then it sounds like it was locked remotely by the Android Device Manager service (original owner might have lost it or something, and remotely locked it). If that's the case, return it.
"Message app makes it harder for the workaround"? What workaround? The Verizon model has both the Hangouts message app and Verizon's Message+ app. You can choose which one you want to use.
"network dialer it dont work esp when youre trying to use this phone as gsm"? The dialer works for GSM, you just have to turn on the GSM radio. Follow the instructions in one of these topics:
http://forum.xda-developers.com/moto-e-2015/general/how-to-verizon-moto-e-2015-gsm-network-t3098953
http://forum.xda-developers.com/moto-e-2015/general/help-confirm-5-1-how-to-verizon-moto-e-t3264258
xtermmin said:
"Device protection"? If it prompts you for a password on bootup even if you factory reset, then it sounds like it was locked remotely by the Android Device Manager service (original owner might have lost it or something, and remotely locked it). If that's the case, return it.
"Message app makes it harder for the workaround"? What workaround? The Verizon model has both the Hangouts message app and Verizon's Message+ app. You can choose which one you want to use.
"network dialer it dont work esp when youre trying to use this phone as gsm"? The dialer works for GSM, you just have to turn on the GSM radio. Follow the instructions in one of these topics:
http://forum.xda-developers.com/moto-e-2015/general/how-to-verizon-moto-e-2015-gsm-network-t3098953. Cant get into hangouts app i only have wifi. Is there any settings app i can sideload
http://forum.xda-developers.com/moto-e-2015/general/help-confirm-5-1-how-to-verizon-moto-e-t3264258
Click to expand...
Click to collapse
I cant get adb to be recognized. I have minimal adb and fastboot everytime i try adb says error device not found. I can only get as far as setup wizard i know all the tricks but even the japanese input language is missing in settings language
cell2011 said:
I cant get adb to be recognized. I have minimal adb and fastboot everytime i try adb says error device not found. I can only get as far as setup wizard i know all the tricks but even the japanese input language is missing in settings language
Click to expand...
Click to collapse
Have you tried installing the Motorola PC drivers and enabling ADB in Developer Options?
As for the Japanese language input, I see it on my XT1528. It's at the very bottom of the list, right before it loops back around to Bahasa Indonesia. (日本語 Nihongo)
I can't get past setup wizard is what I'm saying. And there is no Japanese input the Google one on the keyboard that everyone refers to to get to the 10 key and privacy policy. I know the ultimate goal is to get into dev options. I've been reading. I only have winime for Japanese input for keyboard. The rest is Korean and so forth. Seems to be a newer phone maybe. Today is the 3rd day maybe by 1pm est it will work. I got the phone Fri at 1 PM and reset and changed password. How can I get adb recognized if I don't have USB debugging enabled or unknown sources for the matter. I can't look inside. Stuck at setup wizard or Google protection sign in. Hangouts don't work in shared screen
cell2011 said:
I can't get past setup wizard is what I'm saying. And there is no Japanese input the Google one on the keyboard that everyone refers to to get to the 10 key and privacy policy. I know the ultimate goal is to get into dev options. I've been reading. I only have winime for Japanese input for keyboard. The rest is Korean and so forth. Seems to be a newer phone maybe. Today is the 3rd day maybe by 1pm est it will work. I got the phone Fri at 1 PM and reset and changed password. How can I get adb recognized if I don't have USB debugging enabled or unknown sources for the matter. I can't look inside. Stuck at setup wizard or Google protection sign in. Hangouts don't work in shared screen
Click to expand...
Click to collapse
Sounds like the issue I mentioned earlier. If you can't make it past initial setup due to it asking for a Google account password, then the phone you bought has been locked by the original owner via the Android Device Manager service. The phone you bought might be lost/stolen or the seller is trying to rip you off. Unless the owner left ADB turned on, there's no way around it. Return it and get a new one.
xtermmin said:
Sounds like the issue I mentioned earlier. If you can't make it past initial setup due to it asking for a Google account password, then the phone you bought has been locked by the original owner via the Android Device Manager service. The phone you bought might be lost/stolen or the seller is trying to rip you off. Unless the owner left ADB turned on, there's no way around it. Return it and get a new one.
Click to expand...
Click to collapse
Not even flashing different firmware would work? Or the modem?
cell2011 said:
Not even flashing different firmware would work? Or the modem?
Click to expand...
Click to collapse
Install Moto Device Drivers (download from Motorola).
Boot device into fastboot mode (power off, hold Vol Down, power on).
Connect phone to your computer via USB.
Open command line, go to the Minimal ADB and Fastboot folder.
fastboot.exe devices
If it shows your device, you should be able to downgrade, but I have no clue if this will get around the ADM block.
Follow the stock firmware flash instructions in the General forum: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
If not list or has a weird listing, you won't be able to flash anything. Return it.
Also, flashing modem does absolutely nothing in regards to getting around an ADM block.
Does anyone here have an extra or unlocked for that matter that they can sell. I have 20.00 i can send to someone honest. I use at&t so either xt1528 or unlocked and as long as not on that crazy 72 hour hold sign in crap. That is why im having this problem in the first place. Thanks PM me. Now at 4 days still cant get into my phone. Am i the only one that doesnt have google japanese input? If i had it i know how to bypass. This must be a newer phone all i have is the winime japanese keyboard and that doesnt do anything for me. Im looking for the a with the squirly line to long press i dont have that. I know the method to get to usb debugging etc and factory reset is the goal. But this thing is a brick in my opinion
Be very careful when buying this phone used I'm going on 10 days still have the Google verification on error device was last reset and synced with another account. Xt1528 does not have the bypass or Japanese input keyboard with the (a) to bypass. I've seen all the videos on this model it don't work. Maybe an earlier kernel or build of 5.0 when it first came out but not 5.1. This is just for xt1528 Android 5.1 you been warned. I have a paperweight now
cell2011 said:
Be very careful when buying this phone used I'm going on 10 days still have the Google verification on error device was last reset and synced with another account. Xt1528 does not have the bypass or Japanese input keyboard with the (a) to bypass. I've seen all the videos on this model it don't work. Maybe an earlier kernel or build of 5.0 when it first came out but not 5.1. This is just for xt1528 Android 5.1 you been warned. I have a paperweight now
Click to expand...
Click to collapse
Or just return it and buy one that hasn't been lost/stolen/locked by seller.
xtermmin said:
Or just return it and buy one that hasn't been lost/stolen/locked by seller.
Click to expand...
Click to collapse
Can't. I'm just looking for another now.
cell2011 said:
Not even flashing different firmware would work? Or the modem?
Click to expand...
Click to collapse
I"m in the same situation where I can't bypass the account verification on the xt1528 but in my case it isn't secondhand. The owner isn't tech savvy so they asked someone to setup a google playstore account for them. So when there was problem with the phone and the screen blacked out I factory reset the phone. Everything came back but they don't know the google account that was used so now it's stuck during setup. The japanese keyboard trick doesn't work on this model cause it's not the same one in the tutorials but I was able to get to the dialpad by viewing the motorola privacy policy and following the same instruction. My issue is I can't enable the test mode to activate ADB debugging. *#*#4636#*#* doesn't work.
dknlght said:
I"m in the same situation where I can't bypass the account verification on the xt1528 but in my case it isn't secondhand. The owner isn't tech savvy so they asked someone to setup a google playstore account for them. So when there was problem with the phone and the screen blacked out I factory reset the phone. Everything came back but they don't know the google account that was used so now it's stuck during setup. The japanese keyboard trick doesn't work on this model cause it's not the same one in the tutorials but I was able to get to the dialpad by viewing the motorola privacy policy and following the same instruction. My issue is I can't enable the test mode to activate ADB debugging. *#*#4636#*#* doesn't work.
Click to expand...
Click to collapse
Ive tried that too and its all messed up on the Verizon model. I wonder how many hundreds of phones are paperweights now
cell2011 said:
Ive tried that too and its all messed up on the Verizon model. I wonder how many hundreds of phones are paperweights now
Click to expand...
Click to collapse
man, I have a VRZ paperweight like u. my one is not 2nd hand, I tried with same mail address and password that I used before hard reset. but no luck.
I've re flashed 5.1.1. got same.
now I'm planning to downgrade 5.0. don't know if it'll work or not. coz I was already flashed 5.1.1
plz give me at least one happy news...:crying:
I have a ANS UL40 phone through Assurance wireless / >Virgin Mobile> Sprint.. and am trying to root this phone so I can get the SPC code to run DFS tools. Have used DFS and loaded phone and unlock with default password, but when I try 000000 spc unlock says device offline and all prompts in all fields go from yellow to red and in a few minutes go back to yellow showing device info.
I need info off this phone to flash my SM-N900P phone over to Assurance Wireless. The UL40 phone uses a sim card, have tried in note 3 but no service and then sim locked please reboot phone. I have tries on UL40 many different rooting apks and through pc. Most say root fail or your phone doesn't seem to be able to root. Any help would be appreciated. To root the ANS UL40 and also how to flash over Note 3. I have done flashing before on a note 2. So i basically know what to do. When I did try to flash over the note 3 I just get your account cannot be verified when calling 611 (without the sim) but when I insert sim its says no sim or sim locked reboot phone. Thanks
Guess nobody knows
kingroot rooted the ans, but I rebooted and it earesed it, and it didn't seem to give out permission s, not in a joking manner
---------- Post added at 01:44 AM ---------- Previous post was at 01:41 AM ----------
lexcin said:
kingroot rooted the ans, but I rebooted and it earesed it, and it didn't seem to give out permission s, not in a joking manner
Click to expand...
Click to collapse
do you know which 32bit drivers this phone might use?
I tried that one and it didn't root it and so many other programs and or apk's. Do not know if this phone is arm -- 64-- or 32. I do know that the maker of the phone actually is Teleepock company in China ** http://www.teleepoch.com/en/ ** no info on this model phone on their website..
Default file manager is CyanogenMod File Manager
mjmplus said:
I have a ANS UL40 phone through Assurance wireless / >Virgin Mobile> Sprint.. and am trying to root this phone so I can get the SPC code to run DFS tools. Have used DFS and loaded phone and unlock with default password, but when I try 000000 spc unlock says device offline and all prompts in all fields go from yellow to red and in a few minutes go back to yellow showing device info.
I need info off this phone to flash my SM-N900P phone over to Assurance Wireless. The UL40 phone uses a sim card, have tried in note 3 but no service and then sim locked please reboot phone. I have tries on UL40 many different rooting apks and through pc. Most say root fail or your phone doesn't seem to be able to root. Any help would be appreciated. To root the ANS UL40 and also how to flash over Note 3. I have done flashing before on a note 2. So i basically know what to do. When I did try to flash over the note 3 I just get your account cannot be verified when calling 611 (without the sim) but when I insert sim its says no sim or sim locked reboot phone. Thanks
Click to expand...
Click to collapse
Hi,
My friend just got the same phone and while setting it up for her I noticed that the default file manager is called CyanogenMod File Manager. It's probably meaningless but thought I'd share it just in case there's some sort of CyanogenMod back door. Good luck and if you do get it rooted please let me know.
I found a paid root that will root UL 40 Assurance choose the 6 mo lan.. https://www.oneclickroot.com/support-packages/
I wouldn't have asked on here if I wanted to pay for it, and they are not a guarantee they can do it. have read somewhere that someone ask them to do the same phone and they could not............ And no still no root. Probably does not matter. Talked to Assurance wireless rep today and they said lots of people are complaining about this phone. I have had in less than 2 weeks of getting it, had to have them warranty it and they sent me the same one. It would reboot on it's own and yes did factory reset. Now have the replacement, haven't done any kind of rooting or anything and on day 2 it starting to not be able to make phone calls. Says phone is not responding. Did a factory reset on this one and still doing same thing. Sometimes it does make a call and sometimes not. Pissed I am....
I stumbled across a site. Idk but it looks like it could contain some valuable info you may need or may be looking for. Send me a message or email me for the link. Since I've not posted before, it won't allow me to post the link.
I have decided to go to another provider for my cell phone and the UL40 phone will be no more. After talking to them so many times and finding they are complete idiots. Because they keep sending me a phone that stops working correctly after 1-3 days. Even before I started trying to root. I even talk to a real English speaking (LOL) person and they told me what I already knew, the ANS UL40 phone is a complete piece of ****. So many people have complained to them about that phone they decided not to ship out anymore. Now what kind of phone i will get from other carrier, I'll have to wait and see. Thanks all.............
mjmplus said:
I have a ANS UL40 phone through Assurance wireless / >Virgin Mobile> Sprint.. and am trying to root this phone so I can get the SPC code to run DFS tools. Have used DFS and loaded phone and unlock with default password, but when I try 000000 spc unlock says device offline and all prompts in all fields go from yellow to red and in a few minutes go back to yellow showing device info.
I need info off this phone to flash my SM-N900P phone over to Assurance Wireless. The UL40 phone uses a sim card, have tried in note 3 but no service and then sim locked please reboot phone. I have tries on UL40 many different rooting apks and through pc. Most say root fail or your phone doesn't seem to be able to root. Any help would be appreciated. To root the ANS UL40 and also how to flash over Note 3. I have done flashing before on a note 2. So i basically know what to do. When I did try to flash over the note 3 I just get your account cannot be verified when calling 611 (without the sim) but when I insert sim its says no sim or sim locked reboot phone. Thanks
Click to expand...
Click to collapse
I have the same phone and I still don't know how to get the MLS code, try enableling the diag ports with ##3424# and hopefully that way you'll get the spc I would let you know if I figure it out
I am looking for a custom ROM for my ANS UL40
Hello.
I was wondering if there would be anyone nice enough to make a custom ROM for the ANS UL40. I would do i tbut I don't have the coding skills or patience to do so.
ANS UL40 "Cast" compatibility w/Actiontec ScreenBeam Mini2
Asking if ANS UL40 "Cast" will run Actiontec ScreenBeam Mini2.
UL40 is "CAST" standard compatible with Mini2 (WiFi Mirocast and INTEL WiDi certified) ?
UL40 able to PARE WiFi and update Mini2 firmware. UL40 says CONNECTED, but click "CAST" and phone goes back to WiFi. Mini2 screen says Connection Failed.
If able to preform firmware update, then UL40 is communicating w/Mini2 so, UL40 should be compatible, but "CAST" fails.
Please advise.
Many kind thanks.
Any luck unlocking this phone so far?
Have not tackled that yet. LEMNO if you succeed.
Best.
RussianIce said:
Any luck unlocking this phone so far?
Click to expand...
Click to collapse
FedCURE said:
Have not tackled that yet. LEMNO if you succeed.
Best.
Click to expand...
Click to collapse
Hope someone can figure out how to gain root access on this phone I have it and It would be a blessing
you can unlock the bootloader in android dev settings "OEM unlocking", once in bootloader cmds like "fastboot oem unlock" or "fastboot flashing unlock" do nothing when connected with usb, what a shame. In recovery (vol up + power) there's an option to mount system, it does but I doubt that can lead to anything root access wise, btw, root noob.
mjmplus said:
... So many people have complained to them about that phone they decided not to ship out anymore...
Click to expand...
Click to collapse
Could you elaborate!?
In which market are you in?
It seems to me that they are still shipping it in many markets Assurance Wireless is in, like Oregon for example... so how did you come by that information?
I got this phone a couple days ago and got my msl code by running adb logcat while dialing ##data# and entering the wrong code, it was 536978 and used this on DFS to change it to 000000 then I was able to access everything once I entered ##diag# and then 000000, and enabled diagnostics. If I can get a working stock firmware or boot IMG I could root through magisk and then do separate fastboot boot (magisk patched)boot.img. I am unable to find a stock firmware for this device if anyone can let me know and I'll have root for us.
jdeandeck said:
I got this phone a couple days ago and got my msl code by running adb logcat while dialing ##data# and entering the wrong code, it was 536978 and used this on DFS to change it to 000000 then I was able to access everything once I entered ##diag# and then 000000, and enabled diagnostics. If I can get a working stock firmware or boot IMG I could root through magisk and then do separate fastboot boot (magisk patched)boot.img. I am unable to find a stock firmware for this device if anyone can let me know and I'll have root for us.
Click to expand...
Click to collapse
Did you ever create a working root? I have this phone as well.
micro sd card
Does anyone know what is the maximum micro sd card supported by this phone?
Sorry about post a new thread about this again, but my situation seems a little weird.
I got an S9+, from Australia Optus (but I'm in China), with the latest firmware, trying to get the missing "oem unlocking" option back but failed.
In download mode, both OEM and frp is off , RMM state: prenormal.
My procedure is:
1. Reset the phone without SIM card.
2. After finishing the whole setup and get into the destop, I plug in the sim card. (but didn't login google or samsung account, because I can't connect to google service. So if I want to get through the setup, I can't plug in the sim card or connect to Wifi.)
3. Then I connect wifi and login in samsung account to restore my backup.
4. Open Developer Options.
5. Wait 7 days. (the uptime is over 168 hrs, even over 300 hrs)
6. the "oem unlocking" is still missing .
Or the phone must online "the whole" 7 days?
Because sometimes the phone will lose the network in subway.
And the swiching between network and wifi won't make a difference, right?
I've already consult the Australia samsung customer-service, can't help me online. And the Samsung Centre in China didn't have the access to fix an S9+ sold in Australia.
Hope somebody can help me to fix this, I want to install a third party ROM.
You have to reset your device while the sim card is in the device , then in the setup you have to log in to your both google and samsung accounts , then wait 7 days , and it should appear , if it doesnt appearing simply use google to check how to fix the missing OEM Unlock option
ilan0098 said:
You have to reset your device while the sim card is in the device , then in the setup you have to log in to your both google and samsung accounts , then wait 7 days , and it should appear , if it doesnt appearing simply use google to check how to fix the missing OEM Unlock option
Click to expand...
Click to collapse
thanks! I'll try in this way.
so to clarify, whats the problem when you just leave the sim in, restore/wipe phone, login to google account, then wait 7 days and check dev options ?
jujubeans said:
so to clarify, whats the problem when you just leave the sim in, restore/wipe phone, login to google account, then wait 7 days and check dev options ?
Click to expand...
Click to collapse
The problem is Nothing Changed. OEM unlocking still missing. RMM state still prenormal. Can't do anything.
greenwhale6 said:
The problem is Nothing Changed. OEM unlocking still missing. RMM state still prenormal. Can't do anything.
Click to expand...
Click to collapse
Did you ever get this fixed? Mine doesn't appear either...
daviddema said:
Did you ever get this fixed? Mine doesn't appear either...
Click to expand...
Click to collapse
Check this out. Haven't try it yet because I have to use my phone all the time. But this method is worth trying. Would you mind to reply if you success Or not?
https://forum.xda-developers.com/sa...ide-root-install-twrp-samsung-t3747535/page38
greenwhale6 said:
Check this out. Haven't try it yet because I have to use my phone all the time. But this method is worth trying. Would you mind to reply if you success Or not?
https://forum.xda-developers.com/sa...ide-root-install-twrp-samsung-t3747535/page38
Click to expand...
Click to collapse
Which method? Can't even get started with installing TWRP if I don't get the OEM unlock option in developer options...
daviddema said:
Which method? Can't even get started with installing TWRP if I don't get the OEM unlock option in developer options...
Click to expand...
Click to collapse
You should flash the original fw (mine is optus) and leave the phone without a sim inside, connected to wifi, on all the time. Plugging the chinese sim might not unlock it.
I picked up a secondhand Pixel 4. The seller said that this phone was purchased directly from Google and the only services ever used with it were AT&T prepad and Google Fi, never under any contract. But when I do 'adb reboot bootloader' the device state says locked and the OEM unlock option is greyed out. I have read that some Pixels purchased from Google end up bootloader locked after using Verizon service. If that is the case, is there any hope of getting the bootloader unlocked? Or maybe it got locked by some other means that I'm not aware of. Is there any way to get a history of carriers used with the phone via the IMEI in order to get a better idea of what might be going on?
Also, when I run 'adb shell pm list features' I do notice these lines:
feature:com.verizon.hardware.telephony.ehrpd
feature:com.verizon.hardware.telephony.lte
Does this mean that this is a Verizon model phone? Seems strange that it would have Verizon packages for a Google model phone.
You must have a sim inserted and data turned on for OEM unlocking not to be greyed out. I took a clue I guess from others by inserting my AT&T sim (still greyed out), rebooted (still greyed out), turned on mobile data (still greyed out), and rebooted. Then there was the glorious OEM unlocking option available.
For other clueless people who might read this: I immediately connected my phone via usb to my laptop, shutdown the phone, and held the power and volume down buttons to get into fastboot mode. Then from a terminal on my laptop ran 'fastboot flashing unlock', and the phone gave me the option to unlock the bootloader. adb and fastboot were previously installed.
I have seen other people mention the OEM unlocking option becoming available on their carrier version Pixel phones after inserting a not yet activated sim from another carrier. The latest mention that I saw was here in post #3
https://forum.xda-developers.com/t/manual-unlock-bootloader-for-locked-at-t-device.4374613/
Happy days. Just in time for Lineage OS 19.1
Sell your phone, then buy again with oem unlcok on
fitzly said:
You must have a sim inserted and data turned on for OEM unlocking not to be greyed out. I took a clue I guess from others by inserting my AT&T sim (still greyed out), rebooted (still greyed out), turned on mobile data (still greyed out), and rebooted. Then there was the glorious OEM unlocking option available.
For other clueless people who might read this: I immediately connected my phone via usb to my laptop, shutdown the phone, and held the power and volume down buttons to get into fastboot mode. Then from a terminal on my laptop ran 'fastboot flashing unlock', and the phone gave me the option to unlock the bootloader. adb and fastboot were previously installed.
I have seen other people mention the OEM unlocking option becoming available on their carrier version Pixel phones after inserting a not yet activated sim from another carrier. The latest mention that I saw was here in post #3
https://forum.xda-developers.com/t/manual-unlock-bootloader-for-locked-at-t-device.4374613/
Happy days. Just in time for Lineage OS 19.1
Click to expand...
Click to collapse
Same with my pixel 4 xl, i purchased on second hand market. I check the phone imei offline without other carrier sim and it was an at&t set. However, the bootloader option was not grey out. I quickly, unlock the bootloader after that and installed lineage os 18. . No luck for those whom got greyed out.
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.