Hi, sorry for being noob.
I updated my Yureka to Lollipop via OTA. Everything went smoothly and the phone was running great.
Then I decided to root my mobile and followed the instructions. Downloaded all adb tools and drivers for PC.
By holding shift key opened command window where the extracted adb files were.
Executed command 'fastboot -i 0x1ebf oem unlock'
Then Executed command 'fastboot -i 0x1ebf flash recovery recovery-yu.img'
And then blank..........nothing~!. Tried rebooting, taking out battery, putting it on and rebooting into recovery by holding vol+, vol- and power buttons. Just shows the YU logo and then phone turns blank. Would really appreciate your help guys. Worried :crying:
Solved : See My Last Post.
Same problem. Please help guys.
Did u turned on USB debugging before doing this...?
Flashed from my Yureka
TheIndianSinger said:
Hi, sorry for being noob.
I updated my Yureka to Lollipop via OTA. Everything went smoothly and the phone was running great.
Then I decided to root my mobile and followed the instructions. Downloaded all adb tools and drivers for PC.
By holding shift key opened command window where the extracted adb files were.
Executed command 'fastboot -i 0x1ebf oem unlock'
Then Executed command 'fastboot -i 0x1ebf flash recovery recovery-yu.img'
And then blank..........nothing~!. Tried rebooting, taking out battery, putting it on and rebooting into recovery by holding vol+, vol- and power buttons. Just shows the YU logo and then phone turns blank. Would really appreciate your help guys. Worried :crying:
Click to expand...
Click to collapse
same day same problem please help me if u find a solution....:crying:
Da_Gamer_pk said:
Did u turned on USB debugging before doing this...?
Flashed from my Yureka
Click to expand...
Click to collapse
Yes I had Done everything as mentioned......
Help please
same problem here.
unable to open recovery or bootloader
just YU Initial icon coming and looping.
i used fastboot -i 0x1ebf flash recovery yu-twrp-recoveryx64.img
PROBLEM SOLVED GUYS~!
I downloaded two files
1). cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
2). factory-image-flash-tools-windows-flashtools.zip
I extracted all the contents in one folder of PC. Connected phone in fastboot mode to PC. Then from the folder of PC, executed the flash-all.bat command by double clicking on it. Thats it, after that in a few minutes, My Yureka is alive again.
Here is the thread, please follow all instructions and hit thanks. :good: :laugh:
http://forum.xda-developers.com/yureka/general/yureka-cm12-lollipop-fastboot-zip-t3085621 by RohitJaiswal
TheIndianSinger said:
PROBLEM SOLVED GUYS~!
I downloaded two files
1). cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
2). factory-image-flash-tools-windows-flashtools.zip
I extracted all the contents in one folder of PC. Connected phone in fastboot mode to PC. Then from the folder of PC, executed the flash-all.bat command by double clicking on it. Thats it, after that in a few minutes, My Yureka is alive again.
Here is the thread, please follow all instructions and hit thanks. :good: :laugh:
http://forum.xda-developers.com/yureka/general/yureka-cm12-lollipop-fastboot-zip-t3085621 by RohitJaiswal
Click to expand...
Click to collapse
I have revived my Soft bricked Yureka Using this method. Many thanks.
Also want to conform here that I had PACMAN 5.1 beta while I bricked the phone. I tried this method on my friend's phone with Blisspop ROM too.
Peace. V
hi any 1 help me my android in yu logo showing "image signature verify fail" pls help any idea
fastboot driver
Everything is same except booting after giving the command my device was stuck on fastboot screen but after removing usb cable it boot up and running just like before but hadnt installed twrp.
Device = Yureka Plus
Os = COS12.1
same problem but my phone is not going to fastboot mode and when i pull battarty and re insert it ,, only red light will blow whatcan i do ..my phone is not starting
device- yureka aq5510
os- izer
recovery- twrp
same problem
some one plz help same problem
Related
Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
ejnahuj said:
Hi guys, I recantly decided to update my gt540 from 2.1 to 2.3.3
I followed steps by steps on by this tutorial - http://fdapps.comuf.com/downloads/The LG GT540 Optimus reference page.pdf
Installed rom with fastboot, tried to install Clockwork with fastboot, I typed fastboot flash recovery C:\recovery.img , and then there's <waiting for device> , doesn't go further, I have everything installed sdk, usb drivers and usb debugging activated. Maybe there's some problem with key combination, to get in fastboot. From google I understood, that I have to turn phone off, then press and hold camera + press power button! I did other combinations too, but didnt work.
Just waiting for device..
Any ideas? I read, that if you're in fastboot there's just a black screen, and on pc desktop appears fastboot usb. I have non of that.
Thanks for help in advance.
Click to expand...
Click to collapse
Hello
1. you need to install a ROM with fastboot the most common is europe + fastboot (KDZ) ROM.
http://www.mediafire.com/?96nu9lb6afx22a7
2. once its finished phone will reboot, then fast login into fastboot mode CAMERA + POWER
3. You are missin 1 thing, OEM usb drivers not GOOGLE usb drivers as some tutorial says, those are just for Android Developer Phones (ADP), Nexus One, and Nexus S.
LG_Android_USB_Driver_Rebuilt
http://www.mediafire.com/?pbigrb8cimmxa4d
* these drivers are for your pc to recognize your phone in fastboot mode, they are not the normal LG usb drivers
4. for install the drivers abouve follow these smll tutorials
* if using windows 7:
http://developer.android.com/sdk/win-usb.html#Win7
* if using windows XP:
http://developer.android.com/sdk/win-usb.html#WinXp
once is installed plug your phone in fastboot mode to your pc, now your pc has to recognize your phone wait until it finish installing the drivers and read it properly
5. unzip the new ROM files into C:\*SDK\tools
6. open CMD Terminal and go to C:\*SDK\tools, type:
cd C:\*SDK\tools
7. once in, type
fastboot flash recovery recovery_clockwork_3.x.x.x_swift.img"
fastboot -w
fastboot erase system
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
*Just in case it drops you an error AdbWinApi.dll missing here is the file. place it in C:\*SDK\tools and try again
http://www.mediafire.com/?3s3z5uym2rw5r7u
Any other question PM me
fastboot "waiting for device"
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
murthy.krishna00 said:
I have installed all the drivers and everything is working fine except fastboot. I have "nexus s" with me. The problem is:
I do "adb reboot bootloader" to flash the images, but after that if I do "fastboot devices", it doesnot show my device and if I do "fastboot flash ..", it just displays "waiting for device".
Can any one please help, I need it urgently..
THanks in advance
Click to expand...
Click to collapse
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Quinny899 said:
You need to turn phone off and hold down camera whilst pressing power.
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
Can you please clearly explain it, I couldnt get that. The prob was even though I installed the diver fastboot cannot detect the device..
Turn the phone off normally and when you'from holding down power to turn it on, also hold down camera until you get a black screen.
Sent from my GT540 using XDA App
My 501CG is in a bootloop and can't go to recovery.
The device can be detected by adb but I can't sideload anything. I've tried everything I know but couldn't fix it.
I tried to post a screenshot but the forum won't allow me and I can't explain what the problem looks like so I don't know what to do now...
Please help me. Thank you.
Teks0427 said:
My 501CG is in a bootloop and can't go to recovery.
The device can be detected by adb but I can't sideload anything. I've tried everything I know but couldn't fix it.
I tried to post a screenshot but the forum won't allow me and I can't explain what the problem looks like so I don't know what to do now...
Please help me. Thank you.
Click to expand...
Click to collapse
Can you go to fastboot? Adb still reconize it then go to ADB and type adb reboot bootloader then try to flash the recovery and factory reset. If the problem still exist after factory reset you will need to look up for system.imgs files for the zenfone 5 and flash the system imgs from fastboot
ChristopherXI said:
Can you go to fastboot? Adb still reconize it then go to ADB and type adb reboot bootloader then try to flash the recovery and factory reset. If the problem still exist after factory reset you will need to look up for system.imgs files for the zenfone 5 and flash the system imgs from fastboot
Click to expand...
Click to collapse
Thank you so much for helping me.
When I type adb reboot bootloader, it says <waiting for device> and stays that way.
I have a screenshot of the error but I can't post the proper link. Here's a modified version of the link, just replace the <dot> with a period I guess if that would work. That's the only way I can show what happens to the phone.
imgur dot com/JRcEzaN
Sorry, I'm also not very familiar with how adb, fastboot, and whatever else works, but I learn fast and can follow commands.
Well the mmcblk1 partition i think is messed up @dgadelha can you help us with this?
Hey there!
Thanks @ChristopherXI for noticing me.
@Teks0427, can you please try this guide? It will rebuild your partition table and install Android 4.3.
Hope it helps!
dgadelha said:
Hey there!
Thanks @ChristopherXI for noticing me.
@Teks0427, can you please try this guide? It will rebuild your partition table and install Android 4.3.
Hope it helps!
Click to expand...
Click to collapse
Thank you! I'll try this as soon as I get home. I hope it works...
Well. Did it work? Have any luck?
I'm so sorry for disappearing all of a sudden like that. I had to attend to a LOT of things and I totally forgot about the phone.
I'm gonna give it a go tonight and post whatever happens here right away.
Thanks guys! I really appreciate the help...
Hi! The phone won't go to droidboot mode. PressingPOWER + VOLUME UP brings me to the Asus bootup screen (sometimes with a black background and sometimes with a blue one) and the words
CSC Mode
long press power key to restart system
And sometimes it's just the normal Asus bootup screen (and gets stuck there). On that CSC mode screen, plugging in the USB and typing "fastboot devices" does nothing
D:\501KL>fastboot devices
Booting up in recovery mode works, and when in the recovery mode menu page, typing "fastboot devices" still does nothing but typing adb devices gets this response:
D:\501KL>adb devices
List of devices attached
051c7013 recovery
D:\501KL>
Running (as administrator) the file sec_offline_update_image.cmd from the recovery menu page gets this response:
D:\501KL>fastboot oem backup_config
< waiting for device >
And it stops there.
Also, when plugging the USB cable to the phone, it starts installing an "MTP USB Device" but always fails after a few minutes.
I already tried bringing the phone to the accredited Asus Zenfone repair center here in the Philippines but they said they don't have the firmware to flash this model. They didn't give any explanation nor did they refer me to anyone else who might know how to fix this thing.
@dgadelha @ChristopherXI
I have same problem but now my phone working properly
first download https://drive.google.com/file/d/0B3vLobe8_2u7SWlzZXVTYmFVcXc/view?pref=2&pli=1
and this http://www.mediafire.com/folder/7qapfy4zqvxf6 no need Zenphone4 and Zenfone6
System img and fastboot, recovery and boot file of kitkat https://docs.google.com/file/d/0Byaxd8-Kv2ZISnN4WTZVbXhpeDQ/edit?pref=2&pli=1
http://www.mediafire.com/download/4jb1mlipfrdz3cp/ww+asus-zenfone.com.rar
after that http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
fastboot flash dnx .\sec-dnx_fwr.bin
fastboot flash ifwi .\sec-ifwi-prod.bin
fastboot flash boot .\boot_sign.bin
fastboot flash recovery .\recovery_sign.bin
fastboot flash fastboot .\droidboot_sign.bin
save and run
than your in Kitkat and your problem of Can't mount /cache/recovery/log solved.
rashmi0733 said:
I have same problem but now my phone working properly
first download https://drive.google.com/file/d/0B3vLobe8_2u7SWlzZXVTYmFVcXc/view?pref=2&pli=1
and this http://www.mediafire.com/folder/7qapfy4zqvxf6 no need Zenphone4 and Zenfone6
System img and fastboot, recovery and boot file of kitkat https://docs.google.com/file/d/0Byaxd8-Kv2ZISnN4WTZVbXhpeDQ/edit?pref=2&pli=1
http://www.mediafire.com/download/4jb1mlipfrdz3cp/ww+asus-zenfone.com.rar
after that http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
fastboot flash dnx .\sec-dnx_fwr.bin
fastboot flash ifwi .\sec-ifwi-prod.bin
fastboot flash boot .\boot_sign.bin
fastboot flash recovery .\recovery_sign.bin
fastboot flash fastboot .\droidboot_sign.bin
save and run
than your in Kitkat and your problem of Can't mount /cache/recovery/log solved.
Click to expand...
Click to collapse
Read his problem carefully.
He has a 500KL not a 500CG.
That guide will not work
Apologies for saying thus but if there are no RAW firmware of the LTE model. It's pretty hopeless
Teks0427 said:
Hi! The phone won't go to droidboot mode. PressingPOWER + VOLUME UP brings me to the Asus bootup screen (sometimes with a black background and sometimes with a blue one) and the words
CSC Mode
long press power key to restart system
And sometimes it's just the normal Asus bootup screen (and gets stuck there). On that CSC mode screen, plugging in the USB and typing "fastboot devices" does nothing
D:\501KL>fastboot devices
Booting up in recovery mode works, and when in the recovery mode menu page, typing "fastboot devices" still does nothing but typing adb devices gets this response:
D:\501KL>adb devices
List of devices attached
051c7013 recovery
D:\501KL>
Running (as administrator) the file sec_offline_update_image.cmd from the recovery menu page gets this response:
D:\501KL>fastboot oem backup_config
< waiting for device >
And it stops there.
Also, when plugging the USB cable to the phone, it starts installing an "MTP USB Device" but always fails after a few minutes.
I already tried bringing the phone to the accredited Asus Zenfone repair center here in the Philippines but they said they don't have the firmware to flash this model. They didn't give any explanation nor did they refer me to anyone else who might know how to fix this thing.
@dgadelha @ChristopherXI
Click to expand...
Click to collapse
The sec_offline_update_image is for A500CG/A501CG only.
I'm sorry but I do not own an A501KL so I can't help you with that.
And if ASUS can't help you, sue them for that.
Bro You Should change your """Title:501CG Can't mount /cache/recovery/log ... etc"""
Yes, I'm so sorry. I noticed the error in the title just now. I got confused with my 2 Asus phones that I put the wrong model in the title. Stupid stupid me...
I'm so sorry for the mess.
Thank you all for your help...
I guess it will help you...
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/
a8962383 said:
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/
Click to expand...
Click to collapse
Thank you very much! I will try this as soon as possible...
rashmi0733 said:
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
can you please expalin this paragraph ,can't really understand .
i have everything ready from the links you provided
please reply asap
Click to expand...
Click to collapse
RONUAA said:
rashmi0733 said:
see Last resort method When You are in fastboot mod than flash kitkat fastboot recovery and boot file and reboot to fastboot mod than
go to extracted folder of Asus Zenfone 5 A500CG Debrick and replays system file with kitkat system file and partition.tbl from Zenfone5 folder downloaded form mediafire and edit sec_offline_update_image.cmd remove
can you please expalin this paragraph ,can't really understand .
i have everything ready from the links you provided
please reply asap
Click to expand...
Click to collapse
If You have A501CG than Its Work
use this method
https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455/
Click to expand...
Click to collapse
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Flash Latest NON-HLOS.bin before flashing any volte ROM.
Flash through fastboot
File link
https://drive.google.com/file/d/0B8Vodzmhc0GlXzdtOUFjb29EOFU/view
Extract .zip
Copy NON-HLOS.bin in adb folder
Open command prompt here
Connect phone into fastboot mode
Type command
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Wait till process done.
Disconnect phone
Remove battery and insert again
Goto twrp recovery.
Install any volte enabled ROM.
Enjoy.:good:
OEM unlock command not found
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
nischait said:
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Click to expand...
Click to collapse
nithin1664 said:
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
Click to expand...
Click to collapse
Try without using 0x1ebf and report.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Yogesh1969 said:
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Click to expand...
Click to collapse
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
nischait said:
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
Click to expand...
Click to collapse
I couldnt find the ygdp version of Cynogen, any way I found a way from youtube which solved my problems.
Link : https://www.youtube.com/watch?v=2Gpz65r2pNM
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
For drivers problem install pdanet. And you can refer to the youtube video link (above post) if you want for all needs.
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
Getting your device connected is a very important stage, whether it is system,recovery or fastboot. From what I read , you can connsct through fasatboot, since you flashed cyanogen. Just flash TWRP 3.2.1 or so which is the latest, through fastboot:
fastboot flash recovery twrp.3.2.1 .img ( Remember the spaces, the name twrp.xxx.img should be same as you downloaded. If flash is successful, you can see twrp when you boot to recovery. Then flash supersu file and/or whichever rom you want.
Sorry for late answers.
I was lil busy and sorry for wrong address also.
You could get it from firmwarefile.com
I can't post link here but select yu yureka plus variant and download oldest CBP
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.
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
emiljano539 said:
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
Click to expand...
Click to collapse
I can't boot into recovery, the error message pops up on the screen
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
You have to boot to twrp from the bootloder screen.
Use this recovery to boot from pc and never Flash twrp on pie.
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
lvnatic said:
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Click to expand...
Click to collapse
Again unlock boot loader.
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
emiljano539 said:
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
Click to expand...
Click to collapse
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
lvnatic said:
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
Click to expand...
Click to collapse
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
emiljano539 said:
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
Click to expand...
Click to collapse
Yes, I also have a redmi note 5 Pro and a mipad 4 and both work well with ADB.
Try flashint stock on EDL mode.
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Thanks for the Solution
Inferi0r said:
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Click to expand...
Click to collapse
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
yagya said:
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
Click to expand...
Click to collapse
Thanks for this. This happened to me two weeks ago, had to completely flash stock rom and begin from zero. Hopefully others will see this and avoid starting fresh.