Bootloop state YU6000 - YU Yureka General

Here is how I proceed and stuck in bootloop :
[email protected]:~$ fastboot -i 0x0bb4 oem unlock
...
(bootloader) Start unlock flow
OKAY [ 40.920s]
finished. total time: 40.920s
[email protected]:~$ fastboot -i 0x0bb4 flash recovery recovery-yu.img
target reported max download size of 134217728 bytes
sending 'recovery' (8390 KB)...
OKAY [ 0.661s]
writing 'recovery'...
OKAY [ 0.398s]
finished. total time: 1.059s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.052s
But, neither device is going to off nor anything is happening, just Powered by android logo is showing.
How do I go into recovery mode or switch off the phone.
Kindly help me.

I can only try to suggest, as I don't have your device.
Try variuos combinations :
Just before device is blacking out
1. Press Vol up (Keep pressing) ,wait till it vibrates and the original logo appears. If the recovery you flashed is stock or a working custom recovery, it will open into recovery mode. Then you can do what you want i.e. wipe data ,etc.
2. If the above doesn't work, try with pressing both Vol up and Vol down. Usually Vol down is for fastboot mode.
But, the question is which recovery have you flashed? Is it stock/custom and was it working for you earlier?
Is your rom a custom or stock rom ?

Yogesh1969 said:
I can only try to suggest, as I don't have your device.
Try variuos combinations :
Just before device is blacking out
1. Press Vol up (Keep pressing) ,wait till it vibrates and the original logo appears. If the recovery you flashed is stock or a working custom recovery, it will open into recovery mode. Then you can do what you want i.e. wipe data ,etc.
2. If the above doesn't work, try with pressing both Vol up and Vol down. Usually Vol down is for fastboot mode.
But, the question is which recovery have you flashed? Is it stock/custom and was it working for you earlier?
Is your rom a custom or stock rom ?
Click to expand...
Click to collapse
Thanks for your reply. I tried all efforts by pressing volume up and down both the ways, but phone just switch on and off automatically, nothing else. It is not going into recovery nor into fastboot mode. I don't know why after successful flashing the recovery, which I have down in OP, why phone is automatically in auto switch on and off mode. My device is YU6000 which is having stock rom and recovery.

GirishSharma said:
Thanks for your reply. I tried all efforts by pressing volume up and down both the ways, but phone just switch on and off automatically, nothing else. It is not going into recovery nor into fastboot mode. I don't know why after successful flashing the recovery, which I have down in OP, why phone is automatically in auto switch on and off mode. My device is YU6000 which is having stock rom and recovery.
Click to expand...
Click to collapse
I don't know details of your device bootloader etc. ,but this link has information of flashing Twrp recovery and rooting.
https://forum.xda-developers.com/an...ted-twrp-recovery-yureka-note-yu6000-t3613896
Also, I think you will have to use SP flash tool to flash boot.img and twrp. it should solve your problem.
you will have to install mtk vcom drivers for sp flash tool.
(About battery, last option is to remove cover and battery connector, which is risky.)

@GirishSharma
You can try flashing YU6000 factory image. Since there is no official files released (I'm not sure though) by YU, you can download from Firmwarefiles. You can watch YouTube videos for instructions.

Yes, that can be done by YGDP tool, or SP flash tool. as per the image type.

Related

[Q] TIFU going from GPE5.1 Back to Sense, Please help :)

So, the instructions are below pulled out of the Back to Sense thread.(http://forum.xda-developers.com/showthread.php?t=2733523) got to the end of what i've pasted no problems......
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Everything went well until the after that... I stuffed up royally.. my failure is below...
PS C:\adb> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
PS C:\adb> fastboot flash recovery TWRP_Recovery_2.8.6.2_M8_CPTB.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16804 KB)...
OKAY [ 1.515s]
writing 'recovery'...
OKAY [ 0.940s]
finished. total time: 2.455s
fastboot boot TWRP_Recovery_2.8.6.2_M8_CPTB.img
I realize i skipped the below steps...
Boot into stock recovery
Factory reset
Reboot into bootloader
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever.... one thing worth noting, i can see the internal storage(well some of it) the device is recognized in windows and then internal storage is 10.5gb free out of 10.6gb, Navigating to the internal directory shows 3 directories: 0, obb, and TWRP. 0 is a neverending folder. every 3rd layer deep click it shows the root directory again...
Help would be very very much appreciated!
cheers!
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Cameltoemcgee said:
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever....
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Click to expand...
Click to collapse
If the bootloader was overwritten, damaged or corrupted, the phone would be bricked, and the screen would not come on at all.
This is the second post on the first page where the OP solved their own issue. You guys are getting good at fixing your own problems.

Xperia m Lineage OS recovery and possibly bootloader issues

I'm not sure if it's right place to start this thread but the problem is that after clean install of lineageOS nightly build from 25th of January I have no recovery that's what ROM manager app says, phone doesn't show "SONY" logo while booting which means that I can't boot into recovery mode (and that's obvious because I think I don't have recovery) also phone is not rooted and works without gapps. Is there any option to fix it?
Lineage OS recovery
I installed Lineage OS for my Xperia M which was running on Cyanogenmod 14.1.
After installing the OS I pressed the recovery option after pressing power option, but the set do not boot to recovery by to Lineage OS only. I used TWRP recovery.
I tried to flash TWRP recovery via ADB, but the message is
C:\adb>fastboot flash recovery twrp.img
sending 'recovery' (11208 KB)...
OKAY [ 0.705s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.721s
Can some one help me.
I am new to this forum and a non - techie.
I have moto G2, Sony XperiaM and Nexus 6 all phones rooted. MotoG2 and Nexus 6 are running with resurrection remix.
Xperia M does not have a recovery partition like some other devices. See the "some info" section on this post
I don't know of a fix at the moment, but as a work around in the meantime you could:
flash an image containing a recovery to the boot partition
Code:
fastboot flash boot recovery.img
Then when booting the phone you'd have the recovery options
If you wanted to boot to android, you would need to reflash the boot partition with the boot.img file in the lineageOS zip
Thanks for the reply. Will post after trying this solution.
Sriwelcomesu said:
I installed Lineage OS for my Xperia M which was running on Cyanogenmod 14.1.
After installing the OS I pressed the recovery option after pressing power option, but the set do not boot to recovery by to Lineage OS only. I used TWRP recovery.
I tried to flash TWRP recovery via ADB, but the message is
C:\adb>fastboot flash recovery twrp.img
sending 'recovery' (11208 KB)...
OKAY [ 0.705s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.721s
Can some one help me.
I am new to this forum and a non - techie.
I have moto G2, Sony XperiaM and Nexus 6 all phones rooted. MotoG2 and Nexus 6 are running with resurrection remix.
Click to expand...
Click to collapse
I haven't tried to flash recovery via adb yet but thanks for information that it won't work
Edit:
You flashed twrp.img as far as I remember you should change file name to boot.img and then flash. I'll try it later hopefully phone will boot in recovery mode
I had the same problem on my girlfriend's Sony Xperia M.
Just download the latest Lineage OS nightly (I used 20170131) and extract boot.img from the zip. Then go into bootloader mode (settings -> developer options -> advanced reboot, long press of lock button -> reboot -> bootloader, you should now have the blue light on and the screen turned off), connect it to the PC and run
Code:
fastboot flash boot boot.img
TWRP should now work again
Motherjoker said:
I had the same problem on my girlfriend's Sony Xperia M.
Just download the latest Lineage OS nightly (I used 20170131) and extract boot.img from the zip. Then go into bootloader mode (settings -> developer options -> advanced reboot, long press of lock button -> reboot -> bootloader, you should now have the blue light on and the screen turned off), connect it to the PC and run
Code:
fastboot flash boot boot.img
TWRP should now work again
Click to expand...
Click to collapse
Thanks, you saved me a lot of time.
For anyone else who are in the same shoes:
Note that it is crucial to only connect the USB when it is already in fastboot mode, since if you have to unplug and replug it for driver detection/reinstall purposes, when you unplug it the device simply turns off or reboots to system.
If it is stuck <waiting for device> you might have to visit the device manager and update the fastboot device's driver.
Thanks everybody for your replies. This is how i solved the issue.
Got the phone to fastboot mode using key combination
connected to pc
Confirm device status by typing fastboot devices
Then flashed recovery by typing
Fastboot flash boot boot.img
Twrp was renamed as boot before flashing.
After completion used key combination to go to recovery and i was in twrp.this booting to twrp will take around 10 mins. Be patient.
The os will not be there. We need to flash os and gapps

Unable to change recovery

Hi All.
Just bought a Wileyfox Swift. I'd like to install Lineage OS.
Reboot into bootloader, fastboot sees correctly my phone.
I run "fastboot oem unlock-go", my data gets wiped, then "fastboot reboot" and Android starts optimizing apps. Fine.
I go back into bootloader, now I try to flash TWRP:
Code:
# fastboot flash recovery twrp-3.0.3-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16908 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.284s]
finished. total time: 0.816s
I reboot, Android starts correctly, power off. Go back into recovery but I still have the original Cyanogen recovery, no TWRP. What I'm doing wrong?
Thanks in advance for any hint!
If you are on the fastboot screen after flashing you should just select recovery and go there
There's no selection menu in fastboot mode on this phone. To go back into recovery I have to power off the device and power on again with volume-down + power button; but the recovery I got into isn't the TWRP I flashed but still the original cyanogenos recovery.
Pull battery after flashing recovery via fastboot. Then boot straight into recovery (not fastboot, not normal ROM), TWRP should be there.

Question OP9P stuck in fastboot mode, no OS or recovery Help!

I am new to flashing custom roms, and I got lineage running but I wanted to try Evo X, when I tried flashing through lineage Recovery it booted back into lineage, ok, so I erased all datat through lineage recovery and installed TWRP. I got that on but within a few clicks of messing around I found myself with no recovery or OS and im only stuck in fastboot, I have no idea how to get out of it. mods take this post down if posted in the wrong community. I just though this would be the best place to post it. I am new to XDA, I have these ADB logs from the command I was trying to run
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot boot C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools\TWRP-3.5.1-lemonadep-Nebrassy-2.img
Sending 'boot.img' (196608 KB) OKAY [ 4.500s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I have no idea why it keep failing, I would greatly appreciate any help to get my phone working again.
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
oddlyspaced said:
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
Click to expand...
Click to collapse
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
Click to expand...
Click to collapse
I guess you should try msm tool then
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
RazOne said:
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
Click to expand...
Click to collapse
I have gotten msm tool and my firmware, but nothing is showing up in msm when my device is connected
ive linked a screenshot of what my msm tool looks like, im just so desperate to get my phone back
Power off phone, position mouse cursor o er start button on msm tool, hold down vol up and down simultaneously, plug phone into computer wait a quick second and press start. That should work.
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
Click to expand...
Click to collapse
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
I LITERALLY CANNOT THANK YOU ENOUGH, YOU ARE LIKE THE DAD I NEVER HAD.
Lol, i'm not that old found the answer myself in a forum after 2 days of being stuck in fastboot.
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
hello guys i am facing that same issue but my own show slot_b and then i try to use your step but still not work help me plizzz
Googled the error you have. Check this post (and following ones)
[SOLVED] - Bootloop with completely new OPO9pro after oem unlock
Hello, just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup) Enabled developer options, OEM unlocking and USB debugging. After update, 1*reboot. then another reboot to bootloader, and executed...
forum.xda-developers.com
I think you should start over and use "fastboot flashing unlock" instead of fastboot oem unlock.
Follow the link in that thread. Droidwin has the best tutorials for oneplus you'll find. Never had this error myself, so can't say for sure what to do.

TWRP-Flash but start of Redmi-Recovery

hello,
in Fastboot-mode I flash TWRP successfull, but when I want to boot recovery, it starts Redmi-Recovery 3.0.
No start of twrp-recovery.
Commands: (same commands I have tried with Windows 10, other TWRP-versions I tried too.)
$ fastboot devices
tkx4gm5575vod69p fastboot
$ fastboot flash recovery twrp-3.7.0_9-0-begonia.img
Sending 'recovery' (31380 KB) OKAY [ 0.876s]
Writing 'recovery' OKAY [ 0.248s]
Finished. Total time: 5.123s
Shutdown phone, Press Power On/off + Volume-Up, Press Volume-Up and it starts Redmi-Recovery 3.0.
Where is my mistake?
got done, used alternative twrp
"twrp-3.7.0_9-0-begonia.img"
I think this is official twrp, but this is for Android 9.0
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
edu.mc said:
I tried flash LineageOS20 by using twrp-3.5.0_10-UNIFIED_UNOFFICIAL.img.
I installed Lineage from twrp but now hard brick has happened... nothing boots, no bootloader/fastboot
so I will try windows connects with dead phone and flash Stock-Rom Begonia / Android 9.
Click to expand...
Click to collapse
which lineage did you flash?
There is no official as far as I can see. unofficial too.
lineage-20.0-20220822-UNOFFICIAL-begonia.zip
(I don't know from which address I download it. I searched unsuccessful)
https://sourceforge.net/projects/darkjoker360-developements/files/Xiaomi/Redmi%20Note%208%20Pro/ROM/20.x/lineage-20.0-20220822-UNOFFICIAL-begonia.zip/download?use_mirror=netcologne&use_mirror=netcologne&r=

Categories

Resources