I rooted my phone temporarily with pie root for motorola devices:-
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623
and on some post, it was written that we could flash custom recoveries with it using rashr. I flashed TWRP using rashr but is showed an error "hab check failed for recovery failed to validate recovery image", I ignored for that time but now, I can't use my device because of it. I downloaded an ota update for 4.4.4 and pressed install now, my phone shut down and then it tried to get into recovery and again this error, I selected Normal Powerup but, it would, after one or two minutes, again shut down to install the update. I wanted to know if there is a way to stop it and can I get stock recovery from anywhere to solve it??
nitish159 said:
I rooted my phone temporarily with pie root for motorola devices:-
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623
and on some post, it was written that we could flash custom recoveries with it using rashr. I flashed TWRP using rashr but is showed an error "hab check failed for recovery failed to validate recovery image", I ignored for that time but now, I can't use my device because of it. I downloaded an ota update for 4.4.4 and pressed install now, my phone shut down and then it tried to get into recovery and again this error, I selected Normal Powerup but, it would, after one or two minutes, again shut down to install the update. I wanted to know if there is a way to stop it and can I get stock recovery from anywhere to solve it??
Click to expand...
Click to collapse
you can get the right stock image of your phone here (non-GPE):
http://sbf.droid-developers.org/phone.php?device=14
simply open the zip and look for the recovery.img file
then just put your device in bootloader mode and via
fastboot flash recovery recovery.img
you can get your stock recovery and hopefully then your 4.4.4 update will work
Then you are lucky, that your phone is still not upgraded to 4.4.4.
Just download the factory image from the location as mentionend before and restore.
Now my personal advice:
Do not upgrade to 4.4.4. There is still no Factory image out there.
I am in that situation that my Phone does not boot and i have to reflash.
It is not possible to Downgrade to older Versions for the moment. At least not a clean solution.
So actually i and some others need a solution to make a phone out of their brick.
Hope the factory image will come quick, or at least a proper solution to Downgrade.
bernida said:
you can get the right stock image of your phone here (non-GPE):
http://sbf.droid-developers.org/phone.php?device=14
simply open the zip and look for the recovery.img file
then just put your device in bootloader mode and via
fastboot flash recovery recovery.img
you can get your stock recovery and hopefully then your 4.4.4 update will work
Click to expand...
Click to collapse
I didn't see any firmware matching my system version so I found a number matching my starting numbers in system update, and downloaded a random file with those results
bernida said:
you can get the right stock image of your phone here (non-GPE):
http://sbf.droid-developers.org/phone.php?device=14
simply open the zip and look for the recovery.img file
then just put your device in bootloader mode and via
fastboot flash recovery recovery.img
you can get your stock recovery and hopefully then your 4.4.4 update will work
Click to expand...
Click to collapse
Thanks a tonne, I could upgrade to 4.4.4 and it allowed me to connect to my lg tv usinf wifi direct which further allowed me to use miracast but, the video sometimes get stuck, don't know where the problem is, phone or tv
Hello guys !
Today i decided that i want to unlock the bootloader for my htc one S C2. Managed to do that and managed to root it too. I installed TWRP (version 2.6.3.0) using a guide made by our firend, Bipe ( link here : http://forum.xda-developers.com/showthread.php?t=2175411 ) flashing it from my PC.
All went incredibly good ! Then,i decided that i should flash a new ROM.
I downloaded VIPER ROM and transfered it to my phone via USB. Now...silly me...decided to FULLY WIPE all the data on my phone,using TWRP's advanced wipe settings. I did that. All good. Then i recieved a message from recovery saying that my phone is not succesfully rooted or something similar and they gave me the option to install a new SuperSU. I accepted,by mistake,of curse,knowing that my phone is succesfully rooted after i used the Root Checher app from the Play Store. And then spoof... my phone stuck into a bootloop. Couldn't flash the ROM because i wiped all the data from my SD card,and also i have no backups saved. Furthermore my pc seems to not recognize the phone !
Using the same cable and the same USB slot it detected my old htc wildfire.
Please help me to get my phone back on track
EGandy said:
Hello guys !
Today i decided that i want to unlock the bootloader for my htc one S C2. Managed to do that and managed to root it too. I installed TWRP (version 2.6.3.0) using a guide made by our firend, Bipe ( link here : http://forum.xda-developers.com/showthread.php?t=2175411 ) flashing it from my PC.
All went incredibly good ! Then,i decided that i should flash a new ROM.
I downloaded VIPER ROM and transfered it to my phone via USB. Now...silly me...decided to FULLY WIPE all the data on my phone,using TWRP's advanced wipe settings. I did that. All good. Then i recieved a message from recovery saying that my phone is not succesfully rooted or something similar and they gave me the option to install a new SuperSU. I accepted,by mistake,of curse,knowing that my phone is succesfully rooted after i used the Root Checher app from the Play Store. And then spoof... my phone stuck into a bootloop. Couldn't flash the ROM because i wiped all the data from my SD card,and also i have no backups saved. Furthermore my pc seems to not recognize the phone !
Using the same cable and the same USB slot it detected my old htc wildfire.
Please help me to get my phone back on track
Click to expand...
Click to collapse
please help guys ! I installed the latest drivers from HTC and the PC seems to recgonize the phone but i can't access mass storage !
The phone can also recognize that it s pluged to the PC because i see <<FASTBOOT USB>> when i plug it in.
If you can access twrp look to sideboard your rom again.
superiscch said:
If you can access twrp look to sideboard your rom again.
Click to expand...
Click to collapse
i can acces TWRP . how do i do that if i don't have any backup made ?
If you can access twrp, than you can try to use the order
adb push ROM.zip /sdcard
...to copy a rom to you sdcard. Than you have the chance to flash the rom again.
But in general... Stuck at the bootloop is a famous failure.
If you are S-On (readable at the bootloader) you have to flash the Boot image after flashing any custom rom by extracting the boot.img outside the rom.zip and using the fastboot order
fastboot flash boot boot.img
In general I recommend to flash your phone to S-off when you want to flash custom roms - it makes many things more easier! You can get s-off in example with moonshine s-off.
Hope this could help
Sent from my One S using XDA Free mobile app
Weber2014 said:
If you can access twrp, than you can try to use the order
adb push ROM.zip /sdcard
...to copy a rom to you sdcard. Than you have the chance to flash the rom again.
But in general... Stuck at the bootloop is a famous failure.
If you are S-On (readable at the bootloader) you have to flash the Boot image after flashing any custom rom by extracting the boot.img outside the rom.zip and using the fastboot order
fastboot flash boot boot.img
In general I recommend to flash your phone to S-off when you want to flash custom roms - it makes many things more easier! You can get s-off in example with moonshine s-off.
Hope this could help
Sent from my One S using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for tryng to help but i sent the phone to the service and it appears that this whole procces completely messed up my MTP . so i can't connect the phone to any PC. that means no ROMS,no ADB pushes.
time to say bye bye to my One S i guess...
EGandy said:
Thank you for tryng to help but i sent the phone to the service and it appears that this whole procces completely messed up my MTP . so i can't connect the phone to any PC. that means no ROMS,no ADB pushes.
time to say bye bye to my One S i guess...
Click to expand...
Click to collapse
I'm no expert but if you are S-ON and you can see fastboot usb, then your phone is still fixable IMO.
you can flash a stock rom
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!
skyguy126 said:
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!
Click to expand...
Click to collapse
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
update: I have just figured out that adb is working with CWM, which i have installed right now Yay!now I can push files from my computer!!
https://androidxda.net/how-to-unbrick-moto-g-1st-gen-2013-after-lollipop-5-0-android-update/ :laugh::laugh:
pedrocarboni said:
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it using if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
Click to expand...
Click to collapse
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.
skyguy126 said:
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.
Click to expand...
Click to collapse
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Do this at your own risk:
Your system partition is corrupt, you need to enter adb shell and format /system into ext4s. Search on google for the command as I do not have it on the top of my head. I believe it has something to do with make_ext4s function.
pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Pedro, I have the same problem.
I can only access bootloader and recovery, but using adb sideload I can't flash any image (and version) that works.
I just get boot looping as you, and gpt.bin and motoboot.img files can't be flashed.
I've found that with Lollipop bootloader we can't install an older Android version.
My Moto G is now a paperweight, until the final stock Lollipop comes.
pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Hi, I experienced the same problem. Have you fixed your phone? Please give me some suggestion. Thank you.
Same problem with my Moto G 2013.
I've tried to downgrade and got problem. Now I can't flash an older motoboot.img and gpt.bin.
I'm using CyanogenMod 12, but every time when I boot, there is a line going down over the screen.
This line only disappear when I turn off and on the screen. Then everything backs to normal.
Is there a way to solve this?
This happened to me yesterday, i wento from my US Retail 4.4.4 to BR Retail 4.4.4 then via stock recovery flashing the OTA of 5.0, installed Xposed but gave me slow boots, like 5 min per boot, so i decided to downgrade, flashed 4.4.4 BR but after boot a black screen comes and doesn't go, think of flashing 4.4.2 US but the same isue, then decided to update again to 5.0 BR but stock recovery don't let me flash because an error, i flashed philz touch and do a factory reset, wipe data, cache, and everything, then flashed flashing 4.4.4 BR and then 4.4.2 US, the line down problem is nothing, only appears when you boot and, if you lock your phone for about 2-3 seconds, it dissappear (until you boot again), hope it helps, sorry for bad english
For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.
skyguy126 said:
For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.
Click to expand...
Click to collapse
skyguy126, I've not found any solution for this on forum.
Could you please show me a way?
For those that have problems downgrading, download this and follow this steps.
Once finished flash TWRP recovery and restore your nandroid.
Moto G not Booting, HELP
Hi everyone, I really need help with my moto G, it´s not booting into android after pressing the power button the moto logo comes up and the phone goes directly into fastboot displaying a message in pink color: version downgrade for boot
Failed to validate boot image.
I have been hours checking around for a solution and working now for the third day trying to solve the problem with no luck.
I have downloaded the original firmware for the device, tried to flash it and it doesn´t work, tried other countries firmware and they doesn´t work either.
The process will be partially ok but as it goes to flash the boot.img, recovery and system files it will give an error.
I also tried bootloader refresh, bootloader bricker and blankflash to try fix any possible bootloader issues.
The device has a locked bootloader since it is a moto g from AIO.
Please Help, It´s my only device and I cannot afford another one at this time.
There´s a few images from the flash process and device info
:crying:
You need to unlock your bootloader in order to flash various ROMs.
but in this model the bootloader cannot be unlocked it is CID 0X0010
How did this happen to your phone? What model phone do you have?
It´s a Moto G 2013, xt1032
It all begin trying to install a signed stock firmware that was supposed to be for that specific model: AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml
During the flash process it send some error messages but the process keep running until it finishes, once the device reboot it went straight to fastboot and since then I haven´t been able to get it back working.
Are you manually flashing each partition?
Maybe try a 4.4.4 ROM.
Yes, I have. I´ve also tried other signed firmware that have a .bat file that run all by itself but neither way it worked. It comes up with the error message: Invalid signed Image and below Preflash Validation Fail
Hi, I've updated officially to 5.0.2 but now I am selling the phone.
1) Rooted
2) Bootloader Off
3) Flashed GAPPS
After I did a factory reset, the phone isn't working 100%, I am missing the navigation key, lots of forced closed etc.
I tried to flash a ruu.zip via bootfast but have error.
Can I use a TWRP backup to restore? http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I don't want to mess it up.
story said:
Hi, I've updated officially to 5.0.2 but now I am selling the phone.
1) Rooted
2) Bootloader Off
3) Flashed GAPPS
After I did a factory reset, the phone isn't working 100%, I am missing the navigation key, lots of forced closed etc.
I tried to flash a ruu.zip via bootfast but have error.
Can I use a TWRP backup to restore? http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I don't want to mess it up.
Click to expand...
Click to collapse
To flash the RUU, your boot loader needs to LOCKED or RELOCKED. Open fastboot and type "fastboot oem lock" and then try flashing the RUU using bootloader.
Hi,
How can I find Stick RUU for m8sw?
I flashed TWRP, SuperSu, and xposed for lollipop. after that my phone worked just fine for almost a day. but it is stocked in boot logo. I cant fond anything on the web.
hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.
kpitao said:
hello all,
I need some help here; never seen this before and it's wierd.
I got a replacement HTC OneM8 (Verizon) yesterday, today I tried to setup with a copy of my Viper rom (5.01) but phone came with Android 4.4.4 so I did the following:
• used "sunshine" to unlock the bootloader and install SuperSU.
• install TWRP version 2.8.7.0
• backup stock rooted rom
• install lollipop vzw firmaware
all the steps completed successfully
Now my phone is all weird:
If I boot to bootloader it works fine but if I select "recovery" phone goes to TWRP Recovery v2.8.6.1 FROM here (recovery) any option that I choose to reboot the phone reboots to TWRP v2.8.7 even if I asked to reboot system.
I can never boot to the phone itself (system).
I want to completely remove TWRP 2.8.7 and keep TWRP v2.8.6.1
I already tried to flash the recovery over (was successful) but I'm still with this issue.
Click to expand...
Click to collapse
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery
kpitao said:
I already completed those steps and when I reboot my phone still shows TWRP 2.8.7...... is there a way to manually delete the recovery
Click to expand...
Click to collapse
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.
andybones said:
This should be moved to Q&A section not Development.
But I would run the latest RUU.
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
then re-flash (I suggest fastboot) TWRP recovery 2.8.6.1
Click to expand...
Click to collapse
andybones said:
Flash the firmware.. Has stock recovery. If it boots to twrp after that, you're doing it wrong.
Click to expand...
Click to collapse
the first couples times I did, I choose the firmware "m8vzw_AllInOne_Firmware" and " 4.17.605.9 Modified Firmware ".... both did not work in my case but then I did again with full wipe firmware "4.17.605.9 Full Firmware" and did work.... I didn't have nothing on my phone anyway so, the full firmware which wiped worked..
Thanks