[TMO H932 ONLY] Progress Towards Root/TWRP/ROMs (not achieved yet)

[jameslapc2]

You can get around that. Just stay on the screen before download mode. You have to be at 79% though and it teaches about an hour to finish.

 

[runningnak3d]

Does anyone have an OTA zip for the H932? If so: https://forum.xda-developers.com/v20/how-to/recovery-how-root-t3741088

As near as I can tell, the V30 recovery is the same as the V20....

-- Brian

 

[Josh McGrath]

Im super tired and going to be gone all day tomorrow looking at cars. So check this out in ADB and try things and Ill get back onto things on Sunday or so

In adb: adb shell am start -n com.android.engineeringmode/.qualcomm.DiagEnabled --am
Please note I have only briefly looked at it, and only ran with the phone on, not in bootloader or anything on the few commands I tried.

Also, this is on the very last line of the build.prop, I dont know if we will have to mess with this yet or not but even if we do, it should be easy to bypass/change. I dont know if its even being enforced with an unlocked boot

ro.expect.recovery_id=0xbe6cbed79542225479b7c30de92ef8dc296f38bc000000000000000000000000

---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------

Does anyone have an OTA zip for the H932? If so: https://forum.xda-developers.com/v20/how-to/recovery-how-root-t3741088

As near as I can tell, the V30 recovery is the same as the V20....

-- Brian

If you can find the stock recovery files, you can compare them in Hex editor. I will look too

 

[R800x_user]

Im super tired and going to be gone all day tomorrow looking at cars. So check this out in ADB and try things and Ill get back onto things on Sunday or so

In adb: adb shell am start -n com.android.engineeringmode/.qualcomm.DiagEnabled --am
Please note I have only briefly looked at it, and only ran with the phone on, not in bootloader or anything on the few commands I tried.

Also, this is on the very last line of the build.prop, I dont know if we will have to mess with this yet or not but even if we do, it should be easy to bypass/change. I dont know if its even being enforced with an unlocked boot

ro.expect.recovery_id=0xbe6cbed79542225479b7c30de92ef8dc296f38bc000000000000000000000000

---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------




If you can find the stock recovery files, you can compare them in Hex editor. I will look too

Just tried on device but I got permission denied. Might work better on pc

 

[Josh McGrath]

Are you using terminal emulator or windows?

 

[R800x_user]

Are you using terminal emulator or windows?

The adb shell located in one of the debug tools and terminal emulator.

 

[Josh McGrath]

The adb shell located in one of the debug tools and terminal emulator.

You probably have to use Windows.

 

[Revolts]

Im super tired and going to be gone all day tomorrow looking at cars. So check this out in ADB and try things and Ill get back onto things on Sunday or so

In adb: adb shell am start -n com.android.engineeringmode/.qualcomm.DiagEnabled --am
Please note I have only briefly looked at it, and only ran with the phone on, not in bootloader or anything on the few commands I tried.

Also, this is on the very last line of the build.prop, I dont know if we will have to mess with this yet or not but even if we do, it should be easy to bypass/change. I dont know if its even being enforced with an unlocked boot

ro.expect.recovery_id=0xbe6cbed79542225479b7c30de92ef8dc296f38bc000000000000000000000000

---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------




If you can find the stock recovery files, you can compare them in Hex editor. I will look too

Got this:
"Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] pkg=am cmp=com.android.engineeringmode/.qualcomm.DiagEnabled }
Error type 3
Error: Activity class {com.android.engineeringmode/com.android.engineeringmode.qualcomm.DiagEnabled} does not exist."

 

[runningnak3d]

@Josh McGrath I didn't mean that the recovery was bit for bit identical. From the little bit of decompiling that I have done on the V30 recovery, the fact that it looks for the otacert in the zip is what I mean by "it's the same".

I have no way of getting an OTA for the V30 though, so you guys are going to have to find one / get one / flash back to the original firmware, and then let the OTA come. Before rebooting, use the patched LG UP to dump your system partition so we can get the OTA zip off of it. Once I can see the OTA zip, I can craft one up for you to try, or be able to tell you that it just isn't possible.

I am here helping out in the V30 forums because I WANT an H932 since it has band 71, but I only want it if it can be rooted. Unlike most people, I will help root a phone and THEN buy it, instead of buying one and then hoping it can be rooted

-- Brian

 

[Josh McGrath]

@Josh McGrath I didn't mean that the recovery was bit for bit identical. From the little bit of decompiling that I have done on the V30 recovery, the fact that it looks for the otacert in the zip is what I mean by "it's the same".

I have no way of getting an OTA for the V30 though, so you guys are going to have to find one / get one / flash back to the original firmware, and then let the OTA come. Before rebooting, use the patched LG UP to dump your system partition so we can get the OTA zip off of it. Once I can see the OTA zip, I can craft one up for you to try, or be able to tell you that it just isn't possible.

I am here helping out in the V30 forums because I WANT an H932 since it has band 71, but I only want it if it can be rooted. Unlike most people, I will help root a phone and THEN buy it, instead of buying one and then hoping it can be rooted

-- Brian

I have to do another reset on mine, luckily we are on antirollback 0 still. So I'll check to see if I can find it when I get a chance

 

[ChazzMatt]

I am here helping out in the V30 forums because I WANT an H932 since it has band 71, but I only want it if it can be rooted. Unlike most people, I will help root a phone and THEN buy it, instead of buying one and then hoping it can be rooted

-- Brian

I bought the open market LG US998, because it was assured of getting root vs carrier variants. For the last two years, the open market variants are placed on the LG Developer Bootloader Unlock list.

And now LG is leaving me hanging.

Sent from my official carrier unlocked LG V30+ US998

 

[EMSpilot]

US998

I bought the open market LG US998, because it was assured of getting root vs carrier variants. For the last two years, the open market variants are placed on the LG Developer Bootloader Unlock list.

And now LG is leaving me hanging.

Sent from my official carrier unlocked LG V30+ US998

LG has 5 days to get the V30 on the Unlock Bootloader list or I send mine back to B&H and stick with my V20.

Cheers

 

[lightninbug]

LG has 5 days to get the V30 on the Unlock Bootloader list or I send mine back to B&H and stick with my V20.

Cheers

That'll teach em'...

 

[netgar]

I bought the open market LG US998, because it was assured of getting root vs carrier variants. For the last two years, the open market variants are placed on the LG Developer Bootloader Unlock list.

And now LG is leaving me hanging.

Sent from my official carrier unlocked LG V30+ US998

I don't think they will do it. Better return it.

 

[jcsww]

I bought the open market LG US998, because it was assured of getting root vs carrier variants. For the last two years, the open market variants are placed on the LG Developer Bootloader Unlock list.

And now LG is leaving me hanging.

Sent from my official carrier unlocked LG V30+ US998

Assured by what? Just because US the non-carrier made the bootloader unlock list in previous years doesn't guarantee this years model will end up on there. It would be nice though if LG would just outright answer the question as to whether or not they plan on putting it on the bootloader unlock list.

 

[ChazzMatt]

Assured by what? Just because US the non-carrier made the bootloader unlock list in previous years doesn't guarantee this years model will end up on there. It would be nice though if LG would just outright answer the question as to whether or not they plan on putting it on the bootloader unlock list.

Assured by LG's comments when they created the LG Developer Bootloader Unlock list in the first place. And no, I can't find it right now. But they basically promised "open market" variants would be on the list. That's WHY they were releasing open market variants, for the developer community.

I know nothing is set in stone, but if they changed their minds, they should have announced it publicly.

The of the first time since rooting phones (2010 or so), that I've bought a phone before it could be rooted. I swore I'd never do that. And I did it.



Sent from my official carrier unlocked LG V30+ US998

 

[Jubeldum]

I've got a question and I hope it isn't a stupid one. Since some system apps can be used as an exploit, has anyone looked at the T-MOBILE sim unlock app that comes preinstalled on the H932?

Other brands of phones have been rooted by exploited system apps.

 

[wolfgart]

.....Other brands of phones have been rooted by exploited system apps.

recently ???? Link ?

 

[Jubeldum]

https://www.xda-developers.com/oneplus-root-access-backdoor/

 

[Josh McGrath]

https://www.xda-developers.com/oneplus-root-access-backdoor/

I believe that's what my adb link was for.