yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] MasterKairi0:
sadly no :/

my phon estill wont get past the lg logo :/
[Android Q&A, Help & Troubleshooting] toxinburn:
Got a little news I just got the T-Mobile LG L90 D415 unlocked downloader on it saved copy of aboot to compare in hex edit with the fuel and the unlocked aboot on the L90 only had one single byte that changed so I changed same byte on the fuel and it still boots still didn't get fastboot though...but I'm gonna try some other bytes and see what happens other times I've edited aboot and had softbrick so I think I'm getting close....going to compare the other partitions on my l90 to see what else changed after unlocking it so hopefully this is leading me to the sequence of events we are all waiting for. Also i am not sure but i was digging through the partitions and found a link to download a .CRL file now i am not sure what it is for but it is referenced in the phone i downloaded it from here http://crl.geotrust.com/crls/qctattest.crl and this is same link to it that is within the partitions not sure if this will be helpful to anyone or not just thought i would share it.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
hmmm greeat

now if i can just get my phone to access adb and link securely from lg logo

boot loop
[Android Q&A, Help & Troubleshooting] ibub:
This is potentially very good news. I've been looking at boot modes and power on reason messages in aboot, boot, and recovery. Also all of the init shells. Found some reference to volume up, down, and power. The file you linked to looked like a signature or certificate, but don't know much about that. I think the company/geographical address listed inside may be the same contained in aboot, etc. But haven't had time to check. The ability to install recovery and kernel will be great. But yeah, fastboot is the thing that I've always used to unbrick. We might be forced to nuke laf, and then flash it back while in fastboot. Enable hardware key combinations...
[Android Q&A, Help & Troubleshooting] toxinburn:
Well i have nuked laf but ya if we can enable those keypress should be ready to rock.
[Android Q&A, Help & Troubleshooting] thc2013:
Enjoying the progress on this keep up good work I recently bought another fuel for st phone from straight talk haven't had problems besides minor glitches but looking forward see where it goes [emoji1]

sent from towelrooted LG L34C
[Android Q&A, Help & Troubleshooting] idragoncell:
has anybody Tried to connect this phone to dfs or cdma workshop to try and flash it. the usb port shows up in these programs but they cant connect to it. seems like the diag port is blocked off or turned off somewhere in the settings. does anybody have any tips or know how to turn this on. i have it rooted with towel root.
[Android Q&A, Help & Troubleshooting] thc2013:
I wouldn't mess with it until recovery is found just my opinion

sent from towelrooted LG L34C
[Android Q&A, Help & Troubleshooting] toxinburn:
Well i still think nuking laf partition then powering down then holding down vol up and unplug/replug the usb power should get into fastboot but may have to find a way of disabling the charger all together at least temporarily. I mean if we can just get fastboot all we have to do is send fasboot oem unlock to the device thru console....so I am going to see what i can do to break the charging process just to see if that will change anything cause so far when i do the holding volume up plus unplug/replug usb power from powered down device i get the lg logo followed by a quick screen flash then the charger graphics so i assume bringing down this one more wall of the charger will get me to fastboot and from there unlocked....to be continued.
[Android Q&A, Help & Troubleshooting] toxinburn:
Well one thing you can do not that it really will help a ton though, i found that if you copy the laf over the recovery then do adb shell

su reboot recovery that you can get into download mode in this manner.

[IMG="Fuel D/L Mode"]http://dc440.4shared.com/img/NEaNlZAOce/s7/147faf401a8/fueldownloadmnode.jpg?async&rand=0.1589197547324932[/IMG]
[Android Q&A, Help & Troubleshooting] ibub:
I notice that it says "rooted". Though I don't think that I care about that, I read a file who's sole function seems to be reporting root apps and binaries. I wonder if bootloader redirected to laf because it Couldn't find recovery, or just loaded laf that has replaced recovery. We need to enable logging.
[Android Q&A, Help & Troubleshooting] toxinburn:
Yea rct is responsible for root checking also do not screw with sbl partitions at all got one hardbrick from that....got one fuel left to tinker with i tried reboot recovery with zeroed out recovery all you get there is a lg logo. So it is just from replacement.

---------- Post added at 09:45 AM ---------- Previous post was at 09:40 AM ----------

I may try to zero boot out and laf to see what happens since sbl will for sure be needed although i imagine i will have another brick i need to find out if someone has tried that yet.
[Android Q&A, Help & Troubleshooting] ibub:
Kernel contained in boot (also in recovery and laf). So the only kernel you will have left is laf (I think). ADB available in laf? You, my friend, are a daredevil. [emoji6]

Edit:

Was looking at sbl1 using hex viewer. Readable text starts at address f8fc with boot_authenticator.c. doesn't seem to have ramdisk(empty), or I don't know how to properly extract it. No magic was the message in APKTOOL.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
hmmm ... :/

well i still need you guys to find a wayt o get it to read thru adb becasue im still stuck at the lg logo and it wont detect the device in list ... :/
[Android Q&A, Help & Troubleshooting] ibub:
I haven't used the download tool, but can access via adb, using either the drivers from my p500, or Windows upgraded my drivers. Don't know which.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
hmmm :?

i tried but i cannot install the driver i need a good driver install exe whatll work with windows 8.1

---------- Post added at 04:41 AM ---------- Previous post was at 04:35 AM ----------

i know there has to be a way this phone isnt hardbricked it starts up and everything i used chainfire 3d and it was meant for android 2.3 and lower i know im a dummy but i know this phone has to be softbricked because it still shows up in my device list for windows as LGE android MTP device
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

Loaded bootloader on my old p500 to see the lines displayed:

Fastboot starting

udc start ()

So I searched for udc start, and got a few references of Samsung owners who were flashing in download mode (laf) , and were concerned, because they got that message: fastboot starting udc start

If unofficial flash, they got message in red. I know that Sammy is not LG, and may be set up totally different. But I wonder if there is a possibility that our laf controls fastboot mode, or is it only one way to access it.

Edit:

So I opened the laf ramdisk/sbin/ adbd in hex editor, and found messages towards the end (1f8d8):

ro.product.name�ro.product.model����ro.product.device���bootloader��setting connection_state to CS_BOOTLOADER

��device��setting connection_state to CS_DEVICE

��recovery����setting connection_state to CS_RECOVERY

����sideload����setting connection_state to CS_SIDELOAD

(Sorry, couldn't seem to copy in ascii)

But I think that this says that laf controls these connection states(but not necessarily the only way to control them).And I just looked at boot and recovery, which both contained the same adbd file (158kb)

Edit 2:

Possibly the connection state is determined by which mode the phone is in (which would make this information useless) .But this may hint that there is , in fact, an accessible bootloader mode. and we just haven't figured out how to access (without the oem keys).
[Android Q&A, Help & Troubleshooting] MasterKairi0:
smartypants lol

you are most cleber ibub i beleive you are correct indeed ill try to work on it while you see what you can :)
[Android Q&A, Help & Troubleshooting] nakperry:
Thanks toxinburn and everyone.

I was able to restore my LG L34C phone by borrowing the same model.

Here are some of the commands I used.

C:\platform-tools>adb devices

List of devices attached

LGL34C3ea9c265 device

C:\platform-tools>adb shell

shell@w3c:/ $ su

su

root@w3c:/ # gdisk -l /dev/block/mmcblk0

gdisk -l /dev/block/mmcblk0

GPT fdisk (gdisk) version 0.8.4

Partition table scan:

MBR: protective

BSD: not present

APM: not present

GPT: present

Found valid GPT with protective MBR; using GPT.

Disk /dev/block/mmcblk0: 7634944 sectors, 3.6 GiB

Logical sector size: 512 bytes

Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20

Partition table holds up to 36 entries

First usable sector is 34, last usable sector is 7634910

Partitions will be aligned on 1024-sector boundaries

Total free space is 40926 sectors (20.0 MiB)

Number Start (sector) End (sector) Size Code Name

1 8192 139263 64.0 MiB 0700 modem

2 139264 141311 1024.0 KiB FFFF sbl1

3 141312 142335 512.0 KiB FFFF rpm

4 142336 143359 512.0 KiB FFFF tz

5 143360 144383 512.0 KiB FFFF sdi

6 144384 148479 2.0 MiB FFFF aboot

7 148480 149503 512.0 KiB FFFF rpmb

8 149504 150527 512.0 KiB FFFF tzb

9 150528 154623 2.0 MiB FFFF abootb

10 154624 158719 2.0 MiB 0700 pad

11 158720 164863 3.0 MiB FFFF modemst1

12 164864 171007 3.0 MiB FFFF modemst2

13 171008 203775 16.0 MiB FFFF misc

14 204800 270335 32.0 MiB 0700 persist

15 270336 315391 22.0 MiB FFFF laf

16 319488 364543 22.0 MiB FFFF boot

17 364544 409599 22.0 MiB FFFF recovery

18 409600 415743 3.0 MiB FFFF fsg

19 417792 418815 512.0 KiB FFFF fsc

20 418816 419839 512.0 KiB FFFF ssd

21 425984 427007 512.0 KiB FFFF DDR

22 434176 435199 512.0 KiB FFFF encrypt

23 435200 436223 512.0 KiB FFFF rct

24 442368 458751 8.0 MiB 0700 drm

25 458752 475135 8.0 MiB 0700 sns

26 475136 516095 20.0 MiB FFFF factory

27 516096 581631 32.0 MiB FFFF fota

28 581632 583679 1024.0 KiB FFFF sbl1b

29 583680 649215 32.0 MiB 0700 mpt

30 649216 650239 512.0 KiB FFFF eksst

31 650240 666623 8.0 MiB 0700 eri

32 671744 3178495 1.2 GiB 0700 system

33 3178496 3792895 300.0 MiB 0700 cache

34 3792896 7551999 1.8 GiB 0700 userdata

35 7553024 7634910 40.0 MiB 0700 grow

root@w3c:/ #

root@w3c:/ # dd if=/dev/block/mmcblk0p32 of=/storage/external_SD/system.img

dd if=/dev/block/mmcblk0p32 of=/storage/external_SD/system.img

2506752+0 records in

2506752+0 records out

1283457024 bytes transferred in 424.383 secs (3024289 bytes/sec)

C:\platform-tools>adb shell

shell@w3c:/ $ su

su

root@w3c:/ # dd if=/storage/external_SD/system.img of=/dev/block/mmcblk0p32

dd if=/storage/external_SD/system.img of=/dev/block/mmcblk0p32

2506752+0 records in

2506752+0 records out

1283457024 bytes transferred in 227.449 secs (5642834 bytes/sec)
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

Hey, I found last_kmsg (kernel message) . Seems that they tucked it away inside /data/footprint/

We may be able to glean information from it. :)
[Android Q&A, Help & Troubleshooting] vwnut13:
Still haven't found a replacement LG L34C.4 I live in Vermont, so its not like I have hundreds of Walmart's to check within a 5 mile radius. ;)

Both of my local stores (both in NH actually) said they had some in stock, but none to be found when I got there. Either they aren't putting them on the shelf, or they aren't staying there for long.

I know, I could order one, but meh.
[Android Q&A, Help & Troubleshooting] ibub:
Yeah, I went to buy a spare yesterday, and they had none. Guess I'll have to keep trying.
[Android Q&A, Help & Troubleshooting] nakperry:
I did a fresh install on another Windows 7 PC to document the installation. I am newbie and pardon me if I am stating the obvious or I cant help. My phone is rooted with Towel Root, have ADB Toggle to enable USB Debugging and PC connection is set to MTP.

I copied my folder with the adb programs and drivers to the new PC.

I opened the folder then clicked Shift together with right click the mouse and clicked option: Open command window here.

Typed adb devices at prompt

C:\platform-tools>adb devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

No devices listed because of no adb drivers.

I go to Windows Device Manager and I can see the LG phone not installed correctly and I update the driver by pointing to my C:\platform-tools folder.

C:\platform-tools>adb devices

List of devices attached

LGL34C2a13525 unauthorized

Now with correct drivers I get unauthorized, I need to click on the authentication pop up screen to allow the adb access. Make sure to check Always allow from this computer. (When you brick your phone, it will now automatically connect.)

C:\platform-tools>adb devices

List of devices attached

LGL34C2a13525 device
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
Possible Recovery?

Thanks so much for this! This seems to be the only thread anywhere that is working on this little phone. Keep up the good work folks. I am wondering if a working recovery could be copied into the phone with these ADB partition commands...maybe the recovery from a Verizon Optimus Zone 2 phone, I seem to have read somewhere that it is the same hardware with Verizon Firmware. ??? I am almost ready to go buy a Zone 2 to test for recovery, but money is short for the time being.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
still not helping me get past lg logo quit worrying about that bs and help me get past the lg logo ive been waiting monthes jesus
[Android Q&A, Help & Troubleshooting] yackaro:
MasterKairi0, this thread isn't all about just getting your LGL34C device to boot again, it's about creating fixes and looking through the files in the software etc. to figure out possible ways to make a custom recovery and through that allowing the ability of custom ROMS. and people are posting fixes for problems they run into along the way, and not every fix works for all problems related to it in some way. My LGL34C device has been bricked for months now, but am I pushing them to focus on fixing MY device in specific so I can toy around and probably brick it again? no. in fact, that would be impossible to do as there is no way (other than running ADB over teamviewer, and then only in certain situations) to troubleshoot the phone over a distance. soshut up and let this forum focus on working their way through the phone's software and eventually work their way into the ability of making custom recoveries and in turn roms.
[Android Q&A, Help & Troubleshooting] ibub:
We do need to try to help each other though. I just wish that I/we had some solution that would work. ADB needs to be enabled prior to any modifications...period. That's just the way it is.
[Android Q&A, Help & Troubleshooting] yackaro:
yeah, he's pushing something that can't be pushed until we get through the phone's system and figure it out completely. that's not help. If he'd found another way to fix certain forms of softbrick, and posted it to the public, that would be help. even if it were just a line of code that the phone used to cache .25GB of internal memory to use as ram on top of another 256 MB of memory it would be useful, as we would understand that virtual ram was involved, though i kind of doubt they went so cheap with it as to use vram. All that he said is "whatever your doing is BS, all that matters is fix my phone. it's stuck on the bootscreen." he's simply insulting the current progress.

EDIT he put chainfire3d on android 4.4. bad idea. it's had success cases for devices on android 4.0.4-, but i've put it on 4.1+ devices myself, never had a successful case of cf3d working on any of those, the framework is too different. his only hope is that we pull the graphics driver directory, find out how to adb his phone from its current state, andinject the stock graphics drivers after del'ing the cf3d mod version.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
:) agreed

alright i agree
[Android Q&A, Help & Troubleshooting] microfire21:
bump

anyone get any closer on that bootloader....would like to tinker around with some cm mod builds for this one....cheap phone with okay hardware...bought two of them in hopes someone has already unlocked the bootloader....rooting was a breeze heck just seen the other day someone made a tool to root it lol....best of luck guys I am no good with loader mods but i can port roms and recovery images =p
[Android Q&A, Help & Troubleshooting] yackaro:
dat random smiley

lol
[Android Q&A, Help & Troubleshooting] ibub:
Yeah, I guess I should have disabled the bbcode

:p

Lol
[Android Q&A, Help & Troubleshooting] sk907:
will this help

https://github.com/ameer1234567890/OnlineNandroid/wiki/Supported-Devices

Stumbled across this and was woundering if this might be of any help.... I did check the l34c is on this list
[Android Q&A, Help & Troubleshooting] ibub:
This patch serves to enable online (phone running) nandroid backup app to read partition layout. The application itself requires a custom recovery in order to restore those backups. So we still need to unlock bootloader and compile custom recovery using our device tree. I am hoping that [MENTION=5345928]toxinburn[/MENTION] has the bootloader solution, but as he has been quiet for some time, I fear that he may have bricked another device. Hopefully not. [emoji4]
[Android Q&A, Help & Troubleshooting] MasterKairi0:
thanks Ibub

your doing great ibub i cant beleive how good at this you are im terrible lol
[Android Q&A, Help & Troubleshooting] ibub:
Thanks for the encouragement.

Found FreeGee app, which unlocks bootloader of LG g2 phone. But ours is not supported. Have downloaded older version, but I think that it will brick my phone. No, I'll wait for ours to be supported.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
race day

alright ill wait till you wave the checkered flag :)
[Android Q&A, Help & Troubleshooting] sk907:
interesting folder (noobieness sorta here)

Just going thru and reading some files and found what looks like a script file or something that is titled. .. install.recovery. here is the text I pulled out

#!/system/bin/sh

# If you're implementing this in a custom kernel/firmware,

# I suggest you use a different script name, and add a service

# to launch it from init.rc

# Launches SuperSU in daemon mode only on Android 4.3+.

# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.

# If you want to force loading the daemon, use "--daemon" instead

/system/xbin/daemonsu --auto-daemon &

# Some apps like to run stuff from this script as well, that will

# obviously break root - in your code, just search this file

# for "install-recovery-2.sh", and if present, write there instead.

/system/etc/install-recovery-2.sh

Just trying to do what I can to help out
[Android Q&A, Help & Troubleshooting] ibub:
Yeah, I saw that previously. SuperSU installs it. Thought about switching from automatic, as it states that--daemonsu would force daemon only. But I don't know if it will force ADB recognition, or only disable SuperSU user interface. Could give it a try. Worst thing that could happen, I think, is that I'd lose root, and have to TowelRoot again. [emoji6]
[Android Q&A, Help & Troubleshooting] toxinburn:
Messing with that script isnt going to hlp anythin just so you know also that freegee app has been around for awhile it will not work for the fuel...also yes a properly written boot.img could unlock these but would have to be signed the same as the stock which good luck doing that....the only way i see us getting further on this is getting to fastboot...i would focus on that.
[Android Q&A, Help & Troubleshooting] ibub:
Good to hear from you brother. [emoji4]

FreeGee is being completely rewritten for KK, so I'd still like to hold onto at least a small hope for support. I've been looking at other LG threads, trying to get some knowledge of partition usage and boot sequence. But nothing yet as far as enabling key combinations. Still searching...
[Android Q&A, Help & Troubleshooting] sk907:
just curious

What does fast boot do exactly?
[Android Q&A, Help & Troubleshooting] thc2013:
google is your friend [emoji1]
[Android Q&A, Help & Troubleshooting] sk907:
Lol yes Google is my friend. And a very good one. .... was only asking cuz I ran a fastboot script and my phones still working. ...in fact it's kinda funny it's working. Loads better
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] dmidge:
Hi erveryone,

First of all, thank you for reading my post and trying to help me.

My cell is a Samsung Galaxy Ace II x (GT-S7560M); I didn't found more appropriate place to post this thread. It is a new cellphone : I bought it 3 weeks ago.

I would like to "play" a bit with my phone (change the ROM, root it and everything. It is mainly because I want the Universal Storage Mode back on my cell). But if I do so, I would void the warranty. Since I will probably sell back this phone in few months, I may cause me some problem to explain people that there is no warranty anymore. :( So, I need to do a complete backup of the phone, including the part which is erased by ClockWorkMod recovery! (once this backup is done, I have found pretty much everything I need on Internet).

My question is - how do I do a backup of the boot partition knowing that:

this cell doesn't work on mtd.

the file /dev/block/bml5 (or /dev/bml5) doesn't exist (so what is said in this page http://xdaforums.com/showthread.php?t=1335548 can't be applied)

neither does the file /dev/emmc

So it seems to be a bit more complicated to do a dd backup as found at some place on the net.

Also, since I want to backup the ROM after all these operation, I didn't root my cellphone (It would have voided the warranty) and of course, didn't change my ROM.

For the sake of accuracy, there is the complete answer to the mtd:

shell@android:/ $ cat /proc/mtd
dev: size erasesize name

It is a bit empty, I know. :( Samsung seems to prefer a proprietary format "bml".

I also looked into the partitions file:

shell@android:/ $ cat /proc/partitions
major minor #blocks name

253 0 122880 zram0
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 150 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 12288 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 12288 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1228800 mmcblk0p16
179 17 512000 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 12288 mmcblk0p19
179 20 24576 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 51200 mmcblk0p22
179 23 1000 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1901176 mmcblk0p25

So I got some information, but I can't use them. But all these files can be found in /dev/block. I also checked: it seems that adb knows the dd command (I think not all cells do have it right now).

I think I have said pretty much anything I think is important.

Do you have any idea to help me? :fingers-crossed: Or any questions?

By the way, I have seen there are some cellphones that have an embedded flag, that counts the number of time we flash the boot partition. I have not seen such information on this device, so there shouldn't have any, should it?

Thank you for your help :) and sorry if I miss anything that coulb be on the net/other post. I think I have done a quite wide range of them, but we are never sure we didn't miss anything.

Also, it is my first post on xda, so sorry if I miss any important rule of the forum, but you are welcome to let me know what they are.