yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] tschmid:
Thanks alot ???

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] tropenfrucht:
Sorry if this doesn't belong here.

Is there any chance other LG devices will get bump'd as well. Thinking specifically of the G2, so that we can use Kitkat Roms with Kitkat Bootloader?
[G3 Original Android Development] thecubed:
Wait until tomorrow and find out :)

EDIT: technically later today.
[G3 Original Android Development] if4ct0r:
You guys are awesome :)
[G3 Original Android Development] artecfs:
Great news!!! Thanks a lot.
[G3 Original Android Development] Razertje:
Wow that's great! Can't wait! Let's give our phones some AOSP love! :D
[G3 Original Android Development] ViruuZ:
Niiice! Stay currently in Liquid tethered, hope for PA/CM in the next 3-4 days :)
[G3 Original Android Development] latino147:
So, if the BUMP site is going live today + the leaked KDZ is there = it won't take long before a flashable bumped ZIP can be made with a bumped kernel so chainfires root method can be tried out?
[G3 Original Android Development] dabug123:
With a custom recovery you wouldn't need worry about rooting 5.0 you can just flash root method in recovery!
[G3 Original Android Development] behnann:
But we need root for bump?
[G3 Original Android Development] dabug123:
Well if u took an ota ,kdz ,tot for 5.0 and cant revert then you made a bad choice..Why you would risk that is crazy to me..I'm just going to enjoy flashing 5.0 on my device.
[G3 Original Android Development] :
There is a Sprint specific Bump. You can find it in the original development section of the Sprint G3 forum.

Edit:

Here is the link:

http://xdaforums.com/showthread.php?t=2900588
[G3 Original Android Development] Lennyuk:
[MENTION=1157052]thecubed[/MENTION]

You are probably already aware, however, people are reporting that TWRP no longer is accepted after flashing the bootloader from the leaked 5.0 builds.

Now hopefully I don't need to say this, but this is not after a KDZ flash, this is after people have flashed aboot, boot, system and modem manually via TWRP. (no idea why they decided they needed to flash aboot!)

TWRP then throws up the error the same as you would have expected it you were to flash an unbumped boot.img.

So it looks like whatever method you used to bump things, as expected, is indeed blocked in the new bootloader.

EDIT: Further, it appears you also need an updated LAF partition (download mode) if you are running the new bootloader - which means anyone who updated the bootloder without LAF and recovery is left with no working download mode and no working recovery mode, and unable to boot a rom.

Edit2: Xda may have its first brick as a result of these changes by LG - the guy has no rom installed and cannot access download mode or recovery, but because there are images installed in those partitions he also cannot access fastboot.
[G3 Original Android Development] hashcheck:
i can confirm i just did a CSE flash of 19H Kdz and TRWP will no longer boot. so this isnt entirely correct i believe a CSE flash of KDZ flashed any updated partitions ie aboot
[G3 Original Android Development] Lennyuk:
a CSE flash of the KDZ will replace all partitions, including recovery that is why you no longer have TWRP! my post was talking about people who took the individual images and flashed them from recovery (without replacing the recovery image!).

The new bootloader blocks the existing bump! method, therefore it rejects any currently bumped images, but also rejects the old download mode.
[G3 Original Android Development] rodrigofd:
[MENTION=2315688]Lennyuk[/MENTION], to be more precise, I did ended up with a booting rom (i.e. LG Lollipop 19h rom), thanksfully, because I flashed lollipop system,boot,aboot.

But everything else you're reporting is accurate (by the way, i am 'that' guy :eek:)
[G3 Original Android Development] Lennyuk:
haha, thanks for the input, I was trying to state what the position would become if for some reason your rom corrupted, or if you had not flashed a rom.

There is obviously a huge risk of being software bricked with no apparently way of re-flashing an image.
[G3 Original Android Development] Speedster_1:
Wow

how you holding up buddy? it's crazy but someone was sure to make the first jump. at least we have some info now on the do's and don't(s). Howz the 5.0 looking? any major issues? :fingers-crossed:
[G3 Original Android Development] rodrigofd:
It looks good, promising; however, I am pretty desperate.. Honestly, it doesn't feel as a rounded up, complete version... many lags here and there; systemui/launcher crashes for no reason (without error prompt)... and obviously, no remote chance of rooting whatsoever...

I think at this point my only chance is to return it to warranty... but without root, I can't find a way to 'mask' the fact that I tinkered with it, since the system shows Android 5 version :eek::eek:

My carrier tech support guys aren't known by their cleverness, but I have to give them some credit :p
[G3 Original Android Development] hashcheck:
Yes completely understand however i downgrade to 10m 4.4.2 rom after and rooted and flashed TWRP hotever when trying to boot recovery it stays on LG logo. I tried even fastbooting recovery bit i believe the aboot is still install from when i had 19H Lollipop rom hence no aboot downgrade
[G3 Original Android Development] don1bong:
Will be definitely making a donation this weekend, thank you very much for the hard work.
[G3 Original Android Development] muhamet:
Try starting flash tool with your phone on??I see that worked for some.
[G3 Original Android Development] suljo94:
As soon as bump is up we will just bump the new kernel and try it out on the old bootloader because if I remember correctly the 19c kernel booted fine on the old bootloader, the main problem is here that people who are new to flashing start trying stuff out and brick their phone (saw how to flash kdz or recovery won't recognize kdz way too much) '' that'' guy will probably be stuck on lollipop until someone comes up with an new root method (thought they were going to try to get stump working back because lg did a bad job on blocking it, not sure if they blocked it better now)
[G3 Original Android Development] Lennyuk:
yeah, providing the new bootloader is not required to make the new rom stable, and that won't help those people who buy the phone after the launch of the new software or send their phones for repair as they will likely all have the new bootloader.

In an ideal world we would hope that Bump! is updated to work with the new bootloder sooner rather than later, rather than what will soon be a minority of us, staying on the old bootloader for as long as possible.
[G3 Original Android Development] Speedster_1:
I see, good luck to you man. Maybe u get lucky ;)
[G3 Original Android Development] gdonanthony:
this thread will have a party later for sure :)
[G3 Original Android Development] igylan:
Hey there fellow islander! Nice to see you here. From Cebu too. haha:D
[G3 Original Android Development] thecubed:
Quick answer (I'm on my way in to work now, so can't make any release threads yet): yes, Bump is patched in android L for LG. Do NOT flash it if you wish to keep Bump. This doesn't mean Bump is dead, it's just patched as-is. Again, DO NOT FLASH 5.0/L. If you do, you will be stuck in a time vortex and I will point and make funny faces at you.
[G3 Original Android Development] keaheng:
what do you mean by that? "Bump is patched in android L but if you want to keep bump don't update to android l :confused: "
[G3 Original Android Development] muhamet:
Well lets whait for Root :)
[G3 Original Android Development] Lennyuk:
it means exactly what he said, you cannot use bump! (in its current form) if you flash the Android 5.0 builds. It sounds like they will work on fixing bump so it works in the future, but that might take ages, or it might never happen. For now you are best off staying on KitKat until a bump safe version of 5.0 is released by someone on XDA.
[G3 Original Android Development] RichiN:
There are Android L Previews out there. You shall not flash them, because you'd loose your ability to flash.
[G3 Original Android Development] keaheng:
thx men.. got it.
[G3 Original Android Development] dabug123:
[MENTION=1157052]thecubed[/MENTION] is referring to ota,tot,kdz if someone makes a 5.0 aosp your safe flash rom in bump recovery just don't mess with anything stock
[G3 Original Android Development] keaheng:
I don't know why but I upgraded to 19H yesterday still i could downgrade to 10n and bump still works. all of them were done by kdz..
[G3 Original Android Development] muhamet:
Thx for info
[G3 Original Android Development] suljo94:
In the 19c version downgrading us kind of blocked, so in the final build it probably will be patched to then you will be caught in a time vortex while I and the cubed laugh at you and make silly faces, btw I will try to bump the new kernel and try to boot that on the old bootloader if it works hallo lollipop if not Kitkat it is
[G3 Original Android Development] Galaid:
the party begining soon :good:
[G3 Original Android Development] thecubed:
Bump is released now!

Developers, you can now sign your own boot images!

http://xdaforums.com/lg-g3/orig-development/bump-sign-unlock-boot-images-lg-phones-t2935275
[G3 Original Android Development] bunchies:
Thank!! Gawd
[G3 Original Android Development] ViruuZ:
Thanks for your hard work!
[G3 Original Android Development] rosscarlson:
Cool - thanks. One final newbie question for now - this is just to root/unlock the phone and not actually a ROM to flash on it, correct? Would love to give lollipop a go but it seems there isn't a ROM for the LS990 yet. If I'm just missing it maybe point me in the right direction?
[G3 Original Android Development] KingOfDope:
Thanks for the hard work. Sadly I'm not planning to flash any roms since I am upgrading to android 5.0.

I wish teamcodefire many luck! Thank you once again!
[G3 Original Android Development] Akeel1994:
Thank you!!!
[G3 Original Android Development] :
No, with bump you may flash roms that are bumped. This is the twrp recovery for this device.
[G3 Original Android Development] ticiano_arraes:
Are you getting to fastboot? Did you try extracting the laf partition from the kdz and doing fastboot boot laf.img?
[G3 Original Android Development] if4ct0r:
He has lost fastboot as well.
[G3 Original Android Development] hashcheck:
Can confirm after flashing 20A lollipop Rom if you use the tot file on codefire site and you can downgrade Rom to 4.4 and twrp works again woohoo
[G3 Original Android Development] prcek15:
Could you be more specific, please? Where can I find that tot file & how to downgrade properly to get twrp work again? :)
[G3 Original Android Development] lossah:
idd. ^^ thought it was another error he mentioned. i was just confused. :)
[G3 Original Android Development] rederik79:
Installed without problem on my D855, now backing up my stock rom....fantastic job guys...........
[G3 Original Android Development] CroW_D:
Does this mean we can get aosp Roms to our LG g3 like cyanogenmod?

Gesendet von meinem Nexus 5 mit Tapatalk
[G3 Original Android Development] pRo_lama:
Yeah.
[G3 Original Android Development] ManOnTheMoon:
If anyone wants to know, yes you can use Flashify.
[G3 Original Android Development] CroW_D:
But guys we must wait till developers support the LG g3 i am right ?

Gesendet von meinem Nexus 5 mit Tapatalk
[G3 Original Android Development] ThePeloto:
Working in D855, great work

Enviado desde mi LG-D855 mediante Tapatalk
[G3 Original Android Development] drmspidi:
I thinks this can make thing easier !!

https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
[G3 Original Android Development] Jagdish84:
Rebooting to recovery works?

Sent from my caseless LG G3, because I believe in myself
[G3 Original Android Development] Pfeffernuss:
Like... a... charm! :victory:
[G3 Original Android Development] Cuzz1369:
Yes. But the wait won't be long. The T-Mobile version has booting aosp. I know my CandyKat team has already started work. Shouldn't be long.
[G3 Original Android Development] Cuzz1369:
You can just install as recovery using flashify?
[G3 Original Android Development] CurtisAndroid5:
Yeah. I backed up the stock kernel and recovery img just in case though. Worked perfectly though.
[G3 Original Android Development] Cuzz1369:
OK it flashed fine. I can reboot to recovery but when I try and backup is says I only have 905mb free. I have 14gb.
[G3 Original Android Development] CurtisAndroid5:
I haven't tried to backup yet as I'm at uni then I'm on the train straight to my girlfriends so can't help you there. Im positive TWRP has a storage setting so you'll have to change it to your micro SD instead of the internal storage
[G3 Original Android Development] nobnut:
I just backed up to the external SD just fine.

It reports my internal and external free space accurately also.
[G3 Original Android Development] hrvd:
Done whithout problem with adb.

Just one question, is it safe after that to flash à kdz ?

Envoyé de mon LG-D855 en utilisant Tapatalk
[G3 Original Android Development] john0699:
If we use Flashify, is the bootloader unlocked to??
[G3 Original Android Development] Cuzz1369:
Ya for some reason it was trying to make a 10gb backup...I have it working now.

---------- Post added at 11:47 AM ---------- Previous post was at 11:46 AM ----------

I don't think the bootloader is unlocked either way. Its more of a workaround.
[G3 Original Android Development] CroW_D:
But it is a huge jump forward guys dont complain the time will bring il be sure

Gesendet von meinem Nexus 5 mit Tapatalk
[G3 Original Android Development] MMarkkk:
D855

Download KDZ http://xdaforums.com/showthread.php?t=2791761

Flash http://xdaforums.com/showthread.php?t=2785089
[G3 Original Android Development] :
Can I flash this with Flashify, like a custom recovery?
[G3 Original Android Development] TonyStark R.I.P.:
You can follow along with this

[YOUTUBE]k7a5hnefnnM[/YOUTUBE]

:good:
[G3 Original Android Development] hippo2s:
Anyone experienced Backup to externalSD files being deleted?

Hi Guys,

Successfully got TWRP on D855, installed PA Rom etc.

During the process I had created backups of original stock rom (just before installed PA), then also took a backup of PA+GAPPS, backed up both of them to External SD.

After like an hour I went back to TWRP to check out what is new in 2.8.0.0, when I noticed that the Restore function did NOT list my backups on external SD. I went back into PA and checked with ESFile explorer and saw that the two backups were no longer there on ExternalSD.

I then tried a third time to backup to ExternalSD, and saw as soon as I go back into ROM, the folder with device name was no longer there again! (so did not list in Restore list).

I then tried a fourth time to backup to Internal memory, then made a copy (in essence a 5th backup) using the file manager in TWRP to External SD, and it now say Could not create folder path. The backup on internal memory is still there after multiple reboots & lists in Restore menu

Any ideas? I did triple check the 1st post and did thread search. without finding anything...surely you guys are backing up your stuff!? :confused:
[G3 Original Android Development] silvbm:
Got the same problem, but only backups from today were missing, others were fine. What fileformat is your sd card? Mine was exfat, which isn't officialy supported by TWRP. I reformatted to fat32, and will see if the problem happens again.
[G3 Original Android Development] hippo2s:
Yeah, my microsd is also formatted to exfat. Mine is a 64GB card and I heard FAT32 is inefficient (hence windows formatted it to exfat initially) at size larger than 32GB. I also want to save files larger than 4GB for the 1080p movies I watch... guess will have to live without them.

Will format to FAT32 too and test.
[G3 Original Android Development] autoprime:
use ext4. as long as you're keeping the card in the phone it wont be an issue as MTP doesn't care what format the card is in and will always mount it.

ext4 has no 4GB limit
[G3 Original Android Development] hippo2s:
Thanks for the advice, my machines are Win7/8 so would prefer not to use ext4 as I occassionally pull the microsd and transfer files via an adapter in Win7/8 - Will try FAT32 and see for now.

From my research file format doesn't affects performance much so it's fine.

UPDATE: Backup stays put after formatting to Fat32. So looks ok so far.
[G3 Original Android Development] quadjacks:
For restore failed. Is there step by step instructions on backup and restore somewhere?
[G3 Original Android Development] ryanbg:
[MENTION=2684188]autoprime[/MENTION] [MENTION=1157052]thecubed[/MENTION]

Is Bump based off of CVE-2014-0973? If it is (and the same one Amazon devices were vulnerable to), I am thoroughly floored as to how LG R&D let that one slip by. It was disclosed well before launch, by more than two different researchers. I wonder if LG is hiring...
[G3 Original Android Development] sielski:
Is this work with Androidnow 3.1 New lolipop stock rom?
[G3 Original Android Development] thecubed:
No, Bump is not based off of anything else out there.
[G3 Original Android Development] :
Sorry, wrong thread. Please delete this post.
[G3 Original Android Development] ryanbg:
You guys did a nice job!
[G3 Original Android Development] StephenMSmith:
I'm confused. If I flash this TWRP recovery, can I still stay on stock ROM? If I get an OTA update notification, can't I just reflash the stock recovery before rebooting the phone? Or does this modified bootloader cause issues w/OTA updates too?
[G3 Original Android Development] p70shooter:
Yes you can stay on stock rom.

About ota notification yes you can just reflash the stock recovery and all will be fine. The only issue is that in taking an ota it might block root and block bump.
[G3 Original Android Development] StephenMSmith:
Well that's always a risk, but peeps here always figure out how to get it back. I installed it and works great. All I really want is nandroid backups, so I'm happy user.
[G3 Original Android Development] richsapf:
I followed all directions to a tee but after last command prompt I hit enter and get this: cannot open for read: No such file or directory.

I edited the CHANGENAME to vs985

I downloaded most recent adb

I can see .img file on the internal storage

Should I just install it, .img, using flashify ot twrp(that just keeps force closing though)

can't I just install a .zip rom from my computer?.. or is there a .tot or .kdz that I KNOW I can flash..lol... 3 days now on one issue..whew. Im not giving up either. I just want to get 11C stock Deodexed, thats all.
[G3 Original Android Development] bangprovn:
Sorry for OT,but can I get your attention sir ? I'm trying to port Bump! to another LG Device which called LG-V400 and after using Bump!, I have managed to get to the fastboot mode, but i has been stucking there. No option to boot into recovery. Can you help me building the modified TWRP for it? Thank you very much !
[G3 Original Android Development] tissot:
Yes
[G3 Original Android Development] StephenMSmith:
OK, after reading the OP, I downloaded the signed TWRP from here: http://downloads.codefi.re/thecubed/lg_g3/bump/

but I did NOT run these ADB commands:

adb shell

su

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery

dd if=/sdcard/twrp-2.8.0.0_CHANGEME-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

twrp-2.8.0.0_d850-signed.img installed just fine using Flashify. So I'm confused about the ADB commands listed in OP. What am I missing by not executing them? What do they do exactly vs. just installing the signed TWRP and nothing else?

All I want to do is nandroid backups, which worked great using this TWRP. No ROMs.
[G3 Original Android Development] MicroMod777:
I bumped the twrp for the G2, which it bumped it. But then when I followed the OP directions to flash it, it will not go into TWRP. Is bumping something that will only work for boot images and you guys have to make the customer recovery bumped?
[G3 Original Android Development] Mahapederdon:
Your good to go. Flashify gets the file installed just the same.

---------- Post added at 06:41 AM ---------- Previous post was at 06:41 AM ----------

As far as I know this does not work on g2 at all.
[G3 Original Android Development] StephenMSmith:
OK, so then I could have applied the same signed TWRP using fastboot: flash recovery twrp-2.8.0.0_d850-signed.img, as well? If so, then why the complicated shell commands instead of just using fastboot?
[G3 Original Android Development] teddy0209:
Maybe because there is no fastboot as it is in our device...
[G3 Original Android Development] StephenMSmith:
Doh. Sorry, just got my G3 a couple days ago. I forgot it doesn't have a accessible bootloader.
[G3 Original Android Development] Lennyuk:
To access fast boot you would have had to do some lounger commands anyway, to wipe the LAF image.
[G3 Original Android Development] deathsquad737:
So your saying you can wipe the laf.img and get fast boot?cause I know on the vs985 fastboot was removed

A.L.B/E.B.B
[G3 Original Android Development] p70shooter:
Yep on the d855 at least, you can remove laf.img and get fastboot.
[G3 Original Android Development] gado45:
adb shell

-bash: adb: command not found

I have this error on OSX yosemite. Tried on windows cmd didn't worked for me either same error. what did I do wrong?
[G3 Original Android Development] niksssss:
Is my warranty lost after I do this ? Or I can go back to full stock without any trace of my phone being unlocked with Bump.
[G3 Original Android Development] :
I would like to ask a question purely out of curiosity.

According to TeamCodefire's website, "The only thing our server does is generate a signature - all other aspects such as generating the SHA1sum and appending it to your image" and this is the regular electronic signature process I think.

So have they got LG's secret key somehow?
[G3 Original Android Development] suljo94:
[MENTION=2684188]autoprime[/MENTION] quick question and observation:

question: will downgrading the d85510l bootloader to d85510e brick your device?

Observation: in the d85510l bootloader lg made some changes which prevent you from using tectas his kernel(demigod shows up). but people who never installed d85510L dont have this problem, now the fun part, I think lg made the d85510l bootloader undowngradeble because everybody who flashed 10L that goes back to 10e still gets the same error while people on 10e who have never flashed anything upwards from 10l use the kernel without a sweat
[G3 Original Android Development] :
Well, there may be a bug in signature checking, or key may be short and can be bruteforced easily (Reeeealy unlikely...).

The other possibility is best left undiscussed, IMHO.
[G3 Original Android Development] Robin2:
It means that adb is not installed on your pc. Check the topic on installing adb.
[G3 Original Android Development] deathsquad737:
[MENTION=2684188]autoprime[/MENTION] I took one of the twrp images and bumped it then installed it a screen popped up said kernel crash lol had some other righting but I panicked and shut my phone down but it rebooted and all is good any thoughts?

Sorry to the mods I see there is a q&a forum sorry for the misplaced post.

A.L.B/E.B.B
[G3 Original Android Development] Cuzz1369:
I compiled cm without error for the d852. Bumped my boot.img and renamed it from bumped-boot.img to boot.img. It installs fine but when I go to boot I just get "[740]fastboot mode started" any clue?
[G3 Original Android Development] Rudolpht:
Do this, assuming you are rooted:

Get Terminal from the Playstore.

Hand type in or cut and paste in the commands.

adb shell

su

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery

dd if=/sdcard/twrp-2.8.0.0_CHANGEME-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

You may get an error on the 3rd line, but keep going.

Flashify again and you should be good to go. (this worked for me).