• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM12.1 Unofficial Beta

jacob dj said:
well i cant get into dl mode to be able to use lg flash tool every time i try it loads everything and i unplug an plug back in it dose nothing do you know of a way to force download mode with a debrick.img kinda like the same way to unbrick galaxy s3?????
Click to expand...
I think i posted an unbrick img a while back, although untested. check my posts if youd like.
edit: found it on my Google Drive, will send you a link
 
Last edited:
In the past I had the black screen thing too. I was trying to use the lgflash tool but no download mode existed. I also couldn't load the recovery, until by accident only while the usb was plugged in I got into recovery mode.
So maybe try plugging in the USB to the phone and PC. Then with the phone off try POWER and VOL DOWN or POWER and VOL UP. Try a few times I know It was a desperate accidental loading of recovery but it occurred.
 
still could be the boot.img, which version are you booting? I had cm boot logo hang when trying to enable selinux
Can you pull a log?
 
eduardog131 said:
Nope. Both boot after the LG logo but stop there. ADB says device is offline.
Click to expand...
I would say if it fails to boot after 15 minutes, that something went wrong. He should downgrade to zv3 , run towelroot, and try again without flashing gapps until a successful boot. I know he said he downgraded twice but something had to go wrong.
 
Bad_MOFO_33 said:
I would say if it fails to boot after 15 minutes, that something went wrong. He should downgrade to zv3 , run towelroot, and try again without flashing gapps until a successful boot. I know he said he downgraded twice but something had to go wrong.
Click to expand...
He's telling me how he flashed to stock. This is weird. In his own words. It's not word for word and each time it did the same thing. This time I made him take the boot loader unlock and.
 
Bad_MOFO_33 said:
I would say if it fails to boot after 15 minutes, that something went wrong. He should downgrade to zv3 , run towelroot, and try again without flashing gapps until a successful boot. I know he said he downgraded twice but something had to go wrong.
Click to expand...
Did that again. Still didn't work.
 
Think of this as you will, but I'm not entirely convinced he didn't flash something from another device. Furry of life if you flashed something from another device on your volt, please tell us now. Boot images from a different phone than the one intended can cause havoc like this, especially because the partition layouts are guaranteed to be different. I spent a lot of time pouring over stuff getting the initial device tree up, and ramdisk sizes took the longest and scared me the most. Your persist-lg partition is corrupt, and that could have happened from flashing a boot image with the wrong sizes that ended up writing data where it shouldn't have.

I don't say the above to be mean, but if you flashed anything from a different device, we need to know now to effectively help you out of this jam.
 
whoshotjr2006 said:
Think of this as you will, but I'm not entirely convinced he didn't flash something from another device. Furry of life if you flashed something from another device on your volt, please tell us now. Boot images from a different phone than the one intended can cause havoc like this, especially because the partition layouts are guaranteed to be different. I spent a lot of time pouring over stuff getting the initial device tree up, and ramdisk sizes took the longest and scared me the most. Your persist-lg partition is corrupt, and that could have happened from flashing a boot image with the wrong sizes that ended up writing data where it shouldn't have.

I don't say the above to be mean, but if you flashed anything from a different device, we need to know now to effectively help you out of this jam.
Click to expand...
I can tell you for a fact that I did not flash anything from a different device.
 
furryoflife said:
No, when I would wipe, I would wipe everything but the SD. So I would be wiping Dalvik, System, Cache, Data, and Internal Storage.
Click to expand...

How exactly did you wipe all those partitions? One by one, or in the wipe>swipe to factory reset option? Also, when the problem first started, which recovery were you using? And, if it was twrp, was it the KitKat or lollipop version?
 
whoshotjr2006 said:
How exactly did you wipe all those partitions? One by one, or in the wipe>swipe to factory reset option? Also, when the problem first started, which recovery were you using? And, if it was twrp, was it the KitKat or lollipop version?
Click to expand...
I would go to advanced format, and select them. And I can't remember exactly when it first started. I highly doubt that I would of done this, but the only thing I would be able to think of mixing up, would be CM11 from my S2, but if I remember correctly (and from the file not even being on my micro sd at all) it wasn't even on my SD.
 
Damn. The LG_Persist partition is zereo'd out forever it seems. Not even dd'ing the image fixed it.
 
You must log in or register to reply here.
Back
Top Bottom