I bought a Yureka Plus A5510A recently.
i have tried all the advised methods, but everytime, using any method, the process stops at <waiting for device> as shown in the uploaded pic. i have even tried the available Toolboxes. i even checked this thread (http://forum.xda-developers.com/yureka/help/unable-to-flash-custom-recovery-t3108847) based on the same topic for the same device, however, no results...
all i could do was to flash official CyanogenOS 12.1 fastboot images.
It would be great if someone helps me.
P.S. - Everytime, i complete half of the process, and at least reboot manually, and check, i go to stock cyanogen recovery.
Related
Hello y'all. I tried installling another ROM on my phone (was using Cyanogen 7 SDSL) but I think I messed up somewhere (bricked my phone).
So I followed the steps in the sticky (Flashing on KDZ with battery and SIM out). With this, I managed to boot the stock ROM, yet no logo and boot animation shows up.
When trying to flash something else with fastboot (tried different ones), it eithers give a "too many links" error, or gets stuck on waiting on device (happens when I use the AIO toolkit). Also sometimes KDZ pops up an error too, then says finished, or gets stuck while flashing.
Also worth of note, I can't even boot Recovery (I flash it successfully on fastboot, it just doesn't boot on phone).
I searched through the entire forum, googled my problems and tried EVERYTHING, yet I'm still stuck. Anyone care to help? Sorry if it's confusing.
TL;DR
-Tried flashing another ROM, bricked phone.
-Un-bricked it by following the sticky, boot stock 2.1 (tried alot of files; euro+fast, V20a, V20b, out.kdz, France20V...)
-When booting the phone, no logo/animation shows
-When flashing recovery, it doesn't work on phone.
-When flashing custom ROM through fastboot, it gives "too many links" error, then bricks phone.
-When flashing custom ROM through AIO toolkit, it freezes on "waiting for device"
P.S. I have all the drivers installed, I have tried with the "Android modem" devices enabled and disabled, I tried all modes on KDZ, I tried changing the USB ports (only 2 on the back of PC, tried both) and still no go.
Thanks in advance.
Use aio toolkit cmd version, bcoz gui has lots of bugs right now.
Sent from my LG-GT540 using xda app-developers app
Still no luck. No matter what I do, it either "bricks" the phone (only download mode works), or it gives the "too many links" error.
Sigh.
sargeta said:
Still no luck. No matter what I do, it either "bricks" the phone (only download mode works), or it gives the "too many links" error.
Sigh.
Click to expand...
Click to collapse
i've had similar error once...
try to flash other size bootloader (appsbl) via fastboot
Managed to flash CM6 2.2.1 Utopia (miroslav's I thinki). Any other ROM bricks the phone.
Also, no boot logo/animation at all. (Yes, as I said, tried flashing V20A/B and out.kdz numerous times).
once you have fastboot , do not flash via kdz again !
also, try to flash different bootloader (appsbl) sizes (example 180mb)
then flash recovery , and then try rom's , that are recovery made (backups)
Hi there! I have this question which I'd love to have answered because I've been on this issue for around 2 days straight.
Long story short:
Tried to flash custom recovery using fastboot, didn't work because bootloader locked
Kept on trying the unlocker apps, none of them even installed fully (THIS WAS WHEN I WAS STILL ON LOLLIPOP)
Somehow, at some point, I just randomly rebooted and BOOM THERE WAS TWRP (Sorry, I don't remember how exactly I managed that. As far as I remember, I was only using fastboot and nothing else)
Flashed CM 14.1 unofficial, device gave an error message regarding boot.img (something like "could not load boot.img"
Used stock ROM to flash OTA Android 6.1
Now the Asus unlocker app downloads but on reboot it says "error: unlock fail !!!"
Obviously, fastboot is unable to flash a recovery right now. I tried ignoring the error message and rebooting to recovery to stop the device from loading the stock recovery again but the device still loads the stock recovery.
I'm really tired
P.S: NO, there is no Enable OEM option in my Developer Options menu and YES, I have all the drivers necessary.
Did you get anywhere with this? I have a similar problem except that I couldn't flash Android 6.1 because the vendor had flashed WW 5.0.2 on a CN phone without also updating the CN recovery to WW. So the update failed its consistency check.
I've got TWRP on there now, but can't unlock the bootloader in 5.0.2 - I think this is why TWRP can't flash anything. It can't see the update files, won't switch to external SD, etc. .
I also found and tried flashing a WW recovery but that didn't work either. I'm wondering now if I got the 615 software by mistake.
Hello,
I'll try to detail as much as I can to explain how i ended up Bootlooping :
I tried today to root my LG H870. (imported from Germany, according to the seller).
I followed the tutorial on xda to unlock the Bootloader on the device.
After flashing it, it launched Android the 1st time without difficulties.
I rebooted into TWRP, flashed supersu, then rebooted into Android. Problems started there, the system told me my partition was encrypted, and asked if i wanted to reinitialize it. After doing so, it's been stuck, bootlooping to TWRP, the internal partition empty.
I followed numerous tutorial on how to flash a stock ROM through TWRP, Fastboot, ADB Sideload, without any success.
With TWRP, it was always ending up saying the flash wasdone, without writing a single file in the partition.
I also tried installing stock ROM with LGUP, but once again, didn't seem to work. While in download mode, it was either telling me the phone was an unknown model, on port COM3, or that there was no handset connected.
I then followed another guide, using LG Firmware Extract and LG Flash Tool. It didn't work as expected, but, I don't really know how, it made LGUP seeing my phone correctly. I was then able to flash a stock ROM (H87010f). No error during the process.
After the LG Logo, i get now a blue screen, saying for some seconds "Encryption Progress", and after that "Factory Reset Status", with a big red "2", and it gets stucks there.
Once again, if I get into download mode and into LGUP, i get now the "no handset connected" message.
Is someone on here able to help me?
If more infos are needed, tell me, i'll try to answer!
Thank you all!
Hi everyone
I am posting this because I fail to flash TWRP on my LG G2 (D802, 30c); I would like to flash LineageOS. I have read many guides and posts - however, none worked. So I turn to you for advice -- would you help me, please?
I have managed to flash Cyanogen to my Samsung S2 a few years ago and TWRP and LineageOS to my LG G5 (H850) last year -- the S2 was easy, the G5 very tricky, but the G2 kills me. The G5 took a real effort because no guide worked for my phone, and I had to take a little from this guide, a little from that and add a bit of my own (let me know if anyone is interested in how I flashed LOS to my G5). I have tried the same with my G2 -- but I seem to have come to a dead end.
I am writing all that that to tell you that I have gone to great length before troubling you. Here is in summary what I have done so far and where I stand:
I have installed the sdk toolkit, adb and fastboot properly when I flashed my G5 last year.
Now I have started with the instructions from the LineageOS wiki (wiki.lineageos.org/devices/d802/install). I have activated USB debugging and rooted my phone using One Click root (Before One Click Root for the G2 was available, I could not even root my phone).
Then I flashed TWRP using "dd" as explained in the installation guide in the LineagOS wiki. I also tried it by flashing through the TWRP app (the app said it was flashed successfully). I tried TWRP 3.2.3.0 and 2.8.7.0 for the D802. The result always was as set out below.
After that I turned off my phone and started I by holding power + Volume down, releasing power briefly after the LG logo appeared. I went through factory reset (selected yes and yes), and here the problems begin (the same when I use “adb reboot recovery”). The phone should start into TWRP, but it does not. Instead the start screen with the LG logo appears, and in the upper left corner the following message appears:
ERROR: boot certification verify
[26480]------------------------------------- -
[26480]
[26520] Secure booting Error!
[26570] Cause: boot certification verify
[26620]
[26670]-------------------------------------- -
If the numbers in the square brackets make sense to you: They change every time I boot.
The next screen reads
------------------------------------------------- -
Critical Error!
------------------------------------------------- -
DemiGod Crash Handler : Critical Error!
Some information on how to reboot or access Download mode]
------------------------------------------------- -
Board Info Rev. : 1.1 speed.pvs : 1.3 serial : [...]
------------------------------------------------- -
I have tried many things, including several resets using LG FLash Tool 2014 to flash an entirely clean stock rom and starting fresh rooting and flashing. I also tried LG G2 D802 One Click Root Recovery V1.1, which even failed to root the phone.
My feeling is that the phone prevents me from properly installing TWRP. It does not allow me to boot into the bootloader using "adb reboot bootloader" (the command just restarts the phone). Therefore, I cannot put it into fastboot mode (I also tried the volume-up button method to put it into fastboot and failed), which may be crucial to properly install TWRP. In this regard, it may be relevant that the Developer Options show no option "OEM unlock"; that might be necessary to access the bootloader and fastboot mode…
What do you think? Do you have an idea how to solve the problem?
Thanks a lot and cheers!
Noob here: I need help with my Note 3 (SM-N900V).
I bought a used phone to replace a stolen one; it came with Android 4.0. A few years ago I successfully used Odin to flash TWRP 3.1.0.0 and the stock OF1 Android 5.0 rom, followed by a root with ArabicTool.
Phone works fine for everyday use, including root-requiring apps, but several apps are now requiring a more recent version of Android. Also, I can no longer boot into recovery mode; instead I get a message saying "System software not authorized by Verizon Wireless has been found on your phone".
I thus decided to try to flash the phone from scratch.
First I tried to use ADB and Fastboot to make sure the bootloader is unlocked. Unfortunately, while ADB worked fine, I was never able to get Fastboot to see the phone, despite following the advice of several web pages addressing this issue, and trying several different drivers.
Pressing on, I decided to try to install TWRP again. Booted phone with VolDown, Home, Power. First I tried using Heimdall 1.4, both with drivers from Samsung, and then with the MSM8960 drivers that came with Heimdall, using this command:
heimdall flash --RECOVERY twrp-3.3.1-0-hlte.img --no-reboot
In both cases, all I got was "ERROR: Failed to access device. libusb error: -12"
Therefore, decided to try it with Odin. Booted phone with VolDown, Home, Power. Run Odin 3.12.4_4, which immediately shows "Added". Load TWRP 3.3.1.0 with AP button, click Start...and get a red Fail flag within a few seconds. Log shows "FAIL! (Auth). Phone shows "SYS REV CHECK FAIL: No Version" and "SECURE MAGICCODE CHECK FAIL: recovery".
I didn't even bother trying to flash the LineageOS ROM.
Can someone please tell me what I'm doing wrong? Please don't assume I know anything about what I'm doing.
--
*not an expert*
Verify that you are using the correct build of twrp-3.3.1.
I am using the hlte build of 3.3.1 on my phone (SCL22)... but my gut tells me that you and I wouldn't share the same build.
Nope basic problem is that OP is in the wrong forum for a Verizon phone .
Assuming that download mode still works (if it is, lucky you); I'd suggest reflashing the stock firmware for your Verizon device.
Flashing a stock firmware would *hopefully* fix your recovery and download issues.
Perhaps the errors you described may have been caused by installing the wrong ROM/firmware.
So, NEVER INSTALL/FLASH a custom or stock ROM that is not tested to work on your device. The main reason is because different variants of the same device (N9000, N900A, N900V) use different chipsets, software and drivers. Also, flashing a wrong ROM/kernel/firmware may cause application errors, boot loops, broken recovery/download mode, or a hard brick.