Related
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
If you don't have a Windows machine, it'd be good if we knew what you do have in order to guide you properly.
Flashing back to stock on Linux is quite easy once you've got the tools set up. I would assume MacOS X is similar provided you can get a suitable fastboot or mfastboot binary. (I recommend having them in a directeory listed in your $PATH variable with proper permissions for USB so that you don't need to sudo to use them.)
If you've got no computer, but can boot in a modified recovery, it should be possible to flash the entire stock ROM with that. You wouldn't be able to relock the bootloader though, if that's something you were aiming for.
killjoydreams said:
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
Click to expand...
Click to collapse
If you are on MAC or linux I suppose you have fastboot installed! If not get it installed from here
Now To restore your phone to stock download this firmware.
After Downloading! Extract the firmware. cd to the directory of extraction.
Use the script in the attachement to restore your phone.
OR
Enter these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
You will need the path to fastboot to be added in path variable!
OMG!!!! thank you, thank you, thank you!!!!!
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
OTA updates work regardless of whether your bootloader is unlocked or not.
It's root and other changes to the /system partition that'd prevent such updates from working.
killjoydreams said:
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
Click to expand...
Click to collapse
No no downsides
You can re-lock the bootloader
And you will get OTA updates as well, even if your bootloader is unlocked!
Just have stock recovery
Phone: Moto X / KitKat 4.4
Carrier: AT&T (XT1058)
Problem: Mysteriously stopped booting.
Good News: Fastboot is recognized.
Bad News: (bootloader) Flash write failure
Taking this guide as my playbook - http://forum.xda-developers.com/moto-x/moto-x-qa/kitkat-update-crashed-moto-x-t2535150 I tried to flash on a stock OS. Here's the main spot from the thread I'm working from-
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
The mission objective is simple: retrieve files off of sdcard and factory reset.
So with my mfastboot (not the android one), I'm trying to flash my stock OS back on so I can get a drive in windows and retrieve sdcard files. Actually, ANY OS back on at this stage of the game will be nice.
Things I have NOT done:
1. rooted the phone, or
2. unlocked the boot loader
If doing these will help, let me know.
So I get my download from sbf.droid-developers.org for 4.4.2 & ATT carrier and unpack the files.
flashing for 'partition' in gpt.bin actually works (yay), but I get the above error ("Flash write failure") for system.img and recovery.img
uh-oh
It seems others with this problem changed cables and USB ports, so I tried that. No dice.
Someone said something about permissions, so I started my command window with administrator privileges, also no luck.
Unless, of course, they meant permissions on the phone side of things? Would that actually help?
So at this juncture if my SDCard died I can go for warranty because I never did any unlocking.
However, if the SDCard can be saved, I am willing to void the warranty and unlock. The data on it is valueable to me and yes a lesson I learned here is I should start using dropbox or equivalent service. Noted.
Should I unlock the phone and try mfastboot flash system system.img, or am I already dead?
Factory reset doesn't even work, I get "no valid piv block in sp for system"
I just ran mfastboot erase cache and at the command prompt I get:
(bootloader) Failed to erase partition
FAILED: Remote failure
The phone screen says, 'Failed to erase partition cache'
This doesn't sound good.... Is there anyway can get this thing booted?
Ah, nevermind, it just keeps getting errors flashing everything. Something with the phone itself is seriously wrong.
I've decided to return it. I think my data is lost.
FIxed with this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
My 64gb OnePlus One does not boot anymore.
I wiped system, data, cache, and dalvik and then flashed the 9/20 cm nightly, gapps, and supersu. The device rebooted and I saw the CM loading circle. However, next time I looked at the device, it was back at the Oneplus boot screen. After this, I have never been able to get it past this screen.
I have tried flashing the stock image using this guide (steps 1-3), as well as downloading the fastboot image from cnygn.com and flashing each img from fastboot using these commands:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Additionally I have tried flashing CM11 from TWRP, which still results in the same problem. I am able to access and use fastboot and twrp just fine.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
EDIT: I managed to install ColorOS with this guide, and it boots fine. However, I need CM with Google Play so after trying to get cm11s 33r with this guide, I'm back at square one with the phone not getting past the boot screen. Any ideas?
Hi so i guess you don't have a backup in the device,sometimes the easiest way to fix things is the right way just download this tool the one for your device 16/32gb the second version(v.2) put your phone in fastboot mode and hit cm update in the tool.
---------- Post added at 06:29 AM ---------- Previous post was at 06:26 AM ----------
http://www.youtube.com/watch?app=desktop&persist_app=1&v=5O2e_R_TbVg
android.345 said:
My 64gb OnePlus One does not boot anymore.
Click to expand...
Click to collapse
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
You should just need to do everything that's in the guide you linked, except the 4th step (you don't need to lock the bootloader). Flash the factory images and just reboot (don't flash/wipe/whatever anything else), it should be fine. Make sure you're flashing the right ones though, for example, since you have the 64GB version, you have to flash the userdata image for the 64GB OPO.
I don't think you should look for "1-click" toolkits, they can be more harmful than good since you don't know what you're actually doing.
bradipovsky said:
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
Click to expand...
Click to collapse
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
bradipovsky said:
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
Click to expand...
Click to collapse
Do take a look at the update I have posted regarding ColorOS. Flashing a new rom from TWRP does not help. All fastboot commands work.
Also, I have been flashing userdata_64g.img
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Same problem for me too. Device worked for a week with SOD-s that 2 days ago just rebooted and stay in the loop of logo 1+.. ??
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
I've lost cellular signal in my xt1039 device. Tried many things including reflash firmware/ flash modem... with no permanent solution.
At last fellow brother @lost101 suggested to flash some partitions stated here http://forum.xda-developers.com/moto-g/help/story-lost-recovery-imei-0-t3414511 as a solution. But by searching in google i cant find any.
Can any of you be kind enough to take backup of "dhob" "fsc" "misc" and "hob" partitions from your xt1039 device and by sharing those help me fix my phone? I'll be greatfull forever.
Backing up partition is easy, just install partition backup in your rooted phone. Select raw partition image from setting menu. And its done.
promote
I'm posting this comment just to promote this post, please help me with those partitions if you can.
As far I know, these partition's contain very sensitive data unique to the device. So do not upload these files, and do not flash these partitions on another device. For example, it could cause you to have the same IMEI as someone else, or a multitude of other issues.
As for the actual issue, do your IMEI show up correctly in Android, or is it only the signal that is broken?
Professor Gibbins said:
As far I know, these partition's contain very sensitive data unique to the device. So do not upload these files, and do not flash these partitions on another device. For example, it could cause you to have the same IMEI as someone else, or a multitude of other issues.
As for the actual issue, do your IMEI show up correctly in Android, or is it only the signal that is broken?
Click to expand...
Click to collapse
My imei is intact. Its just my cellular signal that doesn't work. And its not only my issue, there are many with the same problem but no solution. So here I am requesting those partition to try as a solution as stated in this post http://forum.xda-developers.com/moto-g/help/story-lost-recovery-imei-0-t3414511 . I've tried everything else that i could find.
In my country wifi network isn't that available. So without cellular network a phone here is as good as dead. Can you suggest any solution?
Flashing those partitions most likely won't fix your network signal, and could make the problem much worse. In the OP you say you flashed the stock modem, so what method did you use to do this? Did you get the stock firmware and run:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Professor Gibbins said:
Flashing those partitions most likely won't fix your network signal, and could make the problem much worse. In the OP you say you flashed the stock modem, so what method did you use to do this? Did you get the stock firmware and run:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
did those, tried flashing full firmware and downgrading too... nothing worked. Any other suggestions?
Usually factory firmware would fix it, so it could be a hardware issue. Under what conditions did you lose signal - did you flash a ROM?