hello fellows Droids,
i've been trying to fix/unbrick an Acer Iconia Tab A200 for few days now, and nothing seems to work, the Tab has never been rooted before, it's on stock, and it's stuck in the boot logo, i unlocked the bootloader, tried to flash the stock firmware and rom, but it's not working, it uploads the karnel or the rom then it gives me "FAILED (remote: (00030003))" , I could flash the ClockWork recovery, but when trying to flash anything with it, it says to me "can't mount cash/../..", can't mount Sdcard, even if i try to use it to format or wipe, it gives me the same E messages,
I assume my device is still not Rooted, i can't use ADB, since the device is stuck on boot, when i type "ADB devices" it gives me no device,
so only fastboot is working,
so i'm wondering if is there any way to root, my device, or to make it boot again as stock, so i can root it the conventional way ...
you guys would save my life if you show me how to fix it thanks folks
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the 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
Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...
If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Sideload worked perfectly! Thank you so much!
cm11 working only TWRP here , with cwm appears same error
mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse
Hi all. I own a Moto G xt1032 UK version. (GSM right?)
I was on 4.4.4 Epsilon ROM but I wanted to flash stock 4.4.4, so I used a tutorial I found on youtube that set me up to stock 4.4.2, then I upgraded to 4.4.4 and THEN there was another update to 5.0.1. So as you can guess, I upgraded to lollipop and that was it - bootloop. I have tried flashing other roms through fastboot and nothing worked, I get an error when I flash ''system'' that says ''image is too large'' once all is done, phone restarts and its stuck on bootloop once again. The bootlogo changes when I flash different rom etc. But I don't know what to do, any ideas? :/ I have also tried to flash a custom recovery and sideload the Epsilon ROM but I only get an error in my command line that says no device connected after I hit the command. Any suggestions guys? I appreciate any sort of help, thanks guys.
I'll also add that I think I have the 41.18 bootloader if it helps (it says so in the bootloader settings)
When flashing a ROM in fastboot, are you also flashing the gpt file?
Yeah. I flash everything there's to flash as all tutorials instruct.
To try and get your phone up and running, flash a custom recovery from fastboot. Once the recovery image has been flashed, use the phone's volume buttons to boot into recovery. If you can get into recovery, try and flash a custom ROM.
Ah, I forgot to add. When I attempt to flash anything from my storage it says some sort of error coun't mount /sdcard and others when the recovery opens up. I tried flashing other recoveries, TWRP, CWM both show the exact same errors..Can't mount SDcard etc. :/ That is why I tried the sideload method which didn't work for me either.
You're flashing recovery for the falcon?
Yes..for falcon. I've done it a bunch of times before, however I never had the unable to mount error in the recovery..
I don't have my moto g on me but I found Philz Touch (based on CWM) worked besr for me after i switched back from GPE to CM12. I was getting weird error messages in TWRP.