Related
Hi all, came across this new rooting method that is meant for Exynos and OMAP devices when I was reading Appy Geek.
Can any of you try this? I don't have a L9 but I thought that this may be interesting. Post results with device model and software version.
Link (from the same guy who found an Exynos exploit - alephzain): http://forum.xda-developers.com/showthread.php?p=37837568
If it doesn't work, contact him on his thread for further support, maybe he will be able to help.
Sent from a certain phone via Tapatalk 2
not useable on p769 with 10g firmware.
Not work on P768f V10D
does not works on p760d.
it says:
your device seems not vulnerable to exploit included in framaroot.
exFAT said:
Hi all, came across this new rooting method that is meant for Exynos and OMAP devices when I was reading Appy Geek.
Can any of you try this? I don't have a L9 but I thought that this may be interesting. Post results with device model and software version.
Link (from the same guy who found an Exynos exploit - alephzain): http://forum.xda-developers.com/showthread.php?p=37837568
If it doesn't work, contact him on his thread for further support, maybe he will be able to help.
Sent from a certain phone via Tapatalk 2
Click to expand...
Click to collapse
Suddenly there are two such apps with all old scripts embedded into one. These are not any new inventions. Just FRONTENDS. Nothing special.
Works only on S2/S3 and few more vulnerable devices. Not applicable on LG L9 and O2X models. Devs of these apps even don't know LG L9 exists. Tried asking them to look L9, but they never reply. And that explains their calibre.
We should not make threads for every such useless frontends.
We need scripts and apps from real developers who can crack bootloaders, exploit loopholes, compile Roms and kernels.
Sent from p765.
cmahendra said:
Suddenly there are two such apps with all old scripts embedded into one. These are not any new inventions. Just FRONTENDS. Nothing special.
Works only on S2/S3 and few more vulnerable devices. Not applicable on LG L9 and O2X models. Devs of these apps even don't know LG L9 exists. Tried asking them to look L9, but they never reply. And that explains their calibre.
We should not make threads for every such useless frontends.
We need scripts and apps from real developers who can crack bootloaders, exploit loopholes, compile Roms and kernels.
Sent from p765.
Click to expand...
Click to collapse
Do you even bother to do your research properly? Firstly, this is a new app, that uses some exploits this person discovered. Secondly, this is the person who found the massive exploit on Exynos 4 devices that allowed access to all of physical memory, so as to your point about skills or whatever, this person has them. Seeing as he mentioned the app may work for OMAP devices (worked for his OMAP3), I listed it here in the hope that it may work for those unlucky ones screwed over by LG's lockdowns. It is unfortunate it doesn't work. But this is not some app just merging old scripts. It contains original work.
Tl;dr do your research first and stop being such a hypocrite and know-it-all smartass. Your group of users stuck on unrootable V10G thread is infinitely more useless than this thread.
Well one day we will get root I hope
Benduchi said:
Well one day we will get root I hope
Click to expand...
Click to collapse
i recently rooted my l9 using bin4ry's method but first i downgraded software to 10b
I want to start somewhere, I was able to make a jailbreak for my iPhone on 3.1.2 way back when, where can I start for learning how to make a rooting method the L9 or Android in general?
LGP768 Root Guide
I'll be posting a LGP768 Root Guide in Android Development tonight.
Muphet said:
i recently rooted my l9 using bin4ry's method but first i downgraded software to 10b
Click to expand...
Click to collapse
yes Binary's Root works for many earlier roms, which variant of L9 you have?
Title pretty much. I never had to do this with other my devices, my two LG G2s or my other other G3, apparently now I do have to bypass SafetyNet for some of the applications I use, as nothing seems to be working. So my question is where do I start. I see a lot of threads about it but they aren't as user friendly as a lot of the threads and guides in the LG G forums (Thanks to great guides by @xdabbeb and @roirraW "edor" ehT) ((Honestly its one of the reasons I bought another LG G3 was because of the users here)). Basically I am on XDABBEB's VS985 - 3.1.1, rooted (from 10B TOT). However I need to bypass Google safety net for two apps. I see things about Magisk, Systemless Rooting, Systemless Xposed, suhide. I don't even know what most of that stuff means, let alone doing all the terminal command in adb and stuff. If anyone could point me in the right direction that would be great.
Hi! I know you weren't necessarily asking me (and you're welcome, glad I was able to help people), but just wanted to weigh in on only a couple of the aspects I have any knowledge about. First, any rooted (at least stock) ROM on the G3 since Lollipop 5.x is using systemless root - I believe it's the only way root can be implemented on 5.0 and above. However, systemless root by itself doesn't necessarily get you to pass SafetyNet. I am not knowledgable at all about SafetyNet because I have no need for passing it, so I really can't weigh in on it or Magisk, and I haven't used Systemless Xposed.
Systemless anything (root, Xposed, I think there are other systemless mods) means that the system partition, where what really makes Android be Android resides, is not modified. This may be a simplified explanation but there are others who know a lot more about this stuff.
I don't even know if it's possible to implement Magisk or hope for passing SafetyNet on a rooted G3. If you haven't poked around or asked in the non-Verizon G3 sections, you might want to see if anyone's mentioned anything, although of course it might only loosely apply to the Verizon variant.
You probably couldn't run a customized stock ROM like @xdabbeb's VS985 v3.1.1 at all if you hope to pass SafetyNet, but again, this is coming from my limited knowledge. The system partition on any custom ROM is usually fairly heavily modified to varying degrees.
Good luck!
roirraW "edor" ehT said:
Hi! I know you weren't necessarily asking me (and you're welcome, glad I was able to help people), but just wanted to weigh in on only a couple of the aspects I have any knowledge about. First, any rooted (at least stock) ROM on the G3 since Lollipop 5.x is using systemless root - I believe it's the only way root can be implemented on 5.0 and above. However, systemless root by itself doesn't necessarily get you to pass SafetyNet. I am not knowledgable at all about SafetyNet because I have no need for passing it, so I really can't weigh in on it or Magisk, and I haven't used Systemless Xposed.
Systemless anything (root, Xposed, I think there are other systemless mods) means that the system partition, where what really makes Android be Android resides, is not modified. This may be a simplified explanation but there are others who know a lot more about this stuff.
I don't even know if it's possible to implement Magisk or hope for passing SafetyNet on a rooted G3. If you haven't poked around or asked in the non-Verizon G3 sections, you might want to see if anyone's mentioned anything, although of course it might only loosely apply to the Verizon variant.
You probably couldn't run a customized stock ROM like @xdabbeb's VS985 v3.1.1 at all if you hope to pass SafetyNet, but again, this is coming from my limited knowledge. The system partition on any custom ROM is usually fairly heavily modified to varying degrees.
Good luck!
Click to expand...
Click to collapse
Thanks as always. You did help me explain things better at least. That isn't really the news I wanted to hear but I'll peek around and see what I can find. I saw something on reddit about bumping Magisk on a G2 and G3 if you're running CM (is that Cyanogen or Clockwork, see the lack of hand holdi-ness I can't even comprehend the acronyms). But the whole thread was garbled noise to my beginners ears.
Helltech said:
Thanks as always. You did help me explain things better at least. That isn't really the news I wanted to hear but I'll peek around and see what I can find. I saw something on reddit about bumping Magisk on a G2 and G3 if you're running CM (is that Cyanogen or Clockwork, see the lack of hand holdi-ness I can't even comprehend the acronyms). But the whole thread was garbled noise to my beginners ears.
Click to expand...
Click to collapse
You're welcome. CM is CyanogenMod. CWM is the acronym for ClockWork Mod. CM isn't made any more (simple version of explanation); for all intents and purposes it's now LineageOS. No real difference to the end user, just name change.
roirraW "edor" ehT said:
You're welcome. CM is CyanogenMod. CWM is the acronym for ClockWork Mod. CM isn't made any more (simple version of explanation); for all intents and purposes it's now LineageOS. No real difference to the end user, just name change.
Click to expand...
Click to collapse
Well thanks, guess I'll start looking into all of that then. Hope i can get something working
I've been thinking about the myriad of "old" gadgets that are alive thanks to the variety of ROMs available these days.
But a fact that intrigues me is why this device has very few ROMs available ... it really is something that draws the attention precisely because it has a good potential to receive them.
I have been around the G2 Mini forums since, pretty much, when the device was released. If you have a look at the oldest posts, some of them are mine.
In that time, I have seen many devs, at first trying to unlock the bootloader of the device, with Zaaap finally succeeding, by figuring out how the Russians at 4pda hacked the bootloader of the L90, and then he, and others, made some ROMs.
Since then, the only ROM dev that seems to still be working on our device is @mobiusm . Other that him, I still work on my kernel, with the help of @likeadracula . (However, he is very busy and I don't have any features to add, so there is little work done lately)
I don't know why there aren't any other devs, although, I believe it's because of the initial price (250-300 €) so no dev got it, and, even when the price dropped, it was already "old".
So, yeah, that's what I think.
P.S.: This is not a development thread, but a discussion. It belongs in G2 Mini General.
EDIT: Thread moved by mod.
For me, one developer who works on ROMs and one on Kernels, seems like a lot for a nearly 4 year old, non flagship device.
Also, having the newest Recovery & newest ROM which are worked out properly + a neat kernel with all the features you desire should not be taken for granted.
I am very grateful for all the development that has been done and will be done and I wouldn't know why I should get a new phone, 'cause this one works just fine, at least for me.
My surprise in relation to this fact is related that this device does not differ in anything from the L90 in terms of hardware, and the boot unblocking is the same, same procedures, so it is common to see roms for L90 and not for the G2m. This is something I'm surprised about. Obviously I am happy that there is still developer for this device, particularly the rom of my preference that is the LOS, did not abandon it, so 2..3 or more roms for it does not make as much difference since I just like to use the LOS on my devices, for the stability, performance and commitment of the team to all supported devices, however, is my view, other people have divergent thoughts.
Oshmar said:
My surprise in relation to this fact is related that this device does not differ in anything from the L90 in terms of hardware, and the boot unblocking is the same, same procedures, so it is common to see roms for L90 and not for the L90. G2m, this is something I'm surprised about. Obviously I am happy that there is still developer for this device, particularly the rom of my preference that is the LOS, did not abandon it, so 2..3 or more roms for it does not make as much difference since I just like to use the LOS on my devices, for the stability, performance and commitment of the team to all supported devices, however, is my view, other people have divergent thoughts.
Click to expand...
Click to collapse
Actually, precisely because of the similar hardware, it's very easy for the L90 ROMs to be ported to the G2M.
One the devs that have made ROMs for the g2m recently told me that he is using the L90 for initial testing and then uses the blobs for the g2m to make it work. (I don't actually know, but I think that the only problem with the L90 blobs is the camera or the WiFi, if anything)
In fact, it's so easy that anyone, with the most basic knowledge of Linux, can get it to work. I think. I haven't actually tried.
So, find a ROM of the L90 that you like and give it a shot. Just follow an online tutorial and you should be able to port it.
If you need any help, just let me know. Or anyone on the forum (though, some, myself included, are busy)
I was thinking once before to try Slim Rom from l90, but I was afraid to ruin my phone
Boki11111 said:
I was thinking once before to try Slim Rom from l90, but I was afraid to ruin my phone
Click to expand...
Click to collapse
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Vagelis1608 said:
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Click to expand...
Click to collapse
If I try, I'll report
Complicated ... but as I said, it was only a sudden surprise because there were few roms, however, for my daily use, LOS I like, of course some options are always welcome, but if it is not possible, good size too.
Vagelis1608 said:
Just make a backup in recovery
If it works, let us know!
I might even make a small zip that modifies the build props to say the correct information.
P.S.: As always, I take no responsibility. Your phone, your fault. (Disclaimer)
Click to expand...
Click to collapse
not working,error in start installing zip,probably should first edit build.prop and kernel
Boki11111 said:
not working,error in start installing zip,probably should first edit build.prop and kernel
Click to expand...
Click to collapse
In the install script in the zip, there is a command "assert" that checks the device.
Remove that line and it will install.
I would like your opinion if it is worth changing my devices; Moto G Falcon and the LG D618, both in perfect condition, for a Moto G4 Play?
Oshmar said:
I would like your opinion if it is worth changing my devices; Moto G Falcon and the LG D618, both in perfect condition, for a Moto G4 Play?
Click to expand...
Click to collapse
Do you know in which parts the G Falcon and the G4 Play differ?
Is it possible for g2m to die if you try to install a rom of the L90?
Oshmar said:
Is it possible for g2m to die if you try to install a rom of the L90?
Click to expand...
Click to collapse
Nope. Only soft brick (a.k.a. bootloop)
Just restore the backup you (hopefully) made before flashing
Or, wipe /system /data and /cache and then flash a ROM for the g2m.
Still, no responsibility taken
They released an unofficial version of the android Oreo for the L90.
Hey folks,
I've got a relatively simple question about the V30. I've got an AT&T LG V30 which I used the frankenstein method to unlock the bootloader and convert to US998.
What I'm trying to understand is whether or not any of the LineageOS ROMs, or the 9.0 ROM, will work on the AT&T converted V30. My takeaway thus far is that they will NOT work on my device, and my attempts to flash the ROMs echo this, but I'm looking for a more definitive answer.
Am I dumb and just "doing it wrong", or is the 931 converted to 998 unable to run these ROMs?
Cheers!
uberamd said:
Hey folks,
I've got a relatively simple question about the V30. I've got an AT&T LG V30 which I used the frankenstein method to unlock the bootloader and convert to US998.
What I'm trying to understand is whether or not any of the LineageOS ROMs, or the 9.0 ROM, will work on the AT&T converted V30. My takeaway thus far is that they will NOT work on my device, and my attempts to flash the ROMs echo this, but I'm looking for a more definitive answer.
Am I dumb and just "doing it wrong", or is the 931 converted to 998 unable to run these ROMs?
Cheers!
Click to expand...
Click to collapse
No, they won't for now.
For those wanting more information about former H931 and H933 and AOSP ROMs, see here.
Please read around. There are multiple places saying it doesn't work. I am working on this. It is a slow process.
For a definitive. It does NOT work.
me2151 said:
Please read around. There are multiple places saying it doesn't work. I am working on this. It is a slow process.
For a definitive. It does NOT work.
Click to expand...
Click to collapse
I've been looking, however I wasn't able to find if that was for all ROMs, some ROMs, maybe it works now and not at the time the reply was made, etc. It'd be cool if ROMs had a callout on the top post (as it gets updated when there are new releases) saying "INCOMPATIBLE WITH" or something along those lines. Just a thought.
uberamd said:
I've been looking, however I wasn't able to find if that was for all ROMs, some ROMs, maybe it works now and not at the time the reply was made, etc. It'd be cool if ROMs had a callout on the top post (as it gets updated when there are new releases) saying "INCOMPATIBLE WITH" or something along those lines. Just a thought.
Click to expand...
Click to collapse
Thats what i have the FAQ for ^^
I list compatible devices there.
SGCMarkus said:
Thats what i have the FAQ for ^^
I list compatible devices there.
Click to expand...
Click to collapse
Ohhh, see, I'm dumb and see the line in the FAQ that says:
Q. Which Models are supported?
A. So far it works well on the H930(G/DS), US998, VS996 and LS998 (use H930 zip). Other models may have broken RIL or bootloop. People with a H932, please use that zip.
Click to expand...
Click to collapse
And think "oh, I now have a US998 since I converted my 931, so this ROM should work for me."
Most of my lack of making since of this probably stems from the fact that I swear XDA used to have a set of forums for each carriers version of the device, but in the case of the V30, all carrier releases are clumped together under one section.
Thanks for your help! I'll look specifically for 931 in the device list and remember that even though I converted to a US998 via frankenstein, it's not actually a 998.
Cheers!
uberamd said:
Most of my lack of making since of this probably stems from the fact that I swear XDA used to have a set of forums for each carriers version of the device, but in the case of the V30, all carrier releases are clumped together under one section.
Click to expand...
Click to collapse
Yes, previously that was the norm -- even completely separate forums for each carrier, but then most users just focused on THEIR variant/their carrier and missed compatible developments that other variants of the same phone had. "Unified" development is better. TWRP/ROMS for all where possible.*
In this case, if you had a separate H931 or H933 forum, right now there would be no custom ROMs available. All you would have is stock-based ROMs like Boombox. It's also entirely possible we wouldn't have even figured out (together) that someone could flash to US998 in the first place to get bootloader unlock and root. It still might be only original US998 and H930 which have bootloader unlock and root with bootloader unlock codes doled out by LG.
But due to the one forum, and shared development that's how [b @TxanMoe accidentally discovered WTF bootloader unlock while using Frankenstein.[/B] @runningnak3d helped him recover his phone when he ill-advisedly tried to flash his H931 to European H930 after first converting to US998 and running some old Huawei bootloader unlock code he found in an LG G4 forum Yeah, he bricked his phone and we all smirked because he was doing stuff that seemed crazy. But after his phone was recovered, his bootloader was indeed unlocked. That became the foundation of WTF bootloader unlock and root. Without a unified forum, I'm not sure enough people would have paid attention. @TxanMoe would have just bricked his phone and that would have been the end of it; he would have moved onto another phone and we would not have realized the wonderful discovery of the LG bootloader unlock exploit.
There are devs working on the problem of H931 and H933 on AOSP ROMs.
________
* In the Moto Quark forums (Droid Turbo/Moto Maxx/Moto Turbo -- all the same model phone, just different names for some strange reason) the CM dev at the time make sure his stock CM Quark kernel (the foundation of all custom ROMs) was compatible with Droid Turbo when it finally got bootloader unlock a YEAR after all the others. Thus all those variants could run the SAME CM/Lineage-based ROMs and have the same TWRP. The dev that succeeded him @BHB27 kept up that tradition.
It started out as one forum, but then the Droid Turbo owners complained because their bootloader was not unlocked and they were tired of seeing all the "development" the other phone were getting. So, the forums were split almost a year after release, and ONE MONTH LATER the Droid Turbo bootloader was unlocked and suddenly they WANTED all that development back! That's where I saw it was a mistake to split forums. It's better to keep them all together so they can share development.
In the same vein, the V30S should NOT have a separate forum. That was an XDA mistake. It's a V30 Joan, just like all other V30 and all V30S should be here. This is where the V30S ROMs are, this is where the V30S TWRP (Joan) is, this is where the WTF bootloader unlock and root is. They should merge the V30S forum with this one and use that space for something else...
X - stands for any bootloader, so for example the installed Samsung Bootloader or an own one (by the process of changing it, the fuse normally burns)
Hello out there,
is there any way to develop and install an own Linux System on a given Samsung Galaxy Tab and implement the knox security features and use those, a way of rooting and later unrooting the tab and all this without burning of the knox fuse?
How does the knox (software? hardware?) check the given kernel for manipulation? With checksums? And: Is there a checksum to compare with in the chip, that was created at some point in time? How does the knox (software? hardware?) achieve this?
I want to develop it for business reasons.
Thank you for your answers.
Kind regards,
TheLazyGuyDE, Germany
Any interference with the bootloader burning the Knox fuse.
This Videos:
and
and
describe the knox Kernel protection. But how does this work? Is it on a software basis?
How is the comparison getting achieved?
What role does the knox Chip Play within this process? What has to be done Prior/after a Kernel Update and can a Software Change burn the Fuse?
What isn't working anymore after burning the fuse?
How does Samsung put and verify the software on the phones?
Is there a checksum of the installed Android software created in the knox chip?
I don't want to use magisk, but want to have real root mode and want to install an own Linux distribution.
What disadvantages do I have? Can I use all hardware parameters, like SIM-Card, Videocamera, etc.?
Thanks for your answers,
Kind regards,
TheLazyGuyDE
ze7zez said:
Any interference with the bootloader burning the Knox fuse.
Click to expand...
Click to collapse
But how did Samsung themselves prevent this, when they installed their bootloader? There has to be a way to circumvent the burning of the fuse! (I am not a hacker, I am a developer)
System-critical files from samsung are digitally signed with its own algorithm and checked during flashing. Therefore, there is no worry that someone will modify these files and flash. In case of fake flashing, in the mildest scenario the attempt will be rejected, and in the worst scenario the fuse will be burned.
This is why bussiness customers can safely choose samsung products.
p.s.
Hacker does not have a pejorative meaning. It is people without knowledge who demonize hackers, confusing them with crackers.
ze7zez said:
p.s.
Hacker does not have a pejorative meaning. It is people without knowledge who demonize hackers, confusing them with crackers.
Click to expand...
Click to collapse
I do not demonize hackers, I'm sorry if you got that wrong and my words didn't express what I meant: I solely wanted to express, that I am no person who committs any unlawful interference in any aspect, any country in relation to the hacking or cracking of foreign mobile phones or any device.
The only devices I work with and that's allowed are the ones that are mine.
So to speak: Any information or maybe classified information I get is in good hands.
-
In relation to the topic: A digital signature of a kernel seems to be a unique extract from specific bits of it's code, which than has to be programmed into the knox chip to make the comparison possible.
With each Kernel Update, this process has to be done, to make the above mentioned security method possible.
Does anybody know if Samsung offers the possibility of doing so with an own kernel or distro, that is not Android?
Kind regards,
TheLazyGuyDE
TheLazyGuyDE said:
(...)
Does anybody know if Samsung offers the possibility of doing so with an own kernel or distro, that is not Android?
(...)
Click to expand...
Click to collapse
I doubt it.
Samsung does not provide file signing tools.
Verizon has an agreement for the product line, but it is still android based.
Thank you.