Hi Friends,
I have HTC One dual, I unlocked it from htcdev to get android latest updates.
When I have seen Android 4.4 update for my device, I tried to install it, but due to some unknown problem, device was getting rebooted again and again. So I selected option factory reset, but this also not worked bcoz device got unlocked.
Later I have tried to push some .img files on to device, finally the device got tampered, unlocked.
Please suggest me best solution to get android back on the device.
atleast suggets me to install any software in that device.
Thanks,
Anil
Hi Friends,
I have HTC One dual, I unlocked it from htcdev to get android latest updates.
When I have seen Android 4.4 update for my device, I tried to install it, but due to some unknown problem, device was getting rebooted again and again. So I selected option factory reset, but this also not worked bcoz device got unlocked.
Later I have tried to push some .img files on to device, finally the device got tampered, unlocked.
Please suggest me best solution to get android back on the device.
atleast suggets me to install any software in that device.
Thanks,
Anil
Hi Fellow Users!
I just bought LG v10 yesterday with international warranty even though i live in UAE, the problem is i am following all the steps from "step by step guide to root for tmo" but unfortunately i am not able to boot into phone recovery which is odd for me as i am a long time user of android, is that possible my phone doesn't have one? I tried everything adb, manually but nothing worked, i once booted my phone into recovery via adb but i saw green android picture with no command written on it and fastboot didn't worked there so there is that.
1) i tried dirty_cow but stuck at getenforce "permissive didn't appeared which is must needed, i think its related to my bootloader"
2) should i follow LGUP procedure even i am not sure my bootloader is unlocked?
P.S my phone is TMO although its unlocked to use any network.
Please advise, thank you
Unfortunately flashing KDZ file bricked my phone, :crying:
Now its just off it doesn't turn on tried everything any advise?
Update: Went to LG TechServe and handed over my phone to re-flash the original firmware, bad thing they don't cover international warranties as i live in UAE and the model i have is TMO with international warranty so there's that.
Reason to share the story, may people learn from this.
Have you tried with Kingroot app or kingoroot app? These apps can root many devices.
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
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.