I have an unlocked Motorola moto g2, with unlocked bootloader, TWRP installed and rooted stock Android Kitkat.
The battery went completely flat while I was on a road trip, and when I tried to charge it up, it just slows the unlocked bootloader screen, vibrates and then reboots.
I can enter the initial recovery selection screen, but if I select recovery to run TWRP it also just hangs on the splash screen
I've read that the problem could be the battery is too flat, so I took the phone to pieces, and detached the battery connector, and charged the battery to 4.2 V using a regulated external supply.
However, it still doesnt work with a fully charged battery, TWRP still hangs.
I can access the device via fastboot, and tried to reflash the latest version of TWRP, but it didnt seem to help and I'm not even sure if fastboot actually uploaded the latest TWRP as the splash screen, where it hangs, didn't seem to change.
I do not really want to have to completely clear the rom, as I'd loose a load of photos from the road trip, but I've run out of ideas on how to recover the phone.
BTW. It doesnt run up enough to give me adb access.
Can anyone suggest anything else I can try.
RogerClark said:
I have an unlocked Motorola moto g2, with unlocked bootloader, TWRP installed and rooted stock Android Kitkat.
The battery went completely flat while I was on a road trip, and when I tried to charge it up, it just slows the unlocked bootloader screen, vibrates and then reboots.
I can enter the initial recovery selection screen, but if I select recovery to run TWRP it also just hangs on the splash screen
I've read that the problem could be the battery is too flat, so I took the phone to pieces, and detached the battery connector, and charged the battery to 4.2 V using a regulated external supply.
However, it still doesnt work with a fully charged battery, TWRP still hangs.
I can access the device via fastboot, and tried to reflash the latest version of TWRP, but it didnt seem to help and I'm not even sure if fastboot actually uploaded the latest TWRP as the splash screen, where it hangs, didn't seem to change.
I do not really want to have to completely clear the rom, as I'd loose a load of photos from the road trip, but I've run out of ideas on how to recover the phone.
BTW. It doesnt run up enough to give me adb access.
Can anyone suggest anything else I can try.
Click to expand...
Click to collapse
It sounds to me like you either wiped out the OS somehow or you lost recovery.
Try flashing the latest version of TWRP for your specific model number, then boot to TWRP and wipe only the cache and Dalvik/ART cache, do not factory reset and then try rebooting.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It sounds to me like you either wiped out the OS somehow or you lost recovery.
Try flashing the latest version of TWRP for your specific model number, then boot to TWRP and wipe only the cache and Dalvik/ART cache, do not factory reset and then try rebooting.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thanks for the reply
I did try reflashing TWRP using fastboot, but TWRP seems to hang on the splash screen.
But I'm not convinced that fastboot actually installed the new version of TWRP I was trying to flash, as I tried flashing TWRP 3.0.2 , and the splash screen that I see looks like an older version.
So I'll try reflashing TWRP again.
Droidriven said:
It sounds to me like you either wiped out the OS somehow or you lost recovery.
Try flashing the latest version of TWRP for your specific model number, then boot to TWRP and wipe only the cache and Dalvik/ART cache, do not factory reset and then try rebooting.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I reflashed the latest TWRP onto the phone (moto g2 XT1068) using fastboot, and now when I enter recovery I see the latest TRWP splash, for the version I just flashed, (3.1.0.0) however TWRP still hangs on the splash screen
RogerClark said:
I reflashed the latest TWRP onto the phone (moto g2 XT1068) using fastboot, and now when I enter recovery I see the latest TRWP splash, for the version I just flashed, (3.1.0.0) however TWRP still hangs on the splash screen
Click to expand...
Click to collapse
Hmm....seems you might have to fastboot flash the boot.img or system.img from whatever you had when this happened.
Droidriven said:
Hmm....seems you might have to fastboot flash the boot.img or system.img from whatever you had when this happened.
Click to expand...
Click to collapse
Umm.
I can't find the TWRP files backup, but there appear to be plenty of original Kitkat stock roms posted to this forum, so I may as well try using boot.img etc from one of them.
RogerClark said:
Umm.
I can't find the TWRP files backup, but there appear to be plenty of original Kitkat stock roms posted to this forum, so I may as well try using boot.img etc from one of them.
Click to expand...
Click to collapse
Not sure that will work. I suggest doing some searching first.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SOLVED - ALTERNATIVE] Moto G2 bricked - boot loop
I found a boot.img for the phone (XT1068) and tried flashing, but it didn't help
So I then tried flashing the entire stock ROM (using fastboot), but it didn't make any difference.
So I erased all the partitions and reflashed the stock ROM again, and initially I got the broken Android robot screen, but I rebooted it and amazingly Android fired up as if it was a brand new device
I have of course lost all the user data, photos, texts etc, but at least the phone is working again.
In case anyone else has the same problem, I'd probably recommend just trying to erase the cache and try booting and if that failed, try erasing the userdata, as I think the issue was possibly data corruption in one of both of these
I was lucky to find a ROM
http://download1400.mediafire.com/2...L++RETAIL+KXB21.85-14+EARLIEST-by-Reefuge.zip
As most of the links I found to ROMs were old and broken or files had been removed or deleted from the servers
Now that the phone is back with a locked bootloader it is actually updating to Android 5, and I think there is even an official version of Marshmallow for the Moto G2
Anyway, thanks again.... Its a shame I couldn't get my data back, but at least I have the phone working again.
Edit.
In case anyone wants a list of the fastboot commands I used... Here they are..
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe oem lock
mfastboot.exe reboot
Related
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
AbstractXart said:
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
Click to expand...
Click to collapse
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
patspdaphone said:
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
Click to expand...
Click to collapse
So to accept the OTA, did you go through the bootloader/recovery and flash it, or were you able to turn on your phone and accept it? Sorry I don't have his phone on me right now otherwise I would have done it .
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
KidJoe said:
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
Click to expand...
Click to collapse
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
AbstractXart said:
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
Click to expand...
Click to collapse
until the next time the OTA downloads and tries to install
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
KidJoe said:
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
Click to expand...
Click to collapse
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
samwathegreat said:
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Click to expand...
Click to collapse
any ideas?
I just checked device manager and it shows "ADB Interface" and then MOT Single ADB Interface.
But its not showing up under devices when running command "ADB Devices" in CMD
Globalrebel said:
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
any ideas?
Click to expand...
Click to collapse
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
samwathegreat said:
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
Click to expand...
Click to collapse
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Globalrebel said:
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Click to expand...
Click to collapse
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
samwathegreat said:
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
Click to expand...
Click to collapse
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
No water damage, and the phone was literally working perfectly fine 15 minutes ago. Just all of a sudden stopped showing the screen
Globalrebel said:
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
Click to expand...
Click to collapse
Bummer. You appear to have used the correct procedure.
This looks to be a hardware failure :/
Sorry, I don't have any further troubleshooting techniques for you...
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Globalrebel said:
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Click to expand...
Click to collapse
If you unlocked the bootloader they know it. Technically your warranty is void... But they might replace/fix it anyways. Don't mention it and see what happens. Let us know.
I totally forgot I was rooted and had TWRP and I took the OTA update.
Now the phone is in an infinite loop of rebooting.
What do I need to do to remedy this?
Thank you
Same phone, same problem but I was using clockwork mod recovery. You need to flash the stock recovery using Factbook, then the other update will take.
There are some existing threads that will fill you in with the details!
Good luck.
Sent from my Nexus 7 using Tapatalk
There are PLENTY of threads saying you can NOT install the OTA while you have a custom recovery like TWRP or CWM installed. Doing so causes a boot loop. Almost every one of those posts (at least the ones I've made) says if you get into this situation you need to erase your cache to get out of the boot loop
Boot the phone into fastboot/bootloader mode. Then use mfastboot on the PC to erase your cache. Return to stock and try again.
If you are close enough to stock, you can just try to boot the phone into mfastboot mode, flash STOCK recovery, and see if you can install the OTA, or if it will fail (due to varying too much from stock).
this sticky was helpful
MFastboot(Used for manually downgrading to 4.2.2)
MFastboot
For firmware Download pick what firmware you want from the link below... make sure its the one you have. you cannot downgrade
http://sbf.droid-developers.org/phone.php?device=0
reboot to the bootloader
i used only part of the code from the sticky
Code:
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
i was then able to then flash OTA whilst keeping the bootloader unlocked, kept root, kept all my files and settings intact.
Ditto. I just downloaded the pre update firmware and extracted the recovery.IMG file and flashed it with flashify uninstalled xposed framework and boom three reboots and the update is done . reinstall xposed framework and all my settings are still there . VZW Dev edition. Didn't even lose root.
Sent from my XT1060 using Tapatalk
That's how it's done simple and effective.
I did that code line that jadeddjay posted but only did the step through the recovery.img. I then rebooted and it worked perfectly and installed the OTA. I then went back into fastboot and installed TWRP and am rooted again.
just got my brand new developer edition moto x. successfully unlocked the bootloader, successfully installed TWRP recovery, successfully installed SuperSU, rebooted the phone and stupidly tried to update the software through the phone's system software update, got stuck in a reboot loop, and then attempted to flash a ROM. realized i bricked it. now i can't sideload a ROM and every time i try, i reboot to recovery, use the adb sideload, it looks like it's loading, phone says successful, asks if i want to reboot and then tells me that there is no OS.
i am brand new to this, and i've clearly effed it up, but really not sure how to fix it.
i attempted to follow the instructions here http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 but using the step two method but got to fastboot flash partition gpt.bin and got an error in terminal (i'm on a mac)
i would be most grateful for any help at all. i'm really stuck.
thanks in advance.
First... Boot the phone into Fastboot/Bootloader mode.
What is the version listed on the second line?
Next, you'll want to flash the rom that matches that bootloader version using a slight variation of Option 2 on that link... For example, if the bootloader on your phone is 30.B4 then fash the stock 4.4.2 SBF, if 30.B7 flash 4.4.4.
Start the steps with....
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
then use the rest of those commands AS they are written. yes, you'll be repeating the flashing of GPT.Bin and Motoboot.img, and that is intentional!
When you get back to stock, I suggest you take a few minutes/hours to read and familiarize yourself with what has been written.. Like don't take an OTA unless you have the STOCK recovery. If you have a 3rd party recovery and take an OTA you'll be stuck in a boot loop (to get out, boot the phone in fastboot and from the PC.. fastboot erase cache followed by fastboot reboot will stop the loop, then you can flash stock recovery back on there to take the OTA. Never DOWNGRADE the rom on your phone once you have 4.4.2 and up or you will brick, etc.
I recently got a Pure Moto X 2014 and immediately unlocked it. I then tried to root it using the boot image in this thread:
http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264
Apparently that is not the right thing to do for a Lollipop phone, as I found out after booting it (note: I did not flash the boot image, only booted it). The result was it would not boot past the watery 'M' screen.
I've tried to restore using a couple of stock images:
1. the files Motorola shares with you to restore to stock (TMO_21.21.42.victara_tmo)
2. The Lollipop image from graffixnyc (http://www.graffixnyc.com/motox.php) TMO_21.21.42.victara
I'm doing so with the recommended commands using the moto version of fastboot provided with the Motorola download:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
When I do this with the Moto firmware, it boots until the barren fall-like earth picture and then goes black. When I flash the Lollipop image it sticks at the watery 'M'.
I tried installing crdroid ROM, and though I can get to TWRP recovery, it won't install the zip because it "can't install this .package on top of incompatible data."
What can I do? Thanks in advance.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Do that ^
Not sure why you didn't use the official image/ wipe user data & cache, but that'll fix it.
Looks like the step I was missing was wiping data. I formatted data from TWRP and that allowed install of CM based ROM, then I went and restored the Lollipop image including the "erase userdata" command. Everything is happy now.
I knew I'd figure it out as soon as I asked, just didn't want to lose user data. Thanks for trying to help!
Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.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 flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.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 flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi