All,
I'm scared I have bricked my phone or their has been a hardware failure.
Yesterday I had a VS996 rooted via DirtySanta method, with TWRP 3.0.2-1 and WETA 5.0.7. This morning it was off and wouldn't boot (stuck on boot LG logo for 30+ minutes). I tried the following:
1. I tried flashing different ROMs and at first the Internal storage would not mount, but after a couple of wipes it was working but would end with a set_perm error and would still not boot.
2. Then I tried updating the recovery from the bootloader (fastboot) which failed with the error message: FAILED (status read failed (Too many links))
3. I went back to the dirtysanta guide and tried to flash the boot1.img (fastboot flash boot boot1.img) and got the same error. Tried different cables and USB ports to no avail.
Is there any hope for me or am I bricked?
Thanks for you help!
Looks like it may be a hardware issue. It got progressively worse; had to play with it for a while to get it to power on then finally just wouldn't power on at all. I tried using multiple batteries as well. Gave up and sent it to LG for warranty repair (9 days left). I read that sometimes they are root friendly however that never came up during our phone conversation. Got my fingers crossed.
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)
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
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!
Hi,
I initially had G935FXXS3ERHD_G935FXEO3ERG2_XEO installed and flashed Glamour ROM S9+ port some time ago, now i need to return it to stock but no luck...
Using latest odin i flashed:
G935FXXU3ERL3_G935FXEO3ERKF_XEO
and
G935FXXU3ERJE_G935FXEO3ERJF_XEO
(i need to remain on 3 bootloader)
after each flash i receive the NO COMMAND screen, and cannot boot into stock recovery... only way to boot the phone is to install TWRP... I have noticed when i plug the phone is it comes up as GALAXY S9+ so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
i have no idea what else to try
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try