Database Info

NEXUS S SOFT BRICKED, Nothing~ Works!~ Please Help Me!

So I have got this Nexus S (I9020) from Rogers and it is pretty much bricked...
Turns on and freezes at the black "Google" Logo with the lock image at the bottom of the screen...
Hold Vol + / Pwr takes me to FastBoot Mode where lock state - Unlocked and at bottom says
USB Control init
USB Control init End
Standard_Set_Configuration
I try to go into thirs option down (recovery) and I just see triangle with "!" and a green android in middle of the black screen... press up/pwr there and I get Android System Recovery <3e> with only these options:
reboot system now
apply update from /sdcard
wipe data/factory reset
wipe cache partition
------------------------
I can't put a rom or anything on the sdcard to flash with because I HAVE NOT BEEN ABLE TO get the internal sdcard to mount as a USB drive on my PC.
I have tried 3+ days of search for drivers, tried Google SDK + USB Drivers Package / Samsung Driver Package for Nexus S / Fastboot,ADB "device not found" , nothing!!!!!!
Nothing seems to make this device show up in "My Computer" so I can put required files on the sdcard (internal memory) and flash...
I see the device being detected but the drive is greyed out in Explorer
Please help... there is nothing I can do with this phone but to resist smashing it against a wall
PS: The whole issue started when I tried to root using SuperUser.zip or something like that... in any case, phone doesn't boot and doesn't get accessed via Mac/PC ... cant access sdcard, cant load rom, cant flash...
Its Brick?!? Garbage?

You will need to install ClockWorkMod recovery on the phone. In your situation this can only be done by "pushing" (flashing) the .img file to the phone using fastboot.
Once CWM is installed (will replace your current recovery, the triangle with a square) you can access it through the boot loader like you accessed the older recovery.
In CWM, you can mount your sdcard and upload a custom firmware to it and sequentially install it as well. Once the new rom is installed, your phone will work.
In order to do all the fastboot stuff, I really suggest you read the guides in the General Section of this subforum. If you're having issues connecting your phone to your PC, please read up in this section, this issue has been raised a million times and solved just as many times (hint: it's mostly a drivers issue and the PDANet drivers prove to be very successful for Windows).
Good luck,
Greetz

I installed PDANet drivers and went to connect in fastboot and the phone states "Fastboot Status - FAILInvalid Command" at the bottom in grey...

Fastboot devices.

[Q][A700] Need help, i guess i bricked my A700 :-(

Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:

Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.

Itchiee said:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Click to expand...
Click to collapse
I already tried this, when I want to install a update.zip, it stucks at "installing update".
When I want to wipe a partition, it stucks at "formating /xxx" and nothing happens...
I wanted to flash stock bootloader with Nvflash, but I can't find APX drivers for ACER A700

Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
adb reboot bootloader
fastboot erase cache
Click to expand...
Click to collapse

TomONeill said:
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
Click to expand...
Click to collapse
_ update.zip putted on a extrenal SD card doesn't work, it's skipped and CWM is launched.
_ the "adb reboot bootloader" puts the A700 in "APX" mode... and the "fastboot erase cache" is stuck at "waiting for device"...
Thanks for trying to help !!!

May this be a relevant solution??
http://androidforums.com/esteem-all...w-get-out-clockworkmod-recovery-bootloop.html
Edit:
I don't think the device checks for update.zip on the sdcard. Maybe there is a way to move the file to the internal. (adb mount sdcard adb push /sdcard/update.zip update.zip ?

Yeah,
The current CWM seems to corrupt the Data partition (amongst other things). Seems to be a going thing lately. Remember, these are new tabs, and new root & recovery methods, so there are going to be some bricked tabs before things get sorted out. This happens in "ALL" development, and everybody knows the risks involved.
I had the same issue. Couldn't reboot into fastboot, as it seems the OS has to be running?
This is why Skirlax_CZ built the bootloader for the 500/501, so you could boot it into fastboot mode, bypassing the OS. Unfortunately, the stock 70x OEM bootloader doesn't seem to allow this.
Best bet if you can't find the "exact" version rom the tab was shipped with, is to try renaming some full roms to update.zip, copy to sd, reboot (vol + and PWR, and see if it will install and boot. At the worst, it will install a stock bootloader and recovery.
Also, holding PWR, Vol - (I believe) and toggling the rotation lock should wipe User Data.
At the very worse, turn it into Acer Service, suck it up and pay the repair bill.
They will just install the correct service rom and give it back to you.
MD

Touns said:
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Click to expand...
Click to collapse
your situation is just same as mine,seeming bricked after using fatory rest or wiping from cwm,I think it's the problem of the damn cwm.as i know from now there are several devices got bricked,all because of the goddamn cwm.as we know factory rest is the same as recovery wiping,i use the under the official recovery,everything wen fine,but after wiping via cwm from the forum,it appeared the problem.
i tried a lot of method,just as u mentioned,to flash *.img
but i found a curious thing,after dumping series of *.img from a well-mailfuntioning device i can use fastboot to flash "userdata" which the loaction is mmcblk010 or /dev/block/platform/sdhci-tegra.3/by-name/UDA,but after flashing,i can't erase userdata block in fastboot.then i reflashing the data.img to userdata block,then in cwm,i can mount /data,but it's still not able to wipe or format it.then i've found a data.img and flashing the userdata and reboot.then i enter the system,and it forced me to do a factory reset,of course as before,it's not mailfunctioning because of the cwm or the block itself damaged..
but i can enter adb,and i found that i can see the /data and the filesystem in it.then i use mount to modify it,for i can delete or modify the files in /data,and it appears normally.i delete everything in /data.then i want to try to reboot to see if it's working,but after rebooting,the device stuck at acer logo,then i reboot into the cwm,it can't be mounted again.it seems that i can flash the userdata but i can't format or wipe or modify...
and i tried to reflash the bootloader from a well-mailfunctioning deivece,not working,either.
then i go for searching the situation in google,i found there are a lot of similar problems of the tegra device,and the solution is nvflash...
i don't know if there are a block saving the information of partitions just like the PIT file of my galaxy s2,seems we should wait for nvflash?or the method to flashing PIT partitions file?
i installed the nvflash driver by modifying the usb id,but i can't do anything from nvflash,it's not matching.

I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img​
fastboot flash recovery recovery.img​
And then, reboot tablet:
fastboot reboot​
WOW, my tablet works again.
:victory:

kwaiding said:
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img​
fastboot flash recovery recovery.img​
And then, reboot tablet:
fastboot reboot​
WOW, my tablet works again.
:victory:
Click to expand...
Click to collapse
Unfortunately, although somewhat similar, this is not the same situation as the OP had.
The first CWM originally posted a few months ago, was posted by a user who used the totally wrong partition tables, and also, didn't own the tab so it was never tested (after the fact). Basically, it damaged the chipset which required a motherboard replacement. Not to mention a specifically nasty Data_Cap bug in the CWM kernel. No image flashing via fastboot (and probably NVFlash) would repair the damage. The result was several bricked tabs till the CWM was removed. (mine included)
Also note, that the current root procedure is by the same person. Although there is an alternative.
What you had, was simple data corruption on one of the Dev Blocks. This is why you were able to fastboot an image.
Corrupting a partition can happen at any time. Whether rooted, stock, or custom rom. So it's always nice to have ADB to pull your partition images. Just in case.
MD

Is my Xoom bricked?

Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time

Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.

Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.

Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again

Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?

^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.

but, how can I overwrite it? it seems like they are read only...

It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.

Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:

No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.

[Q] Asus bricked, wiped system and data, no fastboot, working adb, cant mount sd card

First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.

Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory:

YU Yureka with no OS stuck on a Bootloop and unable to enter recovery mode.

Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!

Hey! I'm having the same problem with my yu yureka.. Can anyone help me please!
Kaustubh M said:
Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!
Click to expand...
Click to collapse
Hi! I'm having the same problem with this post... Does anyone knows the solution of this problem. I'd be really glad if anyone could help me with this..please!

Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.

im also having same problem i have also unknowingly wiped system & now im not able to flash any rom while flashing its rebooting automatically & i am able to enter in to fastboot mode then i have flashed factory firmware then also its not booting stucked on boot loop.

arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.
Click to expand...
Click to collapse
Bro tried that but nothing........

rss3183 said:
Bro tried that but nothing........
Click to expand...
Click to collapse
Can you be more specific ? Are you facing boot loop too?

anybody please help... facing the same problem and tried the solution as mentioned above but still facing Boot loop. what to do friends. please reply

I suddenly faced bootloop.....then I tried to flash stock rom without root...as a web page suggested me that....it was flashed successfully ...but still I am facing bootloop issue .....can someone pls help me to get out of this mess....pls help me...ASAP !!!

arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
Click to expand...
Click to collapse
as its in boot loop battery has come to an end.... now what? having same problem as the topic creator

If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device

arunbiju969 said:
If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device
Click to expand...
Click to collapse
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a point and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.

Yogesh1969 said:
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a p loopoint and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.
Click to expand...
Click to collapse
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??

Sorry for a late reply...
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
The problem got solved bcos it had a battery problem !!!! Battery showed 90-100%, but could not hold up on boot.
A very strange case. Thanks.

Hi, I flashed my Yu Yureka AO5512 Yesterday and entered into recovery mode and selected the wipe userdata option. When it was doing the process after 20min the process stopped all together and My phone does not start at all now. If i press any button there is no response at all. Looks like phones OS and everything is wiped out. How do i go about from here?

Same problem , Stuck in BootLoop
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks

YuganshT7 said:
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks
Click to expand...
Click to collapse
Sorry to hear that anyway,
By stock lolipop you mean you had the yureka plus with Volte From factory right!!...if so the twrp might have been for the yureka plus with the cm bootloader which got replaced in the new Devcice

I am facing the same problem and in my case I dont think its an battery issue...I was happily using the CM 13.0 Snapshot Rom since a long time...but today morning when I did a soft reset by going into the settings in my yureka...the phone has gone in bootloop...and nothing is working...using fastboot I even flashed the twrp again and also flashed the CM 12.0 Stock firmware..but nothing is working...after the YU logo it restarts....please help...

I am also facing problem maybe worst
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.

Aditi Apte said:
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.
Click to expand...
Click to collapse
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.

FAILED (remote: unknown command)
Yogesh1969 said:
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.
Click to expand...
Click to collapse
But when I am executing other fastboot commands it halts the process between with error "FAILED (remote: unknown command)".
I have read about this error and people suggested that I need to get into "Download mode" not "fastboot/bootload". To get into "download" mode I tried pressing "VoulumeDown+Power+Home", but nothing happened, it simply restarted the phone.
Please advise.
-Aditi