Help in finishing device tree - Android

I am trying to finish up a device tree for my device (samsung conquer 4g) that was started by utankos. Here is what he finished https://github.com/utkanos/android_device_samsung_SPHD600 I have been looking around for a while now but I still dont know what files I need to make and how to make them. Am I able to port over files from another devices tree? Also can someone help me with this and help me get a starting place? Thanks.

bump

bump

le bump

We can't magically tell you "You need files xyz.". Find the device tree for a similar device and base off that, compile, and then just start checking logcats and kmesg's.

Related

[Q] PSFreedom for Eris?

Just wondering if this is working on our devices? its working on the desire now
h t t p: / /forum.xda-developers.com/showthread.php?t=772795
and if so what steps do we need to take to get it working? thanks guys.
According to a discussion on a different forum, a few people have tried this on the Eris but it fails to flash. So still waiting on our phone, sadly they don't list the Eris on their compatibility list. They do list the HTC Hero but I'm not sure if they use the same USB Controller or not. Someone far more educated in this field can help with that.
Googling around a little pulled up a few discussions that appeared to indicate that the eris is a compatible usb controller. But I tried flashing it (one KayosFroyo v32) and as mentioned I get a error during flash... Hopefully someone can get it working.
What exactly is this?
coffindancer said:
Just wondering if this is working on our devices? its working on the desire now
h t t p: / /forum.xda-developers.com/showthread.php?t=772795
and if so what steps do we need to take to get it working? thanks guys.
Click to expand...
Click to collapse
According to the PSFreedom compatibility chart development for the Eris is "In Progress." It appears that a custom kernel will have to be built to support the exploit, presumably not too difficult.
coffindancer said:
Just wondering if this is working on our devices? its working on the desire now
h t t p: / /forum.xda-developers.com/showthread.php?t=772795
and if so what steps do we need to take to get it working? thanks guys.
Click to expand...
Click to collapse
well from what i read from the github tracker @ http://github.com/kakaroto/PSFreedom
he says: This linux kernel module should work on the N900 (RX51 machine).
It uses the musb driver to access the address of the usb and modify it.
If you want to port this, have a look at psfreedom_machine.c and implement the
missing functions for your device. Make it compile-time #ifdef and modify
the Makefile.
To compile, type 'make' inside scratchbox.
dont know how to do this just hoping this will help someone with porting it
UPDATE: just found a small how-to on how to port it if anyone understands this and/or how to do it all ps3+eris owners will forever be in your debt
Q: How can I port it to a new device.
A: Well, first, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’..
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL speed isn’t available .
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it…
Edit: the controller the eris uses is MSM72K
any new developments on this? i see it's now listed on the PSfreedom compatibility list as in progress.
h t t p://psfreedom.com/wiki/index.php?title=Device_compatibility_list
As of this morning the website psfreedom.com is not available as well as the link for the chart is broken. I did many tests with my eris, using a CM6 Froyo rom to Other roms that were ported from other phones with different pse-enable zips. The best I was able to get to was the boot screen with the 3 skateboard androids. That setup was a CM6 2.2 rom with the zip files for the HTC Wildfire. Every other setup the zip failed to flash thru recovery. Thats the best I got so far.
EDIT
cant sleep so I tried to get onto psfreedom website and it is back up. It has been ported to the motorla droid. hopefully soon we will be so lucky
posted in another thread but here it is again.
I dont think we will be seeing this on the eris for sometime as the USB driver used is actually the msm_hsusb driver. This was verified last night when i was in #psfreedom where someone was trying to get psfreedom on an eris and kept running into a problem and it turned out to be because of the msm_husb driver was in use. so until that msm_husb driver is working with psfreedom we are probably SOL.
This is now working on the Eris i tested it for the dev waiting for him to officially release it should be this afternoon.
If what your saying is true I will name my children after you and the dev LOL
Sent from my Eris using XDA App
For the love of humanity don't.
Any way you can list what you did try and where I can get the files needed to try this myself... maybe with instructions on how? I very much want to try this and have been patiently waiting for days now.
http://psfreedom.com/wiki/Device_compatibility_list
have fun guys all credit goes to the Dev rgov and the other devs working on psfreedom
I've carefully read the directions on the PSFreedom Wiki site for Droid Eris. My first question is this:
How can I achieve S-off in the bootloader? My Eris is rooted and I am currently running KaosFroyo v34. When I reboot to bootloader, it shows S-on and I cannot fastboot.
yeah i had the same exact issue that's why i made the note in the wiki. i essentially had to go through and redo the root following jcases post here.
hope it's not against the rules to link this......
http://androidforums.com/eris-all-things-root/121597-how-install-engineering-bootloader.html
Trying now... will keep you updated. Thank you.
Question: Since my phone is already rooted, do I just start at step 6 and flash PB00IMG.zip? To be honest, these directions are kinda confusing to me. I tried this method months ago and was never able to fastboot... maybe I am doing something wrong. coffindancer, I appreciate any and all help you are providing and hopefully you can assist me in getting this PSFreedom up and running.
i think you can start with PB00IMG.ZIP and it will go ahead and reflash the boot loader so it's S-OFF im not positive though. Im a freak and just followed the steps pretty much step by step maybe someone with more experience can explain it better.
So even though you were already rooted, did you still flash the engtools.zip? Or did you skip step 2?
skipped step 2 i believe.
also the dev is redoing the wiki so if you don't see the link for the files just be patient.

[Q] Weird issue with broken ADB in HTC Sense Kernel/Base

Hi there,
I've recently dove into ROM Development for my Evo due to a weird issue that I'm seeing on my device. This issue is also seen on many other devices from tablets to the nexus one. I seem to be one of the only few that's seeing it on the Evo, and the general community doesn't have enough knowledge to assist. I'm hoping someone will know some ideas to try from a cooking standpoint to see if I can fix this for my particular situation and maybe help out the others that are grasping for a fix from Google and aren't getting one.
In my situation, ADB ONLY works on the initial base release of FroYo from Sprint with regards to HTC Sense-based roms. When Sprint released their second updated base, 3.28.651.1, ADB was/is broken. I can get ADB to work in Recovery as well as ANY AOSP rom, so I'm thinking the culprit might be the Kernel (g3a8614e and onwards) and/or the base version.
USB Debugging does not work because the ADBD process is not running. See this Google bug for what the Nexus users are seeing:
http://code.google.com/p/android/issues/detail?id=9437
I'm very knowledgeable, and have tried so many rom and kernel combos it's disgusting YES, I've turned on USB Debugging. the ADBD process does not run, and throws a segmentation fault whenever you try to start it. I've checked my properties file to make sure the service.persist is enabled, yada yada.
I've torn apart the kernel from that initial release and paired it with a later base. The ADBD process then runs, but ADB still doesn't work. I've also, like other users in that link, have pulled out an ADBD process from the working one, and that also does not work, although it too makes the ADBD process function again inside the ROM.
So my questions are:
Can anyone explain what might be causing the ADBD process to be blocked? There's not much documentation out there on it. What part of the ROM build controls all of that? My initial thought was the boot.img, and I've messed around with that, diff'ing an older working ROM with a newer one to no avail.
Can anyone suggest something to try, or a technique to frankenstein something that might work? I'm an Android dev, and I can't put my in process app on my phone and test it because ADB simply doesn't work. My app uses the camera, so I need my phone instead of the emulator. I'd rather not flash an old rom or AOSP rom, because I'm really trying to figure out what's going on!!!
Thank you so much in advance for any assistance you can provide. If you can help me figure this out, I'll gladly send you a donation!
BTW, this subforum is amazing! I stumbled onto it looking for a better way to pack and unpack boot images.

[Q] Asus Zenfone 5 bricked!

Hello guys,
My phone is bricked since i mess around with the build.prop. I found a tutorial to unbrick it, but i can't do it since i haven't toggle the usb debugging in the developers settings. now I'm stuck at the animation. However every thing is working until it says error: device offline. Can anyone help me to make my device online via adb! PLEASE! HELP!!!!
tutorial i use:http://asuszenfone-blog.blogspot.com/2014/07/asus-zenfone-flash-tutorial-via-adb.html
P.S: I'm not an expert at these, but at least i can understand them...
[UPDATE]
i have made it online(sideload), but i can't find a way to flash the ROM... I don't know where to put the folder that contains the ROM...
Pegasus195 said:
Hello guys,
My phone is bricked since i mess around with the build.prop. I found a tutorial to unbrick it, but i can't do it since i haven't toggle the usb debugging in the developers settings. now I'm stuck at the animation. However every thing is working until it says error: device offline. Can anyone help me to make my device online via adb! PLEASE! HELP!!!!
tutorial i use:http://asuszenfone-blog.blogspot.com/2014/07/asus-zenfone-flash-tutorial-via-adb.html
Click to expand...
Click to collapse
Here is a good guide for ADB: http://forum.xda-developers.com/showthread.php?t=2141817
You will want to use push and push your fixed build.prop to /system
You will probably need to reset the permissions using ADB shell and chmod. You want rw-r-r, and I think the code is for that is 644.
luckily i already change to the original build.prop before restarting my phone..., so i don't know why it's still broken...
I am not trying to push the build.prop, i just want to flash the original ROM to my phone to make it like new again...

[DEV] Lets start developing for the M4

The lack of custom roms for our device is depressing, there aren't enough developers for the M4 aqua and while some have moved on to other devices, others don't share their REAL sources and fixes. So what i propose is that we all join forces and do it ourselves, the more people the better it brings different points of view and consequently faster fixes, so for those that are interested here are the prerequisites:
1. A computer
2. A linux distro (most guides will advice you to go for ubuntu or a buntu based distro personally its not my cup of tea, i use gentoo but linux is about choice you choose what suits you. Also if you want to keep your windows you can either dual boot(recommended) or just use a virtual machine which depending on specs it can be slloooww).
3. A starting point (most people don't even try to compile android because they wont even know where to start from, thankfully sony isn't as bad as others and even provides detailed information on how to compile android for their devices, so i suggest to start here http://developer.sonymobile.com/kno...aosp-marshmallow-for-unlocked-xperia-devices/ )
4. Time (compiling times can take very looonnnggg)
5. Patience ( yeah a hell lotta of it)
Still interested?
We can use this thread to post compiling errors , bugs, errors and any android developing related questions, if instead of aosp you want to jump straight to cyanogenmod the instructions are very similar just replace "repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.1_r10" with "repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0" xda also has some very useful threads we can use here are a few:
1. Compiling roms:
CM - http://forum.xda-developers.com/showthread.php?t=2060017
PAC - http://forum.xda-developers.com/showthread.php?t=2662325
2. Debug
Create logs - http://forum.xda-developers.com/showthread.php?t=2185929
Understand them - http://forum.xda-developers.com/showthread.php?t=2274119
Every great dev had to start at some point this might be start of some great devs (we need them), so lets start compiling and bring the marshmallow to the tulip!!!
We have a few custom roms that just need bug fixes. We will get better as time goes on. And would we see a rom of yours anytime soon?
I don't find the m4 binaries in this page http://developer.sonymobile.com/knowledge-base/open-source/open-devices/list-of-devices-and-resources/
Hello guys, as much of you know, I tried so many times to compile roms for our device, but never had success. My device for now enter in a "bricked fastboot" mode, and in flashmode Flashtool say that the device have debugging off. Totally bricked. But, I will never give up with my work for this device. I will make roms for you guys and for my experience, also if I cannot test. So, I installed Ubuntu in my PC, I am syncing the sources and this time I will try very hard! Thanks CarDGee for your post, it will be helpful for errors.
So, what would be our requirements knowledge wise? What programming language base, etc?
Any kind of knowledge of programming language can be useful, but is not needed.
alby_var said:
Hello guys, as much of you know, I tried so many times to compile roms for our device, but never had success. My device for now enter in a "bricked fastboot" mode, and in flashmode Flashtool say that the device have debugging off. Totally bricked. But, I will never give up with my work for this device. I will make roms for you guys and for my experience, also if I cannot test. So, I installed Ubuntu in my PC, I am syncing the sources and this time I will try very hard! Thanks CarDGee for your post, it will be helpful for errors.
Click to expand...
Click to collapse
I think at this point it would be smart to collaborate on a custom rom (probably CM 12.1 because it is closest to stable) so we have a base to develop more roms.
For now I'm working to build AOSP 5.0
I followed the instructions to build AOSP at developer.sonymobile.com
At point 4. it say
Find the software binaries for the device you want to use on Sony’s AOSP for Xperia devices
Click to expand...
Click to collapse
Now i have downloaded the binaries for the M2. It have the Kanuti and Tulip folder inside.
Can i use it for build or do i have to extract the files from the device?
Second question is. I can remove other devices from local_manifests.xml right?
You can also use GitHub sources and put them into android sources with git clone, with this method also if you edit files, you'll not have problems with repo sync.
@dani020110 download the Z5 ones inside the zip you will have kanuti and tulip folders as well.
@alby_var what do you mean "bricked fastboot" is it constantly with blue led on? have you tried holding powerbutton + vol up until it vibrates 3 times?
@jefins although its a plus to know C java etc.. its not a requirement i am a strong believer that you learn by doing it.
@jtg01 yes use the ones from the zip also take a look at this repo https://github.com/SonyAosp you can find the binaries there under platform_vendor_sony and platform_vendor_qcom.
Now i regret not having done one of those "Reserved" on the second post.....
@alby_var what do you mean "bricked fastboot" is it constantly with blue led on? have you tried holding powerbutton + vol up until it vibrates 3 times?
..
Click to expand...
Click to collapse
The device , on a pc without drivers is recognized as qhsusb_bulk. It is recoverable, but any tool doesn't recognize the smartphone.
On a pc with all drivers it is recognized sometimes as SOMC FLASH DEVICE, other times in SEMC FLASH DEVICE. Also this is recoverable, but Flashtool says that the device have debugging mode off. (I cannot boot to the rom to activate it.)
And the only led that the device show is red, it bright up 3 times only when the battery is at 0%
alby_var said:
The device , on a pc without drivers is recognized as qhsusb_bulk. It is recoverable, but any tool doesn't recognize the smartphone.
On a pc with all drivers it is recognized sometimes as SOMC FLASH DEVICE, other times in SEMC FLASH DEVICE. Also this is recoverable, but Flashtool says that the device have debugging mode off. (I cannot boot to the rom to activate it.)
And the only led that the device show is red, it bright up 3 times only when the battery is at 0%
Click to expand...
Click to collapse
Do you have the correct flash and adb drivers on your pc? My second phone is a xperia E4.i had the same problem with SEMC and SOMC.i thought that it was bricked but the problem solved when i installed adb and flash drivers from the flashtool drivers file.
I installed all drivers that is on the Flashtool Folder trought the exe, but Flashtool not start flashing...
So i compiled the sources and got a system.img and a userdata.img in out/target/product/generic ?
I think there have to be a boot.img. Do i have to compile the kernel as well? Cause instructions on sony developer say the repos contain a precompiled kernel.
@alby_var: which version of flashtool do you use? Had also problems to flash firmware on newest version. So i installed Flashtool Version 0.9.19.7. With that it worked fine.
@alby_var try the linux version of flashtool
@jtg01 there must be something wrong because it should be out/target/product/e2303 or out/target/product/tulip did you choose our device after source build/envsetup.sh && lunch? because i believe you just compiled generic android.
Compiled android 6 for 2303, attached the Make log Below. (Pure Sony AOSP)
yet to flash the images and check.
made a small change, the userdata.img is for 16GB as i have a M4 Aqua Dual (E2363) the device should be able to boot up, will add logcat when i have it.
Lots of warnings but was able to make successfully
open the log in notepad++
Edit: First attempt to boot, loops at Sony logo.
will make fresh and check again
@jtg01 there must be something wrong because it should be out/target/product/e2303 or out/target/product/tulip did you choose our device after source build/envsetup.sh && lunch? because i believe you just compiled generic android.
Click to expand...
Click to collapse
Yeah there was a problem. Now it compiled all img's . But userdata.img has only 70 Mb. System is 900 Mb.
Should i flash this?
Edit:
Flashed it got bootloop. Can't take a logcat cause it restart at Sony logo.
But i get a kernel_boot_log. There are multible errors. Maybe someone can help me with that.
Guys I not know how to adapt device sources to the rom for that I am building.. Can anyone please help me?
@RohitBopnna and @jtg01 for some strange reason newest firmware doesnt allow you to flash custom firmware you will have to downgrade to .128 and then flash your roms i am sure it will boot, follow the instructions on Jeffreyvh aosp thread http://forum.xda-developers.com/m4-aqua/development/aosp-6-0-e2303-t3271380
@alby_var I think you should start by compiling something we already have the sources see how it goes, and then move on

[HELP]Flash preloader for mt6750 on LG device[HELP]

hi
the other day i tried to dd in a bootloader to add fastboot to my K8+ (2018) LMX210ULMA and wiped my preloader. The device uses an mt6750 chipset and i had made a back up so i have the approriate software to restore it, i even have the scatter file.
The problem is that there is no da_pl.bin file for lg phones to use sp flashtool, i have no download mode and no fastboot.
i have two pc`s one running ubuntu the other windows 7.
i would appreciate any help
any help at all
ok so ive found some versions of sp flash tool that are supposed to get around the authorization stuff and i have an auth file but i keep getting brom errors. the same one in fact. on linux ifs 0x00. ive been looking at and following the tutorials ivs made android rules and all kinds of things but i cant get it to flash. it started to befote i added the stuff in the tutorials. The red line would go acrross the bottom but now i just get the brom errots.
Thumb up for boldness... :good:
Now you have some interesting project there.
Keep us update if you manage to find out any solution.
No idea how to help but Good luck!
https://blog.hovatek.com/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files/
https://ifindhub.com/download-mtk-secure-boot-da-loader-files-mtk-devices.html
ill get there eventually. I have been looking at all the config and ini files and i hate to say it but security might be essier than you think to overcome. just have to erase a few lines here and there and teplace some as needed. idk ty. Dont worry ill keep you guys posted
i really think sometime we over think and see past the easiest solutions. but what do i know im trying to flash an mtk preloader on an lg phone.
im actually trying to unbrick a few phones. two qc `s and the mtk. I kinda bricked one of my lmx210`s on purpose not thinking it would brick. well jokes on me.
Im have a couple questions maybe somebody can help with. In the past couple months on my journey through madness i have tried a few hindred different ways and more flashtools than you could imagine. So far nothing has worked but ive learned alot of theory.
so far though i know that the mtk board is in bootrom mode. We will get back to that as i have an idea....
ok on the qc boards we have the dreaded 9008 mode. I made some progress today. i wanted to see if the LMX210 could boot from SD card instead of the internal. I believe it can but im having trouble with what to do next. p
i used dd to flash the gpt on my sdcard then formatted the partitions to the proper filesystem. when i plugged it in to the usb it lit up but did not boot. But it lit up for the first time since bricking.
But it only lights up with usb plugged in. Add the batrery and it goes dead. It also doesnt show 9008 mode any more.
i went back and changed the boot and recovery images to reflect using the mmcblk system and now windows device manager can see it. But no boot. im wondering first if i might need a special boot loader to boit from sd and two if i might be able to use the same trick to get the mtk running
Some LG firmwares include some files for SPFT, like LGX240ARAT and LGX230HAT.
but do they work with MT6750? In LGX240ARAT there is a dll that mentions MT6755,
but not MT6750. Newer versions probably needed. Or maybe you could hack it. ??...
part of my problem is not knowing what scatter file to use. these phones have thier info all twaktup. the mtk gives several different board/chip types. like we have 6722, 6755, 6750, 6736 and so on. im pretty sure though its a 6750 board with 6755 chipset but do i use the scatter for the board or the chipset.
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Duhjoker said:
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Click to expand...
Click to collapse
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
CXZa said:
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
Click to expand...
Click to collapse
Hi,
If you can reach bootROM mode by pressing any of the volume keys while you connect the phone (Mediatek Inc. MT6627) you should be able write and read the EMMC with amonet.
The tool needs some modifications in order to make it work to MT6750. You can probably try with the mt6753 version which may work for MT6750:
https://github.com/Dinolek/amonet
For reference, use this commit:
https://github.com/R0rt1z2/amonet/commit/6b57d0a99f42739d3b3b2ce962b32ecb8fefd950
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Duhjoker said:
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Click to expand...
Click to collapse
PM me if you need help editing the python script
Regards.
I really appreciate your offer for help. I was looking at the reference for porting and now that i can see the things that would need changing why not go ahead and unlock the bootloader while we are at it. We could save a ton of devices and at the same time give them th3 extra value of being able to twrp and root them.
I have been looking for some way to unLock the bootloader on these phones for days and though it will be some work being able to reflash the preloader AND unlock the bootloader which was my main intent when i bricked it would be worth the extra effort.
Rortiz2 said:
PM me if you need help editing the python script
Regards.
Click to expand...
Click to collapse
I couldnt post the main.py script in the pm but i can attach it here. Thank you so much.
Here is the raw preloader extracted using salt on my pc.
Ok so i went through your source code for the meizu m2 amonet to match it with source code for the mt6750 and i only had to change a couple things. Its pretty much identical to the commit you pointed me too.
As far as i can see your amonet should work just fine with the sp200/lm-x210ulma boards. I did add my .img files to the bin folder though.
Any way i keep getting errors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Rortiz2 said:
Hi,
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Click to expand...
Click to collapse
Hi,
Didn't continue experiments but now also @Duhjoker might be interested about this last new development...
[EXPLOIT] [BOOTLOADER] Mediatek based LG K10 2017 M250 bootloader secure boot bypass. by @OficerX
https://forum.xda-developers.com/lg-k10/how-to/exploit-mediatek-based-lg-k10-2017-m250-t4183545
MT6755 and MT6750 are essentially the same, MT6750 is cheaper and slower version of MT6755, these are compatible, you can use tools for 6755 on 6750.
Here (https://github.com/arturkow2000/lgk10exploit) you have tools that can help you flash preloader (write_boot0.py), these should work on your device.
Open config.py set BR_DEV_PATH to /dev/ttyACM0
then write: python write_boot0.py --brom path_to_your_preloader_bin
This is slow process, may take few minutes (you will see progress while flashing).

Categories

Resources