On my HTC One M7 Sprint I have the most recent Cyanogenmod 11 snapshot installed as well as a fairly recent version of CWM. I recently could not connect to the network for what ever reason, and was unable to get connected by playing with my settings. This is the first time I have experienced this problem on my device. I rebooted into recovery and tried factory reset to see if that would work things out. While in that process, it was able to reset data, but got hung up on wiping the cache for about an hour.
I restarted the device and was still unable to connect to the network, and tried the factory reset option in the settings, which also got hung up. Now all my device does is boot to the cyanogenmod screen, or if I try to boot into recovery, I get a gray background with the rotating geometrical shape and a small blue bar underneath. I'm at work, so I don't have many tools available here to solve my problem and need some pointers to fix this.
Honestly at this point I wouldn't mind just getting the phone back to stock. If someone could help me getting from here to there, I would be greatly appreciative.
gothmog1114 said:
On my HTC One M7 Sprint I have the most recent Cyanogenmod 11 snapshot installed as well as a fairly recent version of CWM. I recently could not connect to the network for what ever reason, and was unable to get connected by playing with my settings. This is the first time I have experienced this problem on my device. I rebooted into recovery and tried factory reset to see if that would work things out. While in that process, it was able to reset data, but got hung up on wiping the cache for about an hour.
I restarted the device and was still unable to connect to the network, and tried the factory reset option in the settings, which also got hung up. Now all my device does is boot to the cyanogenmod screen, or if I try to boot into recovery, I get a gray background with the rotating geometrical shape and a small blue bar underneath. I'm at work, so I don't have many tools available here to solve my problem and need some pointers to fix this.
Honestly at this point I wouldn't mind just getting the phone back to stock. If someone could help me getting from here to there, I would be greatly appreciative.
Click to expand...
Click to collapse
Try this Sprint HTC One RUU! This will take you back to stock ROM, firmware and recovery.Follow the instructions in the OP.
majmoz said:
Try this Sprint HTC One RUU! This will take you back to stock ROM, firmware and recovery.Follow the instructions in the OP.
Click to expand...
Click to collapse
So I did the steps, and when I ran oem lock it gave me an error saying too many links, but my bootloader screen says s-on rw. When I try to run the ARU wizard, it cant find my phone.
Edit:
I ran the Fastboot oem rebootRUU command to try to fix it, and now I get the brushed htc screen, but when I try to flash a zip, it always says waiting for device. I have all the drivers installed and my computer knows the phone is plugged in, or else I couldn't run the reboot ruu command. I am really frazzled and appreciate your help.
gothmog1114 said:
So I did the steps, and when I ran oem lock it gave me an error saying too many links, but my bootloader screen says s-on rw. When I try to run the ARU wizard, it cant find my phone.
Edit:
I ran the Fastboot oem rebootRUU command to try to fix it, and now I get the brushed htc screen, but when I try to flash a zip, it always says waiting for device. I have all the drivers installed and my computer knows the phone is plugged in, or else I couldn't run the reboot ruu command. I am really frazzled and appreciate your help.
Click to expand...
Click to collapse
I take it that bootloader still is UNLOCKED. Since you are S-ON you cannot run a RUU with the bootloader still unlocked. In the post for the RUU, you can scroll down a little to find the firmware. Download it and install per the OP's instructions. After you successfully install the firmware, then try the RUU procedure again by first locking the bootloader.
majmoz said:
I take it that bootloader still is UNLOCKED. Since you are S-ON you cannot run a RUU with the bootloader still unlocked. In the post for the RUU, you can scroll down a little to find the firmware. Download it and install per the OP's instructions. After you successfully install the firmware, then try the RUU procedure again by first locking the bootloader.
Click to expand...
Click to collapse
It looks like my bootloader is "relocked"
I tried to flash the firmware, but it just hung at waiting for device.
gothmog1114 said:
It looks like my bootloader is "relocked"
I tried to flash the firmware, but it just hung at waiting for device.
Click to expand...
Click to collapse
Review this post Q#2 about installing drivers. Let try to install a new HTC driver but before you do remove the HTC driver from Windows using Control Panel's "Program and Features". When the new one is installed, remove HTC Sync Mgr if it was installed. Once your PC recognizes your phone then try to run the firmware, then the RUU. You should be able to run both of these with relocked bootloader.
majmoz said:
Review this post Q#2 about installing drivers. Let try to install a new HTC driver but before you do remove the HTC driver from Windows using Control Panel's "Program and Features". When the new one is installed, remove HTC Sync Mgr if it was installed. Once your PC recognizes your phone then try to run the firmware, then the RUU. You should be able to run both of these with relocked bootloader.
Click to expand...
Click to collapse
I updated to the most recent driver, and that is the only HTC software installed on my rig. It got pact the initial connection error, but now I keep getting an error trying to flash the firmware.zip from the video. I also try to run the program and it gives me a connection error 171 at the sending stage. I've checked the MD5 for everything. I then tried unlocking to start everything from the beginning. The unlock went fine. and when I ran oem lock it came back as:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.158s
Then when I tried to flash the firmware, I get FAILED (remote:12 signature verify fail)
gothmog1114 said:
I updated to the most recent driver, and that is the only HTC software installed on my rig. It got pact the initial connection error, but now I keep getting an error trying to flash the firmware.zip from the video. I also try to run the program and it gives me a connection error 171 at the sending stage. I've checked the MD5 for everything. I then tried unlocking to start everything from the beginning. The unlock went fine. and when I ran oem lock it came back as:
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.158s
Then when I tried to flash the firmware, I get FAILED (remote:12 signature verify fail)
Click to expand...
Click to collapse
In bootloader/FASTBOOT USB try this:
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot-bootloader
it should say FASTBOOT USB
now type fastboot oem lock
now run ARUWizard.exe from the extracted folder.
majmoz said:
In bootloader/FASTBOOT USB try this:
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot-bootloader
it should say FASTBOOT USB
now type fastboot oem lock
now run ARUWizard.exe from the extracted folder.
Click to expand...
Click to collapse
I'm cleared the cache, and can see my S/N, but I still get the same errors.
gothmog1114 said:
I'm cleared the cache, and can see my S/N, but I still get the same errors.
Click to expand...
Click to collapse
What computer are you using? Are you using USB 3 or USB 2? Are you still unlocked?
majmoz said:
What computer are you using? Are you using USB 3 or USB 2? Are you still unlocked?
Click to expand...
Click to collapse
I have a desktop I built myself. I've used a few usb cords, in both the USB 2 and 3 ports directly attached to the motherboard. Some commands make it clear my computer can communicate with the phone, like fastbooot devices. The ARUwizard program also will progress past the first couple steps, and then get tripped up at the step I described above. I've sideloaded other roms before without it being a problem, but I had some issues getting a stock based viperrom on there before. I don't remember what the hang up was, but cyanogen worked until I lost signal.
I have my unlock token and can unlock the phone without problem. I just get it hanging at the cyanogen boot animation when I do it. When I lock the phone I get the above error, but the phone says it is locked. If I try to run the oem lock command again, it says the phone is already locked. The phone says it is S-on, tampered, and relocked after I run oem lock.
gothmog1114 said:
I have a desktop I built myself. I've used a few usb cords, in both the USB 2 and 3 ports directly attached to the motherboard. Some commands make it clear my computer can communicate with the phone, like fastbooot devices. The ARUwizard program also will progress past the first couple steps, and then get tripped up at the step I described above. I've sideloaded other roms before without it being a problem, but I had some issues getting a stock based viperrom on there before. I don't remember what the hang up was, but cyanogen worked until I lost signal.
I have my unlock token and can unlock the phone without problem. I just get it hanging at the cyanogen boot animation when I do it. When I lock the phone I get the above error, but the phone says it is locked. If I try to run the oem lock command again, it says the phone is already locked. The phone says it is S-on, tampered, and relocked after I run oem lock.
Click to expand...
Click to collapse
It might be the time to try Ubuntu 12.04. Here is a guide to make a Linux USB Q#5, this will allow you to boot into Linux without installing the OS. You have to use 12.04 for this process to work. The newer version requires quite a few extra steps to run the ADB and fastboot commands. The downside is that you will not be able to run .exe files in Ubuntu/Linux. I think if you could get the firmware to run, it would solve some of your issues.
majmoz said:
It might be the time to try Ubuntu 12.04. Here is a guide to make a Linux USB Q#5, this will allow you to boot into Linux without installing the OS. You have to use 12.04 for this process to work. The newer version requires quite a few extra steps to run the ADB and fastboot commands. The downside is that you will not be able to run .exe files in Ubuntu/Linux. I think if you could get the firmware to run, it would solve some of your issues.
Click to expand...
Click to collapse
I wasn't able to get the ubuntu method to work. I tried unlocking and flashing CWM again, which didn't work. I was able to install TWRP. From there I was able to sideload the nocturnal GPE rom, which starts up fine and appears to connect to the network, but then after a few seconds reboots without warning.
gothmog1114 said:
I wasn't able to get the ubuntu method to work. I tried unlocking and flashing CWM again, which didn't work. I was able to install TWRP. From there I was able to sideload the nocturnal GPE rom, which starts up fine and appears to connect to the network, but then after a few seconds reboots without warning.
Click to expand...
Click to collapse
I'm sorry, I'm fresh out of ideas. It might be a hardware issue since it is constantly rebooting and you can not get fastboot to work correctly.
Hi all,
A few days ago I installed a custom ROM, which broke my android pay. I tried to re-lock the bootloader to fix this via the fastboot oem lock command, and i'm now stuck in a bootloop.
I can get the phone to boot into fastboot mode, and it shows up as such when checking via command prompt. I also have a backup of the phone I made a few days ago. I've tried to unlock the phone using the fastboot oem unlock command, but get the following error:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.008s
I bought the phone second hand with an unlocked bootloader, if that makes a difference? I've set up a new Mi account and applied for an unlock code.
Does anyone have any tips on how to proceed? Thanks in advance!
Stupid thing to think relocking your bootloader would fix android pay while still on that custom rom, whe have hacks for that you know >> magisk14/15.2
Do you still have twrp? also try to flash stock images from xiaomi themselves, here.
that should at least get you booting again.
Hi,
Thanks for replying, i'll download the global stable version. Is it a case of sideloading this once complete? I still have TWRP installed if it makes a difference, I just can't reach it :/
Yes I do feel pretty stupid, and thanks for the link to magisk - hadn't heard of it until now but i'll definitely be using when/if I get my Mi back up and running. Is there anyway to unlock the bootloader other than the Mi Unlock app?
Thanks!
EDIT: Okay, so i tried flashing via the MiFlash tool and got the following error:
FAILED: Remote device is locked. Cannot erase.
Any idea of where to go from here?
So, I fixed it! In the off chance anyone is as unlucky/stupid/trigger happy as me, and finds themselves in teh same situation, here's the solution:
If you can't get it into EDL mode because you can't switch it off (mine kept rebooting), follow this video:
https://www.youtube.com/watch?v=ED96PJ-qYMM
It's in a foreign language but is clear enough - take the back off, unscrew the cover and short the pins he shows you after disconnecting the battery, then plug into your computer.
Your phone will pop up as a Qualcommdevice under the ports section of Device Manager. You should then be able to flash via MiFlash as per usual.
Phew, hairy there but sorted in the end. I'll now wait for the unlock code from Xiaomi, and do a bit more reading in future!
A much easier way to solve this problem
You don't have to follow any long tutorial. Nor do you have to open your phone up. Just power it into fastboot mode, download the mi unlock tool that you used the first time to unlock your bootloader and unlock your device once again. Then you can use miflash to flash the fastboot rom on your device and it won't throw up any errors. Once that's done, just reflash the custom recovery. Install the custom rom, use magisk for root and you're good to go. Safety net won't be tripped and android pay will still work. No need to rip your phone apart to fix it.
Hi,
I am having a Moto G6 Indian model ( XT1925-13 ).
I have flashed different versions of Roms in that for nearly 3-4 times with OEM Unlocking in the settings.
But, For the last time. I was thinking that when i change any other rom then i may not get OTA updates. So, that i have tried to lock the OEM and i have given a cmd
Code:
fastboot oem lock
and
Code:
fastboot flashing lock
after that i have rebooted my phone and from then. I have tried to switch ON then. Without my involvment. Phone Booting password has changed automatically. Then I have tried to re-flashed my ROM to stable rom.
Initially I have cleared everything including system, boot also.
Later on when i tried to re-flash the ROM. It was showing a message.
Code:
flashing_locked
in bootloader mode.
I didn't unlocked OEM Option in settings before doing.
Is there any way to reset or to solve this issue.
Even I am ready to solve this issue with hardware solution.
Please do reply me. Thank you.
Oh man. You bricked it quite effectively. Do you have TWRP recovery installed? If yes, you could restore a backup.
You should never re lock the bootloader on a phone that are flashing ROMs on. Expensive lesson.
ProBlem Fixed By Command
i Did same and almost Got heart attack But thanks god problem is Fixed By Command In ADB And Fastboot.
>fastboot flashing unlock
Please Hit Thanks to Support my Reply If this will Also Work for you
I've been an android developers for years and years now and even have made my own ROMs, but this phone....this phone is testing me. I unlocked it months ago to install an original Android 11 ROM, but it was awful and lacked support for even the most basic functionality, so I flashed the stock image back. That alone was a nightmare and I don't remember how I managed it. That being said, the Asus Android 11 update is rolling out OTA and can be downloaded directly from their site. I downloaded it and put it in the root directory, where it is found on start-up, but when I tell it to install, it fails after a few seconds and doesn't give me any explanation for it. I thought it may be that the bootloader is unlocked, so I've been trying to re-lock it for weeks with no success. I managed to get the damn fastbootd mode recognised by my computer and it sees the phone, but when I give it any relock command I receive this error:
"FAILED (remote: Command not supported in default implementation)"I have no clue what to make of that or what it even means. My only guess is that the commands I'm using aren't supported in the latest version of the tools. I've tried the following commands:
fastrboot oem asus-lock
fastboot oem lock
fastboot oem asus_csk_lk
fastboot flashing lock
fastboot oem relock (I don't think that's a real command, but I was irritated and figured it was worth a shot)
I'm at a total loss. All I want is to get Android 11 to the damn thing and the OTA isn't coming through to my phone. The phone itself is an international model I bought from China back before it was released in the US. IDK if that's causing a problem, but at this point I'm out of ideas. I'd also note that normal fastboot, found by going to the bootloader instead of "adb reboot fastboot" doesn't even allow the computer to recognise the phone and when I try to install the fastboot driver via device manager, it outright refuses to install it. There's no apparent way to get it to install the driver anyway. I AM able to get it to install the driver and see the phone while in fastbootd mode.
Anyone got any ideas?
fastrboot oem asus-lock
This worked for me on tencent phone converted to ww firmware. I had no troubles with updating to 11 from 10 as well. I had also no troubles to flash raw firmware with bootloader unlocked.
Waiting now for new ww firmware as CN has been already released couple days ago.. If they didn't fix thing I'm annoyed with I going back to 10!
Try different cable. Had guy from reddit with same problem like yours and simple new cable sorted everything
fastboot oem asus_csk_lk should do it.
I think you may be in the wrong fastboot mode You need to be in the bootloader. Try powering off and boot with Vol UP + Power until you land on the bootloader page (don't navigate to Fastboot from the bootloader menu, just stay on the bootloader menu. Doing 'fastboot reboot bootloader' should also do the trick but suggest trying with the physical buttons.
So, i got a second hand mi 5 last week. Seller told me that it had software issue and I thought I could fix it. Because it was really cheap.
The device was stuck on bootloop when I had it. But I was able to open mi recovery and fast boot menus. i tried many options to flash a stable stock rom. The most useful one was to flash via XiaomiTool v2. It says successfully flashed and reboots but stuck on bootloop every time. (Tried few times already).
the bootloader is locked and no mi accounts binded to the device. Computer detects the device successfully.
I tried adb commands as well, but since bootloader is locked i couldn't get any further to flash or wipe.
Any useful suggestions?
Can you still access to fastboot mode?
If so, you need fastboot oem unlock to unlock bootloader first, before anything else.