Hello,
I have a Moto G (XT1032) since 3 years and all of a sudden, it didn't boot. I had the Stock ROM, I never installed a new ROM or Recovery...
I unlocked my phone and then tried to install TWRP to boot on recovery and make a backup of my data.
I tried several recoveries (twrp-2.8.6.0-xt1032, twrp-3.0.0.0_2-falcon, twrp-3.1.0-0-falcon, twrp-3.1.0-0-xt1032 & clockwork-touch-6.0.4.7-falcon).
I have no problem to send the recovery on the phone. In the fastboot mode on the phone, it says the installation is okay and then, I choose "Recovery" in the fastboot mode on the phone.
The phone reboot and I have the android logo with "No Command". I find this blog : https://wasconet.com/solution-moto-g-android-recovery-mode-no-command/ and so I hold the power button and press the volume up button to enter recovery mode screen.
The problem is, I access the default recovery — which is not TWRP, only a basic recovery where I can't mount the phone. This recovery says :
Android system recovery
LPBS23.13-56-2
...
From there I can reboot, apply update from sdcard or ADB, wipe data/factory, wipe cache, reboot to bootloader, power down or view recovery logs.
What can I do to install a good recovery and to mount my phone to make a backup ?
Thanks guys !
Lately it happens with the latest versions of twrp. Do not boot or boot once, then return the Stock Recovery again.
In my case I can not install v3.1 because it throws me max download size error. :silly:
Try the v3.0.2-2. It works without any problem over my old falcon.
https://dl.twrp.me/falcon/twrp-3.0.2-2-falcon.img.html
I'm not sure if the command works on the Falcon, but first try starting it without flashing it
fastboot boot twrp-3.0.2-2-falcon.img
By the way, can i assume that having Lollipop you have the latest version of the bootloader (41.1A)?
Thanks, it worked ! I made a backup of my files.
Now I try since this morning to install a new ROM... I tried "Factory" in the fastboot mode => Phone blocks on "Bootloader unlock".
With TWRP, I havea lot of problem with the mount. I can see the data but to copy files, it was not possible.
I mount the sdcard in Read Write with the terminal on the phone to copy the Lineage ROM. I tried to install it but I receive an error "1001".
I use now the last version of TWRP, the 3.1.0 with the command fastboot boot. This version works but I have the same error to install Lineage.
I also tried to install the stock version EU 5.1 Stock ROM (Untouched) (522mb) (from here https://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) with adb sideload.
I saw "succesful" but the phone is always block on the "Bootloader unlock" image...
The bootloader version is indeed 41.1A.
Someone should have an idea to install a system ? (any system, I don't care, I just want a phone that I can use )
Thanks a lot !
Usually error 1001 relates to an encrypted or unreadable partition.
Have you used fastboot or mfastboot to install the system again?
Try Repair or Change file system using twrp.
Wipe>>Advanced Wipe>>
Then try to install any ROM.
If doesn't work. Inside of TWRP go to Advanced>Terminal Emulator
Then execute the command df
That should list you the partitions. Share it and if you know how to take it please share the recovery log after doing all this.
I use fastboot to just boot on the recovery.
To install, I don't tried fastboot or mfastboot. I find a guide to flash with mfastboot, I will try.
Yesterday I made all the wipe possible. Today I made a Repair on the system partition.
Here is the result of the df command :
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 446184 20 446164 0% /dev
tmpfs 446184 20 446164 0% /tmp
/dev/block/mmcblk0p33
667328 11836 655492 2% /cache
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /data
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /sdcard
I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
lolo1410 said:
I I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
Click to expand...
Click to collapse
When you unlock the bootloader, all your personal data should be deleted normally, but that didn't happen. The internal memory partition is recognized (that's good) but is unreadable, obviously corrupted. (Sorry for not noticing before)
Try installing the firmware again using mfastboot avoiding BOOTLOADER (motoboot) AND GPT files to see if works. If didn't, flash it again including GPT file (Partitions table).
If it still doesn't work, you'll have to figure out how to repartition the entire phone memory.
----------
By the way, never try to restore that DATA BACKUP. Like i say before, it's corrupted. Search a way to decompress and takes only the important files.
Thanks a lot for your time !
Indeed, it's seems there is a probleme with the filesystem.
I tried a flash of GPT & Bootloader but it didn't work.
Here is the log :
C:\adb\tmp>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.026s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.320s
&
C:\adb\tmp>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.093s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
But I'm not sure if I choose the good firmware & bootloader.
On this link (http://www.filefactory.com/folder/c6cdedc45a775d27), which version can I take ?
Here is the information that I have for the phone :
Motorola G XT1032 - Type M0DEB - FCCID ihdt56pf1 buyed in Belgium
AP Fastboot Flash Mode (S)
41.1A (2015-04-10)
CPU MSM8226 CS
eMMC : 8GB Sandisk
DRAM : 1024MB Samsung S4
Try with one of these, and again. DONT FLASH BOOTLOADER (Usually cant be flashed after unlock but, I do not think you want a paperweight)
Retail EU 5.1
https://www.androidfilehost.com/?fid=24052804347848287
Retail EU 5.1 (NEWER BUILD)
https://www.androidfilehost.com/?fid=24499762636006646
You can download others from Here
https://forum.xda-developers.com/mo...rmware-t3110795?_e_pi_=7,PAGE_ID10,4937194410
After several tests, I find a good package, this : XT1032_FALCON_RETFR_5.1_LPBS23.13-56-2_cid7_CFC.xml
I had no error.
I see your message too late, I flash the bootloader
But it's a 41.1A version, here is the info on this package :
BUILD REQUEST INFO:
SW Version: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keysMSM8626BP_1032.3116.98.00R
MBM Version: 41.1A
Modem Version: MSM8626BP_1032.3116.98.00R
FSG Version: MSM8626BP_FSG_01.101.00R
Build Fingerprint: motorola/falcon_retfr/falcon_umts:5.1/LPBS23.13-56-2/2:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 221.201.2.falcon_umts.Retail.en.FR
Model number: Moto G
Android Version: 5.1
Baseband Version: MSM8626BP_1032.3116.98.00R
Build Number: LPBS23.13-56-2
Build Date: Fri Feb 26 06:59:41 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.221.201.2.falcon_umts.Retail.en.FR
Version when read from CPV: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keys
I followed the guide here https://forum.xda-developers.com/showthread.php?t=2542219 and no error during all the command. I switch off the phone and unfortunately, no boot...
It's block on the "Warning bootloader unlocked" screen...
The phone is still alive and that's good. Keep trying others roms if you want. But as I said before, surely the internal memory of the phone is corrupt. Unfortunately, I can't help you with that.
Maybe here over XDA there's a tutorial about how to solve your problem.
Okay, thanks a lot for your help.
I just tried the Retail EU 5.1 (NEWER BUILD) and same result : no error but blocks on the boot..
I will continue to test other ROM
I ended up in the same situation when trying to flash GPe on MotoG XT1032; the device was only able to boot into fastboot
After booting into TWRP, I formatted the /data partition again (in order to fallback to F2FS instead of ext4) and I used adb sideload to transfer "XT1032_Retail_Brazil_51_Untouched.zip" (you can find it on xda, under "Stock Motorola Lollipop ROM Collection" thread).
Phone was in full working condition once more
Related
I have sitting here a Samsun Nexus S from Fido in Canada. From what I can tell that makes it the 9020a.
It belongs to a friend and he really wanted CM7 on it after seeing CM7 on my Nexus One.
I helped him root and unlock the phone along with installing ClockWork Recovery.
I left before getting around to installing the ROM. He downloaded it through the ROM manager. After the phone restarted though he was just presented with the white Google logo and it never moved on.
I am trying to help fix this, but he wiped the sdcard and the backup that was done when ROM Manager did a backup.
Here is the problem though, I have installed about 5 or 6 different recovery ROM's trying to get this to work, even more ROM's themselves.
I have tried combinations of ROM's and recovery ROM's.
All of them end with me staring at a white Google logo.
I have access to fastboot and the recovery ROM still. So I decided to just go back to stock by flashing the partitions from fastboot. Some of them will flash, but others won't. I can flash the cache, but I can't flash the recovery, data, or system partitions. When I try I get
sending 'recovery' (8192 KB).
OKAY [ 1.029s]
writing 'recovery'...
FAILED (remote: Write Fail)
or this for Data
FAILED (remote: Unkown Partition)
or this for System
FAILED (remote: Write Fail)
Any and all help would be greatly appreciated. Right now the phone is basically bricked. I am going to sleep but will check back in the morning. If I left some information out please let me know.
Did you unlock the bootloader?
fastboot oem unlock
Then follow the on screen instructions. I had to do that to flash certain *.imgs. I think it has to do with the security checks....
Sent from my Nexus S using XDA Premium App
Does the white Google logo have a padlock symbol at the bottom of the screen? If not then the bootloader is locked. What root method did you use?
Sent from my Nexus S 4G using xda premium
And also what were the commands you used to flash the images.
Sorry for the late reply. Some stuff at work blew up and kept me out late.
atrixboy:
Yes, the bootloader is unlocked.
Rem3Dy:
Yes, there is a pad lock at the bottom of the screen.
suksit:
The commands run originally was just to unlock the phone (fastboot.exe oem unlock). The phone was then rooted and the OS was launched. Once in the OS RomManager was downloaded and installed. Through RomManager clockwork recovery was installed. After that CM7 was selected as the Rom to install. The phone rebooted, did its thing in recovery, then booted to this black screen with white Google logo which I have yet to get passed.
Since then though I have flashed several different recovery images trying to get this to work, right now the recovery is: CWM-based Recovery v4.0.1.4
If I install a Rom from zip through the recovery it says it was OK, but I still get the white logo and nothing else on boot.
I have been trying to just flash boot and system images at this point and am having no luck.
When I try the following:
C:\1>fastboot.exe flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.032s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.039s
C:\1>fastboot.exe flash system system.img
sending 'system' (151459 KB)...
OKAY [ 19.073s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.078s
C:\1>fastboot.exe flash data data.img
sending 'data' (4 KB)...
OKAY [ 0.002s]
writing 'data'...
FAILED (remote: Unknown Partition)
finished. total time: 0.032s
If I boot the recovery and go into adb and try and mount the same 3 partitions I get the following:
mount /system - works fine
mount /boot - mount: can't find /boot in /etc/fstab
mount /data - this one runs for like 5 minutes and then fails with the following error: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
I just realized that there is some more information on the screen of the device while in fastboot and I try this. When I try "fasboot.exe flash boot boot.img" I get the following on screen:
Exceed blocks 0x00000020 > 0x0000001e (The exact number of zeros may be wrong, hard counting them at that size)
FASTBOOT STATUS - FAILWrite Fail
Fastboot also indicates at the top of the screen: FASTBOOT MODE - NO BOOT OR RECOVERY IMG
I am able to get into the recovery though...
Not sure what other information to include.
I have run out of ideas. Does anyone know where else could I go and get help with this?
are you flashing *.img files in cwm or bootloader mode?
In fastboot I am flashing .img files, from CWM I am trying to flash .zip. I downloaded a nandroid backup and tried restoring that from within CWM with no luck.
try formatting all memory locations except sd card in "mounts & storage" and fix permissions and then flash img files.
What exactly do you mean by "fix permissions" ?
Edit: Stupid question, found it under advanced.
So I formatted each of the partitions, did the fix permissions option, and then booted back into the bootloader and tried to flash the system.img file with fastboot. It failed.
C:\1>fastboot.exe flash system system.img
< waiting for device >
sending 'system' (151459 KB)...
OKAY [ 19.001s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.006s
Thank you in advance for trying to help, I really appreciate it.
Edit: I just realized at the bottom of the bootloader after trying to flash the system.img file it now says in bold orange text:
Invalid Magic Code! 0x00000003
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
litanyoffail said:
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
Click to expand...
Click to collapse
I can mount:
/sdcard
/system
/cache
When I try and mount /data it takes 15 minutes and then fails. Says: Error mounting /data!
The model is most definitively i9020a, I just checked under the battery. Thanks for telling me where that is.
milesman said:
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
Click to expand...
Click to collapse
I did, but I am trying it again now.
So, I tried that Nandroid backup again, and it says MD5 mismatch. I checked the MD5's myself and they match. The ones listed in the MD5 file, and the files match.
I tried flashing the *.img files from fastboot, and get that failed to write message I posted earlier.
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
milesman said:
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
Click to expand...
Click to collapse
Did this, still having the same problems.
Possible the bootloader unlock corrupted guys? Sounds to me like either a bootloader error else the nand may have died. Unlikely but possible. I read somewhere about loading a custom bootloader to the Nexus S. Maybe try looking for that, I know it was here on XDA, only place to get good help IMHO. The orange error codes are generally related to a corrupt bootloader/bad nand chip to the best of knowledge, feel free to correct me if I'm wrong.
Sent from my Nexus S using xda premium
If the nand was shot, data, SD and system wouldn't mount either. I had a busted nand on my nexus last month, had to send it in.
Seems like the bootloader is unlocked, but acting as if it is locked. Do fastboot devices, make sure the numbers match on your screen and your command prompt.
Something I noticed: If the fastboot flash recovery is failing, how did you get the multiple recoveries on prior to posting here?
Sent from my Nexus S
Hi I've Installed Chainfire(dumbest idea ever) -I had GLTools with only default plugin- ,too check whenever It would be possible to run Portal-So memory is almost full ,so I couldn't do neither full CWM backup ,and Advanced Backup didn't worked for me.
So What I did was flash 4.4.2(and I was on 4.4.4 europe rom -XT1032)
I have Fastboot Reason: UTAG *flashfail* configured as fastboot(no not after installing chainfire)
I was flashing with my premade /.sh file (fastboot flash partition gpt.bin etc.) and it seems like what have been flasheed is:
wirting 'partition'...
(bootloader) Preflash validation failed
FAILED(remote failure)
wirting 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
witing 'boot'...
OKAY
'system' -sparechunk.0
FAILED (data transfer failure (No such file or directory)) - lol? ,I've actually modified VM to have 512 mb of ram instead of 1536mb and cores from 2 to 1.
*fastboot resets*
Fastboot Reason: UTAG *flashfail* configured as fastboot
'system'-sparechunk.1
OKAY
and the rest wasn't flashed ,What can I do ,...I've just clicked factory(up button-congrats idiot-I wanted to go into recovery to say that I can go there and do something from there *facepalm* and clicked Up button ,because I was on factory option).
Okay ,so know I have no UTAG error recovery still works ,phone gets stuck on unlocked bootloader disclamer.
Btw before I started to install chainfire I've followed some instructions:
Code:
Backup
[B] * boot into recovery
* adb backup -f boot.img boot
* adb backup -f system.img system[/B]
Restore
[B] * boot into recovery[/B]
* adb shell echo -n boot > /tmp/ro.bu.restore
* adb restore boot.img
[I][B] * adb shell echo -n system > /tmp/ro.bu.restore
* adb restore system.img[/B][/I]
I've followed ,Failed
As boot.img from 4.4.2 have flashed can I actually flash that( * adb backup -f boot.img boot) boot.img and I don't magic will help me. Or can Actually someone who Have XT1032 falcon_umts do like CWM Backup without any personal stuff and I would try to flash it(Preloader/boot is not corrupted- device unlocked etc.-) ,when I used Used factory then everything seems to be working(expect for the android of course... and I don't know whenever VM will work If I don't have everything flashed).
Btw I can't Flash System.img from before I've destroyed it with Chainfire ,because the size is more than 600/700 mb and it just out numbers max number for sending system partition to fastboot.
Not saying this will definitely work, but if you get the gpt.bin and emmc_appsboot.mbn files from the 4.4.4 OTA zip (probably floating around here) and overwrite the originals from 4.4.2 in your factory image (delete the old ones or rename them to something else), then do the following:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Then flash as normal according to the guide that's floating around here, but leave out the gpt.bin and emmc_appsboot.mbn (you already flashed these) and the motoboot.img or it will brick it!
I just installed Paranoid Android ontop of it(adb sideload-I couldn't get into CWM ,and by accidently clicking factory in fastboot I could then go to CWM) and it works-then I launch PA install minimal gapps then factory reset it in cwm delete all data and slowly update pa update by update(installing 4.4RC2 into 4.45 is an bad idea for overall performance and stability) -I just kinda paniced.And I think ,because I was using generic fastboot instead of provided in guide ,preloadder didn't get corrupted(when to look at It only boot have been flashed correctly , and PA have boot.img in package).
So far so good.
This error has been associated with locked bootloader.
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Shuttwind215 said:
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Click to expand...
Click to collapse
My moto's bootloader is unlocked too, but it still gives the error...
Found an article:
https://giorgiosadventures.wordpres...rom-gpe-4-4-4-to-stock-and-recover-softbrick/
Try this... Lets see if it helps...
BTW, I got this error after converting xt1033 to gpe, then OTA'ing it to 5.0.1, then downgrading to 4.4.2.
@layman806 My moto g allready work look at post #3 this is what I did it[it looks extremly confusing]. It mightn't work for you through
,but if yours moto g have unlocked bootloader then you can do a lot ,and your situation isn't that bad.
lost101 said:
This error has been associated with locked bootloader.
Click to expand...
Click to collapse
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
khiladi_786 said:
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
Click to expand...
Click to collapse
I have the exact same problem on my xt1031 motog. I cant get any roms to boot and I cant figure out what version of gpt.bin i need to use. I get the same error.
Driving me crazy.
not solved
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
heisenberg1546 said:
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
Click to expand...
Click to collapse
This subforum is not for your phone. https://forum.xda-developers.com/2015-moto-g is the place for you.
If you are getting a 'pre-flash validation' error - even with the latest available firmware image - then you have to either wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.
help me plseeeeeeeeeeeeee i m getting preflash validation failed error on gpt.bin and sparsechunk plseee help me anyone i m using moto g3 xt1550 and trying to flash marshmallow.
Hello,
I have a Motorola Moto G XT1032 on which I have successfully unlocked the bootloader. I can access to recovery (CWM 6.0.4.7) and transfer files using adb in this mod. However, CWM does not get past the splash logo (I do get the occasionnal lag when CWM rebuilds the cache, but this is another minor issue). I have tried the following ROMs, installed each after formatting /system, /data and /cache:
cm-11-20140308-SNAPSHOT-M4-falcon.zip
cm-11-20140405-SNAPSHOT-M5-falcon.zip
cm-11-20140504-SNAPSHOT-M6-falcon.zip
cm-11-20140613-NIGHTLY-falcon.zip
cm-11-20140730-NIGHTLY-falcon.zip
cm-11-20140823-NIGHTLY-falcon.zip
None worked. I did checked the md5 checksums. I have also tried installing GApps using gapps-kk-20140606-signed.zip .
I do not know how to get more information on what happens when CM11 stucks during the boot. 'Show log' from recovery only prints some configuration information as well as:
Code:
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
From what I undersood, extendedcommand is an optional executable used to launch stuff at boot.
I found some ideas from another thread and tried locking/unlocking oem:
Code:
$ fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.057s]
finished. total time: 0.057s
$ fastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.037s]
finished. total time: 0.037s
$ fastboot oem unlock
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.008s
Additionnally I also reinstalled recovery:
Code:
$ fastboot erase recovery
$ fastboot flash recovery CWM-swipe-6.0.4.7-falcon.img
I did have a message "Mismatched partition size (recovery)" but CWM starts fine. I then reinstalled CM11 again, but it did not help either.
Would you have further instruction to try and get CM11 to work?
Just a short post to avoid the thread from being buried down into oblivion.
Same happened to me days ago. I was unable to install any custom ROM. I was in Enhdroix and I flashed the original version of my ROM via fast boot but every time I tried to install a custom was stocked and bootlogo. Some how I figured that the boot loader of the original version was corrupted so I flashed a different stock ROM, after that was able to install custom.
The recovery message is normal you can check videos or post.
Hope this helps my friend.
To prevent any further problems, I also recommend that you flash twrp or philz recovery because the stock cwm recovery is outdated and it will give you problems while flashing ROMs in the future...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
ThisIsMadness said:
Just a short post to avoid the thread from being buried down into oblivion.
Click to expand...
Click to collapse
Check previous answers
Thanks for your help, I finally got it to work!
If someone gets stuck with the same problem, here is what I did:
first, fastboot flash recovery to TWRP
reinstalling (wipe and so) CM11 from TWRP did not work any better
I reinstalled a stock ROM following http://forum.xda-developers.com/showthread.php?t=2542219
I did not boot at all (no logo), but I could still get to fastboot
I reinstalled TWRP, and then CM11
it worked!
From my own diagnosis, I must have accidentely corrupted a partition with fastboot flash. Or maybe I wiped something that I should not have. Anyway, by reinstalling stock, I restored all the partitions and could install CM11. I do not think CWM is to blame here.
Hi guys
I have a retail XT1032 from germany and I wanted to throw 5.1 at it.
I downloaded the GPE_5.1_XT1032_LMY47M.M001_CFC.xml.zip and fired every fastboot command that was given in the servicefile.xml flashfile.xml.
After that my phone was stuck at the google logo with the little lock. I tried several combinations of waiting and reflashing and naturally none of it worked.
Then I flashed TWRP which told me it couldn't mount /system, /data, /cache and /sdcard. I did a manual format of these and did the whole fastboot procedure again... didn't work.
Next thing i tried was installing cyanogenmod on the newly and freshly repaired filesystems. Now my phone started but it had no signal. I did some "fastboot flash modem..." with a bunch of images and flashed a few radio.zip files but none of it worked :/
Now i'm sitting here with either a cyanogenmod with no service or a freshly flashed GPE 5.1 which won't boot. And I think I can't go back because of the new gpt.bin, boot.bin and motoboot.bin.
little detail I forgot: everytime i do a "fastboot flash partition gpt.bin" in my terminal it says:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.324s
and on the phone:
Code:
version downgraded for primary_gpt
Which is weird since it's the same gpt.bin I already flashed (41.19 btw.).
I suspect that's the reason for the damaged partitions but have no idea if I'm right and what to do about it
Any suggestions?
'Preflash validation failed' is normal. You would only NOT see it, if you flash a newer motoboot.img / gpt.bin.
Try flashing the GPE Optimized zip here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Also, in TWRP check /data is formatted to EXT4. See FAQ in above thread for more.
lost101 said:
'Preflash validation failed' is normal. You would only NOT see it, if you flash a newer motoboot.img / gpt.bin.
Try flashing the GPE Optimized zip here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Also, in TWRP check /data is formatted to EXT4. See FAQ in above thread for more.
Click to expand...
Click to collapse
Well it's not only that the preflash validation message comes up but the whole flash of gpt.bin fails.
Data is ext4 (i also tried f2fs but... yeah...) and i tried the recovery-flashable gpe.zip files but it didn't change anything.
But thank you very much
treax said:
Well it's not only that the preflash validation message comes up but the whole flash of gpt.bin fails.
Data is ext4 (i also tried f2fs but... yeah...) and i tried the recovery-flashable gpe.zip files but it didn't change anything.
Click to expand...
Click to collapse
Could you provide more information? Does the GPE zip flash and boot up - you just have no signal?
lost101 said:
Could you provide more information? Does the GPE zip flash and boot up - you just have no signal?
Click to expand...
Click to collapse
No it won't boot at all. While flashing one of the gpe.zips it stops with
Code:
E:Error executing updater binary in zip '/sdcard/gpe.zip'
I attached two screenshots. First one shows the partition situation right after flashing the GPE with fastboot. The second one is the error from above
That's a common error. Reboot recovery and try flashing again.
lost101 said:
That's a common error. Reboot recovery and try flashing again.
Click to expand...
Click to collapse
Nope didn't work.
Yesterday I flashed that brasil 5.0.2 image. Nothing failed and my bootloader version was 41.18 afterwards. But again the partitions weren't mountable and the system wouldn't boot. Fixed it with TWRP and flashed CM again. Now it boots and I have service... weird.
It looks a little bit like I can't flash a stock ROM now without breaking that damn thing.
@treax - look what @d3vileyes says here: http://forum.xda-developers.com/showpost.php?p=60682467&postcount=19
Hi all,
I have got a N5 that is not booting (infinite boot animation loop). It's bootloader is unlocked and I can push stuff via ADB so I am assuming eMMC is good.
Also, USB debugging is OFF, phone is ENCRYPTED and NOT rooted.
I can't mount or modify /data and /persist partitions.
I tried reformating with ext2 to destroy encryption but it is not working. I also tried dd method but was unsuccessful.
I am not interested in recovering or rescuing anything from the phone.
Currently trying to figure out how to activate download mode so I can reflash everything using LG Flash tool.
Thanks in advance
EDIT: Bootloader is unlocked but I can't root the phone with wugfresh's nexus root toolkit.
The encyption can disable only with command fastboot flash userdata userdata.img
The userdata.img you can find in the Google OEM ROM Google M4B30Z
It requires the SDK Platform Tools is installed SDK Platform Tools
You may give a chance and with this http://www.wugfresh.com/
Hi Sant514,
'fastboot flash userdata userdata.img' returns this error:
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 0.460s]
sending 'userdata' (137318 KB)...
OKAY [ 4.511s]
writing 'userdata'...
FAILED (remote: flash write failure)
finished. total time: 5.151s
also tried to format userdata:
fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-GqLE95: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
This reformating with ext2, I don't think this helped the situation,
so can you give a chance with tool http://www.wugfresh.com/?
No you do not need to root your device with wugfresh. It has a choice about unbrick... unroot and resτore
in factory condition...
The menu-choice is "Back to Stock / Flash Stock and Unroot" and you will select "Current Status=Soft Bricked/Bootloop"
Nexus Root Toolkit is giving me multiple flash write failures so I think the eMMC is dead.
Thanks for the help...
I had a similar major crash with my D820 (Nexus 5, US version) last month after trying wireless charging with an aftermarket back cover (overheated followed by kernel panic green screen of death). Infinite reboots. Couldn't get past Google logo. Flashed the factory image without the "-w" option which wipes user data, no joy. I figured I was screwed.
So flashed factory image 4.4.4 totally (-w left in the flash-all.bat script). Then flashed the last 2016 factory image (M4B30Z), and it came back. I hate having to reinstall apps (including discontinued ones via the APK borrowed from my other Nexus device), but it's actually good to clean out old cruft.
https://developers.google.com/android/images#hammerhead
As you probably know, you only need to install the Android SDK, Platform-tools (fastboot, adb, etc), boot into bootloader (run "fastboot devices" to see the phone is connected), and the flash-all.bat file will do the rest. Don't interrupt it, the "warning: ... .sig not found" and "sending System.img" steps will take a while. On my phone, the whole script can take 2 mins.
I've never relocked the bootloader after unlocking, but that could resolve the encryption issue .. but IDK, I've never done it.
Good luck.