Related
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e94557, 2013-05-24 14:49:34)
eMC Info: Size 8GB
Device is LOCKED, Status Code 0
Battery OK
Transfer Mode:
USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
Click to expand...
Click to collapse
Anyone got any ideas what might have caused this, and what can be done to fix it?
Leraeniesh said:
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
Anyone got any ideas what might have caused this, and what can be done to fix it?
Click to expand...
Click to collapse
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
ATTACK said:
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
When flashing anything via fastboot (or mfastboot)
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32KB)...
OKAY [ 0.074s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.383s
Click to expand...
Click to collapse
Leraeniesh said:
When flashing anything via fastboot (or mfastboot)
Click to expand...
Click to collapse
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
ATTACK said:
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
Click to expand...
Click to collapse
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
EDIT: Was able to get it to flash using HouseofMoto's RSD XML.
All good
Leraeniesh said:
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
Click to expand...
Click to collapse
And you tried to restore 98.30.1? I know with the leak, it is a two part flashing process. It will reboot after part 1, then you need to reboot into recovery to start part 2. You may need to wait until there's a FXZ to fix it.
This is scary. Ive just RSD'd back to stock and am about to update my phone with all the OTA's. Perhaps ill stop for now.
EDIT: And the OTA process just failed from Stock update. FML.
Maybe try this? This is sourced from Moto's website
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620
If anyone else experiences something similar, you can follow jimyv's post regarding setting up RSD to flash (despite something going wonk with the partition table)
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
techfellow said:
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
Click to expand...
Click to collapse
How did "everything fail?" Just need more details.
xKroniK13x said:
How did "everything fail?" Just need more details.
Click to expand...
Click to collapse
I've been trying this for the past 2 days. I just tried it again so I can give you details, and it worked without any issues, so I'm good.
Thanks to all the previous posters, and the house of moto maker.
This is a guide that is strictly for those who are as impatient as I am to get Lollipop on their Moto G (2014). I know there are several guides for folks in the US, and other countries as well, but currently there is no OTA for Canada yet. We are literally left out in the cold. So, I thought I would put a collaborative guide together so the Canadians can enjoy some 5.0, too!
First and foremost, if you F up your phone, that's on you. This will void your warranty, and I am in no way responsible for any stupidity you conjure up during the process.
I have only tested this on the XT1064, which is the single SIM US/Canada model.
The issue when trying to simply follow the upgrade guide for the XT1064 is that the OTA file looks for a 4.4.4 variant of Android that needs to be the same region as where the OTA came from. If you try to install it on the Canadian versions, you will get an error. So, here goes:
1. Unlock your bootloader. Follow this wonderful guide: http://forum.xda-developers.com/mot...wip-unlock-bootloader-moto-g-2nd-gen-t2875728
2. Download the US version of 4.4.4, it can be found here: http://www.filefactory.com/file/2ygnt0x45vcr/RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
3. Extract the above file to the same location you installed Minimal ADB in the first step (C:\Program Files(x86)\Minimal ADB and Fastboot)
4. Turn your phone off and disconnect it from the computer. Press and hold the volume down (-) button and power button to get into Fastboot mode. Connect your phone to the computer.
5. Run Minimal ADB and run these commands:
PHP:
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_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
I removed the modem commands on purpose, and I will explain why later.
6. Once the phone has rebooted, plug it in to the computer and follow this guide: http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361
You should now have Lollipop on your Canadian XT1064!
If you have issues with the WiFi or cellular, you may have to flash the modem commands again from the old file. I had to download the original Canadian ROM (http://www.filefactory.com/file/78znv8hx0tvt/RETCA_XT1064_4.4.4_KXB21.85-16_cid14_CFC.xml.zip) and using Fastboot flash the following:
PHP:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
After that I had no issues and everything seems to be working as it should. You can relock your bootloader afterwards if you like as well.
Thanks to the other contributors above, I was simply trying to put a quick guide together for us Canadian folks who wish to get Lollipop, too!
Cheers!
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
This worked for me! Thanks for the awesome tutorial!
brianshayne said:
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
Click to expand...
Click to collapse
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
NexusChrist said:
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
Click to expand...
Click to collapse
Yeah - I'm not sure what the problem was - originally it wouldn't take the US ROM due to a downgrade error. Tried it again, after a factory reset and for some reason it went through. Flashing Lollipop and the modem after was no issue at all - so good to go now. It's beautiful.
Thanks for the follow-up.
AKA: I should have just ignored downgrade error + HAB fail on phone, the first time around
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
ramzilla136 said:
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
Click to expand...
Click to collapse
Disregard the error and move on to the next command. You are going to get a few errors. Don't worry.
installing update
verifying current system
/system/app/3c_main.apl has unexpected contents
installation aborted
this is after i run the commands and upload from sd card...
followed your commands and tried few fresh zips
can you please help, it won't let me install the lollipop file
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
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 system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
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 system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Is this procedure better? Any enhancement? Thanks.
Botsok said:
Is this procedure better? Any enhancement? Thanks.
Click to expand...
Click to collapse
This one just avoid you to flash USA KitKat and then Lollipop. This one goes directly to Lollipop.
Doesn't flash Modem/Radio from USA Lollipop because doesn't work on Canadian models, at least didn't work with WIND Mobile model.
WIND canada moto G XT1064 lollipop
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
https://mega.co.nz/#!dk430ZBZ!diHa6V-rcidHFc3niGjshk-2A9ELbqZtCnb63pFK010
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
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 system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Just a super-dooper-uber Thanks To NexusChrist!
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
UnderAppreciatedDev said:
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
Click to expand...
Click to collapse
That happened because you flash the modem from Lollipop... Just flash the modem in OP and you will be ok.
spiritflare said:
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
Click to expand...
Click to collapse
Just a tad bit curious I also have a Wind Mobile Moto G2 and i'm just wondering how you unlocked the bootloader in the first place. If you could please share the process on how you did it that would be great.
Anyone know how we can get the LP bootloader on the Canadian version?
I'd like to be able to update my CM12.
Thanks!
Awesome
I'm on Bell &
everything is working 100% radio/wifi/bluetooth all good
Thanks
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Kewjoe said:
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Click to expand...
Click to collapse
Your carrier is most likely the reason since they have the final say on updates.
Tel864 said:
Your carrier is most likely the reason since they have the final say on updates.
Click to expand...
Click to collapse
But what about the people that bought their phones from Staples. It's unlocked and not associated to any carrier. They are directly under Motorola and still no update at all. Phone are getting 5.1 update already, but we're still at 4.4.4
What's so different in the Canadian market from the US one that the update can't come fast? Specially if the phone is not associated to a carrier and the update should come directly from Motorola
so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.
Having same issue. Restored stock and without root it works. After installing root the same problem occurred
search the site for the firmware. Download the firmware page and look for the file non-hlos.bin. Do the fastboot method but UNCAPS it. The file is in CAPS, rewrite the thing in lower case.
You may also have to flash the NON-HLOS.bin multiple times, it took me 3 flashes to get it to finally flash properly (There is no way to determine if it worked without booting android).
Go to your fastboot files folder
Open notepad
Paste this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
Save it like flashmodem.bat in adb folder
Take from original decompressed ROM
NON-HLOS.BIN & fsg.mbn and copy those files in adb folder with the bat file.
Run it
Enjoy
Remember to remove your sim card
nitros12 said:
so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.
Click to expand...
Click to collapse
zakoda said:
Having same issue. Restored stock and without root it works. After installing root the same problem occurred
Click to expand...
Click to collapse
Restore your stock backup and flash SuperSU 2.62 this should give you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.
[email protected] said:
Restore your stock backup and flash SuperSU 2.62 this should gif you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.
Click to expand...
Click to collapse
Forgot to update my post, solved by flashing the stock ROM and then flashing whatever I wanted on top
Yesterday afternoon my phone decided to throw a fit. I was listening to a podcast via AUX, and all of the sudden my phone reboots. No big deal. However, the phone never booted. So I enter TWRP to restore a backup. Restoration completes fine, however my backup bootloops (uh oh).
LONGG story short, my phone will not boot. Fastboot tells me "Baseband: Not Available" which is...unpleasant. I have tried manually flashing firmware, no dice, bootloops. I finally decided to try RSD Lite, but when it gets to the modem (NON-HLOS.bin) the flash fails. For the record, I'm using the full firmware from the May Security Update, XT1575.
Im starting to become worried this is a real issue. Any help or experience with this type of issue is greatly appreciated!
Are you wiping data?
lafester said:
Are you wiping data?
Click to expand...
Click to collapse
After originally bootlooping, i tried restoring a good nandroid. When that also bootlooped, i reentered TWRP and tried a fresh install of an CM nightly. That install began, but wouldn't progress nor fail. I eventually encountered an error regarding the data partition, so i rebooted TWRP again and formatted data, and again tried installing CM.
When that also failed, I began attempting to flash stock firmware via fastboot.
Sent from my m8wl using Tapatalk
Can you manually push the firmware via fastboot?
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Some people have noted doing the erase command before the flash commands helps, or make 2-3 attempts at flashing the NON-HLOS.bin file are required to get an OK.
Otherwise try flashing the full factory firmware, but expect gpt.bin to fail, that is normal, when you get to NON-HLOS.bin flash execute the command up to 3 times to try to get it to go.
If you continue to get failures, it is possible that your emmc chip is corrupt or defective. :/
acejavelin said:
Can you manually push the firmware via fastboot?
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Some people have noted doing the erase command before the flash commands helps, or make 2-3 attempts at flashing the NON-HLOS.bin file are required to get an OK.
Otherwise try flashing the full factory firmware, but expect gpt.bin to fail, that is normal, when you get to NON-HLOS.bin flash execute the command up to 3 times to try to get it to go.
If you continue to get failures, it is possible that your emmc chip is corrupt or defective. :/
Click to expand...
Click to collapse
Yes, multiple times. The modem would always flash on second attempt. Still wouldn't ever boot.
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
Yes, multiple times. The modem would always flash on second attempt. Still wouldn't ever boot.
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Dumb question... is it looping, or just sitting at the boot logo after the initial boot animation appears? First boot can take what seems like a really long time, over 20 minutes sometimes.
acejavelin said:
Dumb question... is it looping, or just sitting at the boot logo? First boot can take what seems like a really long time, over 20 minutes sometimes.
Click to expand...
Click to collapse
I was getting bootloops originally, since flashing firmware each time I try to boot it sits at the unlocked bootloader screen for a couple seconds, then the blue M for a couple seconds, then the screen turns off and immediately returns to the unlocked bootloader message.
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
I was getting bootloops originally, since flashing firmware each time I try to boot it sits at the unlocked bootloader screen for a couple seconds, then the blue M for a couple seconds, then the screen turns off and immediately returns to the unlocked bootloader message.
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
So it is truly bootlooping... And you tried the full factory images?
acejavelin said:
So it is truly bootlooping... And you tried the full factory images?
Click to expand...
Click to collapse
I believe so! I'm using the following:
XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
I believe so! I'm using the following:
XT1575_CLARK_RETUS_6.0_MPHS24.49-18-4_cid9_subsidy-DEFAULT_CFC.xml.zip
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Did you manually flash all 8 sparsechunks? According to the file contents and service.xml file, the appropriate way to flash this image is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- May fail, if fails twice, just continue
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
EDIT: Also note that after flashing the factory images it is known to fail to boot if you do not do a factory reset with the stock recovery prior to flashing the images... fastboot flash the recovery image, do a factory default, then go through the full list above, step by step, and verify you get an OK after every step, if you don't repeat the step before continuing. I would suggest using the above method manually.
acejavelin said:
Did you manually flash all 8 sparsechunks? According to the file contents and service.xml file, the appropriate way to flash this image is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- May fail, if fails twice, just continue
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
EDIT: Also note that after flashing the factory images it is known to fail to boot if you do not do a factory reset with the stock recovery prior to flashing the images... fastboot flash the recovery image, do a factory default, then go through the full list above, step by step, and verify you get an OK after every step, if you don't repeat the step before continuing. I would suggest using the above method manually.
Click to expand...
Click to collapse
Those were the instructions i was following, but i did not know about this stock recovery issue.
You're saying flash stock recovery, enter recovery and perform a factory reset, and then fastboot flash the firmware package as instructed?
Sent from my m8wl using Tapatalk
DonKilluminati23 said:
Those were the instructions i was following, but i did not know about this stock recovery issue.
You're saying flash stock recovery, enter recovery and perform a factory reset, and then fastboot flash the firmware package as instructed?
Sent from my m8wl using Tapatalk
Click to expand...
Click to collapse
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
acejavelin said:
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Got it, thank you, I'll try this as soon as i get home
Sent from my m8wl using Tapatalk
acejavelin said:
Yes... Failure to do so has caused bootloop on the Moto G 2015, another 3rd gen Moto device
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just followed this step by step, the only thing that failed on first try was the modem, second attempt flashed okay. After sending the "fastboot reboot" command, I get the unlocked bootloader message for a few seconds, the stock blue Moto M for about 10 seconds, and then the screen remains on but blank (black). Its been sitting there for a few minutes and nothing is happening..
Edit: Fastboot is now showing "Not found" under baseband instead of "Not available", as it had been previously.
DonKilluminati23 said:
Just followed this step by step, the only thing that failed on first try was the modem, second attempt flashed okay. After sending the "fastboot reboot" command, I get the unlocked bootloader message for a few seconds, the stock blue Moto M for about 10 seconds, and then the screen remains on but blank (black). Its been sitting there for a few minutes and nothing is happening..
Click to expand...
Click to collapse
Give it at least 20-25 minutes without touching it... too early to make a call yet.
acejavelin said:
Give it at least 20-25 minutes without touching it... too early to make a call yet.
Click to expand...
Click to collapse
After a few more minutes it returned to the unlocked bootloader message and is now back to cycling back and forth between that screen and the blue M..
DonKilluminati23 said:
After a few more minutes it returned to the unlocked bootloader message and is now back to cycling back and forth between that screen and the blue M..
Click to expand...
Click to collapse
Hmm... I am at a loss for what to do then. Sorry.
Sent from my XT1575 using Tapatalk
acejavelin said:
Hmm... I am at a loss for what to do then. Sorry.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
So I decided to try again from scratch, this time its actually staying on the boot screen (the blue M) and has been sitting just like that for almost 30 minutes? WTF. All I can think to do at this point (after letting it set there for another 30 minutes) is letting the phone charge for a few hours to guarantee low battery isnt an issue.
Regardless, I really appreciate your help!! At this point Im hoping I can send it to Motorola to see if they can successfully flash factory software.
DonKilluminati23 said:
So I decided to try again from scratch, this time its actually staying on the boot screen (the blue M) and has been sitting just like that for almost 30 minutes? WTF. All I can think to do at this point (after letting it set there for another 30 minutes) is letting the phone charge for a few hours to guarantee low battery isnt an issue.
Regardless, I really appreciate your help!! At this point Im hoping I can send it to Motorola to see if they can successfully flash factory software.
Click to expand...
Click to collapse
i have the same problem like you
my base band in fastboot says NOT FOUND
even after flashing stock and cutom rom my phone con not recognize simcard signal.
did you solve your problem?
if yes, how?
ehsan_991 said:
i have the same problem like you
my base band in fastboot says NOT FOUND
even after flashing stock and cutom rom my phone con not recognize simcard signal.
did you solve your problem?
if yes, how?
Click to expand...
Click to collapse
I sent it to Motorola to have it "repaired". Basically they just reflashed stock software. I was not under warranty, but they fixed it for free so i didn't bother trying to fix it over and over.
Sent from my XT1575 using Tapatalk
So i was recording a video, when it entered a state where I had to reboot the phone. I did so, and it got stuck. I did a hard reset. The phone then gets stuck at bootloader unlocked. I entered fastboot, selected recovery, and it gets stuck at the twrp logo. Any ideas? I also re-flashed twrp and it still get stuck.
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
acejavelin said:
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
Click to expand...
Click to collapse
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
thebaconbox said:
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
Click to expand...
Click to collapse
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
acejavelin said:
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
Click to expand...
Click to collapse
How do I do that?
thebaconbox said:
How do I do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
acejavelin said:
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
thebaconbox said:
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
Click to expand...
Click to collapse
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
acejavelin said:
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
Click to expand...
Click to collapse
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
thebaconbox said:
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
Click to expand...
Click to collapse
Yes
acejavelin said:
Yes
Click to expand...
Click to collapse
Alright, I flashed everything and my cell service now works flawlessly.
thebaconbox said:
Alright, I flashed everything and my cell service now works flawlessly.
Click to expand...
Click to collapse
Awesome!
hy,
my purenexus rom was running perfectly but today i was installing spotify and it hanged and then i had to retsart but now it stucks on bootloader warning screen .recvory also stucks on twrp logo . now what should i do .i googled and found this thread.please guide me which thread do i need to follow ..will my bootloader get locked again ? where do i have to start it from? i also have nandroid backup of previous custom rom which is truepure rom. please guide me.
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
dzidexx said:
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
Click to expand...
Click to collapse
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
azzammalik said:
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
Click to expand...
Click to collapse
Only with twrp you can save your data.
What version did you used? Try with another, maybe don't flash - only boot.
"fastboot boot NameOfTwrp.img"
If it boot copy your data to pc.
Stock you can flash with fastboot, here is "how to", download and flash the highest version for you model:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Read carefully, don't lock bootloader.