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.
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".
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
Hi there,
i'd Like to flash the Ressurection Remix Oreo Rom, but i don't get it to unlock the bootloader. I'm on Stock A2017GV1.2.0B10 Nougat. TWRP and Backups are done, but when i try to unlock the Bootloader i geht this message in cmd:
adb: error: connect failed: no devices/emulators found
Tried with Zadigs Drivers, ADB divers are installed and it is showed as QS_Bulk.
Are there still some drivers missing or what am I doing wrong there???
Did you enable USB Debugging on your phone?
Victor13f said:
Did you enable USB Debugging on your phone?
Click to expand...
Click to collapse
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Have you installed the Google USB drivers and checked in Device manager if everything is working okay? Here's a link to a guide: https://www.drivereasy.com/knowledge/solved-adb-device-not-found-error-on-windows/
HeikoNote3 said:
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Click to expand...
Click to collapse
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
raystef66 said:
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
HeikoNote3 said:
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
Click to expand...
Click to collapse
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
raystef66 said:
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
Click to expand...
Click to collapse
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
HeikoNote3 said:
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
Click to expand...
Click to collapse
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
raystef66 said:
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
Click to expand...
Click to collapse
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
HeikoNote3 said:
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
Click to expand...
Click to collapse
MiFlash? Where did you read that you had to use MiFlash? ?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Choose an username... said:
MiFlash? Where did you read that you had to use MiFlash?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Click to expand...
Click to collapse
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
HeikoNote3 said:
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
Click to expand...
Click to collapse
Did you enable OEM unlock and USB debugging?
If you did and it still does that error, just use the manual method and follow Controllerboy's guide. That one uses axon7tool, which is much more finicky and ran by commands, but it works
Thanks for all Tipps. Finally did it. Running RR Oreo!
Hi there,
My device(Nokia 6) is detected by PC(win 10) when it is On but not detecting in the fastboot mode. It doesn't respond for any commands. Also, I'm not able to install ROM using OST.
Please help me in this regard.
Thank you.
sasikiranskl said:
Hi there,
My device(Nokia 6) is detected by PC(win 10) when it is On but not detecting in the fastboot mode. It doesn't respond for any commands. Also, I'm not able to install ROM using OST.
Please help me in this regard.
Thank you.
Click to expand...
Click to collapse
Enable usb debugging mode in developer options .
And and after connecting give permission or allow it