Hi guys:
My Evitare had the following symptoms, at the first this was locked, original, AT&T branded, with some little bug in the camera, then I get a unlock code in HTCDEV; I unlock the bootloader and I flash the recovery (finally the TWRP 2.6.6.), then I flash a custom ROM…. Working apparently fine, but with the network locked to AT&T, after a few days I buy a unlock code in Cellunlocker (awesome service), I was working hard various days with the code because the device request the code, I put it but at the restart the phone request again for the same code but this not work (with custom and stock roms), only at the new restart the code works and is recognized for the device. Finally forcing the restart at th same time what the unlock code was entered (in the first time), at the new boot the network is unlocked.. but after this odyssey, the phone boot fine but at the load of the sense loader the signal, data, voice is lost, then the device reboot again in a loop, until the radio is on..
I saw what the logcat is not clear about the reason, but I´m sure that the bug is of security.. In old boots after I reflash the RUU 1.19.502, the device show the message “Restricted access changed”, then the fail is loading the radio, the device selectively load or not the radio.. I resolve this loading forced the device again with the use of the apps Fast Reboot and Quick Boot of the market, because the one x+ alone, boot infinitely in some cases
Do you have some idea of the reason for it?.. I think what the S-Off will cure this bug, then I waiting anxiously for it… This would unlock totally the partitions, hboot, radio, etc.. Thanks in advance!
did you input the code on a PROPER STOCK rom or on a custom rom?
Lloir said:
did you input the code on a PROPER STOCK rom or on a custom rom?
Click to expand...
Click to collapse
Hi, Lloir.. On all the ROMS showed and related with the HOX+.. finally the code did work, but now, the phone lost the radio frequently, the screen don't wake up after the sleep... lately, it´s slow, the touch is not responsive... Finally I think what the HOX+ fo AT&T in some devices have a failure in the eMMC, the logcat show several fatal errors reading sectors or files after random starts or reebots, executig programs, the modem or radio sometimes lost...
No one reaches this conclusion, but I saw several users with same symptoms...
My eMMC according to "eMMC check" is the K1U00M with firmware rev 0x15 and date 11/2012.. it's a "sane chip"
Regards..
*********** 04/10/2013 **************************************************************
Finally, I've changed the motherboard and.. voila!... no more troubles.. Thanks..
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
After rooting my Z2 and backing up the TA partition, I've discovered that the bootloader is not unlockable (it's a Vodafone branded device).
Is there a nefarious way in which to bypass this? I understand that the whole point is to keep it locked, but it's an old enough device so I may have missed where it's possible.
Otherwise what are my options for an up-to-date custom rom? As indicated, I've already achieved root and have TWRP installed. I tried flashing Lineage via recovery but got an E: unknown command [log] error.
I'm in the same boat unfortunately. I bought a used phone that had Vodafone UK. It was marked as SIM-unlocked, and that seems to be true; the service info doesn't show any filled checkmarks nor counters in SIM lock information. However, bootloader seems to be locked forever - flashtool reports "Bootloader status : NOT_ROOTABLE" and phone's service menus also say that rooting status is "bootloader unlock allowed: no".
I wasn't even aware there are Sony phones that are not SIM-locked but are still boot-locked without any way to unlock.
I would really want to upgrade from Android 6 to at least 7 because there are some specific apps that work only from A7. Wondering if there is any custom ROM that would run on stock A6 kernel but with everything else from A7? It should be possible to install such a ROM even on a bootlocked device, right?
Since posting I've discovered some answers. The bad news is that, no, custom ROMs are limited without an unlocked bootloader.
The potentially good news is that you can pay for an aftermarket SIM unlock, which has the side effect of also allowing the bootloader to be unlocked.
I've not tried it myself, but do a search for "Sony cable unlock credits" for some leads.
Yea I also am stumbling upon this same news, in my city there are some shady areas so I will ask around and see if anyone is capable of doing it and will let you know.
So far my phone has bootloader locked, sim locked with 3 attempts left so I will work on unlocking those and then rooting the phone and digging deep after
Lets cross our fingers that somethings comes up
So far online , I find only old videos and outdated information, websites down and nothing else.
One thing is for sure, if your bootloader can be unlocked, you just go to sony official website and follow their instructions and its free and easy,
But if it says ""bootloader unlock allowed: no" then...lets see what can we do.
Hey I am willing to pay, why not if its going to unlock the bootloader 100%
This might be the first problem that everyone didn't encountered yet
So recently I unlocked my bootloader in order to flash custom ROM, but recently I reverted back to stock and decided to lock my bootloader in order to get OTA updates.after getting OTA updates I decided to unlock the bootloader again, when I was trying to boot to bootloader mode, it just shows the bootloader icon and boot back to system. I tried to use the in depth test app but it only shows me to request to exit deeptesting and the query status is not submitted.i tried to request to exit deeptesting but it only says no internet connection. I tried almost everything including flashing previous ROM, changing region, etc but none of it works
My device is Realms GT Master Edition (RMX3360) C.09In