Related
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
So I got a hold of a retail G930x and was successfully able to install TWRP and factory reset with a stock image, only problem was that I never turned off the FRP lock, and when the phone was restarted while updating SuperSU my recovery was blocked. OK, no problem, just flash a stock ROM through Odin mode right? Well for some reason G930AATT1APB5, and G930FXXU1APB4, do not seem to work. At one point I was able to partialy boot into the stock recovery, but at another flash attempt my computer blue screened and I received the error message "An error has occured while updating the device software. Use Emergency recovery function in the smart switch PC software", but Smart Switch returns an error message of "Device Not Supported". I can still boot into Download mode and attempt flashes, but I can't seem to find a working ROM for this phone or a solution to the stock Recovery issue (which is most likely corrupted by now). Any help would be greatly appreciated, thank you.
edit:
edit: so I flashed a recovery image file from ROM.G93xF.XXU1DQFM-v18.0.by.ambasadii.zip and was able to get to the stock recover screen. Unfortunately i get an error message saying "Failed to mount E: /system (Invalid Argument)
Update from external storage is disabled.
Hi all,
When installing TWRP on my daughters tablet I have accidentally flashed boot instead of the recovery with the TWRP image on the tablet using fastboot.
After I realised the error I have flashed TWRP to the recovery partition and rebooted the tablet to access TWRP.
When I was in TWRP I have wiped the data partition and flashed the lineage os rom for this tablet.
First error I noticed was E: legacy property environment did not init successfully, properties may not be detected.
Installation appeared to run properly but in the end I got a lot of E:Unable to stat '/data/.........' messages.
When rebooting TWRP asks to install SuperSu which also shows the same kind of error messages.
At startup I get the Lenovo logo and afterwards only a black screen which is turned on (in the dark you can see that it is active)
I am currently unable to access the fastboot environment, when rebooting using power and volume down it looks like the tablet is in fastboot mode, but when connected to the laptop it shows up as MTP device.
Fastboot or adb itself does not show any connected devices.
When rebooting after the Format data option in TWRP and installing an image I get the following errors :
E:Unable to find partition size for '/recovery,
E:Mount: Unable to find partition for path '/emmc'
E:UnMount: Unable to find partition for path '/emmc'
E:Mount: Unable to find partition for path '/emmc'
I have tried to flash the tablet back to stock rom with the Lenovo/Qualcomm downloader tool but that tool hangs at the Sahara stage and does not proceed after detecting the tablet.
Does anyone have an idea I can try or is the tablet bricked ?
TWRP version is 2.8.7.0 and I am able to access the recovery.
ROM's tried are lineage-14.1-20170520-UNOFFICIAL-x103f.zip and RR-N-v5.8.5-20171113-x103f-Unofficial.zip
USB debugging and bootloader were unlocked in the developer options on the tablet.
I ave rebooted to the bootloader from TWRP after trying another flash, still having a black screen.
In device manager I am now showing Lenovo-HS-USB Diagnostics (COM20), Lenovo HS-USB NMEA (COM21) and Lenovo HS-USB Modem Phone.
Still no luck with adb or fastboot.
Hope someone can help,
Kind regards,
Klaas-Jan
To revert to Stock
You could try the method indicated in this post. Please read the post thoroughly before proceeding.
Note that in step 4 you should be looking for the model number of YOUR tablet.
I have not tried this method myself yet, so I don't know if it works. As always you do this at your own risk, but as your tablet is not working, you may wish to give it a try.
Good luck.
Baldyiskaal said:
Hi all,
When installing TWRP on my daughters tablet I have accidentally flashed boot instead of the recovery with the TWRP image on the tablet using fastboot.
After I realised the error I have flashed TWRP to the recovery partition and rebooted the tablet to access TWRP.
When I was in TWRP I have wiped the data partition and flashed the lineage os rom for this tablet.
First error I noticed was E: legacy property environment did not init successfully, properties may not be detected.
Installation appeared to run properly but in the end I got a lot of E:Unable to stat '/data/.........' messages.
When rebooting TWRP asks to install SuperSu which also shows the same kind of error messages.
At startup I get the Lenovo logo and afterwards only a black screen which is turned on (in the dark you can see that it is active)
I am currently unable to access the fastboot environment, when rebooting using power and volume down it looks like the tablet is in fastboot mode, but when connected to the laptop it shows up as MTP device.
Fastboot or adb itself does not show any connected devices.
When rebooting after the Format data option in TWRP and installing an image I get the following errors :
E:Unable to find partition size for '/recovery,
E:Mount: Unable to find partition for path '/emmc'
E:UnMount: Unable to find partition for path '/emmc'
E:Mount: Unable to find partition for path '/emmc'
I have tried to flash the tablet back to stock rom with the Lenovo/Qualcomm downloader tool but that tool hangs at the Sahara stage and does not proceed after detecting the tablet.
Does anyone have an idea I can try or is the tablet bricked ?
TWRP version is 2.8.7.0 and I am able to access the recovery.
ROM's tried are lineage-14.1-20170520-UNOFFICIAL-x103f.zip and RR-N-v5.8.5-20171113-x103f-Unofficial.zip
USB debugging and bootloader were unlocked in the developer options on the tablet.
I ave rebooted to the bootloader from TWRP after trying another flash, still having a black screen.
In device manager I am now showing Lenovo-HS-USB Diagnostics (COM20), Lenovo HS-USB NMEA (COM21) and Lenovo HS-USB Modem Phone.
Still no luck with adb or fastboot.
Hope someone can help,
Kind regards,
Klaas-Jan
Click to expand...
Click to collapse
The errors look like the ones I got when I installed the TWRP posted here. There's something better available. Have a look on my post
When i try to install zip package with weekly miui12 (unnoficial TWRP) i forgot to mount partitions and now i can't mount it anymore. Try to tick it but nothing happened.
So I can't install any package. Do I brick my device?
Is there any posibbility to mount those partitions?
Twrp errors:
Failed to mount '/system_root' (invalid argument)
Failed to mount '/vendor' (invalid argument)
Failed to mount '/odm' (invalid argument)
Are you trying to install Chinese weekly rom?
easy way to fix is flash stock with xiaomi assiatant by fastboot mode.
ZeroSherd said:
easy way to fix is flash stock with xiaomi assiatant by fastboot mode.
Click to expand...
Click to collapse
I jist flash fastboot rom twice and everything is ok xD
Is there a solution this error? I'm having the same problem.
I have the same problem. Can anybody help?
edit file rom, extract rom .zip, edit updater-script and delete first line. save and make file zip again.
tested rom global stable beta.
how edit updater-script,
https://forum.xda-developers.com/showthread.php?t=2522762
do my tutorial to get the phone and then start again, it's in Spanish but it's simple.
https://www.htcmania.com/showthread.php?t=1565656
you have to install the recovery "TWRP-3.4.2B-0623-REDMI_K30PRO-CN-wzsx150-fastboot.zip" and with that you will not have errors, the twrp of this website gives errors
i have the same problem How i can flash miui china beta on F2 Pro from twrp?
Koziol87 said:
I jist flash fastboot rom twice and everything is ok xD
Click to expand...
Click to collapse
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN
Latin_lion_ said:
IM DESPERATE FOR HELP ON FLASHING THE STOCK ROM IVE READ COUNTLESS ARTICLES AND SEVERAL VIDEOS BUT THERE ALWAYS SEEMS TO BE A NEW ISSUE WHILST FLASHING THE DEVICE CAN SOMEONE PLEASE WALK ME THRU IT GET IN TOUCH WITH ME at [email protected] JUST WANT TO UNBRICK MY PHONE SO I CAN USE IT AGAIN
Click to expand...
Click to collapse
Did you use miflash?
NOSS8 said:
Did you use miflash?
Click to expand...
Click to collapse
yh BUT for some strange reason i cant flash the latest stock rom on my device arb error ive tried everything hoping to find help im new to this first phone ive tried to install custom roms on
I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks
cxm05 said:
I am also having the same problem. I've tried for weeks using miFlash 3030.3.14.0 on my Redmi K30 Pro / Poco F2 Pro.
I get "successful" flashes, but after rebooting, I am stuck at the 5G / MIUI logo. I've try several Fastboot ROM (miui 11, 12, and latest Chinese Weekly) - all result in same place.
I've also tried Recovery ROMs after booting into TWRP 3.4.2 and repairing / changing /data partition. I always end up with one or more of the /vendor /odm / product / system_root as "invalid argument". It's the same when I tried to sideload recovery ROMs
I've tried flashing MIUI 11.0.2.0 twice (fastboot - back-to-back) but still doesn't work.
Anyone have any ideas?
Thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/
NOSS8 said:
https://forum.xda-developers.com/t/failed-to-mount-invalid-argument.4199945/
Click to expand...
Click to collapse
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"
cxm05 said:
Thanks for responding but this hasn't helped. I downloaded 3.2.xxx of the Chinese Mi Assistant. I have flashed multiple ROM (both recovery & Fastboot). I still end up at MIUI logo for hours. The one thing this has helped with is that sometimes after flashing upto the latest version 12.2.2.4.0, I can see systm in the list of mountable partitions (TRWP). But even after I mount system ( and data), I can't install a recovery ROM from a USB stick "/system_root - invalid argument"
Click to expand...
Click to collapse
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download
NOSS8 said:
which version of rom indicates Mi assistant?
Try to install this rom*** below with Twrp (Just wipe-> format data by typing yes(if error reds lignes, reboot twrp and format again),reboot Twrp,flash rom).
No need to mount anything.
TWRP https://androidfilehost.com/?fid=17248734326145679747
***EU rom https://sourceforge.net/projects/xi...MK30Pro_V12.2.3.0.RJKCNXM_v12-11.zip/download
Click to expand...
Click to collapse
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?
cxm05 said:
Didn't work - at one point, I started receiving CRC errors for xbl or xb4 partitions. At best, this version of TRWP does allow me to fully install a recovery ROM with no errors or warnings about partitions not being present, but once I reboot I still end up stuck the logo
Click to expand...
Click to collapse
in flash folder of rom, you have flashall.bat open it in txt format, find two rows that contain CRC and delete it, save file and than try to flash rom again. it will pass. I have the same CRC error and deleting this two row help me to flash rom
NOSS8 said:
First boot with EU rom take 5/6 minutes.
which version of rom indicates Mi assistant?
To be sure, can you describe how you use MIFLASH?
Click to expand...
Click to collapse
The MI Assistant version is 3.2.522.32 beta. Once I start the Mi Assisant client on my phone and then plug my cable, the application prompts me to select a Fastboot ROM on my harddrive. ONce I select a valid imag, it flashes my phone and then reboots. After loading for 15 minutes or so, the phone reboots to the MI recovery where I can select to use Mi Assistant again.
This time, Mi Assistant detects the version of ROM I have installed and advises there is a newer ROM. On this screen I select the first button (which I believe downloads the image from MI server) or the sencond button (which allows me to select a local Recovery ROM stored on my hard drive).
Regardless of which option I choose, the 2nd flash occurs and my phone reboots again. in A cycle until I have the most recent ROM on the phone and it still sits at the MIUI boot screen for 30 minutes. I've gone from 11.2.0.9 ==> 12.2.0.4 ==> 12.2.2.4. All successfully flash to the phone but phone never boots past the MIUI logo.
I've even gone as far as flashing a beta ROM 12.2.2.5 on top of the latet stable version using MI Assistant (flash runs successfully ut phone still never boots).
I have also gone into bootloader mode & flashed the TWRP version you recommended. After botting into this recovery, I can "factory reset" the phone and the sideload the HK 12.2.0.3 rom you provided. The sideload flashes to the phone with no errors, but phone still doesn't boot past the MIUI logo
Hi there
I have the J330F/ds phone.
It won't boot.
ODIN mode says its J330F OEM&FRP LOCK=ON
Binary: U3
I tried latest pie stock rom. It boots into recovery mode only with errors E: failed to mount efs(invalid argument)
dm verity verification failed
and some failed to clear bcd efs(invalid argumenet)
I tried Nougat stock rom too. In recovery mode it gives me failed to mount efs and dm verity failed
After I do factory reset/clear cashe the phone boots to the samsung logo and it stays there.
Same thing happens when with Factory Binary. It boots up to the clock gears and it just sits there.
Since I have OEM and FRP lock on I can't install TWRP
Can the efs error be fixed with efs if someone has it for U3 binary. I think that that error causes the stuck on logo. and it won't even let me boot factory binary???
If someone could help I would really appreciate it.
Fixed it!
I was able to fix it. First I flashed efs.img tar file that I found on the internet.
I was able to boot into combination firmware and I flashed 7.0 stock via ODIN.
I flashed only system.img boot.img and sboot.img. And it worked I was able to remove FRP and OEM lock and they are both off. I tried pie stock and it did boot up and worked but when I factory reseted via menu on the phone the phone was stuck on starting screen and had the same dm verity error. I was not bothered with trying to root it and flashing twrp and the skip dm -verity tar. I just went back to 7.0 and factory reset works just fine there.
The problem was efs corruption or missing altogether. And dm verity can be fixed with root twrp and the skip dm verity tar file which I didn't do but it should fix that too!