Database Users

[Q] Buying a locked D802 and have some questions

Hey guys, I'm getting a locked G2 but don't know if the boot loader will be locked too. Do you have any idea how to check that before purchase? What will be the limitations of the locked boot loader and is it possible to unlock it. Can you explain with few words what wold my options be? I really like the G2 but I might opt for the N5 at the end.

Every G2 has a locked bootloader. Mut every G2's locked bootloader can be bypassed with loki. So in short yes you will be able to flash stuff.
Sent from my LG D802

So the bootloader doesn't matter if you can flash a custom recovery, right ? I mean - what limitations will the locked bootloader bring in the long run, as I'm expecting to use the device for 2 years (buying on contract) ? I read some posts that there are some G2-s with unlocked bootloader and I'm a bit puzzled...

4.2.2 bootloader can be bypassed with a loki patch. You can root, use custom recovery, ROMs, the lot.
4.4.2 has the loki exploit patched and only root is possible so far.

Any idea if the device might ship with 4.4.2 pre installed?
Sent from my iPhone using Tapatalk

axlastro said:
Any idea if the device might ship with 4.4.2 pre installed?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
eventhough it is preinstalled, you can still flash a kdz file to go back to 4.2.2 (to achieve root & custom recovery) :good:

Well that is really good news !
Sent from my iPhone using Tapatalk

Searching for Testers with D850|1|2/LS990/F400/VS985 variant

Hey guys and girls,
I'd look for testers who could check if the merges at the kernel source I've done are working properly.
I'm currently working on building a unified repository of kernel source with which hopefully all variants can be served and from which other developers can start from without having to worry about if the base source does work or has errors.
But even while I look deep into the source and hopefully don't miss anything, i can't really verify if it's working properly, except of compiling, for other variants than the D855, because that's the only device i own, so I need testers that could verify it's functionality.
Prerequisites
Knowledge about fastboot and how to temporarily boot kernels with it (WARNING! always take backups before trying to get to or mess with fastboot)
Knowledge about logcat and how to provide logs
Knowledge about dmesg and how to provide it's information
Note: I'm just integrating other variants at the stock source, there won't be any bells or whistles added, that's not the purpose of this project, so don't expect me to add any overclocking or other features! This may come with another project in the future, but this doesn't matter for now.
The project itself can be found here.
Thanks in advance to those willing to test

Hey,
I've now integrated the LS990 variant, so I'd need testers for this variant to

Ls990 doesn't have root yet
Sent from my LGLS990 using XDA Premium 4 mobile app

I would be happy to test the D851 kernel.

If I'm not mistaken you need to unlock the boot loader to change the kernel? If so the d850 is locked
Sent from my LG-D850 using Tapatalk 2

Tectas said:
the op
Click to expand...
Click to collapse
could you add to the op that it is Advised that they make a twrp backup(of everything but especially modem) before they begin messing with fastboot to minimize the chance of bricking
screwyluie said:
If I'm not mistaken you need to unlock the boot loader to change the kernel? If so the d850 is locked
Sent from my LG-D850 using Tapatalk 2
Click to expand...
Click to collapse
you boot this kernel temporary and not permanently and aslong as you just boot the kernel and don't try to flash it you will not have a problem

evodon84 said:
I would be happy to test the D851 kernel.
Click to expand...
Click to collapse
Great, thanks, unfortunately I'm short on time over the weekend, I'll send you a pm with instructions and the image within the next days (latest on Monday), thanks in advance for testing
suljo94 said:
could you add to the op that it is Advised that they make a twrp backup(of everything but especially modem) before they begin messing with fastboot to minimize the chance of bricking
Click to expand...
Click to collapse
Well, I intentionally added nowhere an image to avoid people not knowing what they're doing going through the steps to get fastboot working and trying to flash the kernel, but probably you're right and I should add an additional warning, it's just a bit tricky on other variants than the D851, because fastboot is needed to get to twrp , but thanks
Sent from my LG-D855

You can add F400 it?
If you support the F400, then I will be very happy

姚鑫海 said:
If you support the F400, then I will be very happy
Click to expand...
Click to collapse
It's not yet supported, but I'm planning to add support for it, as soon I've merged it, I'll send you a pm for testing, thanks in advance
Sent from my LG-D855

Could someone owning the F400 variant please post the value of ro.product.name from their build.prop?
Thanks in advance.
Edit: Nevermind

F400 added, just VS985 missing and it's done so far. When that's done and feedback is well from the testers, I'll start a new project based on this and add features.
I'd btw need testers for D850 still.
Edit: all variants except of d852 are added now, if i haven't missed any.
Edit2: all variants should be merged now.

Tectas said:
Hey,
I've now integrated the LS990 variant, so I'd need testers for this variant to
Click to expand...
Click to collapse
Does this suggest you have root for the Sprint variant? Tia
Sent from my Gunmetal Lg G3

Tectas said:
F400 added, just VS985 missing and it's done so far. When that's done and feedback is well from the testers, I'll start a new project based on this and add features.
I'd btw need testers for D850 still.
Edit: all variants except of d852 are added now, if i haven't missed any.
Edit2: all variants should be merged now.
Click to expand...
Click to collapse
a quick idea yesterday i received an update and accidentally pressed on “update now” button I had the tethered twrp installed so it kept booting in fastboot I couldn't boot normally it always booted in fastboot. now my idea is if you would be able to find what is forcing the phone to boot to recovery and change the command/target file to something on your sdcard and to just boot that, you could set it up to boot into a custom kernel every reboot without a problem.

good
Tectas said:
Could someone owning the F400 variant please post the value of ro.product.name from their build.prop?
Thanks in advance.
Edit: Nevermind
Click to expand...
Click to collapse
Hey buddy I'm very pleased to see F400 haha What can I help you? O(∩_∩)O~

suljo94 said:
a quick idea yesterday i received an update and accidentally pressed on “update now” button I had the tethered twrp installed so it kept booting in fastboot I couldn't boot normally it always booted in fastboot. now my idea is if you would be able to find what is forcing the phone to boot to recovery and change the command/target file to something on your sdcard and to just boot that, you could set it up to boot into a custom kernel every reboot without a problem.
Click to expand...
Click to collapse
Sounds good, but I don't think it's that easy unfortunately. I guess the updater sets an indicator that an update has to be applied, which simply forces a recovery reboot. The rest of it is more or less the dual boot functionality of Siyah, with one exception, we can't change the boot partition without triggering the security, means this functionality would have to reside within system and would have to replace a already booted kernel with another one in memory. That's not an easy task. Another way would be a hacked fastboot which boots an predefined image from the sd, but this would only be helpful if we at least can change the fastboot partition, what probably also triggers the security, but I'm not sure about that. Sorry.
姚鑫海 said:
Hey buddy I'm very pleased to see F400 haha What can I help you? O(∩_∩)O~
Click to expand...
Click to collapse
I'll send you instructions and the image to test tomorrow, if it's OK for you.
Sent from my LG-D855

Tectas said:
Sounds good, but I don't think it's that easy unfortunately. I guess the updater sets an indicator that an update has to be applied, which simply forces a recovery reboot. The rest of it is more or less the dual boot functionality of Siyah, with one exception, we can't change the boot partition without triggering the security, means this functionality would have to reside within system and would have to replace a already booted kernel with another one in memory. That's not an easy task. Another way would be a hacked fastboot which boots an predefined image from the sd, but this would only be helpful if we at least can change the fastboot partition, what probably also triggers the security, but I'm not sure about that. Sorry.
Click to expand...
Click to collapse
ow well back to the cm11 kernel on top of the orriginal to not trigger security idea

So, I've packed Images for D855 and D851 for public testing, there are no bells or whistles added, default behaviour, only difference to complete stock is, they are build with the linaro toolchain, though not with -O3 optimization (it builds fine with it, but won't boot, but just freezes at fastboot, so I left it out for now).
I won't add a guide how to apply those images over fastboot though, if you know how, try it, if not, let it be!!! (but as a hint to those capable of doing it, but just not knowing the exact steps, it's the same as with the tethered twrp, you just have to boot the boot.img instead of the twrp.img)
DON'T TRY TO FLASH IT THROUGH RECOVERY, it won't work, but you for sure can build a flashable zip for yourself from it for the D851, but please don't share it publicly, there are probably some which would try to flash it on other variants and brick their devices because of the locked bootloader.
D855 Test Image
md5sum: 60c062e1d57a51a19fd19151e610a6fc
D851 Test Image
md5sum: ba496fca56c831f078210e8dcd3f8df4
If people with other variants like to test it also, I need the stock boot.img of your device to repack it with the kernel, post it here or send me a pm with it and I'll build and repack one for this device as well.

fgcchevy said:
Does this suggest you have root for the Sprint variant? Tia
Sent from my Gunmetal Lg G3
Click to expand...
Click to collapse
No, I don't have root for sprint, sry.

Tectas said:
If people with other variants like to test it also, I need the stock boot.img of your device to repack it with the kernel, post it here or send me a pm with it and I'll build and repack one for this device as well.
Click to expand...
Click to collapse
Hello I've tried to boot your D855-boot.img in my D855P with success (I've asked you before since my build.prop says global D855 and TWRP was working) but I've noticed that your file is 3.5mb lighter than my stock boot... can you please give a check to my boot.img??
I got this screen, don't know if can help.

badtzo said:
Hello I've tried to boot your D855-boot.img in my D855P with success (I've asked you before since my build.prop says global D855 and TWRP was working) but I've noticed that your file is 3.5mb lighter than my stock boot... can you please give a check to my boot.img??
I got this screen, don't know if can help.
Click to expand...
Click to collapse
That's just because it is better compressed when it's repacked, my stock image has 16,8 mb
It's almost the same, just two small differences in the ramdisk
This is at your init.g3.rc but not at mine:
Code:
#[BEGIN][[email protected]]
chmod 0660 /sys/bus/i2c/devices/0-0036/lm3697_bl_max
chown system system /sys/bus/i2c/devices/0-0036/lm3697_bl_max
#[END][[email protected]]
That's at my init.lge.usb.rc but not yours:
Code:
# vzw llk mode
on property:persist.sys.store_demo_enabled=1
write /sys/class/power_supply/battery/store_demo_enabled 1
on property:persist.sys.store_demo_enabled=0
write /sys/class/power_supply/battery/store_demo_enabled 0
They are the same

Locked Bootloader lollipop root real soon?

It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.

zoid_99 said:
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
Click to expand...
Click to collapse
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.

Junior Passos said:
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Click to expand...
Click to collapse
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"

zoid_99 said:
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
Click to expand...
Click to collapse
Hmmm interesting.
Then the process should be with CF-Auto-Root .
I used one of those before when I first root in Lollipop.
But thought the command "mfastboot boot cf-auto-root.img" only work with unlocked bootloader and not the locked too.
Amazing.

Me excite!

You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting

godutch said:
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
Click to expand...
Click to collapse
Translated... Will it work on moto x vzw?

GatorsUF said:
Translated... Will it work on moto x vzw?
Click to expand...
Click to collapse
No.

cam30era said:
No.
Click to expand...
Click to collapse
OF course

This revelation means that Android 5.0 users*no longer need to run a modified kernel to gain root access via SuperSU (or other root solutions). While not a huge problem on Nexus devices with unlockable bootloaders, the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here, and we can present an exclusive explanation of the changes needed. At least for now (until/unless Google patch this), it is possible to gain root access and then install and use SuperSU on a stock Android 5.0 device, without any kernel ramdisk tweaking. The reason for this is the need for SuperSU to run a service as root, to allow for unconstrained root access on SELinux-protected devices.

Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?

neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader

neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
Thanks Motorola -_-

Buy a nexus 6. That's what I did. Still have the moto x for my wife so I can play with it

Can't afford it right now. If I knew programming, you bet I would be working on it. God I hate Verizon, but been here so long it's my cheapest option.

matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Will the pure edition work on Verizon?

GrandMstrBud said:
Will the pure edition work on Verizon?
Click to expand...
Click to collapse
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.

GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
LTE should work but what about CDMA side of it?

GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
GrandMstrBud said:
LTE should work but what about CDMA side of it?
Click to expand...
Click to collapse
No, CDMA will not work, nor 3G. So you will be confined only to LTE service and Google Voice (or similar).

matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Looks like your idea will not work and maybe that's the reason for this thread? Pure Edition won't work on VZW

Custom ROMs for ZenFone 2 ZE500CL

Is it possible to have some custom ROMs for ZenFone 2 ZE500CL in future? Somebody hear me? Someone? People?

RusLion__ said:
Is it possible to have some custom ROMs for ZenFone 2 ZE500CL in future? Somebody hear me? Someone? People?
Click to expand...
Click to collapse
Currently trying to find devs to help me out with this, I have a bit of an Idea of what I'm doing but need help with making sure I've got the right build flags and toolchains to make a bootable aosp rom for this device.

AlexBodewig said:
Currently trying to find devs to help me out with this, I have a bit of an Idea of what I'm doing but need help with making sure I've got the right build flags and toolchains to make a bootable aosp rom for this device.
Click to expand...
Click to collapse
What about custom recovery? Do you have TWRP or CWM for our phone?

Right now its tethered, but I'm working on a safestrap to counter the lack of unlocked bootloader.

I would cry...in a good way, if you could get this phone safestrapped.
Also... How are some people unlocking there bootloaders with the Asus unlock tool, mine won't unlock. I've had 2 of these phones, both the same. No unlock.
Sent from my zf2e[ze500cl] using Tapatalk

robot_head said:
I would cry...in a good way, if you could get this phone safestrapped.
Also... How are some people unlocking there bootloaders with the Asus unlock tool, mine won't unlock. I've had 2 of these phones, both the same. No unlock.
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I think it might be because technically the ZF2e and the ZE500CL are not the same phone. I mean they have the same processor, screen, and body, but the ZF2e is locked to AT&T, which might be blocking the bootloader unlock.

cmendonc2 said:
I think it might be because technically the ZF2e and the ZE500CL are not the same phone. I mean they have the same processor, screen, and body, but the ZF2e is locked to AT&T, which might be blocking the bootloader unlock.
Click to expand...
Click to collapse
It could also be a lack of space on the internal storage but it's more likely that it won't unlock because of the serial number indicating that it is a zf2e and not the ze500cl.

RusLion__ said:
Is it possible to have some custom ROMs for ZenFone 2 ZE500CL in future? Somebody hear me? Someone? People?
Click to expand...
Click to collapse
I've cracked down this bad boy at last, Got unlocked bootloader and a fully working TWRP 2.8.7.0, Will make a thread soon....

Ze500cl has bootloader unlocked, what about att version zf2e?
Sent from my zf2e[ze500cl] using Tapatalk

robot_head said:
Ze500cl has bootloader unlocked, what about att version zf2e?
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I don't know if it's possible to unlock the ZF2E bootloader. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-ze500cl-unlock-app-t3257815 ( I used this app to unlock my 500CL)

@NerdyNerd9000 any news on Roms. I had a horrible time with the updater script. I have a rom, basically a zip file with a system folder and meta-inf
Sent from my zf2e[ze500cl] using Tapatalk

robot_head said:
@NerdyNerd9000 any news on Roms. I had a horrible time with the updater script. I have a rom, basically a zip file with a system folder and meta-inf
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I've ported boot and recovery from zenfone5 successfully , but I need help flashing the system folder.

@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk

robot_head said:
@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
I don't know if this might help (the second guide, flash full ROM):
forum.xda-developers.com/zenfone2/general/how-to-flash-ota-rom-twrp-t3209545

I know how to flash, its this raggedy little phone controlled by att.
Sent from my zf2e[ze500cl] using Tapatalk

robot_head said:
@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
Same sh*t bro. I tried every single way of making a working updater-script. Gives binary error every time. I'll post my work as soon as I get free time.
---------- Post added at 06:41 PM ---------- Previous post was at 06:16 PM ----------
robot_head said:
@muhammad_fatah could you post your work. I've tried zipME, android script creator, kitchen, but nothing i do can create a working updater script to flash anything. AND most zips won't flash, like certain themed apps, mods, almost nothing will flash except super su and xposed
Sent from my zf2e[ze500cl] using Tapatalk
Click to expand...
Click to collapse
Porting, flashing won't help. Need to compile CM ROM from source. Do you have the device and vendor tree of our phone? Kernel source is already there , need device and vendor tree to get started porting cm.

I do not, and with my locked bootloader (att) i can't flash another kernel. So any rom i flash has to be based off stock, or so heavily modded it looks like cm. ??
Sent from my zf2e[ze500cl] using Tapatalk

AlexBodewig said:
Right now its tethered, but I'm working on a safestrap to counter the lack of unlocked bootloader.
Click to expand...
Click to collapse
UNLOCK USING ASUS UNLOCK Tool
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ZE500CL_UnlockTool_0909.apk

jbetro said:
UNLOCK USING ASUS UNLOCK Tool
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ZE500CL_UnlockTool_0909.apk
Click to expand...
Click to collapse
This method doesn't work for some. Particularly those with the Zenfone 2E variant.

Correct, this is the 2e (economy) version from att, anything att nowadays is unlockable, i even bought a samsung s5 before i knew that, you can't even root that phone, so needless to say, att users have to sit on the bench while everyone else gets to ride the rides
Sent from my zf2e[ze500cl] using Tapatalk

Am working on root with tungkick currently ;)

Hold tight fellas... tungkick is at it again and just made a ZV4 TOT and is now modifying it. Will keep you all updated!
UPDATE: he is copying the TOT file now, getting ready to edit
UPDATE 2: he is now editing the TOT, should be done soon!
UPDATE 3: TOT is finished, about to flash
UPDATE 4: FLASHING
UPDATE 5: 99% done...
UPDATE 6 ( ): The phone boots into fastboot mode, but does not recognize the "fastboot oem unlock" command or any flashing commands. If anyone would like to test, I will ask tungkick if I can provide links for the TOTs

Hope it works for you!!

Wishing you luck! :good::highfive:

Thanks guys!

So the Sprint has a locked bootloader right?
Sent from my LG-H860 using XDA-Developers mobile app

Fastboot oem unlock
...
FAILED (remote: unknown command)
Can not install TWRP

Yes same as H860n
Sent from my LG-H860 using XDA-Developers mobile app

Wait how are you flashing it if the bootloader is still locked?

Sorry man. It was worth a shot.

Has anyone ever bypassed a locked bootloader on any device before?
Is root on a device like this ever been accomplished?
Just need to know if its time to trade in for a h850 or not
Sent from my SM-N9005 using XDA-Developers mobile app

Bootloaders have been unlocked before, or bypassed. Just takes time to find the exploit, and get it right. Seems like there is a way todo it on this device, so we will get it eventually.

wacko37 said:
Has anyone ever bypassed a locked bootloader on any device before?
Is root on a device like this ever been accomplished?
Just need to know if its time to trade in for a h850 or not
Sent from my SM-N9005 using XDA-Developers mobile app
Click to expand...
Click to collapse
Not sure why you have a sprint lg g5 (unless you got it very cheap)
If you are on sprint, afaik no other models work on sprint
If you are using a GSM carrier (and don't care about volte/WiFi calling), and want root, go for the unlockable Intl version h850(if the lte/GSM frequency bands are compatible)

paperWastage said:
Not sure why you have a sprint lg g5 (unless you got it very cheap)
If you are on sprint, afaik no other models work on sprint
If you are using a GSM carrier (and don't care about volte/WiFi calling), and want root, go for the unlockable Intl version h850(if the lte/GSM frequency bands are compatible)
Click to expand...
Click to collapse
Thanks for the reply/advise.
No i do not have a sprint device. Sorry i have just been following all the action where the possibility of Root for my device is greatest. Not much going on anywhere else since root was achieved on h830.
Sadly there is no section for H860n Hong Kong variant， but both devices have locked bootloaders so if root happens here it surely will work for me.
I apologize if i have offended anyone by commenting on the sprint thread
Sent from my LG-H860 using XDA-Developers mobile app

Does modified tot file have root if so can you release it without twrp
Sent from my LGLS992 using XDA-Developers mobile app

How do you modify a tot file? I know how to extract them but I haven't seen how to put them back together before. The reason that I ask is because this would be useful for what I'm trying to do too. Root the sprint G4 on MM. Thanks in advance for the help. @tungkick

comp101inc said:
Does modified tot file have root if so can you release it without twrp
Sent from my LGLS992 using XDA-Developers mobile app
Click to expand...
Click to collapse
+1!
just getting AdAway and freezing a couple of services I don't use would be YUUUUUUGE.

l33tlinuxh4x0r said:
How do you modify a tot file? I know how to extract them but I haven't seen how to put them back together before. The reason that I ask is because this would be useful for what I'm trying to do too. Root the sprint G4 on MM. Thanks in advance for the help. @tungkick
Click to expand...
Click to collapse
if the goal if to patch a system.img with root then add it into a TOT.. this wouldn't work on M due to security in the boot.img... you'd need to unlock the bootloader to edit the boot.img to then allow the modification of system for root.
Patched TOT files work with devices pre-M or devices with unlocked bootloaders, like in the case of the TOT in this thread.
For root on M with a locked bootloader.. a privilege escalation bug is required (usually something kernel level). Altering system.img and finding ways to get it flashed will no longer cut it from M on.
This goes for all the G5 users with locked bootloaders as well.

autoprime said:
if the goal if to patch a system.img with root then add it into a TOT.. this wouldn't work on M due to security in the boot.img... you'd need to unlock the bootloader to edit the boot.img to then allow the modification of system for root.
Patched TOT files work with devices pre-M or devices with unlocked bootloaders, like in the case of the TOT in this thread.
For root on M with a locked bootloader.. a privilege escalation bug is required (usually something kernel level). Altering system.img and finding ways to get it flashed will no longer cut it from M on.
This goes for all the G5 users with locked bootloaders as well.
Click to expand...
Click to collapse
Could we make a tot that just enters download mode without flashing anything for using send_command.exe. I hear that if you don't unplug the phone at the exact right time that you can brick. I think that it would be good for development and flashing roms if we had a tot that did what I just mentioned. Also It would be nice for personal knowledge. I have all sorts of ideas but I need download mode for them and don't want to brick my phone.

autoprime said:
if the goal if to patch a system.img with root then add it into a TOT.. this wouldn't work on M due to security in the boot.img... you'd need to unlock the bootloader to edit the boot.img to then allow the modification of system for root.
Patched TOT files work with devices pre-M or devices with unlocked bootloaders, like in the case of the TOT in this thread.
For root on M with a locked bootloader.. a privilege escalation bug is required (usually something kernel level). Altering system.img and finding ways to get it flashed will no longer cut it from M on.
This goes for all the G5 users with locked bootloaders as well.
Click to expand...
Click to collapse
Is that what team codefire is working on?
Sent from my LG-H860 using XDA-Developers mobile app

autoprime said:
if the goal if to patch a system.img with root then add it into a TOT.. this wouldn't work on M due to security in the boot.img... you'd need to unlock the bootloader to edit the boot.img to then allow the modification of system for root.
Patched TOT files work with devices pre-M or devices with unlocked bootloaders, like in the case of the TOT in this thread.
For root on M with a locked bootloader.. a privilege escalation bug is required (usually something kernel level). Altering system.img and finding ways to get it flashed will no longer cut it from M on.
This goes for all the G5 users with locked bootloaders as well.
Click to expand...
Click to collapse
So far my thought process has been to make a modified boot.img with dm-verity disabled. I made this but have not flashed it yet. If I flash a stock TOT with a modified boot.img with dm-verity disabled, will this still brick the phone?