Hey guys,
Finally decided to flash a new rom (NOS M7) and kernel (KillX) onto my phone, I loaded up the zips onto my sd card and just flashed it using recovery only. I didn't flash boot.img in bootloader/fastboot. I know its stupid, its my fault that I was tired and that I haven't really flash roms since mid 2011 on my sensation after settling on a virtuous rom.
Now my wifi doesn't work (haven't been playing with it much - could be many more things that don't work), but the main problem is that I found out adb doesn't work for my phone anymore when i tried to flash boot.img again. Sure, I can still use my phone as a external drive, but that's about it. Can't find my phone though 'adb devices' when the phone is switched on normally, in fastboot usb, and in recovery. However, I can still sideload a .zip file in recovery. that works.
In fastboot, I get 'This device cannot start. (Code 10) - A request for the USB BOS descriptor failed.' I've tried downloading the newest drivers from htc, updated my sdks, installed/uninstalled htc sync manager - which always came up with 'unable to sync with device that is locked, please unlock device' or something like that even though my device's screen was unlocked.
You probably figured out that I'm not that advanced with technology as some of you peeps out there. :angel:
What do you think I should be doing now?
I feel like I have half a phone working. :crying:
Cheers,
Reece
Which variant do u have ... X920d or e ??
Also it might be best to return to stock first and ten start over again ... Also provide the hboot version from the boot loader screen
I have the x920d,
here's the info.
Hboot - 1.39.0000
Radio 3A.21.306.10
s-on.
What do you mean by return to stock, as in relocking my phone etc... but how? I can't even use adb. I can't really flash roms properly either.
Anyone...??
Try the ADB on another computer, it should work.
I'm still getting no luck with adb on another computer.
What else can i do?
I can even use adb .
Hope that help.
http://forum.xda-developers.com/showpost.php?p=39653035&postcount=12
Note: That guy did with x920e ROM but I think the process should be same, good luck.
Sorry that i took a while to reply.
I just tried going into recovery and wiping everything as per the link,
i can't seem to wipe cache and system. weird. that's what i get for trying to format system or cache
'Formatting /system(or cache)...
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p32
Error formatting /system(or cache)!'
I can now flash boot.img, but somehow that won't mean anything until I can wipe my phone.
Can I try wiping it in bootloader?
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
Hello Guys!
Recently i received my used Motorola Moto G. Phone was nice, I was using it like every teenager, instagram snapchat etc. But last night i wanted to install rom on phone. Saw thread about installing everything, root rom etc. with 1 program. I tought it will be nice, so i downloaded it, run, and there is a problem. It was command line tool, everything gone right, there was messeage about clicking any button to continue, I did it and then my phone restarted, but there was like normal 5.0.2 android not 5.1 what was saying guy who wrote thread about that program. So i thought that i will do everything step by step, unlocked bootloader, installed recovery and when i first time opened recovery from bootloader menu it had problem with mounting data partition. I was trying to install firmware roms, but it had problems with downgrading bootloader. Downloaded 5.0.2 firmware .xml.zip file, it gone ok, i mean there wasn't a problem with motoboot.img, and at every single command there was only okay, there wasn't failed, just had 2 problems on phone screen, it was saying "hab check failed for boot" and "hab check failed for recovery". After typing every single command to fastboot and restarting phone always phone was stucked on boot screen, i mean on 4.4 it was stuck on messeage about unlocking bootloader, on 5.0.2 it was stucked on that 4 colors orbs flying around the screen. Then i was trying to open my stock recovery, but it was always broken, opened android with warning sign on it. When i was installing custom recovery that had problems with mounting /command /log /last_log /last_install, and when i was trying to mount data it couldn't mount it, I was trying to format /data and /data/media, it was always going ok and then i could mount data partition, but my phone was still stuck on boot screen. I was trying to install custom recovery again but it had same problem, just opened android with warning sign. And there is a question, what can I do to make my telephone working.
I'm sorry for mistakes, but my english is not the best
Try reading this thread here and see if that helps.
Hello, I currently have Cyanogenmod 11 on my device, but I want to revert to the stock ROM again.
I have the B127 FW on my external SD as the UPDATE.APP within the dload folder.
I flashed stock recovery and after rebooting a couple of times, the update seemed to work at first, as there was a bar to indicate the progress of the install. But I get a failure to install error. Saying there is no UPDATE.APP.. which I obviously do have.
Anyone know what is wrong? I tried unrooting, putting the dload folder on internal SD, switching FW versions in dload folder (B130, B127, etc.)
I keep getting this error though and I have no clue what is wrong and searching yields no results.
Bump
Time ago I had the same problem. At that time (in my case) I solved changing the SD card, re-downloding the ROM (maybe was corrupted), and obtaining the stock recovery by unpacking the just downloaded ROM. You can try the sme way. For me worked fine.
Thanks for the reply! I will try this and report back on status.
So no thing is working. No matter what I do, I get "there is no UPDATE.APP", any more suggestions?
Try downloading the correct stock recovery. Most of the times it has been reported that as the problem.
Try several version of stock recovery. In this forum, somewhere, there's the link where to download from.
Thanks so much! It finally worked! I just downloaded the B137 FW and used this tool: http://forum.xda-developers.com/showthread.php?t=2433454 to get the recovery.
my problem is the same as above but the phone says i have unlocked device but i never unlocked the bootloader cant flash anything through fastboot except "fastboot update" cant flash recovery or anything cuz technically my bootloader is still locked and now im stuck at rescue mode screen with "attention please update system again" and at the bottom is says "Error Func NO:12(FUNC_LOAD_IOM3)
Error NO: 1
any ideas it would be much appreciated thanks
mattwheat said:
my problem is the same as above but the phone says i have unlocked device but i never unlocked the bootloader cant flash anything through fastboot except "fastboot update" cant flash recovery or anything cuz technically my bootloader is still locked and now im stuck at rescue mode screen with "attention please update system again" and at the bottom is says "Error Func NO:12(FUNC_LOAD_IOM3)
Error NO: 1
any ideas it would be much appreciated thanks
Click to expand...
Click to collapse
Hi. That error has something to do with the sensors I think.
read this: http://forum.xda-developers.com/mate-7/help/factory-reset-rooted-mate-7-t3096641
On page 2 I posted two links, one in chinese and one in italian. In the one in chinese they are talking that this error it's from the sensors. In the second link, that it is in italian I saw that in last post someone told that he had the same error and fixed in service.
hi all,
i have a problem with my xperia l. here's the story :
originally, i have xl with cm12 installed + re-partitioned internal (i'm using this guide), but i have stability issue after some time. then i tried resurrect remix rom, but i still have my problem (even worsen). so i was thinking about checking with stock rom, and i tried to flash stock rom back. but there's a error when processing userdata.sin on first try. i thought my tft was corrupted, so i tried to re-download it and tried flashing again, but the error still there.
after third attempts, the error message started to differ (forgot to log it ). so i tried to get into recovery, but i found error about "failed to mount /cache", "failed to mount /system" and so on. i have tried to mount manually in recovery menu, but failed, and sdcard read 0mb.
i have tried to solve by myself and some solution from forums, and still got no luck with it. what i have tried :
- trying to re-flashing tft again and again. latest error when processing loader.sin :
ERROR - (X10flash.java:520) - Error in processHeader : 22 : The device does not recognize the command.
- trying some recovery like cwm, thunderzap, twrp (i tried after read this post), but no luck and can't find restore filesystem menu).
- trying accessing adb, can't get in
- finally able to get into terminal from twrp, but only found parent folder without anything inside.
so, i think the partitions are damaged or something happened to them and i can't access them.
please help.... :crying:
NB. currently boot into fastboot, flashmode, recovery, charging, led, flashing boot.img, and external sdcard still working, so i hope my xl still can be saved :angel:. and i'm sorry for any typo
UPDATE :
finally hardbricked my phone. i'm getting impatient waiting some reply and no luck searching forum. so i messing around by myself, and found problem on superblock. i've fixed superblock once on linux, but in adb some commands are unavailable, and i can't search for backup superblock, so i tried to reformatted it (followed guide from some nexus forum, well, thinking androids have same base), and then i accidentally disconnect the usb. next is, well, i screamed.
Did you find any solution of this problem????