Related
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Ferguson35000 said:
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Click to expand...
Click to collapse
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Ferguson35000 said:
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Click to expand...
Click to collapse
I got this problem when installing CWM too. I believed the problem is in this line:
fastboot flash recovery CWM-6.0.5.0-peregrine.img
Click to expand...
Click to collapse
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
UncolourTV said:
I got this problem when installing CWM too. I believed the problem is in this line:
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
Click to expand...
Click to collapse
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Ferguson35000 said:
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Click to expand...
Click to collapse
I have the same issue with this program under linux or windows, it doesn't recognize my device. I have activated USB debug, tried under bootloader or with the phone normally started but nothing better.
only fastboot boot recovery.img works.
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
hacktrix2006 said:
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
Click to expand...
Click to collapse
Thank you for answering.
I will try this then come back.
Ferguson35000 said:
Thank you for answering.
I will try this then come back.
Click to expand...
Click to collapse
Same error :
I still have the mismatch thing with mfastboot ...
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
hacktrix2006 said:
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
Click to expand...
Click to collapse
Hello, I have bought the phone less than one month ago.
It was directly on 4.4.4 after unpacking.
Have you tried renaming the CWM file? Maybe the "-" are a problem although I highly doubt it. Did you try re downloading the file? Running the command window as an administrator? Last resort, you could use TWRP, I'm running on this currently and haven't had any problems installing/flashing ROMs with it and imo prefer it over CWM.
Click to expand...
Click to collapse
I have tried both and they both have the same problem :/ CWM as well as TWRP...
Still no idea what happens.
same problem
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
kosamuky said:
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
Click to expand...
Click to collapse
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Back to stock
Ferguson35000 said:
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Click to expand...
Click to collapse
Yes its normal if you have unlocked your bootloader
To get back to stock, download a stock Fw for your device model and region, you can find a link for one if you enter the moto g section of this site and head to moto 4g lte android development section (only section specifically for peregrine model) unpack the fw files into your fastboot directory (windows) reboot your phone to fastboot mode (where u saw the status code) then press control + shift + right click to launch a command prompt window here (from within fastboot directory in windows) then copy and paste these fastboot commands 1 by 1 pressing enter each time until compete.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
So you mean, it is compulsory to have stock ROM in order to install the recovery ?
Because my problem is not to return to stock, it is to install a proper recovery (CWM or TWRP) in order to boot on it without my computer.
Thanks for your help
No but I think your problem is you have corrupt the recovery partition size maybe through bad flash or something so ur unable now to flash a recovery as the partition size is for different device or damaged and flashing cwm will no longer work as the cwm image is too big or too small for the allocation assigned to it as the devices core partition table has changed (can happen when u flash something for the falcon when you have a peregrine), I would flash back to stock via that method to restore to stock partition sizes and then reroot and flash cwm again after, just a guess from my own understanding.
Sent from my XT1039 using XDA Free mobile app
Guys I had the same trouble installing the recovery with the mismatched partition size message. This message is normal and the recovery is already installed on your device. The problem i had when selecting the recovery with the following black screen was that I used the Power Button instead of the up Button.
5) using volume down scroll to recovery and then use volume up to select
So I have a cousins XT1032 I'm trying to fix. What happens is that it doesn't want to boot. After the Motorola Bootanimation it goes to a Black screen, I've read about going into Recovery and Factory Resetting or Wiping Cache and I've done it hundreds of times now and it hasn't changed a thing. I've tried flashing the Stock ROM and everything flashes correctly but when I reboot it goes to the same Black Screen after the Boot animation. I've tried putting a custom recovery (CWM, TWRP, Philz) and it flashes, but when I press Recovery on the phone after flashing, it boots into the Stock Dead android recovery. I'm not sure what else to do. So any help would be great, thanks.
Hmm, so I found something weird... So I said that I had factory reset man times, using Fastboot and Android Recovery, well today I was trying to convert it to a GPE to see if it would work and it didn't. It still did the same thing (black screen after bootanimation) So I tried to Sideload a ROM through Android Recovery and it aborted the installation so I pressed on the android recovery. "Update from SD Card" or something like that and I saw that my cousins old files were still there, they haven't been erased...So I'm starting to think that this is a defect...
But anyways, If anyone knows the solution I would really appreciate it!
No one? :/
Gus194 said:
No one? :/
Click to expand...
Click to collapse
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
NextGenGTR said:
If your cousins files are still there then you can get them onto your computer, if you have cwm or twrp use adb sideload to transfer the contents on to your computer directly. Then you can try whatever you want knowing that the files are back since im guessing thats the most important.
1st: Download http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 ??? Install this
2nd: Put phone in recovery either into cwm or twrp, then open up minimal adb
3rd: Use this command to pull your files into your computer, these will be located in you hdd where you go into program files and etc, basically the root of your computers hdd at C:\
Command = adb pull /sdcard/ c:\
Hopefully this helps you, good luck, mate.
Click to expand...
Click to collapse
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Gus194 said:
Thanks for trying to help man, but like I said if I try to flash anything like a Recovery or anything else it shows that it flashes correctly but when I try to get into recovery it just boots into the dead android recovery one
Click to expand...
Click to collapse
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
NextGenGTR said:
When you flash the recovery do you get an error like some mb error? Try to flash this recovery, it worked for me, i had a similar problem because i flashed android l and the bootloader was different so you need a compatible recovery, i downloaded one today, i need to find link, stay online
---------- Post added at 06:51 AM ---------- Previous post was at 06:46 AM ----------
Here is the recovery i used that worked for me Link for download: https://docs.google.com/file/d/0B3sIJMABIGzAelpNX1RUZUFvV0U/edit
I think you know but enter bootloader than connect your usb and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Gus194 said:
Alright, let me try that Recovery! Thanks so much. By the way it says: Mismatched partition size (recovery)
when I try to flash the recovery
Click to expand...
Click to collapse
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
NextGenGTR said:
Im sure it should work, i had the same error i believe, lol, today i tried changing my dalvik size in build.prop and my phone wasnt booting so i tried flashing recovery and i had the error you was having, then i used these adb commands, i guess i messed my phone up so i can help you in a couple hours later on, lol, coincidences! xD Did it work for you?
Click to expand...
Click to collapse
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
Gus194 said:
Just flashed the recovery you linked to. And nope, didn't do anything. I still boot up to the Dead Android guy recovery. Hmm I'm starting to think that this is a Hardware Defect
Click to expand...
Click to collapse
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
NextGenGTR said:
Since you flashed GPE, try doing this, flash back Motorola stock without doing the erase commands and then try flashing this recovery.
---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------
This is something i found on a thread --- You have to enter recovery straight after you flash it, or the old one will replace it,when you exit the new recovery there will be an option to disable the old recovery.
Click to expand...
Click to collapse
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Gus194 said:
Yea I know about that entering recovery right after flashing and I've done that every time. It never has worked. Hmm something is wrong with this phone. I've factory resetted the phone at least 10 times using the Recovery and another 10 times using Fastboot and the files are still there. I think that it's definitely is a Hardware problem :/ dang
Click to expand...
Click to collapse
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
NextGenGTR said:
I do not know if this will work but it is a wild guess, i had a htc sensation and i was able to use adb commands at the start of boot even when it didnt boot up, so what i am trying to say is boot up your phone and then plug in your usb cable and then try the adb pull command i gave you earlier, im sure this wont work but give it a shot.
Click to expand...
Click to collapse
It probably would work If the phone had USB Debugging on before it got bricked :/ I'm about to give up on this phone. I've tried everything lol.
I'm thinking that the Partitions are corrupted since none of them will format using fastboot. It just says it cant format Raw type partitions or something like that
You have not done ALL of the necessary fastboot commands when flashing the firmware image. Make sure you have an XT1032 4.4.4 image.
Do the following manually, report any errors. Use no other fastboot commands other than those stated below.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
This is a tangent to the issue I had Situated HERE. I am seriously giving up on hope and want help for the love of god. Semester is approaching and I need a functioning mobile
After "fixing" my isssue and being on Lolipop 5.0.2, I realised that my SU binary wasn't present, So I reboot into recovery to realise that CWM isn't present anymore.
Not a big issue, I plug it in and flash TWRP onto it using fasboot commands.
Now i go into recovery and Install Superuser.zip trough TWRP. Then I decide to make a backup of everything. Afterwards I rebooted
The boot logo (The logo in which it normally mentions that Bootloader is unlocked and blablabla) Apears. But then it closes. Apears again but then closes once more. It keep doing than until I boot it into bootloader and close it once arrived there.
If I try to get into TWRP again it closes and continue the cycle.
So I flashed in CWM recovery with the intention to Flash the Stock lolipop ZIP that I done before (which fixed it).
When I boot CWM however, I am presented with a bunch of command lines at the bottom saying
"E: can't mount cache/logs"
and other lines (If you want the exact command lines say so and I will go get them). I didn't flinched to it (sometimes weird **** happens like that and I got used to it) so I go into the install from sdcard. I get this amazing message:
E: cannot mount sdcard
And all gui is not even present. I close the phone and start panicking
################################################################
In other words I need help. I will be checking this thread all the time looking for any help. I am giving up. faced such a problem in my life. I am scared that I bricked the phone for good.
Here is all I know about said phone:
KITKAT MOTO G 4.4.4 from canada (obtained from WIND mobile) most likely XT1034 (Its a mono sim)
The bootloader is 41.18
I used TWRP 2.8.6.2 for xt1032 (This is probably why everything exploded. I didn't realised it was for xt1032)
And I used CWM touch 6.4.0.7 falcon
MORE INFO WILL BE COMING, But I am extremely stressed right now to the idea that I might killed it.
#######################################################################################
#######################################################################################
Here are the CWM error messages
ClockworkMod Recovery v6.0.4.7
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_Install
- Install ZIP
- Choose zip from /sdcard
E: can't mount /sdcard
-Choose zip from /sdcard
##CWM gui closes## only the command lines are showing.
################
Update 1. I calmed down. I searched the error message and found out that it could either be an issue with CWM being currupted. I will reflash it and bring details. If it doesn't work I will format cache (Wiping the cache seems to not work)
Formatting the cache seems to fix all the cache error messages. But the mounting of /sdcard still present an obstacle
################
Why not flash stock firmware?
motofirmware.center
Sent from my XT1031
#######################
Update 2
I did some research and found out that my sdcard might be on logical and not primary and a way to fix it is to use mini partition tool on it. I am hesitant to do this so I will search for other possible issues
############################################
ATTACK said:
Why not flash stock firmware?
motofirmware.center
Sent from my XT1031
Click to expand...
Click to collapse
Because I can't find it.
try to find a 4.4.4, xt1034 canada stock firmware, Not easy. I've look for around 3 hours without success.
I however found a flashable zip for it, so I need to make recovery work, Because to my knowledge you can't flash an entire zip from adb/fastboot
The site you provided doesn't contain the right firmware. I highly appreciate the help though.
####################################
update 3
I decided to try and sideload stock rom lolipop. Seems to be working. Will be updating the results.
Here are the result:
ON MOTO G
-Install zip from sideload
nothing unusual happens
ON ADB
- adb sideload "lolipop stock rom".zip
Loads.....
Sends.....
"*failed to write data 'protocolt fault <Coudn't read status: invalid argument'* "
BACK TO MOTO G
- cancel sideload
Restarting adbd....
status 0
finding update package.....
opening update package.....
E: Can't open /tmp/update.zip
(bad)
installation aborted.
Click to expand...
Click to collapse
So it doesn't work but I found that last bit interesting. I feel like things are clearing up even though no ones is helping me (except for ATTACK, thanks but I will need a lot more help than that ) So help is apreciated
######################################
What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034
Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031
k-kuchen said:
What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034
Click to expand...
Click to collapse
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
ATTACK said:
Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031
Click to expand...
Click to collapse
YES, Omg I didn't knew lost posted Firmwares. Prase the mighty lost god. The first one is exactly it.
I don't mind waiting 1 or 2 hours. as long as I got it nicely set up for september 1 I'm a-ok
If it boots properly I owe you sir.
thegamerchunk1 said:
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
Click to expand...
Click to collapse
The 4.4.4 is also in this thread
Edit: Hosted on AFH -> https://www.androidfilehost.com/?fid=24052804347795180
##############################
Update 4
I tried to restore stock firmware. Back to square 1.
Cache issues.... I fixed it
Can't mount /sdcard.... Can't fix it.
The logo is the only thing I see and whenever I try to close it by pressing the power button, it reboots into the logo screen.
The only way I can truly close it is by opening fastboot menu and closing it there.
WHY IS THIS HAPPENING IM LOOSING MY MIND
I beg someone, anyone, Help me...
######################################################################
##################################
Update 5 Final ****ing update ****
I wiped and formatted /sdcard with philz touch recovery.
It seems that I can mount the sdcard now but I can't flash any roms because it
"Failed to set up expected mounts for install"
I am seriously in the most depressed mood ever. I worked for 4 years in computer development and I never had this much trouble ever. I ****ing give up everything. If someone ever encounter this issue:
you are ****ed throw the moto g in the garbage its dead nada done.
If someone thinks the contrary tell me how I am supposed to fix this. I will check it in about 12 hours.
I will do anything that someone thinks is going to fix it.
So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031
kinda urgent
@lost101 can you help him brother. He is in dire need.....
@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.
ATTACK said:
So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031
Click to expand...
Click to collapse
I flashed it using fastboot. here are the commands I used
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.
lost101 said:
@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.
Click to expand...
Click to collapse
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.
thegamerchunk1 said:
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.
Click to expand...
Click to collapse
Make sure to include the command: fastboot erase userdata
thegamerchunk1 said:
I flashed it using fastboot. here are the commands I used
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.
Click to expand...
Click to collapse
Ok - after you retry flashing, please post those errors. May want to try using mfastboot instead of fastboot as well.
Also you could 'adb push ROM.zip' with a custom recovery, bypassing the sd card altogether, but I think you should get your device to boot first.
Sent from my XT1031
So I had an old Nexus 5 running a custom KK rom. I tried getting it back to stock using Wugs Toolkit. I've been playing with it for hours trying to get it to work. I ended up making it worse and it gets stuck on Google Logo now. I tried using the revert to stock option on the toolkit. It looks like everything is working.. Here is the log..
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: hammerhead
finished. total time: 0.001s
Launching flashstock.bat
and then it just stops.. I tried downloaded two seperate .tgz images from Google. They both do the same thing. It doesn't go out of the bootloader screen or anything. It writes the radios and that's about it.
This is a *very* high-level suggestion - there are many tutorials that take you through drivers/ADB, etc. I just want to give you the script I followed for the manual procedure, which turned out to be extremely quick and simple.
After suggesting Wugfresh's NRT to several people in these forums (I'm a very big fan) I decided to refresh my Nexus 6 with the latest image and make it unencrypted - a problem that doesn't exist on the N5. I wasn't sure that NRT would do this for me, since the script automatically restarts the device and I wanted to be sure that it didn't start before I had flashed a modified no-encrypt boot image, since it would just encrypt itself again. So I downloaded the factory image, a no-encrypt boot image (thanks, doitright ) and TWRP - naturally being very careful to get the right ones. I unzipped the TGZ and the image files down to their final *.img components. To make things simple I renamed the various images to one-word names (e.g. radio.img). I put all of them in the same directory as ADB & fastboot.
Since all Nexus devices are updated the same, this should also work for you. Since you've used NRT I'm guessing that you have the PC drivers already installed. You'll also need ADB/Fastboot. Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Some of these may be overkill (I believe the -w wipe command erases userdata anyway), but it worked for me.
I would say take a TWRP image first as well so that you can recover, but it sounds as if you have nothing to recover anyway.
If the more expert member want to suggest amendments to the script, I won't be insulted...
dahawthorne said:
Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
USB debugging means nothing if you're trying to use fastboot.
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
gregs1213, stop using a toolkit, since you don't know what you're doing. read the above link and the following one as well:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
dahawthorne said:
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
Click to expand...
Click to collapse
Hey, sure, I didn't mean to "attack" you. I noticed that you wanted to help. Really. Thanked you for that.
No worries, beekay. Posts don't allways mean what they look like, which is why we have smilies.
And I did read the articles. I tried with my N6 to attach it in bootloader mode with no USB debugging, and you're absolutely right. I suppose I just read "Remember to switch on USB debugging" so often that I assumed it was needed for any sort of work. Thanks for the tip. It's things like this that encourage all of us to try new things - like flashing a ROM manually instead of with NRT...
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
mraramesh said:
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
Click to expand...
Click to collapse
Toolkits don't teach people stuff, they just hide it from them
mraramesh said:
The problem is Wugfresh NRT
Click to expand...
Click to collapse
I edited your post to show you the error of your ways
Sent from my Xperia z5 using Tapatalk
While replying to another thread asking for help in installing a ROM, I linked to this, and I notice that the OP never did tell us if he managed to get his device working. Feedback is not only helpful to the forum, it's also polite.
So bump for gregs1213's attention...
hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.