I recently tried Validus new ROM with the VS980 and while wiping the phone prior to install it wiped my internal. I attempted to push a ROM from my computer using adb and got Unknown USB device Failure. I tried another computer and got the same thing. After a few reboots in multiple secession I was successful in getting the 2nd computer to identify the device and pushed Validus and Lolipop extreme and the 39a bootstack. I have attempted both and neither actually load. I am not sure if I messed the phone or if I am just doing something wrong.
I have been using Extreme Lollipop by Micromod77 almost since release with almost no issues but when I installed it and the bootstack it just gets stuck at the bootscreen.
BTW the first computer has been formatted multiple times and now has a permanent issue which I will be getting repaired by Lenovo, the other which received the issue once or twice before actually identifying the G2 and allowing me to push the new rom.
Any help would be appreciated.
Related
Hi guys! I have been using [L5/L7][4.4.4][KTU84P][FINAL]Unofficial Paranoid Android 4.4 rom build by Cr3pT and yesterday i installed android tweaker 2, messed around with it a little bit and when I restarted my phone to apply the changes i got into a bootloop. Since then I tried literally EVERYTHING. I tried flashing the rom again, flashing the stock rom by making a zip out of kdz file, adb, wiping and formatting everything (except external sd), and many more (I can't even remember). The only available part of my phone is CWM 6.0.3.2. The one thing that is strange to me is that no matter what the computer doesn't recognise my device (I've tried on two different computers). This makes everything difficult, I can't use kdz updater etc. I have tried reinstalling the usb drivers several times and it's always trying to recognise the device with no success. Does this mean that the internal sd is damaged? Or I messed things up while formatting? I hope someone can help. Thank you.
EDIT: I was able to solve a problem, but it the solution is weird. So I had the stock rom and kdz updater, connected the phone in emergency mode without battery, then plugged the battery back. Although the pc didn't recognise my phone, I started the kdz update with default settings and here is the trick: I had to shake the phone while kdz was flashing the rom (I'm not joking).
thomekk91 said:
Hi guys! I have been using [L5/L7][4.4.4][KTU84P][FINAL]Unofficial Paranoid Android 4.4 rom build by Cr3pT and yesterday i installed android tweaker 2, messed around with it a little bit and when I restarted my phone to apply the changes i got into a bootloop. Since then I tried literally EVERYTHING. I tried flashing the rom again, flashing the stock rom by making a zip out of kdz file, adb, wiping and formatting everything (except external sd), and many more (I can't even remember). The only available part of my phone is CWM 6.0.3.2. The one thing that is strange to me is that no matter what the computer doesn't recognise my device (I've tried on two different computers). This makes everything difficult, I can't use kdz updater etc. I have tried reinstalling the usb drivers several times and it's always trying to recognise the device with no success. Does this mean that the internal sd is damaged? Or I messed things up while formatting? I hope someone can help. Thank you.
EDIT: I was able to solve a problem, but it the solution is weird. So I had the stock rom and kdz updater, connected the phone in emergency mode without battery, then plugged the battery back. Although the pc didn't recognise my phone, I started the kdz update with default settings and here is the trick: I had to shake the phone while kdz was flashing the rom (I'm not joking).
Click to expand...
Click to collapse
3.....
2.....
1.....
LOL!!!!
Really bro i'll quote you
Sent from my LG-E400 using XDA Free mobile app
Hey,
I've messed up my phone many times before but I usually find my way and end up fixing it. This time, I have no idea.
I got a new refurbished LG G2 in the mail after my old one had completely broken down and Rogers honored their warranty and sent me a replacement. This replacement took a while and I became an iPhone guy for a bit (about a month). Usually there aren't much options for the D803 but this time I seen the new 5.0 Lolipop Resurrection Remix for D803 and having been away from andriod for so long I wanted the latest and greatest features so I blinded installed it (after rooting using towelroot and installing recovery through AutoRec). I used TWRP to flash the ROM and then GAPPS right after. When the phone restarted it would pass the LG boot logo but got hung on the Resurrection Remix boot logo for quite some time. I let the phone sit for a few minutes and it finally went to the setup page of the ROM. I input everything and being worried that this would happen again when I restart my phone, I used Flashify to flash a 4.4.4 ROM because I thought it was the 5.0 ROM that was causing the problems. The phone still hangs sometimes. So I thought I would go back to stock using LG Flashtool and a D803 Kdz. (which I've done numerous times before). I then realized that whenever I connect my phone to my computer, it doesn't recognize it at all. (makes no noise, but it charges). The phone doesn't prompt me to select which method I want to use for my usb connection either (usually it asks if I wanna use it just to charge, MTP, tether, etc).
I realized I probably did a couple of things wrong here and I was wondering if anyone knows where I would start to get my G2 back to working order. (I hate using the iPhone)
Any help
Same probem here, i read in other post that it's a problem on boot image, i don't know i kdz tool can be the cause but after that i got back stock firmware doesn't work.
here my post http://forum.xda-developers.com/lg-g2/help/usb-otg-t3012311
Ive been running CM12 for a long time, but today I noticed I had a few missed calls and my phone hadnt rung. I rebooted the phone and it went into a boot loop. I cleared cache, but still bootlooping, dirty flashed the latest nightlie and then a full wipe - all of which resulted in the boot loop.
I restored my phone using the TOT method, but it would get to the setting up google account/wifi etc and reboot.
I used KDZ to install 30b lollipop ROM this seemed ok until reboot and then it would factory reset, optimise apps every time and be back to the setup screen.
I managed to install KK using KDZ and this seems more stable so used IOROOT and Autorec. I then flashed CM12 and GAPPS again, but it started to boot loop again.
I hadnt done anything to my phone prior to the problems - ie. no new ROMs, kernels or even apps.
Any suggestions or does it sound like something more physically wrong?
I have managed to get Cloudy G2 2.2 working without any problems except it isn't recognising my SIM. Does anyone have any thoughts or is this a dead phone?
Hi all, first post in this forum - thanks for any help you can provide.
My wife and I both have LG G2 devices on AT&T. I rooted mine last year with LG One Click Root and successfully added TWRP and have been running Cyanogenmod 13.0 for several months with no issues. I've been able to update, flash, etc without much trouble.
My wife's phone - that's a different story.
She is currently on 5.0.2. I had some issues rooting her phone last week with LG One Click Root so I tried iRoot from the phone app. iRoot was successful in rooting the phone - verified with root checker. I installed TWRP, ROM Manager, and all the associated root apps. Followed the CM wiki to the letter as I did with my G2 and other phones I have successfully rooted. Then I copied CM 13 and Gapps to the Internal drive as the G2 doesn't have a SD port.
Here is where I run into an issue: Every time I try to boot it into recovery, I get a laying down Android with a red triangle above him. I then reboot the phone normally and everything is fine - runs 5.0.2 and it's all good - but it doesn't boot into TWRP. I also rebooted using the power and volume keys but I thought since I had TWRP on there it would reboot into TWRP if I instructed the phone to wipe everything. But it didn't- it wiped everything and booted up into 5.0.2. Subsequent attempts to reboot into TWRP yield the laying down Android figure. I've wiped davlik/cache, etc, to no avail.
I've tried everything I know to do to resolve the issue, but I'd really like to get my wife on 6.0. It's the least I can do for wiping her phone - she was reluctant to let me try and put a new mod on there in the first place. I'd appreciate any tips you folks can provide to get past the laying down Android screen.
Thanks so much!
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).