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
Related
So im stuck with my nexus with no OS... after flashing pure shamu it booted to just a password box... I input my password and it said i had corrupt data. I hit reset... wiped phone... all files GONE... Now what do i do. I cant mount to put recovery on.... I cant do anyting with this phoen right now... anyone had this happen... If so what steps to remedy?
Sounds like you need to try and fastboot the original google files, nuke and repave....
flash the stock img then start again
Flashing stock as we speak... was hoping another optino.... but after years of doing this I kinda know better... live and learn
hell
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
asphalte7 said:
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
Click to expand...
Click to collapse
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Evolution_Freak said:
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
asphalte7 said:
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
Click to expand...
Click to collapse
Should be able to boot twrp now.
but i have to unlock first ... my device is locked
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
you cant unlock it without booting up and enabling allow oem unlocking in the developer options
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
If you can boot to TWRP recovery, then you can ADB push a ROM to recovery and boot it.
Edit: Sorry, I missed the fact that TWRP had been deleted too.
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Evolution_Freak said:
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Click to expand...
Click to collapse
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
Or, if you are still in fastboot, issue this command > fastboot reboot recovery
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
asphalte7 said:
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
Click to expand...
Click to collapse
Then I'm afraid you may be stuck. A RMA may be in your future if no one else can offer a solution.
simms22 said:
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
Click to expand...
Click to collapse
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
asphalte7 said:
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
Click to expand...
Click to collapse
flashing twrp..
fastboot flash recovery recoveryname.img
and flashing a factory img is done while the phone is in its bootloader. there are instruction how here on xda. but to be honest, i dont know if that will work. where did you buy your n6 from btw?
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!)
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
Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp
erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Yepi69 said:
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Click to expand...
Click to collapse
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
NotCat_ said:
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
Click to expand...
Click to collapse
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Njaiker said:
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Click to expand...
Click to collapse
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
NotCat_ said:
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
Click to expand...
Click to collapse
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Yepi69 said:
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Click to expand...
Click to collapse
will try to do that. all tho i think screen goes off first thanks for your help and sparking some hope into me and my phone <3
It finally booted up! After having some hard time shorting test points i finally did and it booted up just fine! Big thanks to @Yepi69
use custom rom
NotCat_ said:
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
Click to expand...
Click to collapse
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
honey ghumaan01 said:
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
Click to expand...
Click to collapse
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
try other slot
NotCat_ said:
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
Click to expand...
Click to collapse
try on both slots
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
Whats the fastboot command to change slots?
Mtp works fine tho.
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
the command to chang slot with fastboot is
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b not sure can be fastboot set-actve a/b , you should use pitch black recovery instead of simple twrp
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
dm me on instagram hsghumaan01
honey ghumaan01 said:
fastboot set_active a/b
Click to expand...
Click to collapse
That command doesn't seem to work on my pc :/ cmd just gives out all commands when i type
fastboot set_active B (on pc)
And nothing happens :/
Are there any particular adb/fastboot files i need to download?
MarcusMario0605 said:
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
Click to expand...
Click to collapse
Took a screenshot of your comment for later, thanks!
Are there any particular adb/fastboot files i need to download?[/QUOTE]
use this tool; https://mega.nz/#!cr4SUIqY!Rzlftk2OFun8XIkNQb2aXRtP7-t3f4DB92vMIl90pgw
(this tool,can disable driver signature,Install all drivers,qcom,etc)
https://forum.xda-developers.com/showthread.php?t=2588979
Download SDK Platform-Tools for Windows ; https://developer.android.com/studio/releases/platform-tools
QDLoader HS-USB Driver ; https://mega.nz/#!EqJwTIzB!KJF3CldYq_u7KylaL0iO6rs05RWs2_dcUfaENjJcDpU
fastboot edl (useful) ; https://mega.nz/#!x6BkXY5A!hx8SXoBwd4-fW1UkZ1poHc7p-MFDaQ85FYH7Yk8bLZ8
See and here how to use adb & fastboot from any directory on pc ; https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
all of these are useful tools,that you must to have on pc
sry for english
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
I already flashed the phone with edl test points. I'm running havoc os +hex
daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
Why not use oem unlock?