Database Develop

[notice] please read!!!

They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.

I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?

U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk

Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.

rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
I've heard it called a "sponge" I like that lol

shard111 said:
I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?
Click to expand...
Click to collapse
coldconfession13 said:
U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
i flashed each file separately yes no errors when flashing everything went through okay but still wont pass google screen

If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk

coldconfession13 said:
If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no.
but after flashing the factory img, you might have to wipe data for it to boot.

jeromechrome1 said:
They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
Click to expand...
Click to collapse
NONE of this suggests that your phone is a brick. In fact, it all proves that it is NOT a brick.
*which is not to say that it isn't BROKEN.
"i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C"
Let me ask you this; did it reboot when you booted into a custom recovery? If custom recovery worked, then it seems like the unit can still be saved.
BTW: LRX22C is also 5.0. Specifically, 5.0.1. 5.1 is not available yet.
So a little bit of clarifications first;
HAVE you tried to perform a factory wipe (via recovery) or otherwise FORMAT (not "fastboot erase") the data and cache partitions? No part of your message mentions formatting the data or cache partitions. If the init is unable to manipulate/mount a possibly corrupt data or cache partition (or possibly some other partitions as well), then it WILL REBOOT.
In addition, some logs of the reboot could be useful if you are able to obtain any. A somewhat modified boot image can enable adb and kernel logging at a point from before the reboot occurs.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I don't think you need a new mainboard.
If what he explained to you is correct, then my previous about fixing corrupt data partitions should solve the issue for you.

Agree with the guy above me. Same thing happened to me on my Nexus 9. Manual flashes all successful but could not boot. Booted into recovery and did a factory wipe and all was well. I know this is the nexus 6, but it sounds like corrupted data.

Soft-Bricked Moto G (2014) won't move beyond Fastboot

Hey guys!
So I've got an issue I'm struggling with on the Moto G (2014). First I'll tell you as much as I can about the phone: I bought it from the Motorola website, so I think it's running whatever the stock firmware is. Also, it's the 8 GB US model and isn't tied to any carrier. (I have it on T-Mobile, but got it directly from Motorola. I was trying to figure out what the firmware is but the closest I've been able to get is by running the Motorola Device Manager app while the phone is in fastboot mode. It says there are no available updates for: 21.11.17.titan_retuaws.retuaws.en.us The bootloader is locked and the phone is not rooted. It's pure stock, though it might have automatically gotten an OTA update to the latest official release, I can't be sure because I bought it for someone else.
Okay, so the problem. I'd bought the phone for my dad and set it up and it worked fine for about two months. Yesterday, he came by my place and asked if I could take a look at it because it was stuck on one screen and since there was no removable battery, he didn't know how to reset it. The screen it was stuck on is the boot screen where the Motorola logo is supposed to come up. It was up, but the bottom half of the logo was stretched to the side and pixelated so my first reaction was "crap, he hit it against something and there's damage to the screen." But there was no visible damage to the screen anywhere (neither from a hard hit or from pressure) and he's got the flip case for it and he said it hadn't been hit or anything.
I tried to power it down by holding down the power button, but as soon as it went off, it tried to start up again. A bootloop that always froze on that messed up Motorola boot screen. I set it on the charger for a bit and let it run through the loop a few times and at one point it got as far as the "world" screen where it shows a cartoon planet. This extended down past where the weird stretch happened on the motorola graphic and it was perfectly clear so I realized there was no damage to the screen, just some sort of boot error.
So then I tried booting into fastboot (hold both volume buttons down along with the power button for a few seconds, release) and I was able to get into fastboot. I tried scrolling down to recovery and then hitting the volume up key to select it but the second I hit the volume up key (the selection key in this mode) it reboots the phone. It doesn't go into the recovery screen, just turns off the phone. I tried this for the "Factory" (reset) option, for the "Normal Powerup" option, and the others. Instead of getting anything different, selecting any of them turns the phone off and nothing happens. The computer is recognizing that there's a device connected to it when I have the phone plugged in via usb in fastboot to my Windows 8 laptop. It also appears that I can enter commands in fastboot. (Though I'm not sure what to put in to fix this so I'm turning to you guys.)
So I can't figure out what's wrong. I've got some experience in flashing roms, both manually and with some of the tools, but haven't had to deal with what I'm assuming is a soft brick before.
Can anyone offer any help?
Thanks very much.

Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4

Roldorf said:
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Click to expand...
Click to collapse
Unfortunately that didn't work. I was able to click the "restore to factory" part and it seemed to do that but I tried it again with the "wipe cache partition" and it just reset. I tried to restart normally and nothing happened. I will start boot and go to the Motorola logo but will always fail there, no matter what I try.

I'm still stuck with the soft-bricked phone. Any help going from Fastboot to somehow getting it to work?
(As I stated in the OP, the recovery options don't work. It seems only the Fastboot area is working.)

try to reflash the rom via fastboot, using the commands on 4.2 on this thread
if you have fastboot working they must work and re-flash the stock rom and everything back to stock...
to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download, very slow download, unzip, to the some folder of mfastboot and give the commands a try... :good:

This is how to solve *ANY* softbrick on the Moto G 2014 (2nd Gen Moto G)
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:

eyhajee said:
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
Click to expand...
Click to collapse
hello eyhajee.
My Moto G 2014 xt1068, running on Android 5.0.2 has some softbrick issue.
I have unlocked its bootloader, rooted it, unrooted it and while I was trying to lock its bootoader, I forgot to enable USB debugging and now it's stuck on fastboot mode.
So I wanna ask that can flashing a custom ROM turn my phone on??

I think so. If you are able to run some basic commands you should be able to flash it to emergency mode.

NEED HELP - Android gone black

Moto X 2014: unrooted with bootloader unlocked. It's running Stock 5.1 and I haven't messed with anything on it. I gave it to my Dad after a few months of using it, so I factory reset it and gave it to him, 2 weeks later he tells me it has stopped working. It boots up normally, but from then on it is black, I can access minor parts of the OS such as the power off menu, the camera (by shaking) and Moto Display, but everything else doesn't work. I have never seen anything like this before, and I am well accustomed to flashing custom ROMs and rooting Android. If it comes down to it I will factory reset it or flash stock, but I can't even plug it into my PC and retrieve any files. Anyone have any idea whats gone wrong?
I have attached a video demonstrating what's happened to help diagnose the problem.

thomaswilloughby said:
Moto X 2014: unrooted with bootloader unlocked. It's running Stock 5.1 and I haven't messed with anything on it. I gave it to my Dad after a few months of using it, so I factory reset it and gave it to him, 2 weeks later he tells me it has stopped working. It boots up normally, but from then on it is black, I can access minor parts of the OS such as the power off menu, the camera (by shaking) and Moto Display, but everything else doesn't work. I have never seen anything like this before, and I am well accustomed to flashing custom ROMs and rooting Android. If it comes down to it I will factory reset it or flash stock, but I can't even plug it into my PC and retrieve any files. Anyone have any idea whats gone wrong?
I have attached a video demonstrating what's happened to help diagnose the problem.
Click to expand...
Click to collapse
If you search the forum here for "black screen" it has happened to other people as well on stock 5.1. Supposedly the fix is a factory reset.
Sent from my XT1095 using Tapatalk

AGISCI said:
If you search the forum here for "black screen" it has happened to other people as well on stock 5.1. Supposedly the fix is a factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok, It was just really surprising thats all. I will factory reset then. Thanks

I am having the exact same issue. Have you had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a few people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?

bjg222 said:
I am having the exact same issue. Have you had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a few people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
Click to expand...
Click to collapse
Unfortunately I couldn't retreive any data from the phone, I can confirm however that a factory reset does fix the issue. The Android automatic backup does work in the broken state so I did manage to restore my settings and apps. But the internal sd card was wiped upon factory reseting. Just an idea of the top of my head: Try running adb backup and see if that works, and then unlocking the bootloader, flashing twrp, restoring the backup, and finally transfering the internal sd card data to a mounted drive using twrp. Thats just a stab in the dark and i dont have the phone on me to test it. Give it a try and lets hope Motorola will fix this bug soon.

Ok, thanks. I did try adb backup, but adb won't recognize the device when it's "booted" & sitting at the blank screen, and the stock recovery doesn't give full adb access. I'm currently looking into the various data recovery options to maybe pull some stuff off after reseting. It's really only a few files that I need, so maybe that will work?

bjg222 said:
Ok, thanks. I did try adb backup, but adb won't recognize the device when it's "booted" & sitting at the blank screen, and the stock recovery doesn't give full adb access. I'm currently looking into the various data recovery options to maybe pull some stuff off after reseting. It's really only a few files that I need, so maybe that will work?
Click to expand...
Click to collapse
Unfortunately the internal SD card mounts using MTP and not like a flash drive, so using the usual methods through Windows to recover wont work. However you could try and restore your internal sd card using this solution: http://goo.gl/OKdV14
As for accessing adb through recovery, you could try this method: http://goo.gl/5T7bhq
Hopefully one of these methods should work, so you can at least recover some of your files.

I had the same problem today. I tried to backup a twrp backup I have made few weeks ago but I still had the black screen. The only solution is to factory reset...
Happily I could have saved my data when I was on TWRP. Anyone knows how to restore sms from the data I have saved ?

Trying To Recover Data After XT1096 5.1 Black Screen Bug

Trying to recover data after XT1096 5.1 black screen bug
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.

rushramia said:
So I encountered this bug about 2 days ago. It's basically a bug that results in an un-responsive black screen for no apparent reason. I tried all the standard support protocols to save my data (i.e. copy files to pc via USB, and using Cellebrite to pull them off) but without MTP or USB Debugging enabled none of these options worked. Both Verizon and Motorolla tech support advised me to factory reset my phone. However being that a reset will wipe all my data, I've refused to go down that path (yet). So after doing some of my own research I came up with the following ideas, which so far have not been successful.
Idea 1 - use adb to sideload an OTA update with a fresh image that will hopefully resolve the black screen bug but not wipe my data. I followed this thread with partial luck. I got about 47% through the sideload process before it crashed complaining about an invalid full image check
Idea 2 - use fastboot to flash all the images except user data (again with the hopes of resolving the black screen bug without losing data) - But I can't seem to find a compatible set of stock images that will play nicely with my unrooted and locked bootloader phone.
Idea 3 - root my phone, load a custom rom (with no black screen bug) and preserve my user data - unfortunately mofo doesn't support an XT1096 root since I've already accepted the 5.1 OTA.
So my question are:
1 - Are there a set of verizon stock digitally signed images anywhere out there that will work with my XT1096 with 5.1 already installed?
if not
2 - Is there any way to root my phone or unlock the bootloader so that I can accept non-factory images without the use of Mofo?
Any help with this is greatly appreciated.
Click to expand...
Click to collapse
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.

I'm in the same boat except I'm on vacation with out my computer. Can I factory reset from fastboot?

Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk

AGISCI said:
1) Yes there are stock signed images for the xt1096. They won't fix your problem. The problem is the data partition is corrupt. Flashing a stock image does not change nor fix the data partition, so it won't help.
2) No, there is no other way.
I am sorry to say, but there is only one solution, which is factory reset. The reason factory reset works is because it will erase the corrupted data partition. Sorry, but you will lose your data, there is no way to recover now. Since you have 5.1 installed, it is also impossible to use mofo and sunshine, so no root and no bootloader unlock neither.
Click to expand...
Click to collapse
Thanks Chris,
I appreciate the response. Do you know where I might find the stock signed images for xt1096? I've somehow hosed my system img so now I can't even get into recovery to do a factory reset (keeps complaining 'failed to validate system image'). I'm hoping to re-flash the stock system.img to fix this problem. Let me know.
Thanks!

Sure here it is:
download
Sent from my XT1095 using Tapatalk

AGISCI said:
Sure here it is:
Click to expand...
Click to collapse
Thanks!
That got me back to where I started. System is no longer 'invalid' and my phone boots up to a black screen. The notifications still work and I can boot into fastboot or recovery modes. I guess my only option now is to bite the bullet and factory reset now (and loose my data). :crying:
Thanks again for all your help!

AGISCI said:
Yes you can. Once you are in fastboot select recovery. Once you are in recovery and see the dead android press power and volume down to open the menu, then select factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
weird. I go into fastboot and got the options: normal boot, recovery, factory and some others and i can cycle through with vol down. vol up is select but no matter what i select it just boots normally (still have black screen)
do i need to unlock something?

I need some more info. Are you on stock rom? What version(4.4.4, 5.0, or 5.1)? Have you unlocked your bootloader with sunshine? Have you rooted woth mofo or kingroot?
Sent from my XT1095 using Tapatalk

Moto X (2013) XT 1058 soft brick (?) [HELP]

Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.

You don't downgrade Motorola phones!
Sent from my iPad using Tapatalk

Is your device fixed now?
mlspot said:
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
Click to expand...
Click to collapse