Hello gang.
I appears this dyslexic numpty has creamed his phone somehow - It's in Soft Brick mode and isn't playing with me any more.
It's a 1st Gen Tesco 8GB, I updated it to GPE and lollipop. But I couldn't get a new sim card working so I flashed Cygo CustomRom with it and now I'm stuck in a bootloop.
I honestly don't know where to start or where to begin, i've followed some tutorials to no avail and I'm wondering if someone would be so kind as to help a fool out. I've tried this http://forum.xda-developers.com/showthread.php?t=2542219 - But I get errors.
Any help would be appreciated.
What errors do you get ? Try relfash the GPe firmware to your device. If you flash the Moto firmware your phone will be bricked from what I know if you have the GPe firmware.
Eurofighter_ty said:
What errors do you get ? Try relfash the GPe firmware to your device. If you flash the Moto firmware your phone will be bricked from what I know if you have the GPe firmware.
Click to expand...
Click to collapse
Keep on getting Mismatched Partition Size.
Then when I finish and reboot it just stays on the bootloader unlocked screen.
Try this:
http://android.clients.google.com/p...incremental-KTU84P.M003_18-LRX21Z.M002_15.zip
Download it and then sideload it with ADB to recovery.
Make sure you have the fastboot drivers installed and adb installed and then write the folowing command
adb sideload
after "sideload" you type the location of the zip file and enter !
Related
Hi All,
I have two G device ( from unknow source, Expansys ? )
worked with 4.4.2, after I get OTA 4.4.4
then have bootloop on boot logo on both device.
I try many of solution with fastboot ( RSD cannot see the device, other moto are working (? )
try to flash with fastboot 4.4.2 retail GB, no results.
After I unlock the bootloader, flash the GPE 4.4.4 xml
get errors failed for boot and failed to recovery on the phone screen while fastboot.
Any idea?
Thanks
zsebob said:
Hi All,
I have two G device ( from unknow source, Expansys ? )
worked with 4.4.2, after I get OTA 4.4.4
then have bootloop on boot logo on both device.
I try many of solution with fastboot ( RSD cannot see the device, other moto are working (? )
try to flash with fastboot 4.4.2 retail GB, no results.
After I unlock the bootloader, flash the GPE 4.4.4 xml
get errors failed for boot and failed to recovery on the phone screen while fastboot.
Any idea?
Thanks
Click to expand...
Click to collapse
Please uninstall the drivers from Device Manager and reinstall the drivers so RSD-Lite can flash the phone. Otherwise reinstall Windows or try on another Windows computer.
Download the latest drivers on Motorola's website.
Download RSD-Lite 6.1.6 from here: https://bitly.com/bundles/johnlgalt/2
What RSD-Lite version are you using?
If this doesn't fix it then this indicates NAND failure.
There is only 1 main point that I wanted to share with others....
DO NOT EVER EVER TRY TO FLASH THE BOOTLOADER OF ANY ROM OTHER THAN 5.0/5.0.1 OR LATER VERSIONS AFTER YOU HAVE UPGRADED TO LOLLIPOP!!.
Let me tell you first what happen if you do so........
1.) 95% Probability of Permanent Hardbrick Device
2.)Intense Graphical Glitches[These can be get rid off by flashing cm12 or any Android OS 5.0/5.0+ since it has upgraded bootloader]
3.)You May NEVER ever recover your device again.
How will you recognize you are about to flash Bootloader??
It usually has a name "motoboot.img"
What if the name is different?!
Let this time the name is abcdefg.img
The guide you may be following will ask you to perform a command line query on fastboot by the syntax-
"fastboot flash motoboot "abcdefg.img"
Pay attention it still has motoboot in command line.
Now why this happens??
I believe that with the release of Android 5.0 aka Lollipop, the Bootloader of ROM has been upgraded and modified to work with ART system efficiently.
So if you flash the older Bootloader over an upgraded one, you are gonna regret your move completely.
What is Permanent Hardbrick?!
This is a state of your phone which cannot be recovered either easily or permanently. Your device becomes completely useless. You will only see a black screen. Neither you will access Fastboot Mode nor Recovery. Your Phone will become a showcase or in other words a real BRICK.
An Advice- If you are going to flash a zip via a custom recovery like TWRP/CWM/PHILZ. First do check it by opening that it should not have the bootloader image file. If it has, make sure you delete it and then try flashing it.
Now I will share my experience-
How I Downgraded successfully
1.) I Installed a custom recovery via fastboot. [TWRP 2.7.1][2.8.1 WILL DO IT TOO]
2.)Wipe Data/cache/Dalvik Cache/etc,..The normal procedure.
3.)Copied the ZIP file of Moto G Revolution G XT1033 4.4.2 Brazil Firmware to my pendrive.
4.)Make sure your pendrive is in FAT32 Format. if not do a format in FAT32.
5.)Connected via OTG Cable to my phone in recovery mode to TWRP Recovery.
6.)Mount OTG Storage in Mount Option.
7.)Chosen my zip file under flash option and flashed it successfully.
Cons: A water like wave keeps coming from the top of the screen to bottom while booting up but goes off as soon as you turn your screen off for the 1st time. then its all normal again.
Link to Revolution G Firmware- https://forum.xda-developers.com/showthread.php?t=2690047
Guys this is my 1st post here that is well laid. Hope you thank me if this helped you.
There's a tool called Motoflasher. It can do a blank-flash your corrupted bootloader with the latest one. But until today it only support 4.3, 4.4.2, 4.4.4. And for 5.0 will be coming soon. Motoflasher is a tool to revive your-corrupted-bootloader-device after do an accidental downgrade. :fingers-crossed:
Yes, but I want to know, what would happen, when you delete the bootloader. Will it still be under device manager. So will it get detected by windows?
Why would someone do that?!
Freakfussel said:
Yes, but I want to know, what would happen, when you delete the bootloader. Will it still be under device manager. So will it get detected by windows?
Click to expand...
Click to collapse
Delete the actual bootloader from the phone?! I would not recommend you to do that. Coz bootloader is the final option for a device's recovery.
hello i have a moto g 2013
i restarted it after formatting it but it wont get past the warning bootloader unlocked screen
please help
What did you format and how did you format?
audit13 said:
What did you format and how did you format?
Click to expand...
Click to collapse
i m sorry i accidentally deleted my os and when i start adb sideload and type adb devices i dont see my device listed there pls help
Can you get into fastboot mode?
yes but i dont know how to use fastboot commands but i see my divice listed there
Do you have the stock 4.4.4 ROM for your phone? If not, try to find it from here and download it: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
How to restore stock ROM: http://forum.xda-developers.com/showthread.php?t=2542219
can i flash android 5.0.2 on my device?
You can flash lollipop if you can find the full rom.
[HELP] Black Screen Even after Restoring to stock firmware & Cannot relock Bootloader
My phone - Moto G XT1033 Asia Dual Sim
I updated my phone to 5.0.2 official via OTA.. And then unlocked by bootloader...
Everything was working fine, after few days, phone suddenly stopped working.
I restarted my phone and after that, every time after moto boot animation, it always gets stuck at a black screen, showing nothing
I tried all the tutorial of Reverting back to stock firmware.. I tried flashing following files via both fastboot and mfastboot... Everything gets flashed successfully without any error.
First I tried 5.1. file named - XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml
Then 5.0.2, ASIARETAIL_XT1033_5.0.2_LXB22.46-28_cid7_CFC.xml
Then 4.4, ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.xml
Still same problem persists.. Phone does not starts after moto boot animation and stucks at a black screen..
I tried to downgrade to 4.3, tried to flash this file fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar, but it always show prevalidation of firmware failed.
Screenshots of my bootloader and the blackscreen have been included....
Also I tried relocking my bootloader several times.. But after flashing a stock firmware, there comes a screen where is it written locked and when I reboot to the bootloader, it still shows unlocked..
This is how my bootloader looks right now http://postimg.org/image/4w8zrwgrp/
Bootloader Unlocked Warning http://postimg.org/image/o76nd4qux/
Moto boot animation works perfectly http://postimg.org/image/m3w85gr21/
And then this black screen comes and phone stucks here. http://postimg.org/image/5775d1ji1/
Fastboot results in Cmd after flashing Stock 5.0.2 http://postimg.org/image/a6ksy5nyv/
http://postimg.org/image/uf86jvn9z/
http://postimg.org/image/5zzyitod3/
Please please please help me now... I have been asking since a long time.. And have described my problem clearly this time..
Is there anyone who can help me
Somebody please help me
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
happiy91 said:
Today I tried restoring to the stock firmware 5.1.1 ( Moto g XT1033 Asia Retail, which my phone had before going dead). I flashed all the files correctly with mfastboot... Everything went right...
Click to expand...
Click to collapse
Post a full console log of your fastboot commands and the corresponding output.
happiy91 said:
I have unloacked bootloader.. And I think since before going dead usb debugging was not on,, I am unable to flash custom recoveries.
Click to expand...
Click to collapse
USB debugging affects only Android and is not required for flashing custom recoveries.
Finally. Somebody replied.. Thanks a lot..
I will just upload the console output and other things in detail tomorow morning..
_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
I have updated the details.. PLease check it now.. And help me please
Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.
_that said:
Not getting an answer is usually a sign that you didn't provide enough information. Most people who could probably help you will ignore your question if it's incomplete.
Post a full console log of your fastboot commands and the corresponding output.
USB debugging affects only Android and is not required for flashing custom recoveries.
Click to expand...
Click to collapse
_that said:
Sorry, I don't know how to fix your black screen issue. However I've seen others reporting a similar problem (but didn't read the threads). And I've read that downgrading your bootloader can brick your device. You also said that flashing the ROMs worked without errors, but you didn't provide a log of your fastboot commands and the output that you got.
Click to expand...
Click to collapse
My phone is not bricked... Output of fastboot commmands in Command prompt have been already included in the post.. I have included the screenshots..
flash custom recoery and rom
if you by any chance downgraded the bootloader (fastboot flash motobot......) in your previous flash attempts there is a chance you have hard bricked your device.
and there is no point locking/unlocking bootloader (fastboot oem unlock/lock) once its unlocked. the only reason you are able to flash stuff you have is because the bootloader is unlocked. and i'm not sure how well you can lock a bootloader thats unlocked.
incase you have hard bricked your device refer; https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
hello
i've bought used moto g 2015 from spain.
the problem is that the device is locked with status code 0.
i've been trying to unlock it, but with no luck.
everything gives the error failed(remote failure)
recently i've used windroid toolkit to unlock bootloader and install twrp like in some tutorials, the app says it's done, but after i enter a recovery the phone hangs and boots again to fastboot.
any help will be appreciated
EDIT:
invoking "mfastboot flash partition gpt.bin" command gives the error too so i am unable of installing stock firmware too
EDIT2:
i've successfully installed stock package but there is still a problem - boot loop.
you need to flash stock rom to remove boot loop.
here is the link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
sachin09 said:
you need to flash stock rom to remove boot loop.
here is the link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
I have already flashed the rom but now i think it could be a bad package. My phone is from spain and i installed before:
XT1541_OSPREY_ORAES_6.0_MPI24.65-33_cid7_subsidy-DEFAULT_CFC.xml
now i'm downloading
XT1541_OSPREY_RETES_6.0_MPI24.65-33_cid7_subsidy-DEFAULT_CFC.xml.zip
is there any way to find out which package should i use for sure?
the last package i mentioned doesnt change anything. phone boots to bootloader not to system.
any news i have the same thing with my device everything was flashed but i get boot faillure ??
nothing... i'll get my money back i guess