Database Develop

Bricked HTC One(writed recovery to boot partition)

Hello dear guru's =)
I have an HTC One international. Today i try to get root access and install custom recovery, whent i flash recovery i missed that chose a boot partition to install it. Now phone boots only into recovery, and from my PC, adb or fastboot don see it, but in usb devices its present.
Im on linux Ubuntu 13.04.
In phone dont have any backup.

The phone can't boot in bootloader?

Guich said:
The phone can't boot in bootloader?
Click to expand...
Click to collapse
When i chose from CWM recovery menu "Reboot recovery", phone boot into download mode, and thats all. Fastboot or adb dont see it.
But. In usb device list:
In download mode:
Bus 002 Device 061: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero / Thunderbolt (Charge Mode)
In recovery mode:
Bus 002 Device 063: ID 0bb4:0f91 HTC (High Tech Computer Corp.)

Assuming you didn't corrupt your boot loader you should be able to get at the boot loader and use fastboot to flash a new recovery.
Power the device off
Hold power and volume down, the phone should turn on and load into the boot loader.
From there you can select fastboot (navigate menu with volumn buttons, power button to select fastboot).
You can use this command to flash a recovery:
Code:
fastboot flash recovery recovery.img

If you can enter bootloader,you may try formatting partitions from fastboot,and flashing them afterwards,that is if bootloader is unlocked.
You can also lock your bootloader and try installing RUU,it will put your phone back to stock,
P.S. - I'm new to this,so please consult with more experienced members,before doing anything

ZloY909 said:
Hello dear guru's =)
I have an HTC One international. Today i try to get root access and install custom recovery, whent i flash recovery i missed that chose a boot partition to install it. Now phone boots only into recovery, and from my PC, adb or fastboot don see it, but in usb devices its present.
Im on linux Ubuntu 13.04.
In phone dont have any backup.
Click to expand...
Click to collapse
you "fastboot flash boot recovery.img"? you may want to check this thread: http://forum.xda-developers.com/showthread.php?t=2478438&page=3
if that doesn't help, post back

Guys, we have to check if he can boot in bootloader/fastboot.
So, @ZloY909, if you're in recovery, adb can recognize your phone?
And, in CWM, there is the option: reboot bootloader?
As download mode you mean bootloader?

ZloY909 said:
Has the same problem, flashed CWM Recovery to the boot partiotion. Can you give me more info about that magic what you are done to cennect your phone to fastboot? =)
Thanks.
Best Regards.
Click to expand...
Click to collapse
fastboot shouldn't be affected.
when you connect your phone to the PC, does it the text in bootloader change from "FASTBOOT" to "FASTBOOT USB"

Guich said:
Guys, we have to check if he can boot in bootloader/fastboot.
So, @ZloY909, if you're in recovery, adb can recognize your phone?
And, in CWM, there is the option: reboot bootloader?
As download mode you mean bootloader?
Click to expand...
Click to collapse
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"

ZloY909 said:
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
Click to expand...
Click to collapse
"screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds" -> that's stock recovery
Before, when you are in bootloader (image attached), are you able to "fastboot devices" and it shows up? because the bootloader is not affected by the recovery.
basically "fastboot flash boot recovery.img" put the custom recovery where the kernel is supposed to be.
First thing you need to get/confirm working is bootloader/fastboot.

ZloY909 said:
adb or fastboot is not recognize my phone. In cwm recovery i have only reboot option or reboot into recovery. I have the same situation as tha developer in other post.
when i chose boot to recovery i have : "screen with a phone icon and a green image like i can connect via usb or something, but then it turns red after about 30 seconds"
Click to expand...
Click to collapse
In cwm adb will work.
So i think you have some issue with drivers.
And, however, if you turn off the phone, you can't access in bootloader with a longpress of power and vol-?

Hey, so I'm the one who had this same situation. What I had to do from what I recall is go to CWM screen, cleared the cache, even in advanced the davlik cache, then I believe (and you might have to try different combinations of this, because I don't 100% remember as I had before tried so many different ways) I unmounted the system mount, then went to reboot from the first screen to get to the bootloader (hold power button and volume down). After this, I clicked on Fastboot and it then went to Fastboot USB. This is where you should be able to connect. Don't leave this screen until you flash the recovery in the right place and then properly install the ROM. Let me know if you get to at least connecting and I can even send over an image for your boot, so you can at least get your phone back.
It can be done, I had the same situation so your phone is not bricked. Just keep working at it.

herrfricke said:
Hey, so I'm the one who had this same situation. What I had to do from what I recall is go to CWM screen, cleared the cache, even in advanced the davlik cache, then I believe (and you might have to try different combinations of this, because I don't 100% remember as I had before tried so many different ways) I unmounted the system mount, then went to reboot from the first screen to get to the bootloader (hold power button and volume down). After this, I clicked on Fastboot and it then went to Fastboot USB. This is where you should be able to connect. Don't leave this screen until you flash the recovery in the right place and then properly install the ROM. Let me know if you get to at least connecting and I can even send over an image for your boot, so you can at least get your phone back.
It can be done, I had the same situation so your phone is not bricked. Just keep working at it.
Click to expand...
Click to collapse
I will check this out. Thanks for your reply.
Now i reinstall to win8, reinstall drivers and adb.

Guich said:
In cwm adb will work.
So i think you have some issue with drivers.
And, however, if you turn off the phone, you can't access in bootloader with a longpress of power and vol-?
Click to expand...
Click to collapse
Thanks for your reply. This help me to get to the bootloader.
Now i try to flash boot.img into boot =)

Ok. I have working phone =)
Thanks for yours replies.

[Q] Verizon Developers Edition help

Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!

08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.

Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!

I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?

08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).

Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.

I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.

08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?

samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.

What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?

It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...

Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.

08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...

Once you are in the boot loader screen does "fastboot devices" recognize your device?

samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.

Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?

08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...

Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.

Happy to help

Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.

Took OTA with custom recovery

Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!

boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.

KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.

switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update

I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev

Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!

slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079

switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...

This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.

switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop

Bootloader Loop

Hey, I have a Moto X 2014. I'm running a cynanogen mod on it. For some reason the phone is stuck in bootloader mode, then starts up with the cynanogen logo, then just goes back into bootloader and repeats. I've held the power and lower volume key to get into the bootloader menu. I've tried normal, recovery, and factory and nothing seems to work at all. I cant seem to figure out how to get into TWRP, which I think if I can that could solve the problem by wiping some data and flashing a new ROM. Any thoughts or ideas how to fix this? Also, the phone wont show up as registered on my computer when I plug in the USB cord, so an command prompt "adb recovery" isn't an option I think. If you need more specifics please ask! Really dont want to have to get a new phone.

You can try to enter recovery through the PC command 'fastboot reboot recovery'. If that doesn't work, look up how to flash the stock firmware using fastboot.

[FIXED] Fastboot? Recovery bootlooping, but never getting there

Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?

you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock

The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(

frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.

hey guys follow this youtube
managed to unbrick my phone

smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..

This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!

the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus