yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] jyarborough:
in the adb command path when it says /by-name/ do i insert the name of the .img twrp??? been a while
[G3 Original Android Development] teddy0209:
Nope, The command is as is, just change the CHANGEME in the name of the twrp image to the Device you're using...
[G3 Original Android Development] jyarborough:
thanks.. getting an error, cant open file for read, no such file or directory..! yet when i go through file manager i can see the .img that i put there on the root of Internal sdcard... Ideas?
[G3 Original Android Development] vesspa08:
Just flash with flashify its easier
[G3 Original Android Development] jyarborough:
adb fastboot wprked

thanks bro.. i copied and pasted(must have had a typo in there) worked.. Im now in twrp 2.8.0. backing up stock.. waiting for some custom roms and a working version of wifi tether, cause sprint is not getting no more money from me to share a signal that im already paying for.. :laugh:
[G3 Original Android Development] StreetkillnHD:
help i get this on the last part

1|root@g3:/ # dd if=/sdcard/twrp-2.8.0.0_d850-signed.img of=/dev/block/platform/

msm_sdcc.1/by-name/recovery

signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery <

/sdcard/twrp-2.8.0.0_d850-signed.img: cannot open for read: No such file or dire

ctory

1|root@g3:/ #

---------- Post added at 11:18 AM ---------- Previous post was at 11:04 AM ----------

fixed it i had to fix the directory on the command

dd if=/storage/external_SD/twrp-2.8.0.0_d850-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

i had to change where it says /sdcard/ to /storage/external_SD/

thats where the file was located.

anyways thanks all it works.
[G3 Original Android Development] thecubed:
Thanks! That'll help a lot. The problem with all these D855XX variants is that they all use different kernels. The Bump process works for them all, we just need to have the kernel and device tree from them before we can build one.

If we get a few spare moments we'll take a look and see if we can get a TWRP built for the -P variant you have.

If you could pull your BOOT and RECOVERY partitions like the above poster, that would be of much help.

Naw, Bump'ing an image is easy. Register for an account, log in, click 'Bump', upload the image, and 2 seconds later it's done!

The whole process is as transparent as possible, 99% of the work happens right in the browser!

You'll also be able to get an API key for yourself so you can use the command-line version of Bump so you don't have to upload images each time using a web interface (useful if you're building CM or anything like that).
[G3 Original Android Development] thecubed:
We're working on that ;) We just need a few spare moments from Dees_Troy to bug him to build a TWRP recovery for it, and we'll Bump and release it.

Just hold on for a few more days!
[G3 Original Android Development] dante_07:
Something Strange happens. When I was bumped my Lg, the first thing I did was create a Backup on my Sd and all goes good. Today, I wanted to create a new backup but, when I try to do in the external Sd Card, TWRP show me an Unable to create the folder error. The mos strange thing is that when I go to the backup folder, the first backup that I created the first day is not there. Maybe someone here with the same issue? Someone that have any explanation?
[G3 Original Android Development] Lennyuk:
Just put it into download mode then flash a KDZ with Flashtool 2014, root and then bump again.
[G3 Original Android Development] gpgon:
IDK the science or method, but the Bump! DEVs have found a way past the safeguards. They worked their magic on TWRP so it could be easily flashed as the recovery IMG. You don't install bump on your phone. And if you're not cooking up anything for an LG G3 just believe in magic like the rest of us.
[G3 Original Android Development] autoprime:
A locked bootloader requires that boot.img's need to be signed by the manufacturer, in this case LG, in order to boot the phone.Trying to boot an unsigned/custom kernel would fail the bootloader check and never boot due to no signature from LG. With root we have access to everything on the phone and we can change "system" part of the rom with no issues.. but for roms with custom kernels and aosp-type roms like CyanogenMod.. an unlocked bootloader is needed since we are not LG and cannot sign kernels. An unlocked bootloader doesn't care if the boot.img (or recovery.img) is signed at all. As long as it's built correctly it will load... no signature needed.

Think of Bump as doing what LG does.. signing the boot.img so that the boot.img is checked and passes the bootloader protection.

Bump gives you the same powers as having LG's official signing tools but the end user never has to worry about signing anything. When we flash stock LG roms we just flash away.. expecting them to already be signed by LG. Or we don't even think of the signing process.. but we assume.. "of course it will work." The same will be true of custom roms.. they will be pre-bump'd by the dev before release. Of course they will just work! :)

Without going into technical details, I can say that this differs from Loki because ,with loki, boot.img's could not be as easily pre-patched for the end user. If you were on a Sprint G2 with ZV7 firmware for example... your Loki'd boot.img would need to be patched for ZV7... and it would not work on ZV8 or any other Sprint firmware. So Loki always had to be patched on-the-fly due to people using different firmware. Was still a great option and not hard to work with.. but many inexperienced users had issues understanding the patching process... or had issues manually patching.. people would swap around bootloader stacks and it got sort of messy. With Bump.. having to worry about which firmware you are on is not an issue.

At this point there is nothing that can't be run on the G3... as long as the development is there (once the Bump website is released for developers of course).

And for anyone thinking of taking an OTA.. please read my thread here on how to update manually to keep root/bump in the future without any worries.

http://xdaforums.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412

Of course you can always just not update at all.. but for everyone who wants to try the latest official LG software.. or modem or kernel... read the link above.
[G3 Original Android Development] r3pwn:
You can pull it yourself via a third party app (such as Flashify) and find the backup at /sdcard/Android/data/com.cgollner.flashify/files/flashify-backup/boot/

Then you can rename the backup to "boot.img" and do whatever it is that you want to do with it.
[G3 Original Android Development] gpgon:
I'll be happy when i can be rid of carrier IQ
[G3 Original Android Development] Dougi:
hey uys,

quick question , bump is like unlocking the bootloader with the install of TWRP at the same time right ??

it's not an obligation as with just rooting , you can push a custom recovery and then flash a custom ROM .. right ??

:) :) :) thanks for the help
[G3 Original Android Development] teddy0209:
Not roms but images (e..g. recovery.img, boot.img) needs bumping...
[G3 Original Android Development] Dougi:
ok, thanks for the reply,

but with the app flashify , flashing a custom recovery is even more fast and easy, for rom's it's another story..

is there any rom's that can be flashed with bump at the moment ??
[G3 Original Android Development] Lennyuk:
Any rom that uses a stock kernel can be flashed at the moment, the only things you cannot flash are modified kernels/custom kernels (boot.img), to flash these we have to wait for the Bump! procedure to be released so the developers can bump their stuff ready for us to flash.

when its bumped end users will not have to do anything other than flash in the same way we always have done.
[G3 Original Android Development] Dougi:
ok that means that i don't even have to root, to flash a custom recovery or custom rom's or a custom kernel : with aroma not bump
[G3 Original Android Development] Lennyuk:
I think you are confusing yourself

You need root to flash Bump! - all Bumps is is a specially modified TWRP - modified in such a way so it can flash things on the G3.

Once you have TWRP you technically don't have to keep the device rooted, or can flash an unrooted rom, if you so wished.

Aroma is not an app, it is an installation method that requires a recovery such as TWRP (which is Bump!) to install.
[G3 Original Android Development] Dougi:
Correct me if i'm wrong, i can flash custom rom's , kernel's , if i root my phone and with a custom recovery that i can install with flashify.

i'll wait to see more with the bump thing
[G3 Original Android Development] Lennyuk:
If you have root you can flash a custom recovery with flashify (although I strongly recommend you learn how to do it properly with ADB). The only recovery that works with the G3 at the moment is TWRP that comes with Bump!

From TWRP you can flash customs roms and kernels. In order for the G3 to accept anything that includes a custom kernel the kernel needs to be modified by the developer (not by you), this is something that in the near future all files will be so you won't need to even think about this step, but right now the process for how to 'Bump!' boot images is not yet public so you cannot yet flash any custom kernels.

Roms are fine, they will either be pre-bumped by the developers (when made public) or use a stock kernel anyway, so you can just flash these like you would with any other phone.
[G3 Original Android Development] autoprime:
yes! as [MENTION=4214526]skeamznz[/MENTION] has answered.. do not take OTA's if possible.. if you want to update do so manually.

to fix your exact issue of getting stuck in TWRP after OTA see my thread here: http://xdaforums.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
[G3 Original Android Development] autoprime:
to take the bounty and run.. that would suggest that more than 1/3 of the bounty was paid out. lol.

thank you to 25% of you that kept your word on pledges. and thank you to those who did not pledge but donated after the release. seriously, it's much appreciated by everyone on the team. I assume the remaining 75% are waiting for the Bump site to go live? :D

And it's funny that this thread sees the most complaining... but this specific thread is for all the models that had no part in the bounty... and is where we are seeing the least amount of donations. And no... this dev work isn't about the money.. but when people wanna bring money/bounty into the convo.. I have no issue being transparent. And again... thank you to those of you who did not have models part of the bounty and still chose to donate.

as for the hold up on Bump site... building a brand new site to handle everything takes time. the onslaught of attacks from China after the mention of Bump has increased drastically... and once the Bump site launches will only attract more attacks. I assume that no one is considering all the server protection and backend work that is required to properly defend the server without ever going down from all the DDOS attacks and everything else going on. Plus database management... UI coding... backend coding..

Also, there is lots of dev work going on behind the scenes in regards to AOSP... which you'll all cry about anyway due to camera not working. Everyone needs to relax.. we have an ENTIRE LG community to take care of... it's a lot bigger than just getting you a kernel so you can overclock your G3.
[G3 Original Android Development] TonyStark R.I.P.:
As this thread becomes further away from its core, which by the way is Development, I felt it a good idea to post the following here as well.

Thank you all, I too am a member of XDA, I appreciate when things flow smooth and without needless interruption:
[G3 Original Android Development] gregbradley:
Thread cleaned,

[MENTION=535343]all[/MENTION], relax and go do something else for a bit to get some perspective
[G3 Original Android Development] gregbradley:
OK folks, this just got serious

I have been through this entire thread and deleted nearly 500 posts of "Thanks" "Great work "When is it updated?" "Donated", plenty of arguing and name calling and so many duplicate posts and other useless posts which in no way contribute to the development of Bump. Hopefully now the spam has gone people will be willing to read the thread.

Any more and I will just close this thread and infractions will follow.

Thread cleaned for the last time.
[G3 Original Android Development] saigon66:
Can i use Flashify on my D855 with this img?
[G3 Original Android Development] gregbradley:
Use search before posting!

http://prntscr.com/50g2mi
[G3 Original Android Development] radzik2908:
Can i use Flashify for restore stock recovery?

Wysłane z mojego LG-D855 przy użyciu Tapatalka
[G3 Original Android Development] walda:
You can backup and restore the current recovery in flashify.

... tapat@lked
[G3 Original Android Development] gregbradley:
Seriously?

Thread closed.

[MENTION=1157052]thecubed[/MENTION], and anyone else, PM me if you have any issues or questions.
[G3 Original Android Development] gregbradley:
Thread opened

Hopefully people have had time to assess how this thread should move forward. i.e development

I am still watching

Greg
[G3 Original Android Development] Gugus38:
May I suggest some ideas? I hope the team will be able to read this and it doesnt get deleted... this is a serious and honest suggestion for the good of the project.

- create a private subforum, for recognized rom devs only (request access via PM to the bump team), then give them the address and credentials to access the site

- keep the site address on a dynamic IP which would be communicated on this private subforum periodically

99.99% of the people here wont actually need the bump site, only developpers will !

I am no expert, but wouldnt this avoid the security/DDOS issues? (if you dont know the address, you cant attack it...)
[G3 Original Android Development] u1988:
[MENTION=1157052]thecubed[/MENTION] [MENTION=6053822]IllegalArgument[/MENTION] [MENTION=2413393]Shelnutt2[/MENTION]

Hi,

there is any reason to keep G3 ver. update I'm afraid the LG will block soon Bump to prevnt Unlock the bootloder...

like they block Stump in L/M Ver. (D855) maybe even PurpleDrake soon?

So then we all can't flash custom roms untill the next Bump if there will be any more .. ?

https://docs.google.com/spreadsheets/d/1hs0qlcGP80gl9wC0r9bs0AWMD-1D9iGgC9ulCG9roMs/edit#gid=0

Thank you for the great job so far:good:
[G3 Original Android Development] paratox:
HERE IS THE SOLUTION! also made by our guru autoprime!

and the second thing you need is patience. therefor i have no link for a howto. you have to learn it on your own. :P
[G3 Original Android Development] thecubed:
Thanks for the suggestions - however we've got this covered. The servers where the Bump site is hosted are very secure, and are connected to a rather large internet pipe. A DDoS would merely be a drop in the bucket compared to the amount of traffic we currently do a day. (Codefire's downloads site pushes around 60-80TB per week and on average we sustain one 6Gbps DoS attack per day without any affect to the systems)

We haven't released the Bump site yet because we're working on what to do if LG patches this - we're really concerned with causing accidental bricks, so we're holding off for a bit until we get a feel for what LG is working on.

Please don't take any OTAs. Consult [MENTION=2684188]autoprime[/MENTION] 's helpful thread for instructions on how to roll your own OTA without losing root or having your bootloaders upgraded.

Thanks!
[G3 Original Android Development] u1988:
Thank you!

This one,right?

http://xdaforums.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
[G3 Original Android Development] mnurolcay:
Looks like there's an updated twrp for d855, do we have a bumped one?

http://teamw.in/project/twrp2/262
[G3 Original Android Development] jaythenut:
im sure lg dont care about bump with 10 million g3 sold and way less then 1% root and have bump twrp

why would they spend the money patching it i just cant see it myself
[G3 Original Android Development] ticiano_arraes:
They already patched the stump and ioroot in some versions so they do care. And care enough to patch downgrade option too
[G3 Original Android Development] dmeinder:
I think that waiting longer to get a feel may be inadvertently causing the concern. If bump site was released, and all that are rooted we're on custom roms....like aosp, they can't patch. So the longer the wait, the more chance for fw upgrade patches.

Also lg has openly admitted that they will eventually release g3 boot loader unlock, therefore I'm guessing the previous patches mentioned were just a fluke.

Also why can't we package a working bumped fw in order to downgrade, then install custom roms in the event of lg patch......sorry but it just doesn't make sense.
[G3 Original Android Development] _Infamous_:
I dont understand why the wait for bump, if lg is going to patch it, it wont make a difference since most of us wont update our phones and most of us will be on aosp roms. Maybe its time for me to move on thanks. Is bump really fully operational so confused.
[G3 Original Android Development] dabug123:
we all have appreciation for what you have done man but I can't think of any custom ROM that gets ota's .I also know bump twrp is taking ota for a reason..At the end of the day any person who roots takes on the responsibility of reading instructions.. Bump being released today or next year will always have possibility of being patched..lg already has twrp bumped its public,so please sir let the community enjoy custom ROMs or all the hard work =lg winning !
[G3 Original Android Development] ViruuZ:
+1 for dabug, [MENTION=1157052]thecubed[/MENTION]: please launch bump for all our G3 owners...
[G3 Original Android Development] suljo94:
It is eventually team codefire their choice, but releasing it now without having an fail save(if lg patches it) could result into people not being able to root and unlock boot loader when lg releases an update for the people that already rooted/unlocked this wouldn't be a problem but for people that haven't bought the phone and are planning on buying it this is a huge problem. not to mention the fact that lg with their strict anti-rooting/unlocking policy might do something that makes sure the android lollipop version won't boot on rooted devices(maybe a check), I know that this is a bit paranoid but with lg you never know, so let the team take their time and when they are convinced that lg won't be a threat they will release

Extra: team codefire could open there bump methode to devs by letting them pm there boot images and the team bumping them(after checking credentials of course):cowboy:. not sure if there is a signature check/md5 check on kdz files(download mode) but you could try altering the version number of an older kdz file in order to trick the bootloader thinking that it is an update instead of a downgrade

extra extra: don't write +1 this isn't google plus either write somthing constructive or hit the thanks button onder the ppost you like because admins will close this thread down again if people don't start following the rules

if you have something to say about the extra-extra-part do it via pm because experience has thought me that somebody will probably start arguing with me now because of the extra-extra-part.

haven 't you heared lg won't release, it was just an e-mail in order to stop people asking the same question over and over again, also they never publicly anounced it, it was just an e-mail to a dev
[G3 Original Android Development] r3pwn:
That's odd. CyanogenMod initialized repositories (haven't filled them yet) for several G3 variants... Without the actual BUMP! method available, this seems rather strange...
[G3 Original Android Development] timmytim:
They may have:

A, found the same exploit and are going to use it to bypass the bootloader themselves.

B, found the BUM'd TWRP source somewhere and figured it out for themselves.

C, found out something that we dont know. Maybe Team Codefire has released the method to CM/PA/AOKP/etc.

D, got tired of waiting and decided to intialize repos for attention :p

Either way, something good is going to come soon!
[G3 Original Android Development] r3pwn:
I'm betting they're just placeholders for now...
[G3 Original Android Development] timmytim:
That, and it's still a little buggy. :eek:
[G3 Original Android Development] thecubed:
We're working with the teams to ensure Bump integration into their build process through our API before we release the whole shebang.

With that said, though, we're still waiting a bit before releasing Bump into the wild. We don't know what this next OTA is going to do, and we'd like to ensure we have a handle on it before we give the community a tool that they could potentially use to brick mass amounts of phones.

Remember here: if we go and just say "screw LG" we're going to make them hate us - which is not our goal. Releasing a tool that bricks users phones after an OTA accidentally, ergo driving up their repair costs, is not in our best interests.

If the OTA comes out and Bump is patched, we'll figure out how it's patched and make Bump work with it.

Regarding OTAs - just flash TWRP, and you won't be able to take an OTA for the most part. You'll boot to TWRP and the update will fail (or so it would seem). Us waiting to release a Bump tool does not bother anyone who wants to ensure their device remains unlocked. Simply flash TWRP and disable OTA and you're good to go. There's no magical clock hanging over your head here for "time left to unlock".

Also, in regards to everyone PMing me asking for me to Bump things for them:

Please remember that I am not a robot, I also have a day job. Private messaging me and asking "hey man can u bump dis 4 me?" then not linking your image, or disconnecting from IRC shortly after asking does me and you no good. I cannot read your mind, or download from a magical URL that I do not have ;)

Secondly, we're trying to ensure proper trust here - what I don't want to see is a 3rd party distributing a Bump'd ROM until we have the site up and figured out what's going on with the newest possible OTA efforts.

I realize this isn't a popular opinion, however we'd really appreciate your understanding when it comes to this.

We released Bump a bit too early, honestly we should have waited another 3 or so months so that it wouldn't get patched on this phone's lifecycle. Unfortunately, we got ahead of ourselves and need to sit back and think this one through before we potentially either cause issues with future devices, or make LG lock the phones down so tight that Samsung phones seem like easy targets.

Again, to everyone who's been patient and helpful - extra thanks to you guys. We've got your back, it's just gonna take some more time :)
[G3 Original Android Development] thznutz87:
Appreciate the update [MENTION=1157052]thecubed[/MENTION]! All I'm hoping for is bump to go online around the time L sources drop for building. Is that kind of the plan, sort of, maybe? [emoji88] [emoji88]
[G3 Original Android Development] CroW_D:
I agree with you I think they will wait till ota for Android l is out to be sure it won't brick the phones and it is still working.

Gesendet von meinem Nexus 5 mit Tapatalk
[G3 Original Android Development] paratox:
would it be possible to bump! tectas custom kernel?

D855-rin-1.6.img: AndroidFileHost | xda | dev host

md5sum: 7c67d2817d58941fd596e8ed16e21a5c

please please please! this would sweeten us the waiting time!

at now i need a pc every time when i want to reboot for fastbooting the image again.

it is also really stable at now so this would really be nice to have.
[G3 Original Android Development] OhMrBigshot:
As much as I appreciate the concerns, wouldn't we flash a rom which would naturally disable ota for stock anyway? Might as well let us start flashing roms. And post a warning.