Hello,
A few days ago I wrote a new implementation inspired by the work of CyboLabs and Codefire that in harmony contributed for the creation of Open_Bump. Basically I rewrote Open_Bump using POSIX C to run directly on LG G2 or any compatible device with Open_Bump. So now you can bump any kernel or recovery using the target device, validate images to know if they have been bumped and other things.
The source code and binaries for Linux and Android found at: https://github.com/ferreirawax/cbump
FAQ
What is POSIX?
POSIX is an API for Unix-like systems (Linux, Android, etc).
But what are the benefits of this?
Considering the benefits already mentioned above. Other example, if you are a developer, you will probably will get rid of Python or even get rid of everything and create a script to bump the Kernel/Recovery on the flash time.
And why the original developers did not do it?
I do not know.
I do not know how to use it.
See the readme in the link above.
Click to expand...
Click to collapse
Cheers!
It will be useful for developers, thanks for the effort
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
wulsic said:
Nice work, I guess the reason why it remained in Python was because it was just working fine once you installed python on your linux environment. And the only way to bump on android was what was implented in multirom to first unloki the boot.img and then sign it with the LG key.
Just some questions:
so if you use cbump with -f then it will check or it's bumped and then flash it but if it's loki then it will not flash it and it will only say that it's not bumped right?
And with your usage:
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdin]
Is it both stdin or must the last one be stdout?
Code:
usage: cbump [-f|--flash] [-a|--avexado] [stdin] [stdout]
Also could you perhaps explain a bit with how to use it on android, like where to put it and those things a little bit more explaination.
Just asking as I won't check the complete code now and as I am tired and I am still a newb at this level of writing codes etc but it look's :good: but still, I am not sure how much we will use cbump in Android and perhaps also in multirom but I'll check it out perhaps tomorrow or later more. Still thanks for your contribution:good:
Click to expand...
Click to collapse
Hello,
I know that Python works well, but Cbump was thought to be portable. I did not even know about MultiROM, I checked now and discover that he used the unrepresentative signature in many standard unicodes which is not an elegant method. About -f, yes. I had not thought about Loki up because I have no reason to use Loki instead of Bump (Without disregarding the Dan's splendid work), Maybe I can add support for Loki verification later. About streams take look here, I'll add more information/instructions in thread soon.
Thanks.
@ferreirawax
Very cool work. Can't wait to expand on this and find more use cases!
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Sj12345 said:
how I know if my devices is bump supported? I know it works in G2,G3 on lollipop 5.0.2, right? now I own a G flex 2 on 5.0.1, can this work?????
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You're in the WROOOOOONG thread, buddy...
jeebspawnshop said:
You're in the WROOOOOONG thread, buddy...
Click to expand...
Click to collapse
haha,no I dont buddy, LG exploits can be used for all LG devices (we have root on g2,g3,g4,gflex,gflex2 with the SAME EXPLOIT) He understands how the exploit "bump" works... so I need help from HIM to try this in my devices
....... thanks
From Readme.txt
"The flash function uses MSM identifier to detect partition block, Tested only on LG G2, Probably works too with LG G3 and others LG devices powered by Qualcomm."
Sorry its me again
I have a lot of question???? can you help me? @ferreirawax
I have two partitions on my phone (aboot and boot), which should be used???
I will dump the correct partition with
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/data/media/0/boot.img
then use your tool like
Code:
cbump /data/media/0/boot.img /data/media/0/cboot.img
flash partition with
Code:
dd if=/data/media/0/cboot.img of=/dev/block/bootdevice/by-name/boot
and try to booting up....so if this boot up means it works?
and my next step will be make a TWRP recovery???? I will be carefull cause My phone doesnt have kdz or tot for go back to stock... I only have my own backup from dd
@Sj12345 this is a rewritten version of open_bump so if bump didnt worked on your device this won't work either. Lollipop isn't working with bump only jellybean and kitkat as far as I know. Also I suggest before doing these things to learn what the partitions etc are before you will hardbrick yourself. Aboot is the bootloader. Boot is the boot.img so that's the kernel.
It probably will result into an security error.
Sent from my LG-D802 using Tapatalk
One word: COOL
This is awesome, thank you so much. Now we can use .zip to bump and flash, just like loki method. Will make testing things SO much easier. Won't have to re-bump the image every time
You the man!
Now if u can get one for the G4 n get the $10,000 bounty!
Sent from my LG-H811 using Tapatalk
5 Star For You [Excellent]
Testing Cbump to our devices
Awesome Tools! :good:
It should help multirom?
Inviato dal mio LG-D802 utilizzando Tapatalk
Edited
Sorry for the bump (ehehe), but does anyone have a mirror of this? Nvm, solved!
https://github.com/dorimanx/cbump
Related
Hi all ,
I want to share script for bump kernel.I have tested with D80230a/30d is working.
the original script from LG G3 thread [GUIDE][ROOT][BUMP][TWRP] Imageprep: Auto-script to Add Bump+TWRP for Rooted LG G3.The original script for install TWRP+Bump kernel for LG G3 .I modified the script for bump only
In bump.zip contain
- boot_bump
- boot_original
- tmp
- bump.sh
Instruction
1. Extract boot.bin from kdz firmware
2. Unzip bump.zip to bump folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Put boot.bin into boot_original
4. copy bump folder to /sdcard/bump
5. Install Terminal Emulator app from play store
6. Open Terminal Emulator then use a command
$ su
# cd /sdcard/bump
# chmod 750 bump.sh
# sh bump.sh
Click to expand...
Click to collapse
PS.
- $,# is a command prompt
- After $,# is a command
After script have done,You can see bump kernel at
/sdcard/bump/boot_bump/lollipop-bumped-boot.img
All credit
@topet2k12001
http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
@Skin1980
http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Thank you
All credits for @Skin1980 http://forum.xda-developers.com/showthread.php?t=2957648 and his live bump script
6ril1 said:
All credits for Skin1980 http://forum.xda-developers.com/showthread.php?t=2957648 and his live bump script
Click to expand...
Click to collapse
OK! ,Thank you.
Nice!
Happy modding!
6ril1 said:
All credits for @Skin1980 http://forum.xda-developers.com/showthread.php?t=2957648 and his live bump script
Click to expand...
Click to collapse
somboons said:
OK! ,Thank you.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yup, @Skin1980 is the original creator of "live bump + Sharpening Mod". Used with his permission and duly credited in my thread as well.
Works great!!! Tested on boot.img extracted from 39a kdz. Bumped good.
When you gonna make this Windows based????
MicroMod777 said:
Works great!!! Tested on boot.img extracted from 39a kdz. Bumped good.
When you gonna make this Windows based????
Click to expand...
Click to collapse
Next step I'm making tool for this run on windows but need connecting phone.
MicroMod777 said:
Works great!!! Tested on boot.img extracted from 39a kdz. Bumped good.
When you gonna make this Windows based????
Click to expand...
Click to collapse
There is already a bump-tool for windows in G3 forum
http://forum.xda-developers.com/lg-g3/general/bump-window-version-t2956829
tropenfrucht said:
There is already a bump-tool for windows in G3 forum
http://forum.xda-developers.com/lg-g3/general/bump-window-version-t2956829
Click to expand...
Click to collapse
@MicroMod777
Have you tried ? I have ued but not work for me.
Just drag and drop the boot.img (or recovery.img) on the bump.exe in windows explorer.
Worked for me on win7-64bit.
somboons said:
@MicroMod777
Have you tried ? I have ued but not work for me.
Click to expand...
Click to collapse
Last time I tried it wouldn't boot, but yours did.
Hi, question to OP:
so with this patch, we can use LP bootloader? or still must use KK or JB?
i see in script that kernel is unpacked, then packed back.... question is why?
did you know that BIN and IMG is the same thing?
just rename *.bin to *.img
it's will be written the same to raw partition.
any way. well done. will be needed soon for my builds.
dorimanx said:
Hi, question to OP:
so with this patch, we can use LP bootloader? or still must use KK or JB?
i see in script that kernel is unpacked, then packed back.... question is why?
did you know that BIN and IMG is the same thing?
just rename *.bin to *.img
it's will be written the same to raw partition.
any way. well done. will be needed soon for my builds.
Click to expand...
Click to collapse
I'm waiting your work.I think you will work to make kernel for G4 too when it commig
this is not my work, bin,img is a same.I don't change main code of owner.
sorry for the noob question....
if we bump the lollipop kernel,can we use earlier custom roms directly in LP bootloader?
or it is needed to downgrade the bootloader?
Varun800 said:
sorry for the noob question....
if we bump the lollipop kernel,can we use earlier custom roms directly in LP bootloader?
or it is needed to downgrade the bootloader?
Click to expand...
Click to collapse
Need to have kk or jb bootloader.
LP bootloader will not boot any custom kernels or recovery.
Sent from my LG-D802
https://raw.githubusercontent.com/berryman13/Open_Bump/master/open_bump.py
Here's a fork I took right before it was taken down.
Not that it'll be of much use. Still cant boot LP bootloader, meh..
---------- Post added at 03:16 AM ---------- Previous post was at 02:44 AM ----------
dorimanx said:
Need to have kk or jb bootloader.
LP bootloader will not boot any custom kernels or recovery.
Sent from my LG-D802
Click to expand...
Click to collapse
Yeah. That's really lame, such a bummer.... I took a look at the code myself, and it seems to want to support lolli but doesn't work with lollipop bootloaders/recoveries/kernels. At least on my D800.
---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------
dorimanx said:
Need to have kk or jb bootloader.
LP bootloader will not boot any custom kernels or recovery.
Sent from my LG-D802
Click to expand...
Click to collapse
Yeah. That's really lame, such a bummer.... I took a look at the code myself, and it seems to want to support lolli but doesn't work with lollipop bootloaders/recoveries/kernels. At least on my D800.
Can this be modified to bump a twrp recovery.img?
MicroMod777 said:
Can this be modified to bump a twrp recovery.img?
Click to expand...
Click to collapse
No need to be modified it also works for recovery images. Ofcourse for JB/KK BL
@berryman13 It won't be taken down, especially after all those discussions it probably won't make any difference if it would be taken down as it's already wide on the web.
https://github.com/CyboLabs/Open_Bump/
wulsic said:
No need to be modified it also works for recovery images. Ofcourse for JB/KK BL
@berryman13 It won't be taken down, especially after all those discussions it probably won't make any difference if it would be taken down as it's already wide on the web.
https://github.com/CyboLabs/Open_Bump/
Click to expand...
Click to collapse
I have something even better! You know how CyboGenik or something posted this originally on xda and there was a huge explosion? Everybody was so pissed. Then he removed a few keys from it and republished the entire branch,
I got a fork of it early though
like immediately; before it was rebased. Compare the code, there's additional keys. PMing you.
berryman13 said:
I have something even better! You know how CyboGenik or something posted this originally on xda and there was a huge explosion? Everybody was so pissed. Then he removed a few keys from it and republished the entire branch,
I got a fork of it early though
like immediately; before it was rebased. Compare the code, there's additional keys. PMing you.
Click to expand...
Click to collapse
Interesting. Do these additional keys help bump on LP? On our LG G Pad 8" v480 and v400 we are completely locked down on LP. We can even unlock our tablets which does nothing while on LP. I've bumped twrp.img and it still give security boot error. Maybe your additional keys can help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It have been about 2 years, I finally get a U11 plus to make TWRP device tree with working decrypt function.
Source: https://github.com/sabpprook/android_device_htc_ocm
Please download latest TWRP build in following link.
[Android 8.0]
twrp-3.3.1-0-ocm_171001.img
twrp-3.3.1-0-ocm_171201.img
twrp-3.3.1-0-ocm_180601.img
twrp-3.3.1-0-ocm_180901.img
twrp-3.3.1-0-ocm_181001.img
twrp-3.3.1-0-ocm_181101.img
[Android 9.0]
PS. watch out the last 6 digits at the filename, it must equal to your system's android patch level. e.g. 2017-12-01 (Dec, 2017) = 171201, otherwise TWRP will not decrypt data partition.
PS2. U11+ already get Android Pie update, but this update will break data decrypt function in TWRP recovery.
@nkk71, thanks all the works you've done for us.
Thank you very much!
https://i.imgur.com/71t8xrY.png
https://i.imgur.com/qebNB0C.png
https://i.imgur.com/ubxYZsN.png
https://i.imgur.com/gsbaG2K.png
https://i.imgur.com/xIW8llN.png
https://i.imgur.com/Fzrdhwt.png
Awesome!!
yay. now to get more dev support behind this!
excellent! Please, try to put up a github repo for it, if not already
Hopefully it works fine.
If HTC rolls out kernel sources, I might try some blind development, as I don't have the device, but wanna support it.
Should you need to unlock the official htcdev before they can put?
mapleshadow said:
Should you need to unlock the official htcdev before they can put?
Click to expand...
Click to collapse
Yes, unlock then you can boot it.
Thanks for this! Going to try and get it up and running later today - Need to unlock the BL first.
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Any idea what's going on?
aurelienlux said:
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
Any idea what's going on?
Click to expand...
Click to collapse
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
http://featuresunlocker.com/root-install-twrp-recovery-htc-u11/
Yet sent from my amazing silver U11
jauhien said:
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
Yet sent from my amazing silver U11
Click to expand...
Click to collapse
I didn't flash since I wanted to test it out before using the fastboot boot command recommended in the original post. However this does not seem to work. I wanted to get twrp running so I could use magisk for root
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
aurelienlux said:
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
Click to expand...
Click to collapse
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
tbalden said:
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
Click to expand...
Click to collapse
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
Click to expand...
Click to collapse
OK, that's very professional. :good:
Just others be aware that you should make sure you have a way backwards.
aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
Click to expand...
Click to collapse
That would be fantastic and very good of you if you could share it. Many thanks!
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
sabpprook said:
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
View attachment 4342230
Click to expand...
Click to collapse
Looks like you're building in android 7.1 for Oreo decrypt, won't work without the needed sepolicy changes and plat/non_plat contexts, please check the current gerrit updates for the standard HTC U11:
TWRP vold_decrypt patch: https://gerrit.omnirom.org/c/26652/
EDIT2: U11 Oreo decrypt device tree changes needed for a 7.1 build: https://gerrit.twrp.me/c/2756/
If you end up with decryption successful, but it doesn't actually mount /data, then you may even need an updated kernel https://gerrit.twrp.me/c/2761/
which is what we needed. EDIT: Obviously that's a U11 kernel update not a U11+ one, so don't try to use that kernel
Some things will still get changed. I also recommend you build in real DEBUG mode, the straces have much more info than a log or dmesg. by using TW_CRYPTO_SYSTEM_VOLD_DEBUG := true
Prot02018 said:
That would be fantastic and very good of you if you could share it. Many thanks!
Click to expand...
Click to collapse
There you go: https://drive.google.com/open?id=1nkzK_wbSgC6HSlOsNqOc79f94p7v_3wz
That's version 1.05.400.13. I managed to decrypt it successfully using the latest RUU Decryption Tool on Windows. I have a decrypted boot.img and system.img but I haven't yet uploaded those to my drive.
Waiting for your Good news.
This is the Pixel 2 XL's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Cant wait to try it
Toejam1998 said:
Cant wait to try it
Click to expand...
Click to collapse
Tell me if it's work for you
I'll wait for a few others as well
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
does this do the critical unlock as well?
razgriz1234 said:
does this do the critical unlock as well?
Click to expand...
Click to collapse
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
mauronofrio said:
I have integrated "fastboot flashing unlock_critical" for pixel 2 xl only, i have not tested it but it should work
Click to expand...
Click to collapse
ok cool thanks for the quick reply
razgriz1234 said:
ok cool thanks for the quick reply
Click to expand...
Click to collapse
I saw now that i forgot to unlock the flash factory image option for all 4 Pixel, i have released an update to solve that, tell me if it works
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
jaythenut said:
This saved my ass last night got bootloop from hell nothing would flash at all run this and boom back in business so like to say thanks for the tool :good:
Click to expand...
Click to collapse
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
mauronofrio said:
I'm happy this tool helped you:good:
Do you flash a factory image with this tool?
Click to expand...
Click to collapse
Yes mate
jaythenut said:
Yes mate
Click to expand...
Click to collapse
People like to see feedback and in this thread this is the first
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
I think way early on it was established we can't have it unencrypted once the OS install it's completed, unless something changed or I got it wrong. Lol
almahix said:
Does this tool work well for Pixel XL2? If I wipe phone to unencrypt, will flashing stock re-encrypt it?
Click to expand...
Click to collapse
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
mauronofrio said:
You can uncrypt your phone but if you.flash a stock rom, the kernel at first boot will automatically encrypt your memory again. There are 2 different encryption, one by code and one with standard image key. At this moment the twrp will automatically uncrypt the system key but you need to manually write the code (if is setted). The tool will uncrypt both method, the flash of stock rom will re-uncrypt with system key but not with code key
Click to expand...
Click to collapse
Grazie.
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
dricacho said:
I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
I think it too, but i don't know why.
dricacho said:
Just got my Pixel 2XL the other day and am excited to root and start modding. I have been monitoring this thread just to see what issues people are running into but it looks like not many people are even doing this surprisingly. I mean that's why I bought this Google phone, so I don't have to deal with locked bootloaders that these carriers put in them to discourage rooting. I know this phone is also locked but it's not for the purpose of keeping people from rooting them. I just think that it's so odd that this thread has very little activity.
Click to expand...
Click to collapse
mauronofrio said:
I think it too, but i don't know why.
Click to expand...
Click to collapse
The device is very expensive, has dual partitions, has gotten a lot of bad press, and not near as Dev friendly as some others. Having said that, there are about 5 custom roms, root, exposed, substratum, and various launcher and active edge mods. So it's not like we're hurting too bad ??
Hi there. Would any of you 'One' owners be gracious enough to get a system dump for devs to take a look at?
Instructions to do so are here:
https://www.mylgphones.com/how-to-g...tiions-from-lg-android-phones-with-lg-up.html
Any help would be appreciated. Thanks
bacon612 said:
Hi there. Would any of you 'One' owners be gracious enough to get a system dump for devs to take a look at?
Instructions to do so are here:
https://www.mylgphones.com/how-to-g...tiions-from-lg-android-phones-with-lg-up.html
Any help would be appreciated. Thanks
Click to expand...
Click to collapse
I'd like to do this but I want to make sure my personal data is not part of this. Would I have to wipe my phone first?I don't own a laptop but have access to one. I'll try to get this done in the next couple weeks
This would be greatly appreciated.
To answer your question, as long as you don't dump the 'data' partition, no personal data will be copied.
/system
/vendor
and maybe /boot
are ones that would be worth exploring.
Don't be scared about this process. It's simpler than you think. If you have ANY questions about the process, PM me.
Thank you for considering,
-bacon612
Sent from my LG-US998 using Tapatalk
mortysantiago said:
I'd like to do this but I want to make sure my personal data is not part of this. Would I have to wipe my phone first?I don't own a laptop but have access to one. I'll try to get this done in the next couple weeks
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
much appreciated :good:
Looks like there's no usb driver support for this device. Will update if LG comes back with positive news
mortysantiago said:
Looks like there's no usb driver support for this device. Will update if LG comes back with positive news
Click to expand...
Click to collapse
Ok. Thanks for your continued efforts on this. If you are willing, there another way to get a dump using a bootable USB stick running Linux. It's a tool called FWUL. You download a zip file. Use a program to write it to a USB stick (in windows) (preferably 16gb) and it boots your PC to a custom tailored Linux environment with a bunch of handy Android tools including a program called SALT which is designed for use with LG phones. All of this happens from the USB stick and won't impact the laptop in any other way. The beauty of it is that it won't require drivers like windows does. Part of the reason the dev designed the tool.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
Check that out and let me know your thoughts.
Edit. This SALT tool actually won't allow you to dump specific partitions, yet. That feature is presently being worked on now. I'll post back here when its available.
mortysantiago said:
Looks like there's no usb driver support for this device. Will update if LG comes back with positive news
Click to expand...
Click to collapse
No idea if this works but https://www.lg.com/ca_en/support/support-mobile/lg-LMQ910UM
TotallyAnxious said:
No idea if this works but https://www.lg.com/ca_en/support/support-mobile/lg-LMQ910UM
Click to expand...
Click to collapse
@mortysantiago worth a shot
TotallyAnxious said:
No idea if this works but https://www.lg.com/ca_en/support/support-mobile/lg-LMQ910UM
Click to expand...
Click to collapse
Tried this already, thanks though. When you use the tool a list of LG devices shows up but not this one. LG twitter has been responding to my DMs and they're going to reach out to their support team and get back to me. My fear is LG will point me to Google but we'll see. Will update once LG responds
mortysantiago said:
Tried this already, thanks though. When you use the tool a list of LG devices shows up but not this one. LG twitter has been responding to my DMs and they're going to reach out to their support team and get back to me. My fear is LG will point me to Google but we'll see. Will update once LG responds
Click to expand...
Click to collapse
Does LG Bridge work? Like the tool that offers to "repair" the phone. It's downloads the kdz to do that.
If this is doable. Then you won't have any personal info revealed. Because it would be a kdz.
Other option is to see if this site works. https://lg-firmware-rom.com/
It's basically a web version of LG Bridge to download the kdz
TotallyAnxious said:
Does LG Bridge work? Like the tool that offers to "repair" the phone. It's downloads the kdz to do that.
If this is doable. Then you won't have any personal info revealed. Because it would be a kdz.
Other option is to see if this site works. https://lg-firmware-rom.com/
It's basically a web version of LG Bridge to download the kdz
Click to expand...
Click to collapse
There exist no kdzs of the G7 One (or Q9 One).... sadly. Thats why we need a partition dump.
It could also very well be that you need LG UP 1.15 (which is currently in the works) to function properly.... :/
SGCMarkus said:
There exist no kdzs of the G7 One (or Q9 One).... sadly. Thats why we need a partition dump.
It could also very well be that you need LG UP 1.15 (which is currently in the works) to function properly.... :/
Click to expand...
Click to collapse
Ah pooo! This is so lame
i'll give FWUL by the fabulous @steadfasterX a try tonight and see if this is doable, i have a funny feeling it's not going to. (and i thought my G4 was frustrating...)
in regular ubuntu, lsusb shows: Bus 001 Device 004: ID 1004:631c LG Electronics, Inc. G2/Optimus Android Phone [MTP mode] - i'll see if anything shakes down in FWUL and reply back either way, cheers!
Any luck with the system and vendor partitions dump?
I installed several drivers, but could not get a new COM port to show up in Device Manager.
Does anyone have a working driver for LGUP?
I was prepared to test out uppercut.exe with LGUP, but getting hung up on prerequisite 4 as indicated: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Following the instructions to install LGUP here: https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26
I was able to detect the phone and attempt to perform a dump, however I can't get past "Error: 0x2000 skip write protected lun"
From my limited understanding, I believe we require an engineering version of laf.bin for Snapdragon 835 (MSM8998), and of course a way to flash or temporarily boot it.
http://4pda.ru/forum/index.php?showtopic=951883&st=160#entry85370250
I couldn't figure out how to get this phone into Fastboot. Does anyone know the trick, or if it's even possible on this model?
We might need some help from @runningnak3d in here.
@skyblaster Versions of LAF shipping with Pie or later now require an RSA key to read anything other than the GPT (no version of LG UP with that key has leaked yet). You are correct that the engineering LAF is unlocked, but flashing it still requires the RSA signed SHA256 hash of the partition, and that doesn't exist for any of the engineering LAF partitions that are out there. LAF is a dead end for rooting LG phones. They can still be rooted with a firehose and the engineering abl (one exists for the V35 and G7 -- and the G7 eng. abl will work on the V40) -- all models except the TMO versions of the G7 and V40.
There is another use after free kernel exploit out there that will work on any kernel version up to the one shipping with 10, but I have not had much time (or luck yet) actually exploiting it. If (when) it can be done, then the root procedure would be almost identical to the DIrtySanta root for the V20: Get temp root, flash eng. abl, root....
-- Brian
Can someone share the stock camera APK? I need it please
Hi everyone,
I tried to backup the system, vendor and boot partitions with the SALT tool by @steadfasterX on xubuntu but only ended up with empty files titled system_a.img vendor_a.img and boot_a.img . Not sure if there are any other options left to try but I am looking for things to do right now with the whole pandemic going on so if there are any other ideas out there, I have lots of time to try them right now.
There is a fella who shared on telegram that they got a G7 one dump after getting root access. Did anyone get any of the partition dumps they needed yet?
Hello Everyone,
I recently bought this device G7 play with on-going offer with MetroPCS. Since last one week, I've been getting my hands dirty on successfully building and booting the kernel from the source code provided by moto here https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PPYS29.105-134-7
I would like to share with you all my progress currently.
Working:
Boots
Touch works
Not Working:
Camera
Baseband (radio)
A lot more
Screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will update my progress here and release it once I manage get around few major issues and also I'm working on building TWRP for our device from source.
Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx
Hello, is this 32bit or 64bit?
brickhayabusa said:
Sorry for my ignorance, but what does this mean for the g7 play development?, Thnx
Click to expand...
Click to collapse
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
Electimon said:
Hello, is this 32bit or 64bit?
Click to expand...
Click to collapse
It is a 64 bit build
kD said:
I will try to build a functional TWRP, custom kernel and maybe even a ROM.
It is a 64 bit build
Click to expand...
Click to collapse
Do you have telegram?
@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.
Spaceminer said:
@kD
You might be able to get LTE working by reflashing the modem and wiping modemst1 & 2. Your kernel might actually get around the security problems we have with installing twrp on stock as well. I'd love to do some testing with it. If you feel like dropping me a link, please send me a pm.
Click to expand...
Click to collapse
Sent a PM to you.
Thanks for your work!!!
A custom kernel for this device will be amazing! Go on!!
Using this kernel im going to build halium-boot eta s0n
This is amazing!! Please continue, you are a hope for us and share your progress with us
nothing new?
@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt
Spaceminer said:
@kD
I don't know if you saw this but one of the devs from Motorola finally updated the build process. You'd have to adapt some minor things like folder names, and the -j number but it should work. I can't believe how stupidly complicated building the kernel modules are. No body would remember this line for line, and they waited like a year to tell us this crap.
https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-PPYS29.105-134-7.txt
Click to expand...
Click to collapse
Seems like great news! When we can get a 64 bit OS running ill make a zip to convert from this 64 bit rom to 64 bit halium 9!
Hey man! Good work! Any news in your 64bit kernel?
@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", @ARGV) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.
Spaceminer said:
@kD
How do you get past this part compiling the kernel?
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\" ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat ~/android/kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config ~/android/kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig || ( rm -f ~/android/out/target/product/generic/obj/kernel/msm-4.9/mapphone_defconfig && false )
It originally gave me an error because of an extra ' symbol in there. Upon removing it, the command goes through, but... It drops me into some kind of "perl shell" that I can't get out of to enter the next commands. I almost have a script ready to auto build our kernel, but that perl command is holding up progress.
Click to expand...
Click to collapse
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.
ErikAlvarez00 said:
Hi @Spaceminer.
I'm a new XDA Developers Community member. English is not a my first language. I'm a Software Engineer in my country and I'm 23 years old.
Even so, I'm going to try to support you with anything. I don't know a lot of Android, I've done some Android applications and I know a very little about root, recovery and custom kernels.
I don't know perl, but I've seen that you have forgotten to write ' at the end of this part:
join("\n#\t", @argv) . "\n"
PD: I'm from Mexico. Greetings.
Click to expand...
Click to collapse
That explains the problem. I removed one of those, because it caused an error, but it really needed to be moved to the end... Thank you so much!
What's wrong with this command?
I need help with the syntax on this. There's an error somewhere and I can't find it, so I can't finish building a 64bit kernel. I've tried moving the ' symbol to a few places and nothing works. I'm very lost on this part.
Code:
( perl -le 'print \"# This file was automatically generated from:\n#\t\" . join(\"\n#\t\", [user=2467029]@argv[/user]) . \"\n\"' kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config && cat kernel/msm-4.9/arch/arm/configs/msm8953-perf_defconfig kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/debug-sdm632-channel.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-msm8953_32.config kernel/msm-4.9/arch/arm/configs/ext_config/moto-sdm632-channel.config ) > $kernel_out_dir/mapphone_defconfig || ( rm -f $kernel_out_dir/mapphone_defconfig && false )
Edit: I think that I found the solution. It should actually be this according to build instructions for other Motorola devices.
/bin/bash -c "( perl -le 'print "# This file was automatically generated from:\n#\t" . join("\n#\t", @argv) . "\n"'