yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] XDVRMX:
adb doesn't work if your device booting isn't ahead enough. Seems that your recovery has gone, this usually bhappens when you perform a format data from fastboot or if you flash a new kernel. Try to shut down completely the device wait some minutes and then enter in fastboot to flash a new recovery
[Android Q&A, Help & Troubleshooting] ibub:
I am not familiar with this brand of device, so three possible options. Try touching "enter fastboot mode " on the warning screen, or is there a keypress combination to enter fastboot, or adb reboot fastboot?
[Android Q&A, Help & Troubleshooting] LeoPap:
Thank you all but I think I'm out of luck... Take a look!
[Android Q&A, Help & Troubleshooting] XDVRMX:
This command works only if you have unlocked your bootloader. If you got this error, then seems it's locked [emoji848]

Inviato dal mio G8141 utilizzando Tapatalk
[Android Q&A, Help & Troubleshooting] ibub:
Try fastboot devices. I think you are in fastboot mode. Adb won't work here. Only fastboot commands.
[Android Q&A, Help & Troubleshooting] LeoPap:
Hey, this is a step forward, you are right, it seems I'm in fastboot. So what can I do now? Fastboot flash boot twrp.img ???
[Android Q&A, Help & Troubleshooting] ibub:
Well that depends. I don't know if the lenovo has a combined kernel and recovery or if they are in separate partitions as I am used to. On another device (LG) the partitions are separate and I would

fastboot flash recovery twrp.img

but if it is a combined kernel/recovery then the command might possibly be something like

fastboot flash boot twrp.img

but I'm really not sure. It might be a good idea to search your device forum to find out. Even then you might have to

fastboot oem unlock <token >

where the token is a code that you have to obtain from lenovo support
[Android Q&A, Help & Troubleshooting] LeoPap:
1000 thanks for your help up to here! I found on lenovo forum this:

Lenovo S60 has a secure boot, locked bootloader and signed boot.

Info from imwangwang:

it means the ROM will validate bootloader, bootloader validate kernel image, kernel validates systemimage

What does this mean? Nothing or we are closer?
[Android Q&A, Help & Troubleshooting] ibub:
The bootloader must be unlocked if you can obtain the token from lenovo support. There are ways to get around this by flashing a "bumped" kernel/recovery. But in your situation it might not even flash (locked). The bumped kernel might be designed so as to allow a custom ROM to pass verification. More on that subject here

https://source.android.com/security/verifiedboot/dm-verity

Kernel/recovery from your device forum or from twrp website should already be bumped. The question is: will it flash?
[Android Q&A, Help & Troubleshooting] ibub:
Factory reset is easy. That is the ONLY function of recovery that works ATM. Go to settings/ backup and reset/ Factory data reset. You can also backup data to Google there. :)
[Android Q&A, Help & Troubleshooting] R.Suave:
Great news. I should have known to look there. Thanks
[Android Q&A, Help & Troubleshooting] FlyingPoo:
I did not know about the Loki tool, good find. I had dumped and decompiled the laf partition. I have no way of knowing how to get to it through commands tho. I think its used for LG's proprietary flash tool.

I have aboot dumped and took a look at it in hex editor. Most aboot partitions are signed and cant be modified

as they pertain to the hardware in the phone. HOWEVER, we can read them and use the info in them as the Loki tool does.
[Android Q&A, Help & Troubleshooting] arisenastyoat:
I hope you guys can get this figured out I also have an LGl34c and I would like to get CWM on to it. Thank you and have a nice day.
[Android Q&A, Help & Troubleshooting] stevotdo:
Loki exploit already Patched

The method that Loki uses is patched in our aboot.

Relevant Patch Commit

Verified with disassembly of my aboot from my LG lgl34c Fuel

ROM:0004A454 "kernel/ramdisk addresses overlap with aboot addresses.\n"

ROM:0004A684 "Device tree addresses overlap with aboot addresses.\n"

ROM:0004A6BC "Boot image buffer address overlaps with aboot addresses.\n"

ROM:0004A6F8 "Signature read buffer address overlaps with aboot addresses.\n"

Relevant exploit section from Loki author djrbliss' notes:

I'm still digging lol
[Android Q&A, Help & Troubleshooting] stevotdo:
The Recovery image gets verified just like the boot image. I've built cwm recovery against my tree for the l34c fuel but it doesn't pass bootloader image verification. Luckily our bootloader shares code with many other devices. If someone finds a new way to unlock the bootloader then it should be possible for us as well. It's a daunting task but atleast developers with certain other phones are essentially helping too.
[Android Q&A, Help & Troubleshooting] ibub:
I am not sure that I am convinced. These messages are surrounded by many other error messages that could not all be true at the same time. I think that they are called for display only when these conditions are present. Granted, I am possibly wrong about this. But I'm just not ready to give up that easily. I'm gonna look again at that commit. ;)
[Android Q&A, Help & Troubleshooting] toxinburn:
Is their perhaps a way to break the verification?
[Android Q&A, Help & Troubleshooting] ibub:
That's basically the function of the Loki patch ( if you read the copied text above). I was thinking to try it after buying a test phone. But I need to do more research. I've compiled cm9 a couple of times, and just recently found out that cm10 will now build on my 32bit machine. But the necessary changes have not yet been included in the cm11 branch of android_ build (toolchain ). So I may need another computer just to be able to make the boot.img, and apply the Loki patch.
[Android Q&A, Help & Troubleshooting] toxinburn:
Ok so cm11only works on x64? I had heard Loki will work up to 4.4 myself but 4.4.2 is patched....also heard that the aboot is already patched on these as well hopefully that isn't the case. I would be willing to try the build on 64bit system too if you have it ready I tried a Marko build but kept failing.

---------- Post added at 01:54 AM ---------- Previous post was at 01:52 AM ----------

Lol mako not Marko gotta love autocorrect
[Android Q&A, Help & Troubleshooting] ibub:
Hey brother. I don't have anything ready. Haven't bothered to sync cyanogenmod 11, because I can't build it. Haven't got device tree yet. Haven't even downloaded Loki patch. My build.prop says 4.4 :)
[Android Q&A, Help & Troubleshooting] ibub:
Yeah brother, looking at the text for the Loki patch, I (or you) would have to first compile CWM and boot.img from cm11 source and our device tree. So might as well build complete Rom. Need to repo init etc etc cyanogenmod etc. Set up build environment (sudo apt get build essentials, etc ), source build/ envsetup.sh etc etc. Then, once we have recovery.img and boot.img, we can use Loki tool to flash (hopefully) these to our device. I can give you some helpful links, or you can wait until I obtain the proper hardware. It is a bit of a task to get it all set up. The good news is that the Loki tool will actually check to see if it is safe before flash. The bad news is I can't seem to get adb to be active on this device. :p
[Android Q&A, Help & Troubleshooting] yackaro:
since you don't have a 64 bit machine, I have a 64 bit gaming rig with windows 8 and a secondary hdd with windows 7 on it, and i'm planning on changing to a win8+ubuntu dual boot soon, so maybe you could help me learn to compile cyanogenmod 11? my phone is currently softbricked (as mentioned on my page 1 posts) and i really want to get it both unbricked and with a custom rom. I'm installing ubuntu for the better OpenGL speeds and the windows 7 is getting dusty/moldy. I've been trying to get into coding and modding for quite a while now and have gotten pretty far over the last month with minecraft modding/java programming, and i would love to expand even farther than minecraft modding (making roms etc.?) but yeah as long as I have someone to walk me through it i'm ok.

EDIT

Teamviewer is a good software i highly recommend it (if you want to help me figure this out and help me get a build environment set up this is the software to do it with, it's much more efficient than trying to figure things out through a text chat).
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5839451]yackaro[/MENTION]

Check your PM
[Android Q&A, Help & Troubleshooting] toxinburn:
Well I wanted to mention I found something in the aboot while using a hex editor...found something that is literally a typo from the programmer will post more when I. Get home may be why stock recovery doesn't work....stay tuned. They actually have a command to recovery where they spelt it as recvoery surely that's a problem.

---------- Post added at 07:29 PM ---------- Previous post was at 06:33 PM ----------

okay so here is a copy of a post i made on androidarea51.com

Hi all I was just curious if anyone else had seen this I made a copy of my aboot and was looking it over in a hex editor and came across a weird line, that I assume is a screwup during programming and wondered if correcting it would help anything at all....the offset i am looking at is blocks 4B0F8-4B10C and this is the text emmc_set_recvoery_msg notice RECOVERY is spelt incorrectly. Im pondering if I should change this to the correct spelling and push it to my phone or not lol, the last time i messed with aboot i had to recover it in linux it wouldnt even boot up to the logo, however the one good thing about these is the qualcomm bulk mode from there with linux you can get into the partitions through usb and push back the original file.

---------- Post added at 07:54 PM ---------- Previous post was at 07:29 PM ----------

well....i changed those values using hex editor and soft brick r us lol, will have to fix it again oh well it was....worth a shot however.
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

I just took an md5 sum of aboot and of abootb, and guess what...THEY ARE IDENTICAL ;) I think that one is checked against the other during startup. So if we make a change to one, then we need to make the same change to the other, ...I think.
[Android Q&A, Help & Troubleshooting] toxinburn:
Interesting in deed. What do you think it could mean their are a couple other b versions of other blocks as well. Like Tz for instance.

---------- Post added at 12:50 AM ---------- Previous post was at 12:48 AM ----------

Also you can change the b version without changing the other not sure what it does though I did this just to see altering the b and not the other phone boots fine alter the primary and not the b I get softbrick

---------- Post added at 12:55 AM ---------- Previous post was at 12:50 AM ----------

So it seems in theory if the primary is changed and the b does not match you go to softbrick is the security simply checking to see if aboot matches abootb? If so we may finally be getting somewhere will have to check into it more tomorrow I think I may get another one of these phones just for testing gets a bit old unbricking mine lol.
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

Or b could simply be backup. Another theory.
[Android Q&A, Help & Troubleshooting] toxinburn:
That is what I assumed as well....but then the question is why exactly would you need those backed up the average user without root would never access this nor were we intended to...so what would be using the backup?

---------- Post added at 01:52 AM ---------- Previous post was at 01:13 AM ----------

I wanted to post another finding about the aboot and abootb I have noticed that while the md5 may be the same the two are not exactly identical if you do a side by side comparison everything in deed is the same until you get to the very bottom the aboot has ANDROID-BOOT!... where the abootb does not have this line.....for some reason. this is at the blocks 1FFE00-1FFE0C. Those are the only differences.
[Android Q&A, Help & Troubleshooting] LeoPap:
ok, so what do you advice me to do first? I don't know what to do, it is the first time i go so deep in android and i have no knowledge / experience ... I feel a bit st^pid for all these questions but ...
[Android Q&A, Help & Troubleshooting] LeoPap:
I'm trying to do all these... Failed is the only answer.
[Android Q&A, Help & Troubleshooting] Teddy Lo:
The only reason why it didn't work was because when the LG logo appears you have to let go of power (while still holding volume down), then press and hold power again until reset screen appears (note: dont let go of the volume down at all until the reset screen appears, only let go of the power button then press and hold it again after)
[Android Q&A, Help & Troubleshooting] ibub:
Try rename twrp.img to recovery.img and temporarily boot to it using

fastboot boot recovery.img

I am not a fastboot expert, but it seems safer to try it before flashing it
[Android Q&A, Help & Troubleshooting] LeoPap:
Nothing... I don't understand it... Why??? Failed, same error. But thank you for your help!
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

Ok, I found it. Seems I had copied the same partition twice. I dd again, and now the md5 does not match. Oops. I'm gonna use hex editor to remove those lines, just to see if I get a match. Any way to use diff on these? Edit: No, I changed it to zeros, and they don't match. So much for that theory. :(
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

Well, one more time. Seems that my changed aboot did not get properly saved. Tried it again, and they do indeed match. The theory is back. :rolleyes: I must have been tired. :p
[Android Q&A, Help & Troubleshooting] toxinburn:
well im basing this on some stuff i had read in the hex editor, seems if we had proper usb cables that if you plug it up while holding the volume while phone is off it should go to download mode, has to be a certain special cable though.....dont remember the specs....it would be the same as the one the service techs would use if it was sent in, of course who the heck would send in a 30 dollar phone for repairs lol.

---------- Post added at 09:02 PM ---------- Previous post was at 08:11 PM ----------

Oh ya btw i got a buddy that is more experienced that is gonna pull that repository and try to make a build hopefully it will work....fingers crossed on the loki.
[Android Q&A, Help & Troubleshooting] dianlujitao:
maybe it has a special bootloader
[Android Q&A, Help & Troubleshooting] yackaro:
lol? though that is possibly true, but most likely it would be using the abootb as either a backup for aboot or a verification system to try to make sure aboot isn't modified.

EDIT:

though it you think about it verification wouldn't make much sense since abootb is just as easily modifiable as aboot, but i don't have firsthand experience I'm just going on the fact that ibub found it that it's probably in the same directory or something.
[Android Q&A, Help & Troubleshooting] yackaro:
Any luck yet?
[Android Q&A, Help & Troubleshooting] ibub:
Ok, I dd sbl1 and sbl1b, which I believe may be secondary boot loader (fastboot?) . And again those two partitions are identical.
[Android Q&A, Help & Troubleshooting] toxinburn:
Hey yackaroo I have recovered mine from softbrick a couple times now, i can try to help you out but first of all your gonna need to get linux on your comp, thats the only way I know to help you.
[Android Q&A, Help & Troubleshooting] FlyingPoo:
What is this method you speak of?
[Android Q&A, Help & Troubleshooting] stevotdo:
I built a 56k/130k/910k Factory cable yesterday for one of my Fuels that's in bootloop. I tried the key presses shown in the bootloader image but no dice. Any suggestions that you can think of. I tried getting it into any of the other modes but nothing works. I've got firmware for the verizon variant and I was going to try and flash it to the phone.
[Android Q&A, Help & Troubleshooting] ibub:
When flashing firmware to my previous LG p500, I didn't need a special cable. As I recall, the LG update tool was able to put the phone into download mode. But the drivers need to be installed to computer first. To use KDZ, I think I had to hold key combinations for the p500, but not power button, while plugging into computer. This would set download mode. But with this phone...I'm stumped.

Edit:

What is the function of this cable?

---------- Post added at 03:55 PM ---------- Previous post was at 03:22 PM ----------

Please document any successful methods here on the thread, for the benefit of everyone here. I have a feeling that there will be a lot of bricks here. :rolleyes:
[Android Q&A, Help & Troubleshooting] ibub:
I see that /dev/sdf6 for aboot corresponds with/ dev/ block/ mmcblk0p6 that I've used to dd the partition. Thanks for all this. It'll be very useful. :)
[Android Q&A, Help & Troubleshooting] FlyingPoo:
I tried to get this to "stick" by creating a script (ex, recoverytxt.sh) to drop in /etc or /system/etc and even tried /system/bin.

I think my root access has gotten messed up because I cant seem to modify anything in those folders.

Confirmed it DOES work tho to get menu text in recovery.
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=3646165]FlyingPoo[/MENTION] This is a copy of my post at androidarea51

So I copy/pasted that script to a text file, and renamed it as recscript.sh,* fired up terminal emulator and typed su >enter <br />sh /storage/external_ SD/recscript.sh>enter, and yeah, it works like a charm. The easier method, which also works, is to open the text file, select all, and copy/paste it into terminal, after su of course<br/>
[Android Q&A, Help & Troubleshooting] toxinburn:
Even with root their has been a few files I had to chmod 777 to open but afterwards I could.

---------- Post added at 07:47 PM ---------- Previous post was at 07:35 PM ----------

I wanted to ask a question to my fellow fuel owners please get usb drivers and lgmobile support tool and plug in your device mine is shown as LG v-500 with lgl34c software the v500 is the g pad so that's strange but their is a workin cwm and twrp Loki for that and it seems to have same hardware furthermore I have noticed if you soft brick it by messing with the aboot plug it up to pc while it's in bulk mode with lgmobile support tool click options update recovery and enter the imei it starts a download so maybe their is a way to figure out how they sign their files or some other exploit there just thought I'd throw this out there.
[Android Q&A, Help & Troubleshooting] ibub:
So I tried again to make a small flash from external sd using stock recovery. This time I copied update.zip to sdext2 ext4 partition (just to see if it was recognized). Unsuccessful. Tomorrow will try with sd formatted as primary ext4.
[Android Q&A, Help & Troubleshooting] yackaro:
so we finally have access to recovery, now we need an image rip of the stock rom..... i didn't quite understand what you were doing with the unbrick thing before the quoted text, don't really have access to my softbricked Fuel right now i'm not currently home and i thought it was useless to take something that doesn't work.... we need to get some kind of flashable rom available so we can unbrick this thing asap when problems occur instead of... well... abandoning use until a solution is found... and my brick has nothing to aboot or the like, i was daring enough to find out that custom boot anim's didn't work....anyone got a backup of the stock boot animation? i could use it if there's a way to get to it on the device without actually having access to the OS... or whatever... end of post cause i'm confusing myself with my own words.
[Android Q&A, Help & Troubleshooting] ibub:
I have boot animation.zip. Saved it when I took it out. Without it, android animation is default. I like it better. When I get a chance, I'll upload. [emoji4]
[Android Q&A, Help & Troubleshooting] yackaro:
wait so it will unbrick if i just remove it completely? *cave johnson voice* why, I never thought about that. That's just GENIOUS!

I'm doing it right when i get back home.... whenever that is.... ok this voice is just losing it's sense of humor, I think I'll end it now. *end cave johnson voice*

---------- Post added at 09:36 AM ---------- Previous post was at 09:25 AM ----------

something off topic i wanted to note from a misspelling of toxin's...

hah you reminded me of my old password right there, I don't use it anymore so I thought I might just say for the lols, all you would've had to do was put the last two o's down as 0's... and i'd've been saying bye bye to my roblox acc. about three years ago before I thought up a genious password for myself and changed everything to it. And I don't play roblox anymore anyway so why would I care.... I'd change the password back and give it to every living soul out there and the first one to get on it and change the password keeps it. ooh the days.... ok now back to the topic...
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
LG L34C Boot Animation Files

Here You Go. Hope These Will Help You Out. They are From a Straight Talk Branded Lg L34c.
[Android Q&A, Help & Troubleshooting] yackaro:
thanks i'll put them in my phone as soon as i get home. I got softbricked cause I got a boot animation of like, way too high res or something. all I know is I flashed the animation with an animation changing program and it wouldn't go past the boot animation.
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
Missing Files

Also, I don"t seem to hare a Recovery file in my /Cache/Recovery folder. I Don't recall deleting it, but can't find it anywhere. Do you guys have the big recovery file in that folder? I'm trying to get the phone into Recovery Mode with the Connectbot terminal method, but it's a no-go. I would really appreciate any help on this.
[Android Q&A, Help & Troubleshooting] ibub:
Don't need recovery there. Only need command, which the above script installs.

Edit: There is a recovery file contained in extracted recovery, in ramdisk/sbin 428kb. But I don't know if it is the same file.

Edit 2: [MENTION=5960149]TECHADDICT5610[/MENTION]

Are you trying to remote from another android? I never would have thought of that.
[Android Q&A, Help & Troubleshooting] yackaro:
well i'm trying to get into my bootlooping phone with ADB and everything, with no luck. guess i'm stuck like this. i can't figure out how to get the thing in bulk mode and I can't even squeeze adb access with adb wait-for-device. all it does is boots, vibrates, goes into the blank recovery, waits a few minutes, reboots with a vibrate, repeat. :confused: :crying: :mad:

EDIT:

but i have no idea why it's booting itself into revocery, i thought there weren't any working links to it from aboot/abootb?
[Android Q&A, Help & Troubleshooting] ibub:
I believe that the usb connection, which also charges the phone, is acting as a constantly pressed power button. So it keeps rebooting. System is unable to boot, so it then defaults to our stripped down recovery. But I know that none of this helps. Can't stay in recovery long enough to do anything with adb. Can't use recovery without adb. Sorry brother. I don't know how to help you.
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
Recovery, and CWM- Playing Around

Thanks for your reply, and help. Not trying to connect with another Android. I just like the challenge of rooting, and getting the usability of these Android phones up above the limitations the carriers put on them. I bought the little L34 at Walmart, just to have a new toy to phreak. My daily driver is an HTC Incredible 2 on Verizon Pre-Pay. Don't ask how, but I like having a smart phone on Pre-Pay without the contract, or the extra $29 charge a month. I don't abuse the data, just like being able to have Android on my phone for games and utilities, etc. My goal with this little LG is to get the Boot Loader opened up, Get CWM Recovery on it, and switch the NAM off of Straight Talk over to Verizon. It's really just the challenge that appeals to me. Besides all that, I just couldn't resist a KitKat phone for just $30. I will post anything useful that I find in my research here in this thread. Thanks Again.