Database Develop

[Q] Need to unlock bootloader, but borked device

Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?

Few threads about this today. Seems a regular user error. Can't think of a fix right now..

rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.

boot to bootloader, fastboot oem unlock from fastboot command console on computer.

TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.

Have the same problem and try to solve it with Motorola. No luck at the moment.

lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot

simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22

rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.

TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.

rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...

Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.

I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).

You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.

beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???

simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).

I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?

efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...

You're all using the newest fastboot?

flash the factory img
edit.. nevermind, i see ive already said that

HELP PLEASE! Stuck in bootloader, NEXUS 6

Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.

Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.

Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app

Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518

I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking

toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.

sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.

idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.

sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.

toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.

sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?

Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.

idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.

You don't need adb.

sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?

jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked

sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.

rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled

Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6

hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)

Urgent advice needed on Razr i XT890

hi, my phone Razr i XT890 is showing the Red Moto Logo, I tried to factory reset by going into fastboot also but nothing happened, I can find many thread here about the same problem but nothing conclusive could be found in those threads, hence I sent my phone for repairs, the technician hooked it up to a computer and said that most likely it is a software issue and the phone would be ok, after waiting for an hour I was told that the emmc has died and it cannot be replaced and the only solution would be to change the motherboard, since the mother board is not avaible in the market I looked it up on aliexpress and it costs around 70$ where as a new/refurbished phones are listed for 75$, need you guys advice on whether it can be repaired or not and if yes then how. I am a regular user and not an expert like you guys so if you suggest any thing plz do it in detail. FYI its a factory unlocked phone which had jelly bean OS and I never rooted it or did any hanky panky to it. Thanks

What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.

Hazou said:
What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.
Click to expand...
Click to collapse
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.

cooljatt18 said:
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.
Click to expand...
Click to collapse
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?

Hazou said:
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?
Click to expand...
Click to collapse
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !

cooljatt18 said:
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !
Click to expand...
Click to collapse
This is most likely solvable. Try that flash methods a few post above and see what happens s

Hazou said:
This is most likely solvable. Try that flash methods a few post above and see what happens s
Click to expand...
Click to collapse
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it

cooljatt18 said:
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it
Click to expand...
Click to collapse
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk

AGISCI said:
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !

cooljatt18 said:
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !
Click to expand...
Click to collapse
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk

AGISCI said:
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
thanks a ton!!!

hi, guys sorry for posting so late, was super busy, any how haven't got a mechanic to flash the phone, guess I will have to do it myself, request you to answer my queries
.1) a mechanic to whom I went convinced me to believe that the problem was due to a faulty battery and he could fix it in 5 mins flat, He opened the phone did some tinkering with it, I am not sure what but the phone was in same condition ie Red logo on booting. Was very disappointed came back home and I tried to restore it through fast boot and I noticed that the Battery Current was coming as 4.1 V earlier it was 3.7 !!! I am sure that the mechanic messed it up. Now my question is will it harm the phone, battery or any other part?? Should I just leave it the way it is ie 4.1V and not try to rectify it to bring it to 3.7V.
.2) I am not able to get a mechanic who can flash the phone as suggested in previous posts, pl tell how I can do it myself, I am a newbie at this and have zero knowledge of the process, pl tell what all software are needed! And hardware if any. All I have got currently is the firmware posted in previous posts.
Thanks

Moto G 4G (uk model) Stuck on wallpaper

Hey Guys, i'm really struggling to find a solution to this as every time i try to google a solution it just comes up with a load of results trying to tell me how to change my wallpaper :/
So basically, overnight, my dad's Moto G 4G started to act strangly. It can still:
Boot up normally
Power Off normally
Vibrates when notifications come through
Rings, all be it temporarily when called and can be answered if connected to the car's bluetooth.
However, it will no longer display any of the UI (other than the Power Off dialogue) and the wallpaper. I can see that the phone isn't completely frozen as the wallpaper in use is a live wallpaper which you can interact with via touch.
When the phone is plugged into my laptop the phone is showing in 'my computer' but it shows no files, same situation in recovery and fastboot too.
I've tried wiping the cache from recovery but it's still the same.
There was one instance where the first time i plugged the phone into the laptop via usb it brought up the whole ui, icons, status bar and all, for like 2 seconds.
Now, back to nothing. Not sure what to do from here. I'm desperately trying not to factory reset it as my grandfather (my dad's dad) passed away recently and i'm pretty sure there are files on here which are now irreplaceable

jhaedee said:
Hey Guys, i'm really struggling to find a solution to this as every time i try to google a solution it just comes up with a load of results trying to tell me how to change my wallpaper :/
So basically, overnight, my dad's Moto G 4G started to act strangly. It can still:
Boot up normally
Power Off normally
Vibrates when notifications come through
Rings, all be it temporarily when called and can be answered if connected to the car's bluetooth.
However, it will no longer display any of the UI (other than the Power Off dialogue) and the wallpaper. I can see that the phone isn't completely frozen as the wallpaper in use is a live wallpaper which you can interact with via touch.
When the phone is plugged into my laptop the phone is showing in 'my computer' but it shows no files, same situation in recovery and fastboot too.
I've tried wiping the cache from recovery but it's still the same.
There was one instance where the first time i plugged the phone into the laptop via usb it brought up the whole ui, icons, status bar and all, for like 2 seconds.
Now, back to nothing. Not sure what to do from here. I'm desperately trying not to factory reset it as my grandfather (my dad's dad) passed away recently and i'm pretty sure there are files on here which are now irreplaceable
Click to expand...
Click to collapse
Ouch, looks like an emmc problem, some partitions may be corrupted.
1st be sure if the usb cable is ok, i have seen many cable going nuts and loosing data but still charging.
If the usb cable is dead you will need a working one anyway to try to recover the phone after you got your data.
Also try apps like airdroid works, you can save everything wirelessy from your pc.
When you have a working cable and still failed to save data you can try to flash a recovery that allow mounting partitions to your pc ( twrp ) whitout booting the os, since for what i understood your android installation got corrupted somewhere and is borked.
Wich model is that one ? should be an XT1072 right ? YOU MUST BE SURE or flashing the wrong stuffs can totaly BRICK your phone.
If it's an XT1072 i have uploaded for you the latest UK stock image to mega.nz so you can dl it quickly
https://mega.nz/#!fId0yD4a!LjyEIjRXse092l7j_JL0Ky324EK6SS4vK4kdqGcS9XY
You will need fastboot + mfastbbotv2 and here they are
https://mega.nz/#!bdEDBDiQ!3KlB6WfUxUep1QR7XSvwpuCuxWnktfCh7YBX020HqmY
Put everything in the same folder ( ex c:\phoner )
open a dos shell whit admin privileges and navigate to that folder, then use this commands and check after every commands if you get back the OK on flashing (you can copy-paste them into the shell)
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata <--- DON'T use this only if you wasn't able to recover your data whit the others methods
mfastboot.exe reboot
The phone should have rebooted, may take longer to boot don't panic, now the phone should be ok and if you didn't wiped the userdata it should be 100% the same as before whit the latest stock fw, my advice is to do a full factory restore to use it, so once you recovered your data do a factory reset from the android menu.
If the phone isn't a 1072 as supposed dl here the correct zip http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC
If you have more questions, especially on flashing twrp/stock just ask before doing anything that could turn the phone into a stone.

Thank you Dr. Nic for your incredibly informative response
Firstly, I was wrong initially, it is actually a XT1039 (first gen 4g) but this does appear to be listed on the file factory page you linked so I should be fine with the instructions.
What I do want to ask though is:
Is there anyway for me to boot twrp without installing it as a temporary basis? I'm sure I've done this before previously on my old moto x but it has been a while. I seem to recall you can type in a fast boot command and get it to boot to twrp. The phone is not rooted or bootloader unlocked (which i know will wipe the phone if I do it so that isn't really a permanent option yet)
Secondly, is there any way for me to find out which stock rom files I need without being able to access the os and looking in settings? I know it is a xt1039 but there are about 5 different, carrier based versions available and I don't want to flash the wrong one.
Thanks again for all your help
If this goes to plan you will have made my father's Christmas special

jhaedee said:
Thank you Dr. Nic for your incredibly informative response
Firstly, I was wrong initially, it is actually a XT1039 (first gen 4g) but this does appear to be listed on the file factory page you linked so I should be fine with the instructions.
What I do want to ask though is:
Is there anyway for me to boot twrp without installing it as a temporary basis? I'm sure I've done this before previously on my old moto x but it has been a while. I seem to recall you can type in a fast boot command and get it to boot to twrp. The phone is not rooted or bootloader unlocked (which i know will wipe the phone if I do it so that isn't really a permanent option yet)
Secondly, is there any way for me to find out which stock rom files I need without being able to access the os and looking in settings? I know it is a xt1039 but there are about 5 different, carrier based versions available and I don't want to flash the wrong one.
Thanks again for all your help
If this goes to plan you will have made my father's Christmas special
Click to expand...
Click to collapse
So 1 thing at time
Probably the others fw you saw was olders versions too or for others regions, i suggest to use the same as you have or the latest
You are completly unable to check your current os installed from phone infos ? have you checked everything on the box ? somewhere there must be some infos, maybe under a barcode sticker.
This should be your latest UK stock, XT1039 aka "peregrine", do you rember if you was on 4.4.4 or 5.1 ? you should flash the same version to improve the % of not loosing something.
Clean Stock 5.1 http://www.filefactory.com/file/dpx...RINE_RETGB_5.1_LPB23.13-17.3_cid7_CFC.xml.zip
So, the cable is ok ? are you able to issue commands whit fastboot ?
If yes unlock the bootloader to install a modded recovery, you will need that to copy your files, and if that fails last try is flashing stock whitout deleteing userdata, but the corruption could be both in /data and /system so after the recovery you will have to do a factory reset anyway.
To boot twrp you have to flash it, don't worry if you want the phone full stock again is the last step you have to do that to fix the corruptions happened, and it's no 100% success rate too since that could happened becouse the emmc is failing

(SOLVED BY REPLACE MOTHER BORD) firmware version

hi,i need this version ale-l21c113b130,i have search on internet but,i can found,any idea????

try here, http://huaweip8lite.blogspot.co.uk/ just use google to translate & scroll down for rom list

gordonyoung53 said:
try here, http://huaweip8lite.blogspot.co.uk/ just use google to translate & scroll down for rom list
Click to expand...
Click to collapse
Thanks for your reply,i will try with version ale-l21v100r001c432b136a,to see if can i unbrick my phone

cristi.blidariu said:
hi,i need this version ale-l21c113b130,i have search on internet but,i can found,any idea????
Click to expand...
Click to collapse
To unbrick your phone the fastest way is to unlock bootloader which takes you 10-15 mins, and fastboot flash any rom. Easy peasy.

pilililo2 said:
To unbrick your phone the fastest way is to unlock bootloader which takes you 10-15 mins, and fastboot flash any rom. Easy peasy.
Click to expand...
Click to collapse
i have bootloader unlock,i have try many firmware to flash via adb,but when i type fastboot reboot only led blink red for 2 sec and then green for 10 sec,after that the phone shutdown,if i try to turn on same thing,led blink red the green,i dont have any clue what is the problem

To flash a firmware you must use Fastboot commands NOT adb. ADB commands are for when android is already booted. First flash boot.img, recovery.img... etc and then reboot your phone. Its should be working or at least booting. You should check out the mega-thread recently posted in the general section. It might help you.

pilililo2 said:
To flash a firmware you must use Fastboot commands NOT adb. ADB commands are for when android is already booted. First flash boot.img, recovery.img... etc and then reboot your phone. Its should be working or at least booting. You should check out the mega-thread recently posted in the general section. It might help you.
Click to expand...
Click to collapse
here what i use
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot(i have try all version based on single sim and dual sim,the same error,when is try to boot the led indicator blink red then green and is shutdown,if i try to turn on same error led indicator blink red then green,the only option that i have is just to putt the phone in fastboot/rescue mod,so i don't know what is the problem )

Wow ive never heard of that :/ Have you tried flashing recovery before cust? Thats what I usually do. And I also use mfastboot instead of fastboot.

pilililo2 said:
Wow ive never heard of that :/ Have you tried flashing recovery before cust? Thats what I usually do. And I also use mfastboot instead of fastboot.
Click to expand...
Click to collapse
is not my phone,and to be honest with you i have upgrade and downgrade my phone(ale-l21c432b170) many times with out problem,but with this one i dont have any idea what is the problem,so this is his history,it was on ale-l21c113b130 single sim and my friend try to make dual sim by flash version b41c>>b46b>>b052,at the end she will end up with balong error,so his restart phone and from there the phone wont boot up,not even in recovery,so what is the problem????

I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry

pilililo2 said:
I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry
Click to expand...
Click to collapse
k,thanks for your reply

pilililo2 said:
I have balong bug in my phone and it doesnt really do anything, just a wrong build.prop but phone works perfectly, im on 565 single sim. Im sorry but a really have no idea on what is happening to your friends phone since ive never had that error. Maybe you could try talking to some more experienced users such as Sokkoban to see if he can help you. Sorry
Click to expand...
Click to collapse
Balong bug -> make sure your 1 on the right location or 2 install the vendor file from your build (vendor MM should do)
cristi.blidariu said:
is not my phone,and to be honest with you i have upgrade and downgrade my phone(ale-l21c432b170) many times with out problem,but with this one i dont have any idea what is the problem,so this is his history,it was on ale-l21c113b130 single sim and my friend try to make dual sim by flash version b41c>>b46b>>b052,at the end she will end up with balong error,so his restart phone and from there the phone wont boot up,not even in recovery,so what is the problem????
Click to expand...
Click to collapse
charge battery. check if bootloader is unlocked correctly ( connect device to pc -> hold volume down while powering up)
open console and type
Code:
fastboot oem get-bootinfo
you should get this
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
if that's the case...
install Twrp 3.0.2
boot into twrp (volume down and volume up while powering on)
wipe everything (dalvik/cache/data/system/internal)
unbrick.
to make everything easier here is a thread.
take those files. it's all prepared (just click once )
also sorry for the noob explaining. you probarly are wellkown with android but it's a custom by now
---------- Post added at 19:19 ---------- Previous post was at 18:59 ----------
btw your problem is that you flashed the custom.img before the recovery it should be in this order.
boot.img
recovery.img
cust.img
system.img

Lordbannakaffalatta said:
Balong bug -> make sure your 1 on the right location or 2 install the vendor file from your build (vendor MM should do)
charge battery. check if bootloader is unlocked correctly ( connect device to pc -> hold volume down while powering up)
open console and type
Code:
fastboot oem get-bootinfo
you should get this
Code:
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
if that's the case...
install Twrp 3.0.2
boot into twrp (volume down and volume up while powering on)
wipe everything (dalvik/cache/data/system/internal)
unbrick.
to make everything easier here is a thread.
take those files. it's all prepared (just click once )
also sorry for the noob explaining. you probarly are wellkown with android but it's a custom by now
---------- Post added at 19:19 ---------- Previous post was at 18:59 ----------
btw your problem is that you flashed the custom.img before the recovery it should be in this order.
boot.img
recovery.img
cust.img
system.img
Click to expand...
Click to collapse
i have try with many firmware(extract files from update.app)but,none was work,every time the same error,I think it might be a problem with the partition,or maybe if i can find someone with version c113b130 and try to flash boot an recovery i will have a chance

cristi.blidariu said:
i have try with many firmware(extract files from update.app)but,none was work,every time the same error,I think it might be a problem with the partition,or maybe if i can find someone with version c113b130 and try to flash boot an recovery i will have a chance
Click to expand...
Click to collapse
it goes the same way.
as i told you try installing twrp first wipe everything and then flash it but do it in the order i gave you.
first boot.img
second recovery.img
third cust.img
fourth system.img
this problem occured before. (cant find the thread anymore) but it should work.
and the way is see it you have nothing to lose at this point so

I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/

pilililo2 said:
I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/
Click to expand...
Click to collapse
K,thanks for the point,it no mater wich order i flash files,the problem is the boot partition wich meen that i am not able to boot in recovery(not even in stock revcovery)i have try to wipe data by using command fastboot -w and press enter but he gave me command not alowed
Sent from my ALE-L21 using XDA-Developers mobile app

pilililo2 said:
I also told him that. Usually when I flash a rom I also flash recovery before custom, but for no reason at all haha didnt know it could cause a bootloop if done cust before recovery :/
Click to expand...
Click to collapse
Yeah i'm not sure eather but they use to hammer this into us that it become an OCD thing for me
and it wwas the only thing i could see what was wrong.
cristi.blidariu said:
K,thanks for the point,it no mater wich order i flash files,the problem is the boot partition wich meen that i am not able to boot in recovery(not even in stock revcovery)i have try to wipe data by using command fastboot -w and press enter but he gave me command not alowed
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
weird that's mostly the case when your bootloader is locked. altough it says PHONE unlocked" it isn't always the case. what do you get when you type
fastboot oem get-bootinfo
could you post it?
rip? http://forum.xda-developers.com/showthread.php?t=2456665
it's with the P6 i know but... those are the same symptones

Lordbannakaffalatta said:
Yeah i'm not sure eather but they use to hammer this into us that it become an OCD thing for me
and it wwas the only thing i could see what was wrong.
weird that's mostly the case when your bootloader is locked. altough it says PHONE unlocked" it isn't always the case. what do you get when you type
fastboot oem get-bootinfo
could you post it?
rip? http://forum.xda-developers.com/showthread.php?t=2456665
it's with the P6 i know but... those are the same symptones
Click to expand...
Click to collapse
i run command fastboot oem get-bootinfo and show bootloader unlock