[Q] HTC One X+: infinite loop (in some cases) - HTC One X+

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..

Related

Is my bootloader unlocked? Rooting status: UNAVAILABLE in service menu

Unlocking bootloader wasn't allowed on my phone, but I decided to give it a try anyways. Flashtool reported that the unlocking process was finished, but the progress bar was stuck somewhere at the half-way point for 10 minutes or so. After this, rooting status in the service menu changed to Unavailable, and I can't tell whether my bootloader is unlocked or not, or somewhere in between.
I tried flashing a custom rom, it gets stuck indefinitely on the animated boot screen, but I don't get any errors, crashes, or warnings while installing the zip in TWRP.
I noticed that after the "unlocking" procedure, my phone takes significantly less time to boot and the interface seems to lag less.
So what is going on here? Have I really somehow unlocked my bootloader?
Try relock bootloader, and unlock bootloader again
I have the same issue
I want to unlock my bootloader and in status it says available no or when i tried to unlock it it says unavailable
Please help
Mine too.
I can only use my Sim slot 2 (slot 1 is not working)
I need help.
I tried installing the new marshmallows from Xperifirm but still not working.
Rooting status: UNAVAILABLE

Moto Z bricked OEM Locked

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

Moto G4 needs help Unlocking Bootloader

Motorola G4 XT1625
Minor Problem: Phone will not start normally, only boots into Fastboot mode.
Minor Problem: Phone is oem Locked
Major Problem: I never went into "settings" on the phone and ENABLED OEM UNLOCKING.
Question: Is it possible to get this phone flashed with stock ROM?
A little background. Not a developer, phone started acting up a few days ago, shutting down or rebooting on its own, do not remember anything such as an update or my clearing of the cache occurring in that time frame, but I was still hoping it was a software issue that would work itself out. Now the phone fails during start up and reports this
STARTUP FAILED
ERROR: Failed to pass validation , backup to fastboot.
It does mention I should use Software Repair Assistant to recover the phone, which correct me if I'm wrong , only works with Verizon phones. I did try the SRA, it connected to the phone, but would stall about halfway through.
I have found much info on this forum regarding unlocking the bootloader of this phone, I have installed on Moto tools on my PC, requested and received an unlock code, connected to the phone and can send commands via command line. Unfortunately when I send the oem unlock the phone responds that I need to enable development mode in settings, which I cannot get to because the phone wont boot to the OS. Is there an easy way around this that I'm just not seeing?
In the end the problem may be hardware related, I just hate to give up on it so easily. Contacted Motorola about the device, as it turns out the unit was 6 days out of warranty ( that's if you use the Amazon ship date, it was only actually 2 days out if you use the activation date). Their response was as expected, sorry can't help you, thanks for being a Motorola customer, have wonderful day, next........
MSC 1/24/18

can't sign into account

I found some old threads covering this issue but none where it was resolved. I was given a brand new Note 4 which ended up with a bug on the lock screen (kept saying incorrect pin). I ended up wiping everything (which bricked it), then flashed a new ROM on with someone's help. It starts up again and asks for wi-fi info etc., but once I get to the MI sign in screen it keeps saying incorrect details. I know my details are correct, so is there anything I can do about this to get the phone actually working again?
Delete all data and flash custom ROMs if your Ur bootloader us unlocked.

Corrupted Bootloader & Missing IMEI (But phone still works)

So basicaly I was being lazy and in a rush. I had done something like this before on much older phone(s) with no issues...
I backed up my working LG G5 in TWRP all partitions. I brought exactly the same model for my wife and wanted to restore my backup to that phone (I have made many customisations on my rom and didnt want to have to manually do it all again for her)
However after unlocking the bootloader, flashing TWRP and installing new base rom (all went fine) I then went to restore my old backup onto this new phone, stupidly I ticked all partitions to restore. I have a feeling that I should have only done the larger partitions. Once I rebooted I got the "cant be trusted" message, I reflashed in UPPERCUT but then the phone booted and then had secureboot enabled. I hit the wrong password (as there was none) 30 times which then forced a format. Now the phone boots fine and works 100% BUT...BUT....
I now can no longer unlock the bootloader as I think its trying to use MY phones bootloader (as its unlock.img says its the wrong one, I have tried both MY phones original unlock.img and my wifes new phones unlock.img but both dont work) I cannot relock the bootloader as it says its already locked... this also now means that through LG official software I cannot recover the phone. Only UPPERCUT can see the phone. I can get to download mode and fastboot.
Also the phones IMEI now says 0, this worried me however her SIM card is working 100% fine (I guess that the IMEI
is cached somewhere, but im worried that if I use some cleaning tools it may scrub it and then she will have no network access)
So basicaly if her phone starts to play up (or I want to upgrade it to Oreo / Lineage at a later date) can anyone offer me advice on how to...
A: Fix / Restore the bootloader (I dont mean recovery) Im confused as to if this is stored on a chip or can be reflashed from the kdz firmware images.
B: Resore the IMEI (I have it written down) incase we get any network issues in the future. Can it be resored or regenerated without some fancy hardware, ie only through software.
C: I dont have Root or TWRP access it seems, any way of Getting Magisk or Super SU on a phone without bootloader unlock, root access or TWRP?
I have had many years experience and never bricked a phone but almost did this time.
I decided to post a solution here, because it was one of the first Google results when I was looking for some help.
Long story short, I did exactly same mistake of restoring all partitions, including the EFS, between two same LG devices. Turns out it messes with IMEI, which is a big no no and phone locks. Now you can't unlock the device again, because there is no IMEI to use in unlocking. Also no flashing or erasing anymore, because it just fails.
So the IMEI needs to be restored first.
My phone was in a bootloop constantly showing the "cant be trusted" message, but I managed to fix that using LGUP. Apparently not all partitions are locked, because trying to flash the same system with LGUP fixed the bootloop, but failed to flash clean system and the data that TWRP flashed was still there. Trying to restore system to factory settings also fails, but it doesn't matter.
Fortunately I was able boot the system, which made fixing it easier than you'd expect:
1. Fixing the IMEI from booted system (no root or unlocking needed):
- Access the hidden menu on your device by dialing a proper number. For LG G5 H850 it is *#546368#*#850#
Where 850 in the last part is your phone model. The number will vary for different models.
- Go to SVC Menu -> CRCWIZARD Test
- Switch tab to Auto MID
- Here you can enter your new IMEI and WiFi and BT MAC addresses, or you can just generate it.
You can also use the generate option for all values and then manually change only the IMEI for the original one.
- Press MID Write button and reboot your device.
- That's it. IMEI issue should be fixed now.
2. Now that you restored your original IMEI, you can again unlock your device using the same unlock.bin file that you used to unlock bootloader the first time.
Voila. From now on the device is again unlocked and you can just go back to flashing whatever you need.

Categories

Resources