Related
NOTE: Says when on rsd mode failed to boot 0x00001
on fastboot same + is says failed to format pds and does't connect to the pc after that
i have over 50 hours in 5 days looking for way to fix no luck .
i try my luck with Fastboot. I first tried flashing the recovery with no luck. I then tried flashing over the official moto files (boot/sytstem/....)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
....
If i follow that order boot/system and recovery fail then userdata says it works and it lets me flash the other options (but clearly just says they work it looks like it's lying)
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
.......
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 11.598s]
writing 'userdata'... OKAY [ 0.164s]
finished. total time: 11.764s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.688s]
writing 'boot'... OKAY [ 3.462s]
finished. total time: 4.151s
.....
If I try fastboot oem unlock I'm prompted with the unlock message and after hitting accept. I see the following error on the screen
ERROR: Failed to format UDA.
Error while unlocking device.
My next try was with RSD light. I tried flashing all of the images for my xoom off this site . all of them give me the following error:
Failed flashing process. Failed Flashing process. Interface AP-OS: Error flashing subscriber unit. Device API error: 0xE0020085 Address: 0x1F870 Command: ADDR (0xE0222085); phone connected
I ran out of ideas on what to do next. One post i saw said try using a nand backup but I can't find one that will work.
Any help would be great. I really love my XOOM and I'm sad i can't fix it.
So I don't have a procedure to fix it but the guys at #android on Freenode gave me a bunch of tips which eventually made my phone work. It loaded a custom rom (liquid smooth) and I can make calls.
Sorry if I can't give you a more precise solution... if someone can figure out the exact reason why I was able to install a custom rom properly, it would help us find a solution to fix the GPT.BIN error.
In a nutshell, I was getting errors when trying to install a custom rom via TWRP (bypassing the stock rom errors) but now I'm able to install a custom rom and run it fine. Please read the logs despite all the crap around it.
Here is the chat log... follow though and do what I did - the solution might be in some fastboot commands I tried:
[08:31] <Jonnyw2k> what does "fastboot oem unlock" say
[08:31] <asdfsdfsadf> (bootloader) Device already unlocked! FAILED (remote failure) finished. total time: 0.003s
[08:39] <asdfsdfsadf> writing 'partition'... Preflash validation failed FAILED (remote failure)
[08:39] <asdfsdfsadf> mfastboot
[08:40] <asdfsdfsadf> not sure what the error is.....
[08:40] <Khaytsus> Well that just looks vulgar at a glance
[08:42] <Jonnyw2k> asdfsdfsadf there is a "fastboot oem fb_mode_clear" command that apparently sometimes helps, but that seems to be more todo with a fastboot issue
[08:42] <asdfsdfsadf> ... OKAY [ 0.002s] finished. total time: 0.003s
[08:43] <asdfsdfsadf> same error when I flash gpt.bin
[08:43] <DrChandra> Perhaps the partition is damaged.
[08:43] <Jonnyw2k> try flashing the gpt now
[08:43] <Aevum> what phone is it ?
[08:43] <asdfsdfsadf> moto g xt1032
[08:44] <DrChandra> Consider the erase and format commands within fastboot
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> just did -w
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <Aevum> fdoijghfiodjhadt
[08:45] <Aevum> try this http://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> formatting 'userdata' partition... Creating filesystem with parameters: Size: 6173884416 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 23551 Label: Blocks: 1507296 Block groups: 46 Reserved block group size: 367 Created filesystem with 11/376832 inodes and 50150/1507296 blocks sending 'userdata' (98165 KB)... writing 'userdata'... OKAY [ 9.953s] erasing 'cache'... OKAY [ 0.24
[08:46] <asdfsdfsadf> Aevum: tried that twice... to give you some insight, I upgraded to 4.4.4 GPE on a non-gpe device, many people got bricked when they tried to downgrade
[08:47] <asdfsdfsadf> After fastboot -w command, same error when trying to partition
[08:47] <Aevum> i dont know what flashing tools motorola uses, becuase theres usuayl the fastboot and ADB
[08:47] <Aevum> and also a proprietary tool from the manufacturer for bathc flashing
[08:48] <asdfsdfsadf> RSD Lite doesn't detect hte phone in fastboot
[08:49] <Aevum> theres usualy a fastboot and a flashing mode
[08:49] <DrChandra> RSD might be asking for a fastboot version and mismatching against whatever is being returned by the bootloader. It could e part of what Motorola uses to prevent anything but their own tool from being used.
[08:52] <Aevum> can you get ADB access ?
[08:52] <The0x539> y'know what
[08:52] <asdfsdfsadf> Aevum: yes ADB works
[08:52] <The0x539> I'll wait until I actually get it
[08:52] <DrChandra> I don't think he can boot, so he won't have adb
[08:53] <asdfsdfsadf> ADB works from stock and custom recovery
[08:53] <asdfsdfsadf> They both can get pushed files
[08:53] <asdfsdfsadf> But when it's time to install
[08:53] <asdfsdfsadf> they fail
[08:53] <DrChandra> asdf: So the main OS is what isn't booting?
[08:53] <asdfsdfsadf> Yes
[08:53] <asdfsdfsadf> But main os can't even get installed
[08:53] <DrChandra> Can you mount anything from recovery?
[08:53] <asdfsdfsadf> Anything I throw at it gives a partition error
[08:54] <asdfsdfsadf> Let me go to recovery and I'll give you the exact errors
[08:54] <Aevum> you are pre flashing the correct boot.img for every rom before, no ?
[08:54] <DrChandra> I wish fastboot could boot directly into recovery. I have to operate it from the screen to get there, or double boot.
[08:54] <asdfsdfsadf> Aevum: yes
[08:55] <Aevum> and the hboot versions coinside ?
[08:55] <DrChandra> Damaged flash memory
[08:55] <Jonnyw2k> you can "fastboot boot recovery.img"
[08:55] <asdfsdfsadf> Jonnyw2k: lfashes but nothing works after it finishes
[08:55] <Aevum> i would format the whole internal memory and start over with a stock image
[08:56] <DrChandra> Jonnyw2k: Yes, but you're not booting what's on the device, and transferring it takes forever.
[08:56] <Jonnyw2k> he's trying that its the partition table that is messed up but he cant flash a new one
[08:56] <asdfsdfsadf> >adb push Rom.zip /sdcard/
[08:56] <asdfsdfsadf> Let me transfer this
[08:56] <asdfsdfsadf> IT's a rom
[08:56] <asdfsdfsadf> And I'll give you the message in TWRP{
[08:56] <DrChandra> I use TWRP
[08:57] <asdfsdfsadf> TWRP works here... it just can't install ****
[08:57] <asdfsdfsadf> Let me get the message
[08:57] <asdfsdfsadf> 1 minute
[08:57] <Sloth514> how come i feel like this conversation should b in #android-root
[08:58] <DrChandra> Well, if the main OS partition (system) is messed up, you can't mount it, and/or you can't write it, so trying to get TWRP to install Rom.zip isn't going to work.
[08:58] <asdfsdfsadf> wow
[08:58] <asdfsdfsadf> mother****ers
[08:58] <asdfsdfsadf> rom booting :/
[08:58] <asdfsdfsadf> PC detecting phone during boot
[08:59] <DrChandra> ADB to main OS?
[08:59] <asdfsdfsadf> I adb'd liquidsmooth rom.zip
[08:59] <asdfsdfsadf> and ran it from TWRP
[08:59] <asdfsdfsadf> IT installed with no issue
[08:59] <asdfsdfsadf> Rebooted
[08:59] <DrChandra> Oh, ran it. YOu didn't install it.
[08:59] <asdfsdfsadf> Liquid smooth is now loading...
[09:00] <asdfsdfsadf> Still loading. I guess the first time is slow
[09:00] <Jonnyw2k> DrChandra he flashed the rom.zip from TWRP, and now is booting the rom
[09:00] <DrChandra> He didn't say he flashed it
[09:02] <DrChandra> asdfsdfsadf: Did you do an Install from TWRP, and select Rom.zip from the sdcard?
[09:02] <asdfsdfsadf> Yes DrChandra
[09:02] <asdfsdfsadf> After pushing it with ADB
[09:02] <DrChandra> OK, he flashed it
[09:02] <asdfsdfsadf> But I tried that before and got errors
[09:02] <asdfsdfsadf> Some command I typed in fastboot must have fixed it...
[09:03] <DrChandra> How is it that TWRP knows how to write the system partition and all the flash tools don't?
[09:03] <asdfsdfsadf> But right now the issue is that I'm stuck at the animated boot scren (never got this far)
[09:03] <asdfsdfsadf> normally it takes time, but not several minutes, right?
[09:03] <Jonnyw2k> you can try and reboot
[09:03] <Jonnyw2k> press and hold power till it turn off
[09:04] <Jonnyw2k> then turn it on again
[09:10] <DrChandra> Well, if the device is badly broken enough, even fastboot won't work.
[09:10] <Khaytsus> fastboot will _always_ work unless you somehow broke the bootloader
[09:10] <DrChandra> logcat is miles above that
[09:10] <asdfsdfsadf> fastboot works, it just won't flash gpt.bin... wait let me try that again now that liquidsmooth actually got flashed though TWRP
[09:10] <Khaytsus> logcat requires the system be at least in some normal condition, even if it's boot looping or something
[09:10] <Leeds> Khaytsus: it seems that - at least at one point - fastboot was working in the sense of responding, but not working because the partition table was so screwed that it couldn't read/write partitions
[09:11] <Khaytsus> Leeds: Heh. Interesting. I suppose if you break _partitions_, yeah....
[09:13] <Khaytsus> fastboot flash partition gpt.bin <-- looks like this is what you do
[09:13] <asdfsdfsadf> So: fastboot flash partition gpt.bin Gives me: writing 'partition'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.423s
[09:14] <asdfsdfsadf> Which is the original error
[09:14] <DrChandra> I've never seen fastboot write to "partition" before. It's always "system", "boot", "userdata", or "cache"
[09:15] <asdfsdfsadf> The only difference between now and then is that the rom actually boots but just stays stuck on the animation screen
[09:15] <Khaytsus> That error means unsigned or unrecognized img file
[09:15] <Khaytsus> You sure this file is valid?
[09:15] <asdfsdfsadf> Yes, tried 2 copies
[09:15] <asdfsdfsadf> Ok something just happened
[09:15] <asdfsdfsadf> Rom just loaded
[09:15] <asdfsdfsadf> I'm on the home screen
(Rebooted twice after it was stuck on loading screen)
Sorry for the long thread... Cleaning up the chat logs to make it more clear.
newklear85 said:
Sorry for the long thread... Cleaning up the chat logs to make it more clear.
Click to expand...
Click to collapse
don't get it xD
man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."
hansdepaula said:
man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."
Click to expand...
Click to collapse
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?
gpt.bin for 4.4.3 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\443>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.352s]
finished. total time: 0.373s
C:\Users\Hans\Desktop\443>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.302s]
writing 'recovery'...
OKAY [ 0.181s]
finished. total time: 0.485s
C:\Users\Hans\Desktop\443>
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
---------------------------------------------------------------------------
gpt.bin for 4.4.2 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\442>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Users\Hans\Desktop\442>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.165s]
finished. total time: 0.479s
C:\Users\Hans\Desktop\442>
same
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
-------------------------------------------------------------------------
my fastboot dnt write nothing,
i think, sone thing have format partitions to RAW system
and i cant white or format then..
see more logs about my case: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
maybe you can help..
thx..
newklear85 said:
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?
Click to expand...
Click to collapse
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version
Fresroqir said:
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version
Click to expand...
Click to collapse
Only thread in here that can potentially make it work... almost no attention lol
For the mobile network, flash the radio that came with stock.
man, you can upload to me a new gpt.bin and motoboot.img ..
4.4.4 maybe
i only have 4.4.3 and lower versions, and it dont work..
:/
I have a Moto G (XT1032) running Android 5.0.2 that went out of charge one day. It then decided to boot into a black screen - i.e. I can see the Motorola splash screen (animation) but all I get after that is a black (grey) screen, not responsive to touch.
I tried a few things and they didn't work -
Fastbooted and selected 'Recovery' option - The Motorola logo (first screen of startup splash screen) appears briefly. Then the device returns to fastboot menu saying 'Boot Up failed'
Fastbooted and selected 'Factory' - The Motorola splash screen appears, boots into same black (grey) screen again.
The fastboot menu says "Device is LOCKED. Status Code: 0". I did not enable USB debugging before my phone stopped working.
How do I get my phone working again?
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
lost101 said:
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
Click to expand...
Click to collapse
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.084s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.330s]
finished. total time: 0.418s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash motoboot motobo
ot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.151s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.957s]
finished. total time: 1.112s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.035s]
finished. total time: 0.132s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash recovery recove
ry.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.591s]
writing 'system'...
OKAY [ 7.728s]
finished. total time: 17.323s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.955s]
writing 'system'...
OKAY [ 8.082s]
finished. total time: 17.042s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 9.657s]
writing 'system'...
OKAY [ 8.179s]
finished. total time: 17.843s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 6.347s]
writing 'system'...
OKAY [ 6.282s]
finished. total time: 12.635s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.943s]
writing 'modem'...
OKAY [ 0.780s]
finished. total time: 2.727s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.022s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.279s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboot
Click to expand...
Click to collapse
Thats all that i got... i don't know what else to do...
Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
pradeeppk said:
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
Click to expand...
Click to collapse
i do it, but i get the same message, "No Command"
lost101 said:
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
Click to expand...
Click to collapse
I see something wierd now, looks like the memory of the phone dosent save anything... sometimes, when the boot animation stops, i see the message of "1 of 1 Updates, android its updating" and then go to the black screen again... but, if i flash the phone, i shouldn't see that message, rigth? so, why i can still see it? how can i erase all the memory for sure???
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
lost101 said:
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
Click to expand...
Click to collapse
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Joncillo said:
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Click to expand...
Click to collapse
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
lost101 said:
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
Click to expand...
Click to collapse
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Joncillo said:
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Click to expand...
Click to collapse
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
lost101 said:
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
Click to expand...
Click to collapse
when i wipe the device, i get some errors.
E: MTP already enable
Formatting data using mkfs.f2fs...
Done
E: Unknown MTP message type 1:
You may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to stat '/data/data/com.google.android.gms/app_sslcache/www.googleapis.com.443'
E: Unable to stat '/data/data/com.google.android.calendar/databases/timelydata.db-shm'
...done
but don't wipe anything...
i try ADB Sideload but get an error too.
Starting ADB sideload feature... (After 10 minutes)
FAILED ADB Sideload complete.
and the CMD on windows says "Error: device not found"
also i try to install TWRP as zip, but when i restarted, enter into recovery and then i have the same android with error "No Command".
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
lost101 said:
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
ahhhhhhhhh... i see... so, i have a dead phone... well, i'm going to try what you said in that post, thanks for all your help!!!
I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....
@Peterrrrr said:
I wiped everything in trwp when I was going to install Lineage, I did the misstake to restart the recovery and now Im stuck in the bootlaoder.
I need to install the stoc firmware via fastboot/bootlaoder but can't find any img file, only zip file of the Stock firmware.
Is is possible to install a zip file via fastboot?
Fastboot recognize the phone when typing the commando fastboot devices, so I see the serial nr.
If I try to install twrp img both on boot and flash recovery commando I get this:
PS C:\Android> fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.598s
PS C:\Android> fastboot flash recovery twrp-3.2.1-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.574s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.579s
I have tried the MsmDownloadTool V4.0, but the deviced manager in windows doesn't find the Qualcom....
Click to expand...
Click to collapse
I have never tried msmtool, but it sounds like a driver issue. Maybe take a closer look at their instructions
You can try these fastboot flashable stock roms.
You have few options to solve your issue. Now you are in slot B. You can change switch partition to A with fastboot. Try use: fastboot --set-active=a. It will switch to partition A and then try to boot/flash recovery. Also you have try to use fastboot roms with flashall.bat. There are few availaible in forum.
If you would like to use MSM you have to connect phone in proper mode to PC. Power off and hold Vol+ then connect. Also try to install latest Qualcomm drivers.
Msm tool
Download and use msm tool
!!!!!DISCLAIMER!!!!!! --- below info is provided as is without any warranty, do it on your own risk
I ported TWRP for Tab E10 from Asus Nexus 7 2012.
Installation:
1. Unlock bootloader.
2. Flash in fastboot (fastboot flash recovery <File name>)
3. Reboot to recovery from bootloader interface with volume buttons.
4. Uncheck Mount system partition read-only in Mount, and remount it.
5. In Advanced/File manager erase recovery-from-boot.p inside /system/
6. Done!
Bugs:
Encryption. You can use adb sideload or external sd.
Changelog:
26/12/2022
Initial port release.
27/12/2022
Userdata now uses F2FS.
Encryption fixed.
Added option to flash IMG to system.
17/02/2023
Added initial support for X104L.
Credits:
@Augustoandro for his guide "[GUIDE]Porting TWRP without source"
@jskelgaard for test with X104L model.
can't get it to work
C:\Users\jh\Downloads\platform-tools>fastboot flash recovery x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'recovery' (15502 KB) OKAY [ 0.500s]
Writing 'recovery' OKAY [ 0.336s]
Finished. Total time: 0.880s
C:\Users\jh\Downloads\platform-tools>fastboot boot x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'boot.img' (15502 KB) OKAY [ 0.490s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
jskelgaard said:
can't get it to work
C:\Users\jh\Downloads\platform-tools>fastboot flash recovery x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'recovery' (15502 KB) OKAY [ 0.500s]
Writing 'recovery' OKAY [ 0.336s]
Finished. Total time: 0.880s
C:\Users\jh\Downloads\platform-tools>fastboot boot x104f\twrp-3.7.0_9-0-v2-x104f.img
Sending 'boot.img' (15502 KB) OKAY [ 0.490s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are sure to have "TB-X104F"? Exists others models like X104L.
Try to reboot from bootloader, maybe hotboot not work properly
mr.lfrl990 said:
You are sure to have "TB-X104F"? Exists others models like X104L.
Try to reboot from bootloader, maybe hotboot not work properly
Click to expand...
Click to collapse
as far as i can reed the x104l and x104f is the same except lte connection, but yes...i have two of the x104l versions.
Reserved