It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile variants, the fastboot scripts are just bricking them. Well I found a fix for these issues. Those who just want to convert can skip the MSM Tool process and get right to the conversion process as long as they're already running OOS11.
First thing is first, you need to be on OOS11. If you have a T-Mobile variant and you have flashed it with India firmware, you have to use a modded T-Mobile MSM: https://forum.xda-developers.com/t/...ariant-flashing-as-well.4454357/post-87050821
If you have a T-Mobile variant that hasn't used the Indian 9 Pro MSM Tool, is on OOS12, and you're just wanting to convert, you need this tool: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
If you have a global variant or a global variant that has been flashed with Indian firmware, you can use this MSM (choose O2 for global or India for India in the Target dropdown, check Sha256, uncheck use lite firehose, it's a multi-target MSM Tool): https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
If you don't know how to use the MSM Tool, there are other guides around here, that's outside of the scope of this post.
Once you are back on OOS11, unlock the bootloader. We also need USB debugging enabled.
Now we need a tool called Fastboot Enhance. This wonderful tool allows you to directly flash OTAs from fastbootd and it doesn't have the same brick risk that flashing with fastboot scripts does.
Download it and unzip it somewhere.
Next we need the OOS11 global downgrade package (or whatever region you are wanting to switch to, global is recommended for T-Mobile variants) from here: https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
Fire up command prompt in the folder you have your platform tools and run:
adb reboot fastboot (if you do adb reboot bootloader you will then need to type fastboot reboot fastboot to get to fastbootd)
This will take you into fastbootd. It will have a screen that has three different languages to choose from on it. Go ahead and fire up Fastboot Enhance now.
It may take a few seconds for the app to recognize the device but when you see it in the list, double-click it to get to the main screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check that it says that the device is in fastbootd. Now we just need to click Flash Payload.bin and choose the OTA we downloaded earlier (we don't even need to extract the zip, the app does that for us). If it pops up with an unrecognized partitions error, you're either not in fastbootd, you didn't MSM back to stock (you cannot do this with a custom recovery), or you grabbed an OOS12 OTA. Do not continue and check that everything is correct otherwise you will brick and have to start all over with the MSM Tool. Likewise, if it pops up an alert about cow partitions, don't continue. Go to the partitions screen and search for cow and delete them all.
Once it's done, boot the device, factory reset it in the settings (this is mandatory as Fastboot Enhance does not erase the device like a normal downgrade would do and this can cause problems), set it back up, and then do the OTA process to get back to where you want to go.
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
Click to expand...
Click to collapse
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
applyscience said:
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
Click to expand...
Click to collapse
Did you use the copy partitions zip? You will brick if you don't do that after a MSM.
Process is:
MSM
Upgrade to C.48
Extract boot, dtbo, and vendor_boot from ROM
Fastboot flash dtbo, vendor_boot, and boot in that order
Reboot to recovery
Factory reset
Run copy partitions script
Reboot recovery
Flash ROM
Reboot
It shouldn't brick if you follow that process exactly.
zacattackkc said:
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
Click to expand...
Click to collapse
Awesome, glad that it worked for you! There were two other testers before you as well as myself that have confirmed this method works, I guess I should have put that in the post. Thanks for being a guinea pig
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
zacattackkc said:
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
Click to expand...
Click to collapse
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
EtherealRemnant said:
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
Click to expand...
Click to collapse
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
zacattackkc said:
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
Click to expand...
Click to collapse
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
EtherealRemnant said:
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
Click to expand...
Click to collapse
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
YourLocalDund33 said:
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
Click to expand...
Click to collapse
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
EtherealRemnant said:
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
Click to expand...
Click to collapse
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
YourLocalDund33 said:
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
Click to expand...
Click to collapse
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
I recovered my bricked LE2110 from Oneplus 9 pro Indian msm tools and I wish to restore it to Oneplus 9 global rom. I try to use the "Fastboot enhance (version 1.3)" to flash the payload.bin into my LE2110, but I cannot find any "lfash" button ! The only button I can see is "Extract Image", am I missing something ? I try local upgrade but it cannot find the firmware file ! Please help !
EtherealRemnant said:
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
Click to expand...
Click to collapse
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
YourLocalDund33 said:
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
Click to expand...
Click to collapse
Which mod are you using? There have been a bunch posted in this forum.
EtherealRemnant said:
Which mod are you using? There have been a bunch posted in this forum.
Click to expand...
Click to collapse
the one from the op. its the one thats said its multi support for indian and global
YourLocalDund33 said:
the one from the op. its the one thats said its multi support for indian and global
Click to expand...
Click to collapse
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
EtherealRemnant said:
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
Click to expand...
Click to collapse
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
YourLocalDund33 said:
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
Click to expand...
Click to collapse
It's not the MSM Tool that's borked, it's the ROM itself.
Looking for a stock c61 LE2115 Global boot.img (oneplus 9)
I overwrote mine trying to root and now I can't get the phone to boot back into c61. I have access to fastboot though
Related
Hello! I got a huge problem, i cant activate the wifi or the mobile functions on my phone after flashing it. Also in abote phone it says its a oneplus 7t (not pro)
May i have flashed a oneplus 7t firmware? I have tryed the volte fix with no ressults.. When i bricked the phone i did an flashall using fastboot, but culdent flashs system and vendors. Please help me!
I did the same thing as well. I ended up using the msm tool to flash the 9.5.3 gmba software then downloaded and updated to the 10.0.3. after that finished I downloaded the 10.3 global update and went smoothly. Then go to bootloader and flash twrp and root. First time you flash twrp make sure you check the box for ramdisk otherwise recovery won't stay as twrp, it will just keep going back to stock recovery. Also before you restart your device you have to flash magisk otherwise your phone will not boot. Also if you restart and their is no cell reception or cannot turn on wifi you will either have to go back and uninstall magisk then reinstall or do the process all over again. I did the 9.5.3 because I tried others and failed to reflash. The 9.5.3 seems to always work for many people
Knorrigbollen said:
May i have flashed a oneplus 7t firmware?
Click to expand...
Click to collapse
Impossible to tell what you've done. You haven't given sufficient info. Only you know what has been done to the phone so far. Where did you get the file, what is the file named, etc.
You have 3 threads going, none of which have sufficient info for anyone to provide proper help. Making multiple threads is not the right way to get help. Just confuses those trying to help you, and will make the situation worse. Stick to one thread, and give as much specific info as possible, as I've noted here: https://forum.xda-developers.com/on...ease-soft-bricked-phone-t4044311#post81668605
Im sorry im panicing
I tryied to flash the stock rom from this site after failed to root. THe fastboot one, when flashing it fails to flash system a and b, says partion not found
Hello again!
Ive been trying the msm tool, i downloaded it from here
https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909
It says it shuld support my version (hd1913) but MSM tool says "unsupported Target EU)
HOw can i fix this?
Also, ive flashed a oneplus 7t image, shuld i flash a new image and brick it then use msm tool?`
now it says Devices not match image. The post says it shuld support my model.
Moderator Announcement:
Thread closed and content removed on request of OP.
- Oswald Boelcke
I SERIOUSLY would like to know how you get that bug report so I can get any files for the stylo 6 boost mobile
Where did you find the zip or link to the site hosting the zip in the big report? I can get that far but I really want any help on getting similar files from this specific device model/variant
I am not gonna lie your post is an oasis in a desert and I hope this does find its way into the right hands to push root dev
Me to I have the lg stylo 6 from my cable company
I'm currently browsing through the root directory to see if I can pull the boot.img.. there's a method of rooting it with magisk manager.. the bigger issue is how to reinstall the modified boot.img.. I think we will need the bootloader unlocked
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just checked on firmware download and the kdz for lgup is available to download.. in theory because I don't have a pc to verify.. a possible root method might be as simple as, extracting the kdz file, modifying the boot.img with magisk manager, rebuild the kdz file with a kdz tool.. then flashing the modified kdz with lgup.. then install magisk manager after 1st boot and hope we have root.. feel free to test or share any other ideas..
Spoiler
It seems like very few working on this project.. I've come across a dual mode lgup made by one of our developers capable of crossflash.. probably the best version of lgup to flash firmware with modified boot.img.. I'm also buying a laptop for experiments on this device.. I now have 2 versions of the stylo 6 to play with.. hopefully I don't go overboard and turn them to paperweight .. the only thing I need is the method or tool to rezip kdz to try achieving root myself.. if anyone find such a tool, please share ..
The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.
Yeedatoy said:
The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.
Click to expand...
Click to collapse
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
Spoiler
lowkeyst4tus said:
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
View attachment 5179601
Click to expand...
Click to collapse
Give it a shot, it's not as confusing as it may look at first glance. Just put everything in the same folder on you computer. Open the tool and select your KDZ file. Extract it, and it turns it from a KDZ file into DZ file. Select extract DZ in KDZ tools next, and it will fully extract the file. You'll see a bunch of bin files. You can simply rename bin, to img for boot, and then copy it to your phone and patch it with magisk. Then copy the patched boot image back to your PC and change the img extension back to bin and rezip the KDZ.
Do you have fastboot access on the Stylo 6?
Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash
lowkeyst4tus said:
Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash
Click to expand...
Click to collapse
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.
haise.zero said:
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.
Click to expand...
Click to collapse
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results
Spoiler
lowkeyst4tus said:
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results View attachment 5181357
Click to expand...
Click to collapse
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!
haise.zero said:
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!
Click to expand...
Click to collapse
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development
lowkeyst4tus said:
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development
Click to expand...
Click to collapse
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!
haise.zero said:
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!
Click to expand...
Click to collapse
The unlocked model according to Best Buy is LMQ730QM.. I can't find a download source yet but I'm still looking
Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.
haise.zero said:
Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.
Click to expand...
Click to collapse
Great job bro.. use dual mode lgup from XDA as it's designed for crossflashing and supposed to have more features than regular lgup.. let me know if you sim unlock with Q730QM firmware.. Q730TM is the Boost Mobile model.. I have that and the Q730AM in gradient blue from cricket wireless.. I want to crossflash both to Q730QM
Alrighty, well I've been halted. Before I could get to flash, I installed the LG drivers because LGUP wasn't detecting my device (or maybe I was just being dumb).
After that... the phone stopped being recognized. In device manager it says Unknown USB (Device Descriptor Failed)
I've looked online, no solutions have helped. I've installed the Google USB drivers through Android Studio, I've uninstalled the device and reconnected the phone, tried reinstalling the LG drivers, I've factory reset the phone, tried a different USB port, a different cable, and nothing. After I factory reset, it showed up for a bit, but upon a reconnection it crapped itself again and refuses to show up.
Any ideas? I can't continue development if I can't communicate with the phone.
Never mind, possibly? It works after uninstalling the device and replugging again... for the 20th time. But ADB still won't recognize the phone even as unauthorized; it just doesn't show up. Weird... I guess I'll tinker and get back to the post here in a while.
It's back to the error... so damn weird. I'll look into it. If and when I find a solution I'll let you know.
Development has been paused for the time being.
Unlocked bootloader and acheived root/magisk on b140dl aka blu view 3, i did search for this phone on xda before(1 week ago as my first stop) and could not find, or across across web, after deep hair pulling, disapointments in the dark ( I Im pretty new at this guys), and not trying to present something already found or reinvent the wheel, just trying to perpetuate the freedom to "really OWN your device and perceverence of never giving up and you shall prevail!!!!! Any questions, pm me
rtype77 said:
Unlocked bootloader and acheived root/magisk on b140dl aka blu view 3, i did search for this phone on xda before(1 week ago as my first stop) and could not find, or across across web, after deep hair pulling, disapointments in the dark ( I Im pretty new at this guys), and not trying to present something already found or reinvent the wheel, just trying to perpetuate the freedom to "really OWN your device and perceverence of never giving up and you shall prevail!!!!! Any questions, pm me
Click to expand...
Click to collapse
Im now working on removing orange status warning (only meaning unlocked bootloader with 5 sec. delay)
I did extract my stock image in .bin dump as well as extracting .img partitions from this dump. I tried the few online methods of altering the lk.bin hex and reflash leading to no boot, no lights, no nothing as if a security encryption signature principal must be in place, to put a halt if not matched. Not sure but could sure use some advice, Im kinda new at this.
I've also been trying to figure out how to port a twrp recovery, which i also attempted, flashed, same result-phone black, no boot, so i flashed back original, back to normal,(what a scare on such a dead response!!- holding power button down and nothing) So ive softbricked twice, and recovered twice without a problem.
Specs
Helio p22 mtk chipset (6762)
4.19.127 kernel android 11
I do realize each phone has different specific source and understand this determines if twrp compatible, correct me if im wrong my friends, im just learning and open, one more thing, ive gotten a status of p22 from installed play store app device info, cpu-z. no root permission. mtk _client tool gives me p35 as my processor which is the (6735). Maybe the difference is negligible in the two 2 readings? or the mtk_client is old and rounds the 6762 to 6765, as maybe there differences are small enough to ignore 62-65 differences? Like i mentioned Im very new, and though ive researched a lot, this is tough, but i must say, I love a good game of chess!!!!
. Ive currently got two of these phones and Im starting from scratch tryna do the same thing you are. So at least youre not alone. I figured id kinda follow the guide for the b130dl (since that seems to have so much success even with other variants and devices) idk how much help I will be, seeing as I havent done any development of any kind for about 5 years.... But since I have 2, lmk if there is anything kinda risky you wanna try. (After I catch up of course)
Yeah right on, im goin at orange status removal once again, I did do a little homework, and beleive the inability to flash any custom partition is due to encryption of partitions by dm verity and or AVB preventing boot even if rooted? Not sure exactly but reading and learning. btw my friend, Im Rob, pleasure to meet. I dont know any coding, though ready to learn, just mods a bit, though im relatively new to that as well, but i try being creative, and was stoked I actually pulled off root on this newer phone, unlocked the bootloader with mtk_client, from git-hub, no problem : https://www.google.com/url?sa=t&rct...er/mtkclient&usg=AOvVaw1EA0UgBcE8bbeVuiVn4L7c
I then read all partitions to my laptop which dumped in .bin form, from there i looked everywhere for a root on this phone. too new, as i found nothing. That made me think if mtk_gui could pull off unlocking the bl, what else can it do? So read its readme a bit and noticed the magisk root using adb and fastboot, with accompaning custom magisk for mtk. Thought i was probably wasting my time as this phones security is newer. Well, it worked, so bootloader down, root accomplished with magisk, now this orange state, which i tried online hex manipulation of lk.bin file and flashed it to original lk.bin partition on phone, no boot. Tried making a custom logo.bin and same flash, no boot. So used my mtk_client tool to flash my backup abov 2 partitions and, booted right up, no problem which led me to investigate this vb meta and AVB which im currently trying to grasp. Oh and yes i figured out how to take a complete flash dump into a .bin file with mtkclient, so I have backup of partitions from this tool by reading partitions section, and also backup by using the read flash option under flash in the tool. It gave me one giant file called user.bin. I researched what bin and img files are and learned we can use 7 zip or any storage compress/decompress software or cd iso software to open bin files, so preceded with 7 zip on user.bin file and was able to extract the partitions in .img format, really cool, so now i have backup in3 styles lol .bin partitions, .img partitions or 1 .bin complete rom dump which when opened with 7 zip gives you the img forms, been fun, but this orange state and security stuff seems a bit tricky to understand, so thats where im at my freind, Let me know you need any help, Good idea about starting with previous phone guide, my thoughts exactly as well when i started gettin my hands dirty lol What a universe in these gadgets, awesome
Is there anyway you could post a guide of sorts. Looking to unlock the bootloader and root (aren't we all).
Am relatively new at this. Last phone I rooted before this year was the Epic Touch! Please at least list which downloads are needed. Thanks in advance. *Jaymi*
Thsi a Specs by your phone?
Okay. Let's go to the beginning.
I have a friend who knows how to handle Mediatek phones. He even has a BLU MT6762 with Android 9. He compiled the TWRP himself. Maybe compile one to you.
I'll try to send him a message to know if he can help you.
But the bigger question is about the original firmware (without ROOT/Magisk). Have you tried using the Smart Phone Flash Tool (SPFT) to copy all the firmware? Is there an official stock firmware? So you could use the scatter.txt file to use SPFT.
If you couldn't use SPFT then were you forced to use mtk_client?
To unlock bootloader, can you use this guide?: https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
Update:
Okay. He agreed to help. He asked someone to put the stock recovery.img file attached to the message and information about fastboot:
Code:
fastboot getvar all
and fastbootd:
Code:
fastboot getvar all
Furthermore an experienced user should contact him to test the TWRP files he will compile. So think hard if you can get your phone back to normal if something strange happens. Usually just reinstall the stock file and everything will be simple. One more detail: you should be able to understand that the test needs the phone with the full wipe process and without using magisk at the moment.
rtype77 said:
Yeah right on, im goin at orange status removal once again, I did do a little homework, and beleive the inability to flash any custom partition is due to encryption of partitions by dm verity and or AVB preventing boot even if rooted? Not sure exactly but reading and learning. btw my friend, Im Rob, pleasure to meet. I dont know any coding, though ready to learn, just mods a bit, though im relatively new to that as well, but i try being creative, and was stoked I actually pulled off root on this newer phone, unlocked the bootloader with mtk_client, from git-hub, no problem : https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjlsKWdh7b2AhVXjokEHXJ1DD4QFnoECAsQAQ&url=https://github.com/bkerler/mtkclient&usg=AOvVaw1EA0UgBcE8bbeVuiVn4L7c
I then read all partitions to my laptop which dumped in .bin form, from there i looked everywhere for a root on this phone. too new, as i found nothing. That made me think if mtk_gui could pull off unlocking the bl, what else can it do? So read its readme a bit and noticed the magisk root using adb and fastboot, with accompaning custom magisk for mtk. Thought i was probably wasting my time as this phones security is newer. Well, it worked, so bootloader down, root accomplished with magisk, now this orange state, which i tried online hex manipulation of lk.bin file and flashed it to original lk.bin partition on phone, no boot. Tried making a custom logo.bin and same flash, no boot. So used my mtk_client tool to flash my backup abov 2 partitions and, booted right up, no problem which led me to investigate this vb meta and AVB which im currently trying to grasp. Oh and yes i figured out how to take a complete flash dump into a .bin file with mtkclient, so I have backup of partitions from this tool by reading partitions section, and also backup by using the read flash option under flash in the tool. It gave me one giant file called user.bin. I researched what bin and img files are and learned we can use 7 zip or any storage compress/decompress software or cd iso software to open bin files, so preceded with 7 zip on user.bin file and was able to extract the partitions in .img format, really cool, so now i have backup in3 styles lol .bin partitions, .img partitions or 1 .bin complete rom dump which when opened with 7 zip gives you the img forms, been fun, but this orange state and security stuff seems a bit tricky to understand, so thats where im at my freind, Let me know you need any help, Good idea about starting with previous phone guide, my thoughts exactly as well when i started gettin my hands dirty lol What a universe in these gadgets, awesome
Click to expand...
Click to collapse
I get handshake error with mtk client on my b140dl, on both windows and relived iso. Would love to have mine unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys, I am a total noob with android but I have this same model hone and I have a custom OS. I'm not sure what it means outside of:
"my crazy ex gf managed to get spyware on my new phone like the day after she got the cops to take my old one (Jan 12th) and has been ruining what's left of my sad existence"
But google isn't giving me any results for this firmware version or really this model phone at all so if it would help people working on modding it and there is a way I could like dump the data from it somewhere?
jayleemcnabb81 said:
Is there anyway you could post a guide of sorts. Looking to unlock the bootloader and root (aren't we all).
Am relatively new at this. Last phone I rooted before this year was the Epic Touch! Please at least list which downloads are needed. Thanks in advance. *Jaymi*
Click to expand...
Click to collapse
Hi Jaymi, sorry for the late 2 month late response, been totally busy and other places, but yes, i think i will make a guide, to the best of my ability as im relatively new at this as well and have never wrote a guide, but shall give it my best! Any questions, just ask, Rob
Can someone show me how to do this? it appears OP has been offline and nobody ever got around to actually SHARING THIS METHOD OF BOOTLOADER UNLOCK... I used to unlock my phones bootloaders all the time around 2014 but the game has changed and now you gotta edit files on notepad and download github sources it seems...
tl:dr: NEED ISNRUCTIONZ pl0X!!
rtype77 said:
Yeah right on, im goin at orange status removal once again, I did do a little homework, and beleive the inability to flash any custom partition is due to encryption of partitions by dm verity and or AVB preventing boot even if rooted? Not sure exactly but reading and learning. btw my friend, Im Rob, pleasure to meet. I dont know any coding, though ready to learn, just mods a bit, though im relatively new to that as well, but i try being creative, and was stoked I actually pulled off root on this newer phone, unlocked the bootloader with mtk_client, from git-hub, no problem : https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjlsKWdh7b2AhVXjokEHXJ1DD4QFnoECAsQAQ&url=https://github.com/bkerler/mtkclient&usg=AOvVaw1EA0UgBcE8bbeVuiVn4L7c
I then read all partitions to my laptop which dumped in .bin form, from there i looked everywhere for a root on this phone. too new, as i found nothing. That made me think if mtk_gui could pull off unlocking the bl, what else can it do? So read its readme a bit and noticed the magisk root using adb and fastboot, with accompaning custom magisk for mtk. Thought i was probably wasting my time as this phones security is newer. Well, it worked, so bootloader down, root accomplished with magisk, now this orange state, which i tried online hex manipulation of lk.bin file and flashed it to original lk.bin partition on phone, no boot. Tried making a custom logo.bin and same flash, no boot. So used my mtk_client tool to flash my backup abov 2 partitions and, booted right up, no problem which led me to investigate this vb meta and AVB which im currently trying to grasp. Oh and yes i figured out how to take a complete flash dump into a .bin file with mtkclient, so I have backup of partitions from this tool by reading partitions section, and also backup by using the read flash option under flash in the tool. It gave me one giant file called user.bin. I researched what bin and img files are and learned we can use 7 zip or any storage compress/decompress software or cd iso software to open bin files, so preceded with 7 zip on user.bin file and was able to extract the partitions in .img format, really cool, so now i have backup in3 styles lol .bin partitions, .img partitions or 1 .bin complete rom dump which when opened with 7 zip gives you the img forms, been fun, but this orange state and security stuff seems a bit tricky to understand, so thats where im at my freind, Let me know you need any help, Good idea about starting with previous phone guide, my thoughts exactly as well when i started gettin my hands dirty lol What a universe in these gadgets, awesome
Click to expand...
Click to collapse
Hey, I have a B140DL and unlocking it's bootloader has become personal. I have achieved root on other handsets and tablets, but this little bastard is something else. I was just inquiring to see if you ever put together a guide. Any advice is greatly appreciated. I will say for a cheap phone, it has been a Mother-Fuxxer!
iamx51 said:
I get handshake error with mtk client on my b140dl, on both windows and relived iso. Would love to have mine unlocked.
Click to expand...
Click to collapse
I kept getting handshake error also. Then I started getting device not configured. Have you made any headway?
One more thing, out of curiosity I ran the command "fastboot flashing lock" and I got a menu that asked Do you wish to LOCK BOOTLOADER? Locking your BOOTLOADER will wipe your device of all DATA! You must then flash your phone with a stock ROM.
Looking into this device myself and having a hard time. I haven't rooted a phone since a droid x2 and back then i did it with some kind of software through an ubuntu terminal. Not sure what's being used now but has anyone been able to do this or can anyone offer any tips or guidance?
oldt7mer said:
Looking into this device myself and having a hard time. I haven't rooted a phone since a droid x2 and back then i did it with some kind of software through an ubuntu terminal. Not sure what's being used now but has anyone been able to do this or can anyone offer any tips or guidance?
Click to expand...
Click to collapse
MTK Client and Python with Chimera exploit can supposedly do it. Look to GitHub. Hope you enjoy a challenge. I have made little problems.
ive been playing with this all day and its safe to say this is impossible with currently released tech on the latest security updates. the only way youre going to be able to do this is if youre able to force the phone into brom mode. doesnt seem possible from where im standing unless that can be done, would have to be done through a hardware mod.
oldt7mer said:
ive been playing with this all day and its safe to say this is impossible with currently released tech on the latest security updates. the only way youre going to be able to do this is if youre able to force the phone into brom mode. doesnt seem possible from where im standing unless that can be done, would have to be done through a hardware mod.
Click to expand...
Click to collapse
in case i wasnt clear, if you are on 2021 security updates with this phone (i.e. havent updated it or just got it and declined updates) you can easily unlock the phone with mtkclient and root with magisk; however if you've installed the 2022 security updates, brom mode is basically disabled making it impossible to unlock the phone.
oldt7mer said:
ive been playing with this all day and its safe to say this is impossible with currently released tech on the latest security updates. the only way youre going to be able to do this is if youre able to force the phone into brom mode. doesnt seem possible from where im standing unless that can be done, would have to be done through a hardware mod.
Click to expand...
Click to collapse
Run the fastboot command "fastboot flashing lock". Do that and tell me what you think. Trust me. Just be sure to read the prompt on your phone.
oldt7mer said:
in case i wasnt clear, if you are on 2021 security updates with this phone (i.e. havent updated it or just got it and declined updates) you can easily unlock the phone with mtkclient and root with magisk; however if you've installed the 2022 security updates, brom mode is basically disabled making it impossible to unlock the phone.
Click to expand...
Click to collapse
MTK Client has been no go. Lib USB error and NO BACK END error.
So I have been testing out a number of different custom ROMs without having any issue until I flashed Lineage 19.1 and decided I didn't like it. I tried to move to StagOS and everything just went south. The recovery refused to boot after being flashed. I tried it multiple times and it would just bring me back to fastboot after a black screen and the device giving a vibration. In this process I lost the installed ROM too because at one point I tried to reboot and see if it would boot normally (I had a feeling that it wouldn't but it was already late and I wanted to get a working device again and go back to bed so I tried it) and had to fuss around with the phone quite a bit to get it to boot into fastboot so I could shut it off and put it in EDL mode because if I didn't get the timing right, the force reboot dropped me right back to the black screen and then the phone went unresponsive for a bit again.
Went and ran the MSM Tool to get it back to stock global ROM. That worked fine. Updated to 11.2.10.10 which also worked fine. Unlocked bootloader, device wiped itself, rebooted and the device failed to boot. It dropped me to fastbootd. Tried to reboot and it just kept going back to fastbootd.
Okay, let me try this again. MSM a second time. Worked fine. Updated to 11.2.10.10. Worked fine. Unlocked bootloader, device wiped itself, rebooted aaaand... device dropped me back to fastbootd again. Tried to do the manual recovery with fastboot and it failed to flash a bunch of files with some saying that protected partitions can't be flashed and some saying the partition doesn't exist despite me following the entire process exactly, including the reboot in the middle. Okay, guess it's MSM time again.
So now I ran MSM the third time and decide maybe it's an issue with 11.2.10.10 (even though I swear I was able to unlock the bootloader just fine when I did this exact process the last time when I was first downgrading from OOS 12 to install a custom ROM for the first time last week) so I go to unlock right after MSM before updating. That works perfectly. I guess I must have been wrong about the way I did it the first time? Hmm.
I have to say that I have never actually had such difficulty with any device before and as you can see from my signature, I have had a ton of them. When I first got this thing and started reading in the forum, I thought it was weird seeing so many people with bricked devices. Yeah I don't feel that way anymore. It's a good thing that we have the MSM Tool because for some reason, it's just really easy to wipe these things out.
I was able to get StagOS back up and running with no problem after updating to 11.2.10.10 by using the same recovery I was trying to flash that didn't work before so I have no clue what the issue was that broke everything and I'm also not sure why I was unable to unlock the bootloader on 11.2.10.10 but all's well that ends well.
Now I'm going to set up Signal and Google Voice and go to bed. It's almost 4AM here.
Y'know, I went through pretty much the same thing yesterday trying to install Stag. Currently stuck in EDL and I cant flash due to param preload if using lite firehouse or sahara error if not. Any chance you could send a link to the exact MSM tool and ROM?
EDIT: This is only a few minutes later but I am now flashing the India OP9 Pro rom and it seems to be working without giving me error. Fingers crossed though.
EDIT2: IT BOOTS, I am so ready to refuck everything up : )
Soldre said:
Y'know, I went through pretty much the same thing yesterday trying to install Stag. Currently stuck in EDL and I cant flash due to param preload if using lite firehouse or sahara error if not. Any chance you could send a link to the exact MSM tool and ROM?
EDIT: This is only a few minutes later but I am now flashing the India OP9 Pro rom and it seems to be working without giving me error. Fingers crossed though.
EDIT2: IT BOOTS, I am so ready to refuck everything up : )
Click to expand...
Click to collapse
I have a global NA variant OnePlus 9 and this is the one I use.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
I don't know why I had so many problems. I'm not new to this, my device list is in my signature and I put custom ROMs on most of them and never had an issue like that before, but at least I managed to figure it out and get it working again lol. Gonna stick with Stag, never would have left if I didn't need Verizon support temporarily.
EtherealRemnant said:
I have a global NA variant OnePlus 9 and this is the one I use.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
I don't know why I had so many problems. I'm not new to this, my device list is in my signature and I put custom ROMs on most of them and never had an issue like that before, but at least I managed to figure it out and get it working again lol. Gonna stick with Stag, never would have left if I didn't need Verizon support temporarily.
Click to expand...
Click to collapse
None of the ROMS I've tried have supported verizon, stag is supposed to get it in the next update. Gonna have to find a way to MSM the stock op9 ROM bc right now I can only get op9 pro MSM to work :C
Is your phone a le2110 ? Is le2115? Mine le2110 Chinese variant , I had flash with Chinese ROM , then flashed it with the global ROM , that cleared my software issues , got drivers msm tool of OP remote team including ROM
jab5555 said:
Is your phone a le2110 ? Is le2115? Mine le2110 Chinese variant , I had flash with Chinese ROM , then flashed it with the global ROM , that cleared my software issues , got drivers msm tool of OP remote team including ROM
Click to expand...
Click to collapse
It's LE2115.
If I have to use the MSM again I'll just have to remember not to upgrade to 11.2.10.10 until after I unlock the bootloader because that worked fine, it seems like there's something broken in the unlock process for global 11.2.10.10. Been running StagOS without issues since.
EtherealRemnant said:
It's LE2115.
If I have to use the MSM again I'll just have to remember not to upgrade to 11.2.10.10 until after I unlock the bootloader because that worked fine, it seems like there's something broken in the unlock process for global 11.2.10.10. Been running StagOS without issues since.
Click to expand...
Click to collapse
I always unlock bootloader immediately after msm when I'm on firmware 11.2.4.4 always have and zero issues.
mattie_49 said:
I always unlock bootloader immediately after msm when I'm on firmware 11.2.4.4 always have and zero issues.
Click to expand...
Click to collapse
Yep was exclusively an 11.2.10.10 issue.
Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
easy way all right?
NishiMoon said:
Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the View attachment 5675937 easy way all right?
Click to expand...
Click to collapse
No need to wait for months to get any image. You can use msm read back. F8 when it opens.( oneplus )password and read back the images you want to your C/drive.
Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18
NishiMoon said:
Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18
Click to expand...
Click to collapse
I have been looking for a way to do this for my LE2117 for so long could you. Type a quick walk through on your method with EDL and Terminal or I can just try with the MSM Tool Readback I just found that out as well.
NishiMoon said:
Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the View attachment 5675937 easy way all right?
Click to expand...
Click to collapse
Any Link to this Stock Boot.img ?
Let me see if I can find it in my files
mattie_49 said:
No need to wait for months to get any image. You can use msm read back. F8 when it opens.( oneplus )password and read back the images you want to your C/drive.
Click to expand...
Click to collapse
Do I Need ROOT to do this on a T-Mobile OP9 ?
( seems too easy...)
barguybrady said:
Do I Need ROOT to do this on a T-Mobile OP9 ?
( seems too easy...)
Click to expand...
Click to collapse
No
NishiMoon said:
Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18
Click to expand...
Click to collapse
So...
Are you gonna offer any further supporting details, links, comments, or such about using EDL mode?
I cannot find any list of Commands, at least for a Linux Shell ?
barguybrady said:
So...
Are you gonna offer any further supporting details, links, comments, or such about using EDL mode?
I cannot find any list of Commands, at least for a Linux Shell ?
Click to expand...
Click to collapse
I don't know anything about Linux . I mentioned msm read back to pull images from what build your using. And how to use and password. One must partially find their own way eventually. We all have Google , I know there is info on what I shared.
mattie_49 said:
I don't know anything about Linux . I mentioned msm read back to pull images from what build your using. And how to use and password. One must partially find their own way eventually. We all have Google , I know there is info on what I shared.
Click to expand...
Click to collapse
Yes. I had one last time to access a Win 10 computer, late last night.
Using the MSM readback mode is Ridiculously EasY!
( maybe That's why some of these Forums have gotten quiet lately..? With Readback, getting ANY boot.img is almost easier than other methods...)
With root & magisk, I'm All Set !
May The Force Be With You All !
barguybrady said:
Yes. I had one last time to access a Win 10 computer, late last night.
Using the MSM readback mode is Ridiculously EasY!
( maybe That's why some of these Forums have gotten quiet lately..? With Readback, getting ANY boot.img is almost easier than other methods...)
With root & magisk, I'm All Set !
May The Force Be With You All !
Click to expand...
Click to collapse
If your into flashing builds may I suggest Pixel Extended here in the threads. Surely nice.
mattie_49 said:
If your into flashing builds may I suggest Pixel Extended here in the threads. Surely nice.
Click to expand...
Click to collapse
Hah !!
I was thinking about That One !
Bought the OP9 for the camera - and after 19 months on Lineage, with g-Cam & Open Cam, I was contemplating switching to Pixel Ext for it's advertised camera compatibility...
But, I doubt I'll keep this phone for much longer, mostly due to All the Issues that brought me here in the first place, carrier branded.... yadda, yadda, yadda....
SO, with Root, I think I'll keep using OOS, handle the Updates from t-MO as they come along, and Every Time I get Frustrated at this thing - use that as a reminder to Buy an International and Unlocked Phone from my Guys In Chicago....and run what-ever I wish, in any way I wish - WithOut Advertising or Bloat ! !
barguybrady said:
Hah !!
I was thinking about That One !
Bought the OP9 for the camera - and after 19 months on Lineage, with g-Cam & Open Cam, I was contemplating switching to Pixel Ext for it's advertised camera compatibility...
But, I doubt I'll keep this phone for much longer, mostly due to All the Issues that brought me here in the first place, carrier branded.... yadda, yadda, yadda....
SO, with Root, I think I'll keep using OOS, handle the Updates from t-MO as they come along, and Every Time I get Frustrated at this thing - use that as a reminder to Buy an International and Unlocked Phone from my Guys In Chicago....and run what-ever I wish, in any way I wish - WithOut Advertising or Bloat ! !
Click to expand...
Click to collapse
Fyi latest 5.7 PE has fully functional Oos cam. All video modes working perfect like stock. Slo-mo ,4k 8k. I'm real picky and always msm back to stock. I've def found a home.
mattie_49 said:
Fyi latest 5.7 PE has fully functional Oos cam. All video modes working perfect like stock. Slo-mo ,4k 8k. I'm real picky and always msm back to stock. I've def found a home.
Click to expand...
Click to collapse
That's quite AN Endorsement !