need help in installing cm12.1 in yu yureka - YU Yureka Q&A, Help & Troubleshooting

I am using all in one tool for changing my ROM but while unlocking bootloader it is showing an error.
ADB is out of date
What should I do?
I am using cm 12 right now.

Related

cannot flash any roms ..

i am unable to flash any rom into my device using twrp or custom yureka recovery..pls help fast
moderator pls delete this thread...actually i posted in tension that device is not working..not it is working fine
tried
using twrp--- it is just flashing screen but not flashing any rom to device
using custom recovery --- it says signature verificaiton failed even i downloaded it from official cyanogen mod website
solved
akhilchirra said:
using twrp--- it is just flashing screen but not flashing any rom to device
using custom recovery --- it says signature verificaiton failed even i downloaded it from official cyanogen mod website
Click to expand...
Click to collapse
atlast after hard bricking my phone..some how recovered my yureka back...now working properly..:fingers-crossed:

What version should i choose CM13 to install

Guys im having a trouble installing CM 13 in my Asus zenfone 2 laser ze550kl .. Should I choose the latest nightly or the first release snapshot? Please reply... I tried flashing the latest CM13 but I ended up bricking my phone so I fixed it and manage to put it back to stock.... When I tried flashing the latest then reboot the result is stucked in fastboot mode... I downgraded my phone to lollipop so that I can unlock my bootloader then flashed twrp then downloaded the latest CM13 and I failed... Can someone help me with this... I want the CM... Im a noob and I want a step by step clear guide... To all expert out there pls do help

stuck on bootloop

Hi, I have yu yureka plus yu5510a p2 which had stock Android 5.1 with locked bootloader, I have installed cm 12.1 from Rohit Jaiswal method. now after 2 months my device is keeps rebooting on yu logo even after flashing stock cm and whenever I try to flash via ygpd tool, it's not even getting detecting in that tool but device manager shows Android bootloader interface. Any solution for this?
any1 here? guys?
Happens with me also not also flashing any roms
Here is the fix. You don't need to change ROM or battery
https://m.youtube.com/watch?v=Q60ZkevoESc
I tried but messedup with it
siddhesh9146 said:
Hi, I have yu yureka plus yu5510a p2 which had stock Android 5.1 with locked bootloader, I have installed cm 12.1 from Rohit Jaiswal method. now after 2 months my device is keeps rebooting on yu logo even after flashing stock cm and whenever I try to flash via ygpd tool, it's not even getting detecting in that tool but device manager shows Android bootloader interface. Any solution for this?
Click to expand...
Click to collapse
Hi , flash twrp..
and install stable ROM... I had used Resurrection Remix OS with volte update. Its great. You too give a try

Yu yureka plus Yu5510A stuck on bootloop Hw ver P1 ,on KitKat Yu os

Dear All
Im stuck at yu logo bootloop. I have gone almost through all posts. And was unable to get a solution.
I bought my phone with Yu os KitKat version. Rooted and installed twrp. Installed resurrection remix and was working fine, except for the battery. So decided to install quake Os. As it is from.android 5.1 . Got stuck at bootloop. So afterwards clean wiped using twrp and installed nitrogen os. Which worked, but no compatible gapps. Then decided to come back to cm11 stock rom. Which again crashed and was having vertical blue line issue which I sorted out by flashing cm13(flash_all.bat file). But still in bootloop. Flashed cm12(flash all) . Still on bootloop. Finally tried ygdp with Yu os reliance jio firmware, again on bootloop. Can someone help me? Is there any solution.
If someone can help, im.sharing my what'sapp number +91.9744.75.7702. hope someone can help me. And I bet all files and links given the posts are now either not working or the downloads has been expire and cannot be downloaded again. So kindly post on the links for a solution.
Thanks in Advance. Hope the moderator can understand my situation.

[FIXED] Can't install any custom rom, but stock Lolipop is ok

I tried to install a custom rom on a a6000. I installed the lolipop stock rom on top of the KitKat stock rom, and managed to boot to it without a problem. I then installed TWRP installed is: 3.3.1-0, and tried to install a custom rom (more specifically I tried this unofficial Lineage). For some reason, the installation fails with:
e3004: This package is for device: Kraft-T, a6000, K30-T,A6000, Kraft-W, Kraft-C, k30t, msm8916,Kraft-A6000,wt86518; this device is .
Updated process ended with ERROR 7
Click to expand...
Click to collapse
when booting into the stock lolipop rom installed I can see that the device is the A6000. I find it strange how the recovery doesn't write which device it is on this error message.
What am I missing here? Usually with other phones, as long as you manage to install a custom recovery then it's a breeze. I cannot figure out how the custom roms don't get installed. Any help appreciated
Managed to flash it in the end. The flash files contain assertions checking if the zip is okay to be flashed on the device (whether the model is the one intended for example).
I found it strange that the error message did not show the model of my device as I was 100% sure it is a A6000 and that is a ROM intended for it.
I ended up overriding the assertion in the file, which seemed to be straightforward to do and the image was flashed without any issues.
DO NOT TRY THIS AT HOME unless you are 10000% sure the image is intended for the device. ?
runningdap said:
I tried to install a custom rom on a a6000. I installed the lolipop stock rom on top of the KitKat stock rom, and managed to boot to it without a problem. I then installed TWRP installed is: 3.3.1-0, and tried to install a custom rom (more specifically I tried this unofficial Lineage). For some reason, the installation fails with:
when booting into the stock lolipop rom installed I can see that the device is the A6000. I find it strange how the recovery doesn't write which device it is on this error message.
What am I missing here? Usually with other phones, as long as you manage to install a custom recovery then it's a breeze. I cannot figure out how the custom roms don't get installed. Any help appreciated
Click to expand...
Click to collapse
Hi... Actually you can flash custom ROM on Lenovo a6000.
Im also using Lenovo a6000 and I'm running custom ROM.... feel free to Reply if u need any help..I'm glad to see that you will.?

Categories

Resources