i got bricked my mi a1
i unbricked via test point after that ohone reboot in wizard
i read flashung persist fix..but i cant do it..phone dont accept that command
so i decide to erase system vua fastboot erase system_a and _b
after that i flash many rom and i only get m i logo and reboot..
i try edl and fastboot method both with same result
any idea how can i unbricked and get it wqorking back again..its new phone
just work for 2 days and 3 turned off lol
please help me to recover
I have the same problem, did you find a solution?
AgustinPatatas said:
I have the same problem, did you find a solution?
Click to expand...
Click to collapse
did you try to get into fastboot mode and use the MiFlash to install a new rom on it? often works
erickxd said:
did you try to get into fastboot mode and use the MiFlash to install a new rom on it? often works
Click to expand...
Click to collapse
I try flash with Mi Flash the last update but the screen of "Android One" is displayed and it is restarted, without being able to enter in the system. It stays in a restart loop.
AgustinPatatas said:
I try flash with Mi Flash the last update but the screen of "Android One" is displayed and it is restarted, without being able to enter in the system. It stays in a restart loop.
Click to expand...
Click to collapse
you don't need enter in the system's phone to do this. just use mi flash on your pc with your phone connected in fastboot mode. search about using MiFlash, it's simple
erickxd said:
you don't need enter in the system's phone to do this. just use mi flash on your pc with your phone connected in fastboot mode. search about using MiFlash, it's simple
Click to expand...
Click to collapse
That's just what I did, what I mean is that when I finish flashing the most recent rom, the phone turns on after finishing the process Mi Flash and the phone starts to restart itself without being able to enter the system and I have to resort to flashing the rom "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" to be able to enter the system again, however does not recognize the sim and if I try to update from the option offered by Android the phone starts to restart itself, same as the aforementioned
Related
please help me friends.....
i have redmi 2 and its model no. is 2014818.i rooted my phone by zip file throug updater app.after installation super su app installed automatically.then i opened super su app and it prompts to select continue with normal recovery or twrp/cwm custom recovery.by mistake selected second option which is twrp/cwm custom recovery.then clicked continue.after that my phone booted and that after stucked at mi logo.
my phone is not going to recovery mode.it is stucked at mi logo.
But it is going into fastboot mode properly.also i flashed latest rom by fastboot method and it shows success result in mi flash tool.but after booting it agian stucked at mi logo.i also tried to flash by command prompt by using adb and fastboot tools.all commands i give gets executed properly but the problem is not solved
i went to Mi service center.he told me that "i will do some software update.after some time he came up and said that the phone is taking much time and stucked at mi logo.
then he assumed and told me that ,there is an issue in motherboard i.e. the motherboard is currputed.
but in my perspective i dont think so, because all the fastboot cammands and functions are woring properly.
please help me in this situation and suggest me that whether it is software issue or hardware, and also about the chances of resuming to life of my phone.
you should try to flash the firmware again but don't forget to select clean_all while flashing from mi flash tool. if your phone doesn't revives then maybe it's hardware issue.
and yes also try to install custom recovery and custom os after flashing firmware maybe your phone gets a new life.
U can't flash stock ROM by fastboot r8?
Have u tried to flash T.W.R.P by fastboot by using mi flash tool(try to use latest version of mi flash too).
And direction is here.If that succed then all is good.
not worked
Bhavesh_khatri said:
you should try to flash the firmware again but don't forget to select clean_all while flashing from mi flash tool. if your phone doesn't revives then maybe it's hardware issue.
and yes also try to install custom recovery and custom os after flashing firmware maybe your phone gets a new life.
Click to expand...
Click to collapse
I have done clean install And everything already.But not Working and now phone is not going into fastboot mode also and also not booting on pressing power button.
On connecting to pc the notification message appears and says "unrecognizable device and device may be malfunctioned".
Done already before writing this thread.
raymond_bqg said:
U can't flash stock ROM by fastboot r8?
Have u tried to flash T.W.R.P by fastboot by using mi flash tool(try to use latest version of mi flash too).
And direction is here.If that succed then all is good.
Click to expand...
Click to collapse
i tried to flash TWRP and CWM recovery By Adb and fatboot method using commands (command prompt method) amd on giving commands all executed properly but not resulted.
From now phone is not going into fastboot mode also and not booting on pressing power button.
On connecting to pc the notification message appears and says "unrecognizable device and device may be malfunctioned".sometimes it is detected as Qualcomm Device on connecting.
In that case your device is hard bricked. You need professional help.
But check if your device is listed or not in device manager if it shows an exclamation mark try to update the drivers and though your device doesn't boots into fast boot mi-flash would probably detect your phone and than flash hope it would recover your device up-to certain extent.
I only understand your problem why because I too same thing as you did.
Lavnish said:
please help me friends.....
i have redmi 2 and its model no. is 2014818.i rooted my phone by zip file throug updater app.after installation super su app installed automatically.then i opened super su app and it prompts to select continue with normal recovery or twrp/cwm custom recovery.by mistake selected second option which is twrp/cwm custom recovery.then clicked continue.after that my phone booted and that after stucked at mi logo.
my phone is not going to recovery mode.it is stucked at mi logo.
But it is going into fastboot mode properly.also i flashed latest rom by fastboot method and it shows success result in mi flash tool.but after booting it agian stucked at mi logo.i also tried to flash by command prompt by using adb and fastboot tools.all commands i give gets executed properly but the problem is not solved
i went to Mi service center.he told me that "i will do some software update.after some time he came up and said that the phone is taking much time and stucked at mi logo.
then he assumed and told me that ,there is an issue in motherboard i.e. the motherboard is currputed.
but in my perspective i dont think so, because all the fastboot cammands and functions are woring properly.
please help me in this situation and suggest me that whether it is software issue or hardware, and also about the chances of resuming to life of my phone.
Click to expand...
Click to collapse
Simply flash twrp recovery n your phone through adb drivers or contact me. I can't give you video tutorial because I don't want you make that mistake again. my mail id: [email protected]
Alrighty I think praveen66542 is not wrong.
I have actually a redmi 2 and I had exactly the same problem a year ago; I've tried all the methods but it didn't work
So i've do is :
I installed Android SDK + ADB Drivers
I Turned my phone into fastboot mode
And I wiped all data from ADB But if you don't want to loose your data you can always do a backup from ADB and then wipe device's data
I think that's the one and only working solution.
Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.
Hi, friends please help me
My phone is dead, I am trying to flash via miflash tool. It takes more than 4000 seconds, it's stuck in userdata.img flashing,I disconnected USB from my pc. Now it's booted in Mi logo and it's shows erasing
Wait till erasing logo vanishes , try to boot into fastboot mode and then reflash the IMG i.e stock ROM if logo doesn't erases , try to force the rebooting into fastboot mode
Custom rom 243 said:
Wait till erasing logo vanishes , try to boot into fastboot mode and then reflash the IMG i.e stock ROM if logo doesn't erases , try to force the rebooting into fastboot mode
Click to expand...
Click to collapse
Trying to flash via miflash tool, it take time more than 4500 seconds
fasilpoochengal said:
Trying to flash via miflash tool, it take time more than 4500 seconds
Click to expand...
Click to collapse
Stuck in userdata.img flashing
What do, Plz help
fasilpoochengal said:
Stuck in userdata.img flashing
What do, Plz help
Click to expand...
Click to collapse
fasilpoochengal said:
Click to expand...
Click to collapse
Go into EDL mode from Fastboot using command:
Code:
fastboot oem edl
Then flash stock ROM from there using Mi Flash and choose Clean all and Lock option
If by any chance your bootloader is locked because of flashing stock rom before, please unlock your bootloader as it works only on unlocked bootloaders.
Warning: This will erase all your data.
Try selecting clean all and lock option located at bottom of the mi flash tool . But data will be lost . Period
I had that problem too once. Definitely unlock your OEM via fastboot command:
Code:
fastboot oem unlock
And try again. If no result fastboot boot TWRP by Deadman
Code:
fastboot boot „name of the TWRP” .img
and go to wipe»advanced wipe»select all beside otg and USB (system, dalvik, cache, internal storage) and try again. If no result either do the same but flash some custom ROM following the guide on the ROM's thread and stay on it or try again.
If nothing helped just go to service center they will do it sometimes even that same day.
If I've helped, please press that "Thanks" button!
Best regards
The tool is changing the device name after the first reboot it makes, you only have to close the tool, re open it and then start the process again.
fasilpoochengal said:
Click to expand...
Click to collapse
just update/repair usb driver or try with other pc
DaveCZ said:
I had that problem too once. Definitely unlock your OEM via fastboot command:
And try again. If no result fastboot boot TWRP by Deadman and go to wipe»advanced wipe»select all beside otg and USB (system, dalvik, cache, internal storage) and try again. If no result either do the same but flash some custom ROM following the guide on the ROM's thread and stay on it or try again.
If nothing helped just go to service center they will do it sometimes even that same day.
If I've helped, please press that "Thanks" button!
Best regards
Click to expand...
Click to collapse
Unable to mount storage
fasilpoochengal said:
Unable to mount storage
Click to expand...
Click to collapse
:crying:
fasilpoochengal said:
:crying:
Click to expand...
Click to collapse
Unable to mount storage
fasilpoochengal said:
Unable to mount storage
Click to expand...
Click to collapse
Then use the option next to advanced wipe. Ignore any errors it may give you as long as there is "success" on top of the screen! Then proceeded to installation of the ROM. Also remember to after the wipe and any flash reboot to bootloader and boot TWRP again. The process is anoying but it may fix your problem.
I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Did you unlock boot loader? After that press volume up and power button,then you can enter fastboot screen. After that use fastboot flash recovery twrp.img
I have same problem plz help
1. boot into fastboot.
2. make sure fastboot can see the device 'fastboot devices'
3. fastboot flash recovery twrp-xxx.img
4. boot into twrp.
Did that work?
chr0 said:
I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Click to expand...
Click to collapse
Did you find any solution to this problem?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Yes. Use Powershell instead of the normal cmd
chr0 said:
Yes. Use Powershell instead of the normal cmd
Click to expand...
Click to collapse
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Utsav_vats said:
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Click to expand...
Click to collapse
Nope. Just used Powershell to execute the bat file and then push TWRP.
CMD wasn't working for me.
Hello, the problem started today after going from pixel experience to the stock room, I went to miflash and flashed the last update, after doing that the phone started to restart itself and in the Mi Flash program it marked the command "fastboot reboot" so I decided to enter in the fastboot mode and the phone restarted, the problem persists, it keeps restarting without being able to enter the system, I made a wipe from the original recovery, since I can not enter twrp since in minimal adb fastboot it says me that the phone is not found with the oem enabled, and if I try to put the command "fastboot oem unlock" it tells me that the oem is not enabled the same, I would appreciate your help, thanks.
AgustinPatatas said:
Hello, the problem started today after going from pixel experience to the stock room, I went to miflash and flashed the last update, after doing that the phone started to restart itself and in the Mi Flash program it marked the command "fastboot reboot" so I decided to enter in the fastboot mode and the phone restarted, the problem persists, it keeps restarting without being able to enter the system, I made a wipe from the original recovery, since I can not enter twrp since in minimal adb fastboot it says me that the phone is not found with the oem enabled, and if I try to put the command "fastboot oem unlock" it tells me that the oem is not enabled the same, I would appreciate your help, thanks.
Click to expand...
Click to collapse
You should've let the mi flash do it's thing. Don't touch the phone, but since the damage has already been done, you have to flash rom via edl mode.
WhatzIt2Ya said:
You should've let the mi flash do it's thing. Don't touch the phone, but since the damage has already been done, you have to flash rom via edl mode.
Click to expand...
Click to collapse
Thanks, I have managed to get into the system, however at the time I receive an update of the December patch I update it and at the end of the update and give it to restart so that it is installed it stays in a restart loop, it reaches the screen android one and it reboots, any solution?
P.S: In the ROM that worked for me, it was the "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" however does not recognize the sim
AgustinPatatas said:
Thanks, I have managed to get into the system, however at the time I receive an update of the December patch I update it and at the end of the update and give it to restart so that it is installed it stays in a restart loop, it reaches the screen android one and it reboots, any solution?
P.S: In the ROM that worked for me, it was the "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" however does not recognize the sim
Click to expand...
Click to collapse
When I updated it. I uninstalled magisk, relock the bootloader, and reboot the phone a couple of times (to chack for corruption and stuff). Then I installed the update. Try flash pie rom with mi flash tool.