Database Develop

[Q] Phone stuck in red M

Hi guys! For the last days my phone had been giving some errors (usually the Maps application failing), that I didn't pay attention to.
Today when I woke up I tried using my phone and all applications were failing, so I just tried to turn it off and on, but it never went on again! It is just stuck in the red M.
My phone is fully stock and has Jelly Bean, I have never flashed it before or anything.
So I read some guides about flashing, and I tried doing it with RSD Lite but got the error : "no remval message notification" (screenshot attached)
Do you know what may be happening? Is there some chance for "bringing it back"?
Thanks!

I also tried unlocking it to no success:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.550s

[Q] Bricked Nexus 6 ?

So My nexus 6 decided not to turn on anymore after plugging into the charger last night. Pressing on the power button for hours it would only power on once and then stay stuck on this message across the screen "ap fastboot flash mode (secure)" in red. After about a minute it proceeded to the bootloader which looks like its been messed up, on the top right where you would see the options "recover", "restart", etc the word appears without any of the coloring behind it.. I've tried to boot to recovery (using TWARP) but it just restarts and goes right back to the same screen with the same message. If I attempt to shut off the phone it won't turn back on for another several hours of pressing the power button. I know it charges because I've seen the battery icon when off and it was full, I've also tried different outlets and chargers and tried those outlets and chargers on my Nexus 7 in which it works fine. I've also tried a wireless charger as well to completely rule out it being a charging issue.
I managed to get it back on again and decided to plug it into my PC. I was able to detect it with fastboot devices and then proceeded to completely restore to factory setting using the stock google images assuming the bootloader could be damaged. When I ran the command to flash the updated bootloader it failed. Then again the bootloader was on the screen in which it looked distorted
:~/Android/Nexus 6/shamu-lrx22c$ fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing 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) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.104s
~/Android/Nexus 6/shamu-lrx22c$ fastboot devices
ZX1G222NKR fastboot
~/Android/Nexus 6/shamu-lrx22c$ fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing 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) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.105s
:~/Android/Nexus 6/shamu-lrx22c$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
This is where I am at now. What I've noticed is that at one point I was able to boot directly into the bootloader using power and volume down and in that the bootloader seems normal. But as of now I am unable to do that.
My next step is to get the phone on again and try to manually boot into bootloader and attempt to flash again.
Any ideas or suggestions or questions?

I hope I'm not speaking out of my butt here... I do remember reading on here that you were actually able to boot the device using the boot image on the pc without actually flashing it. If I read that right, and if I remember correctly, it was fastboot boot.img instead of fastboot flash boot.img.
Hope this helps.

Larzzzz82 said:
I hope I'm not speaking out of my butt here... I do remember reading on here that you were actually able to boot the device using the boot image on the pc without actually flashing it. If I read that right, and if I remember correctly, it was fastboot boot.img instead of fastboot flash boot.img.
Hope this helps.
Click to expand...
Click to collapse
Sounds like something to try but my phone won't power on at all. So I can't even attempt this. I was thinking could the bootloader be damaged? would that cause the phone not to power on?

No clue.

stock or rooted..decrypted..
Fiftysilver said:
Sounds like something to try but my phone won't power on at all. So I can't even attempt this. I was thinking could the bootloader be damaged? would that cause the phone not to power on?
Click to expand...
Click to collapse
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.

as was mentioned you can try and boot recovery from RAM basically via the pc, but the device needs to be in fastboot mode first
the command would be fastboot boot recovery_image_name.img
That reboots device with the recovery loaded into RAM. I only tried it with TWRP but assume Stock would do the same....
Another thing to check maybe the fastboot executable as well, I had to update to latest SDK

paztine said:
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
Click to expand...
Click to collapse
The only thing I did with my phone was root it on stock and unlock the bootloader. I was on 5.0.1.

paztine said:
Whats the status of your phone before you got into this mess..Are you on stock or custom rom? Most phone doesnt go off like yours unless its an hardware issue.
Click to expand...
Click to collapse
I'm going to go with it being a hardware issue because now it won't turn on at all anymore. But what I want to figure out is how did it come to that point. I'm thinking a power surge or a defect in the turbo charger. TBH I never trusted that Motorola turbo charger, something about pumping a lot of juice into my phone to charge it quicker screams potential short circuit.
But hopefully I can get the phone replaced via my warranty.. But my bootloader was unlocked so I don't know how well that would go.. But then again the phone can't turn on.

I need advanced help: Problem with XT1068 bootloader. Read in detail the problem pls.

Thanks for your time trying to help me, I REALLY appreciate that​Well, before telling you the problem, here is my device info:
- Moto G 2nd GEN XT1068
- I was in Android 5.0.2 Stock
- Bootloader version 48.83(*)
- CID: 0x000C​The problem: A few days ago, with no reason (haven´t modified NOTHING at all), I turned on my device but it booted in bootloader mode... strange... so I just selected 'Normal powerup', after some seconds in the boot logo, it return to bootloader mode... always!.
Anyway, I siad: I just have to restore my firmware. Problem > I had not unlocked my device´s bootloader. Ok, I am just going to unlock (the same way as always) but, sometimes, when I enter this command mfastboot oem get_unlock_data I get this:
Code:
C:\Users\SebastianD\Desktop>mfastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 5.008s
After many attempts I got my unlock data, then I did what I had to do: I went to Motorola Unlocking Website, entered my string, the code was sent to my e-mail (I did it with 2 e-mail accounts and got the same code), BUT! when I use the command mfastboot oem unlock UNIQUE_KEY I get, ALWAYS, this:
Code:
C:\Users\SebastianD\Desktop>mfastboot oem unlock [my_unlock_code]
...
(bootloader) Unlock code = [my_unlock_code]
(bootloader) unlock data invalid!
FAILED (remote failure)
finished. total time: 9.984s
I talked to Motorola service, but they say they do not have support for this because of their terms and stuff about the bootloader unlocking.
If you are more comfortable with spanish, here you can help me: LINK: Spanish Thread
This is freaking me out! I need help!​

Reserved: To post the solution... if I get a solution.

Reserved: Just in case to provide more information to solve the problem.

Wrong sub forum
Sent from my Moto G 2014 using Tapatalk

Vidhanth said:
Wrong sub forum
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
+1 
 @sebastiandg7 http://forum.xda-developers.com/moto-g-2014/help

I'm even friends with problem XT1068, does not generate the code to unlock only fault as shown below: Unit turns on shortly after return to the screen in AP Fastboot Flash
D:\android-sdk\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 5.027s

I don't know why you have 'm' in front of 'fastboot oem get_unlock_data', anyway the instructions on this page are what I followed.
http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728

XT-1063 Flashing errors

Hi guys! Its my first time posting a problem, i usually manage to fix it by reading and looking for info, but this time im really stuck
My cousins phone turned off one day and it never booted right again, got stuck in Moto logo... He tried to fix it (Not sure what he did, but my guess is that he somehow deleted a partition or someting), and now, it wont flash anything, just keep getting this error in every line:
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Click to expand...
Click to collapse
I was able to unlock the bootloader (Device is UNLOCKED. Status: 3) but still cant flash anything, i tried almost every single post i could find in the web but no luck at all...
It boot directly into fastboot mode and when i press the power up button the logo image was replaced by this http://imgur.com/JH4CAq1
Bootloader version is 48.86 and when connected to the PC it is recognized as "Fastboot Titan S"
If anyone can help me i'll be really greatful!
Thanks for reading and sorry for my pooooor englando :laugh:

Can't properly re lock bootloader

Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?

Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10

Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com