Hello, first time posting on XDA! Please let me know if I've done anything wrong.
I have a Moto G Pure, and I'm attempting to remove the bootloader unlocked warning. When reading through other XDA posts, I've gathered that I need to go into fastboot and flash the logo partition with a modifiied logo.bin file. However, in order to flash the partition, you need a bin file to flash it with.
I've gone through the process of rooting the phone, and now have root access with adb. I'm currently looking for a logo.bin file, however I don't believe I'll be as lucky as having it lay around. However, I've noticed two files in the /dev/block/bootdevice/by-name dir: logo_a and logo_b. Both of these are around 100mb big, so I have reason to believe these are what I'm looking for.
As to what I'm confused about: Which logo file do I choose, and how do I convert it to a logo.bin file?
Thank you everyone for your support, as this is my first time messing around with a phone. I am a developer who uses Linux, so I'm not going in completely blind. If there's anything I'm doing incorrectly, if not everything already, please let me know.
OoLunar said:
Hello, first time posting on XDA! Please let me know if I've done anything wrong.
I have a Moto G Pure, and I'm attempting to remove the bootloader unlocked warning. When reading through other XDA posts, I've gathered that I need to go into fastboot and flash the logo partition with a modifiied logo.bin file. However, in order to flash the partition, you need a bin file to flash it with.
I've gone through the process of rooting the phone, and now have root access with adb. I'm currently looking for a logo.bin file, however I don't believe I'll be as lucky as having it lay around. However, I've noticed two files in the /dev/block/bootdevice/by-name dir: logo_a and logo_b. Both of these are around 100mb big, so I have reason to believe these are what I'm looking for.
As to what I'm confused about: Which logo file do I choose, and how do I convert it to a logo.bin file?
Thank you everyone for your support, as this is my first time messing around with a phone. I am a developer who uses Linux, so I'm not going in completely blind. If there's anything I'm doing incorrectly, if not everything already, please let me know.
Click to expand...
Click to collapse
@OoLunar
Please read the guidances that are stuck on top of every forum prior to your next posting like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator
I apologize for posting my question in the wrong category, thank you for your patience @Oswald Boelcke
I found a stock image online which uses logo_a as logo.img, so now it's just a matter of converting that img into a bin
OoLunar said:
I found a stock image online which uses logo_a as logo.img, so now it's just a matter of converting that img into a bin
Click to expand...
Click to collapse
You're doing this wrong. First download your stock ROM from here: https://mirrors.lolinet.com/firmware/moto/ellis/official/
Then extract the zip file, and grab the logo.bin file.
Open it with Moto Boot Logo Maker: https://forum.xda-developers.com/t/...ker-source-code-included-version-2-4.2848667/
Take the normal boot logo from your bin file (You should be able to extract the existing boot logo from the bin file into an image file using this tool) and then overwrite the warning image with it. Save your modified logo.bin file, and flash it to the phone with `fastboot flash logo logo.bin`
You're doing this wrong. First download your stock ROM from here: https://mirrors.lolinet.com/firmware/moto/ellis/official/
Then extract the zip file, and grab the logo.bin file.
Click to expand...
Click to collapse
Thanks for giving me the link, however when downloading https://mirrors.lolinet.com/firmware/moto/ellis/official/TMO/, which I believe is the TMobile download, I only have logo.img, not logo.bin. I can't mount the logo.img and see the contents of it like I could with any other img file, likely due to a missing filesystem driver
Bash:
[[email protected] ~/Downloads/XT2163-4_ELLIS_TMO_11_RRH31.Q3-46-20_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_CFC_R3_CFC.xml]$ sudo mount logo.img /mnt
Password:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
The Boot Logo Maker isn't able to open the file either, saying it's an "invalid logo.bin file loaded" (which I expected, but tried anyways)
Sanras said:
You're doing this wrong. First download your stock ROM from here: https://mirrors.lolinet.com/firmware/moto/ellis/official/
Then extract the zip file, and grab the logo.bin file.
Open it with Moto Boot Logo Maker: https://forum.xda-developers.com/t/...ker-source-code-included-version-2-4.2848667/
Take the normal boot logo from your bin file (You should be able to extract the existing boot logo from the bin file into an image file using this tool) and then overwrite the warning image with it. Save your modified logo.bin file, and flash it to the phone with `fastboot flash logo logo.bin`
Click to expand...
Click to collapse
Additionally, in the servicefile.xml, there's this XML key:
XML:
<step MD5="c3ca0c450dd4fbca182a522f8dbe62a0" filename="logo.img" operation="flash" partition="logo_a"/>
Which was what I meant by logo_a as logo.img
OoLunar said:
Additionally, in the servicefile.xml, there's this XML key:
XML:
<step MD5="c3ca0c450dd4fbca182a522f8dbe62a0" filename="logo.img" operation="flash" partition="logo_a"/>
Which was what I meant by logo_a as logo.img
Click to expand...
Click to collapse
Huh, ok. That's weird, I wouldn't have expected the logo file to be that. I did this on my Moto Z3 Play, and it had a normal logo.bin. I'm afraid I can't help you in that case.
No worries. I know a lot of other people have messed with logo.img before, since they have Snapdragon CPU's (Qualcomm has logo.bin iirc). Are there not any converters for the file formats, or any programs that can read the logo.img file format?
hi, I am trying to remove the orange1 screen that is unlock warning screen. When I try to replace it the new text screen start appearing how I can remove that.
OoLunar said:
I've gone through the process of rooting the phone, and now have root access with adb.
Click to expand...
Click to collapse
Can you post a link describing the process you used? Thanks
I don't actually remember which methods I used, though I'm relatively sure ImageMagisk was involved. Do note that rooting involves unlocking the bootloader which will start a factory reset on your phone.
I'll probably root my phone again soon to get root SSH access to it (as I did previously). When I do, I'll be sure to post the links/describe the methods I used.
As for my original question, I believe logo_a was the file I was looking for, though I cannot confirm as I never followed through.
OoLunar said:
I don't actually remember which methods I used, though I'm relatively sure ImageMagisk was involved. Do note that rooting involves unlocking the bootloader which will start a factory reset on your phone.
Click to expand...
Click to collapse
Good tip, thanks. I'm planning to root a Moto G Pure ( https://www.gsmarena.com/motorola_g_pure-11145.php )myself so that's why I'm interested in the process. Here's a link I found: https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
Was it the one you used or was it something else? Thanks
Damn, all the genius on this forum and no one figured it out? The moto pure is mediatek, just like the moto g power 2022 tonga
greerdd said:
Good tip, thanks. I'm planning to root a Moto G Pure ( https://www.gsmarena.com/motorola_g_pure-11145.php )myself so that's why I'm interested in the process. Here's a link I found: https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
Was it the one you used or was it something else? Thanks
Click to expand...
Click to collapse
Hey! I've finally gotten around to rooting my phone again. This time however, I rooted a Moto G Play instead of Pure. From what I remember with my Pure, the process was still the same.
The issue I had this time when rooting was the Motorola website was incorrectly saying that my phone was not qualified to unlock the bootloader. Here's the link I used: https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-b
When submitting the "Can my device be unlocked?" request, the website will submit a post request as following:
Code:
curl -X POST \
"https://en-us.support.motorola.com/cc/productRegistration/verifyPhone/<line 1>/<line 4>/<line 3>/"
These "lines" or "parts" are your device id retrieved from fastboot oem get_unlock_data. Take the device id, put it all on one line, removing any extra (bootloader) or INFO at the beginning. Once your device id is on one line, the same format that the support website required, you are going to "split" the device id by their #. Literally replace the # with a newline. Then open up the following URL in your browser:
Make sure you're logged in on the website.
Code:
https://en-us.support.motorola.com/cc/productRegistration/unlockPhone/<line 1>/<line 4>/<line 3>/
After that, you should be redirected to https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-c, receiving an email with your code very shortly. Then follow https://forum.xda-developers.com/t/guide-un-locking-motorola-bootloader.4079111/ as expected. To install Magisk, I referenced https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
I hope this helps <3
Related
Hello!
It seems like I am one of the few people to have a RS987 variant of the V10. I love everything about this phone, but it's killing me not having root access. I've avoided making a topic dedicated to this variant by posting in other threads and PMing people, but I've gotten nowhere.
I'm unable to unlock the bootloader like the T-Mobile variant even though I have to ability to enable "OEM Unlock" in the dev settings, and I've attempted to flash the Verizon VS990 5.1.1 KDZ to my phone in hopes I could root it after flashing it but it failed.
I'm willing to donate $40 to anybody that can provide a root method for RS987 variant of the V10.
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
SoulAce1290 said:
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
Click to expand...
Click to collapse
This just the KDZ for stock 5.1.1, which I provided
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
https://mega.nz/#!8k1UyCyC!Z2NIKvNOEkXBiElMLrXkv0RyPKhCN2q0KvlI1OH6ImY
this DZ file with
https://mega.nz/#!xgMgBIQD!VHtXeIlzpPydKRICtGfBUjXvtdN-KNtqX6U9bu3bY8Y
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Succeeded in flashing out.dz ... but
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
WillyPillow said:
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
LINK REMOVED
this DZ file with
LINK REMOVED
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Click to expand...
Click to collapse
joatamonk said:
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
Click to expand...
Click to collapse
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Pre-rooted system.img file for RS987 LG V10
WillyPillow said:
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Click to expand...
Click to collapse
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
@joatamonk
I just remembered what the problem is. I forgot a critical step in making the DZ
Unfortunately, I'm a bit busy recently, and I might not be able to fix this until next week. Sorry to keep you waiting.
joatamonk said:
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
Click to expand...
Click to collapse
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
No luck
WillyPillow said:
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
Click to expand...
Click to collapse
I thank you greatly for your efforts, however this .dz file didn't work. It got farther than the last one you had made. After flashing it with LG UP 1.14 the phone would reboot, show the android guy (the one with a spinning gear in it's belly), that screen would stay for about 5 seconds, phone would restart again, and then get stuck on the initial LG power up screen, it never played the startup sound or showed the animated LG logo.
RS987 must be a little different than the Verizon version? Perhaps it only loads signed kernels, or signed images or something?
Is this .dz file made from the pre-rooted image I had uploaded? Is there software that can be used to pack .DZ files from the .img file? So that I can try different methods of rooting system.img and flashing that to the phone?
The good news is the phone works fine after I flashed the stock RS98712a file back to the phone.
Thank you again for your efforts, they're appreciated.
Joata
Subscribed
Hello there,
as you may know you can change the oem splash screen on the OnePlus 3, as provided in this thread by @makers_mark here.
That program only needs minor fixes to work with OnePlus 3T splash partitions, and I have attached the source code and a windows binary below.
To use it, extract the "OnePlus3TInjector.zip" and run the commands in the command prompt in the folder you extracted the zipfile into.
To decode use:
Code:
OP3TInject -i LOGO.bin -D
After having changed the image files, use
Code:
OP3TInject -j fhd -i LOGO.bin
I have tested this and it works on my phone, but you still have to USE THIS ON YOUR OWN RISK.
If you want to see how this looks, take a look at this video here: https://www.youtube.com/watch?v=DWj2WRpcoqI
If you want a custom bootlogo but can't use the tool you can pm me an image file or post one here down below. I will send you a zip file that you can flash in recovery.
To use this, get the "Stock" zip from below, and replace the modified.logo.bin in it with the one produced by the injector, then flash in your recovery.
If you do not want to use your recovery use a terminal emulator on your phone and run the command as root:
Code:
dd if=/sdcard/Downloads/modified.logo.bin of=/dev/block/platform/soc/624000.ufshc/by-name/LOGO"
To go back to stock logo.bin, flash the zip file attached below.
Please note that this does not remove the warning that your phone is unlocked.
Finally a big shoutout to @prmcmanus who tested this for me. Leave him a like!
I also thank @makers_mark for all the work he has done on the OnePlus 3 and the original OP3Injector.
Jo_Jo_2000 said:
Hello there,
as you may know you can change the oem splash screen on the oneplus 3, as provided in this thread here:
That program only needs minor fixes to work with OnePlus 3T splash partitions.
Unfortunately I cannot provide a compiled program here because the original program was not published under a proper license, but I can tell you that you just need to change line 35 of the file "src/LogoInjector.v1.4.c" from the zip archive linked in the thread below to be "#define MAXOFFSETS 32" instead of "#define MAXOFFSETS 28" and recompile the program.
I have not yet tested it, so I do not know whether this works or just bricks your phone, so USE THIS ON YOUR OWN RISK.
If you want to test this for me, but do not want to compile the program yourself, you can flash my "beta-test" version linked below. Follow the instructions from the original thread above. Remember to backup your current LOGO partition.
Note to moderators:
I know that this should rather belong into the development section, but I do not yet have enough posts to post there, so I put it in here. Sorry about that but I do not want to randomly spam other threads to get the 10 responses needed.
Click to expand...
Click to collapse
Thanks. I put in a bit of time trying to figure this out with a 3t and git code. First: I wasn't interested in the "logo" partition exactly, but more about that "unlocked bootloader" and it's associated tag warning and timeout that comes up each boot after unlocking bootloader. I found the timeout and the text that goes on the screen here in the code (the bootable bootloader code) : ~/sandbox/oneplus3t/bootable/bootloader/lk/app/aboot/aboot.c : I even tested changing that, but there was no easy way to to "give it out" aside from as part of a custom ROM done from source.
Are we talking about the same thing? Or : are you talking about just replacing one logo partition content with another and it has nothing to do with the unlocked tag warning & timeout (5 sec.)?
Thanks.
---------- Post added at 05:06 AM ---------- Previous post was at 04:48 AM ----------
OK: I checked it out and it has nothing to do with the unlocked bootloader warning, which I'm working on as said above and have gotten rid of on my own phone (which I no longer have..). That's completely about the file I mentioned above "aboot.c" in bootable/bootloader/... tree.
But nice going anyway, -- thanks.
Nope, these are different things. I'm refering to the logo partition which stores images while the warning message is hardcoded into the bootloader which you probably cant change because it's signed by OnePlus.
Also OnePlus hasn't released their bootloader sources (I think) and the bootloader in the source tree is just the generic base for all quallcomm bootloaders (aka Little Kernel).
So sorry to disappoint you but you won't be able to remove that warning with LOGO editing.
Jo_Jo_2000 said:
Nope, these are different things. I'm refering to the logo partition which stores images while the warning message is hardcoded into the bootloader which you probably cant change because it's signed by OnePlus.
Also OnePlus hasn't released their bootloader sources (I think) and the bootloader in the source tree is just the generic base for all quallcomm bootloaders (aka Little Kernel).
So sorry to disappoint you but you won't be able to remove that warning with LOGO editing.
Click to expand...
Click to collapse
So the rom I built from their 3t sources must have used boot.img as a "prebuilt"? Does that sound right? I guess I could unpack boot.img and figure out how to get rid of the delay with a binary overwrite. (I wouldn't look forward to testing that ;
It's in the bootLOADER which is not a prebuilt nor a thing you build yourself when you build a custom rom. Its build, maintained and signed by OnePlus so they and only they can alter the bootloader (I think so, maybe "flashing unlock_critical" does the trick here, but dont try it or you will irreversibly hard brick your phone).
Also good luck with a binary overwrite, I hope you know ARM assembly.
To get that clear, the warning message has got _nothing_ to do with boot.img, they are two completely different things and no matter what you do with a boot.img, you won't get rid of that warning!
I know there's a flashable .bin that gets rid of that exact same unlocked bootloader msg and delay on the moto x pure 2015 (XT1575). Maybe it's similar. I've attached the file.
I doubt that this will work... the original logo.bin is about 16mb and even if I just repack it with the original images it's only about 700kb
noahvt said:
I doubt that this will work... the original logo.bin is about 16mb and even if I just repack it with the original images it's only about 700kb
Click to expand...
Click to collapse
Good that you are concerned and looking for errors I might have made!
However I am very certain that the file indeed is only .7 MB large because:
1. That program (without mods) works on the oneplus 3, whose file is also only about that large
2. The first 786432 bytes (the size of the recoded file) of the original LOGO.bin dump are identical
3. the remaining 16 mb are zeroed out and contain no data
4. the program produces correct images
I would be happy to try it out, because I do not have access to a PC where I can run the MSM Downloader in case I brick things!
Greetings.
g96818 said:
I know there's a flashable .bin that gets rid of that exact same unlocked bootloader msg and delay on the moto x pure 2015 (XT1575). Maybe it's similar. I've attached the file.
Click to expand...
Click to collapse
The OnePlus 3t's warning is hardcoded into the bootloader, so unless you find a bug in sbl1 or break rsa you won't get around that.
I compiled this and got it working, but can't share for the same reasons as OP.
If anyone wants a custom logo, PM me the picture and I'll make an image file for you
prmcmanus said:
I compiled this and got it working, but can't share for the same reasons as OP.
If anyone wants a custom logo, PM me the picture and I'll make an image file for you
Click to expand...
Click to collapse
So you can use this without bricking your phone?
Jo_Jo_2000 said:
So you can use this without bricking your phone?
Click to expand...
Click to collapse
Yep, working on mine
Hey, @prmcmanus... PM'ed you!
@Ker~Man did you get my reply? It doesn't look like Quick Reply works :-S
prmcmanus said:
@Ker~Man did you get my reply? It doesn't look like Quick Reply works :-S
Click to expand...
Click to collapse
I sure did, and thank you! How do I install these, though? Flash in TWRP? I'm not too keep with .bin files. Thanks again!
Ker~Man said:
I sure did, and thank you! How do I install these, though? Flash in TWRP? I'm not too keep with .bin files. Thanks again!
Click to expand...
Click to collapse
look in my opening post, I've written two methods there.
Ker~Man said:
I sure did, and thank you! How do I install these, though? Flash in TWRP? I'm not too keep with .bin files. Thanks again!
Click to expand...
Click to collapse
Put the phone in fastboot mode and flash:
Code:
fastboot flash LOGO filename.bin
Jo_Jo_2000 said:
look in my opening post, I've written two methods there.
Click to expand...
Click to collapse
That 2nd method, I didn't know you could do that in the terminal! Nice
Jo_Jo_2000 said:
Hello there,
as you may know you can change the oem splash screen on the OnePlus 3, as provided in this thread here:
That program only needs minor fixes to work with OnePlus 3T splash partitions.
Unfortunately I cannot provide a compiled program here because the original program was not published under a proper license, but I can tell you that you just need to change line 35 of the file "src/LogoInjector.v1.4.c" from the zip archive linked in the thread below to be "#define MAXOFFSETS 32" instead of "#define MAXOFFSETS 28" and recompile the program.
Click to expand...
Click to collapse
I apologize for not responding to you soon enough. When I figure out an encoding, I release the source code for the encoder and decoder that I build for a couple of reasons. And one of those reasons is so you can do like you did! And you did it right! Thanks for asking and giving a link which in my book is good enough for proper credit. Feel free to share the binary with whoever:good:
I replaced the logo injector .zip file because it created an error when executed by some people.
You can use it now.
Jo_Jo_2000 said:
I replaced the logo injector .zip file because it created an error when executed by some people.
You can use it now.
Click to expand...
Click to collapse
Does my device have to be "Critical Unlocked"? I have an unlocked bootloader but when I try "fastboot flash LOGO" I get "FAILED (remote: Partition flashing is not allowed)"
EDIT: flashing it with dd works though
Hey all,
I recently purchased a Unihertz Titan Pocket and I'm looking to try out LineageOS on it. I found this project on Github and have read through the instructions; however, they are for the *Unihertz Titan*, not the Pocket. I'm not sure they will work for the model I have and regardless, I'm wary about trying something that I know little about. Could anyone take a look at the link and let me know if the instructions could work for me?
Here are some additional links, for anyone else who is working on the same or similar goals:
-Official firmware and flash tool from Unihertz (for trying to restore bricked/messed up devices)
-Rooting Guide for Unihertz Titan Pocket
I am interested in flashing a custom ROM such as LineageOS onto my Unihertz Titan Pocket. It's my understanding that I will need custom recovery software such as TWRP in order to carry out the installation process. There is no official build of TWRP for the Unihertz Titan Pocket, and I haven't been able to find any unofficial builds for it either. So I have three questions:
1) Does anyone know of an unofficial TWRP build for my device?
2) Is there someone who might be able to create an unofficial build? I am willing to help as best I can, but my knowledge of how to do so is essentially null. I found this thread for the TWRP Builder project, which looked awesome, but seems to be defunct at this point. I also found this answer from a contributor to the project, who claims (as of 2021) that the project is on hiatus but "making a progressive return." The thread looks pretty dead to me though so it's hard to tell if they are back up and running in any capacity.
3) Is there another way to flash a custom ROM without TWRP? For example, these instructions (for a different model, the Unihertz Titan) don't mention using TWRP.
[For others with a Unihertz Titan Pocket, I asked about finding and installing a build of LineageOS on this device in another post here]
Kisa3908 said:
Hey all,
I recently purchased a Unihertz Titan Pocket and I'm looking to try out LineageOS on it. I found this project on Github and have read through the instructions; however, they are for the *Unihertz Titan*, not the Pocket. I'm not sure they will work for the model I have and regardless, I'm wary about trying something that I know little about. Could anyone take a look at the link and let me know if the instructions could work for me?
Click to expand...
Click to collapse
@Kisa3908 Welcome to XDA! I hope you'll always get the support you require.
Prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Android Q&A. Additionally, I merged your other thread into this one. Please also review the XDA Forum Rules, to which you agreed to adhere when you registered a few hours ago, and post only ONCE respectively in an existing thread instead of creating a new one.
Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
did the author succeed in his trials?
I am looking to obtain root on Pocket, but would rather have someone who has done it already guide me if necessary
I was able to install LineageOS on the Titan Pocket, following this tutorial:
Rooting Cubot KingKong Mini 2 | Deadbadger
Jakub Kaderka personal webpage, electronic hacking, projects,etc.
deadbadger.cz
What I am not able to do is to use the numbers on the physical keyboard, does anyone have an idea how to make it work? I assume it's something with the keyboard layout. I installed the KIkaInput.apk thinking that is the one missing, but still not working.
talmid01 said:
I was able to install LineageOS on the Titan Pocket, following this tutorial:
Rooting Cubot KingKong Mini 2 | Deadbadger
Jakub Kaderka personal webpage, electronic hacking, projects,etc.
deadbadger.cz
What I am not able to do is to use the numbers on the physical keyboard, does anyone have an idea how to make it work? I assume it's something with the keyboard layout. I installed the KIkaInput.apk thinking that is the one missing, but still not working.
Click to expand...
Click to collapse
There's a tool on github (look for uinput-titan-pocket on google, you should find it) that maybe can help! If you succeed in making the keyboard work could you please share the info? I want to get a lineageOS GSI but the Titan Pocket is my main phone so I need it to be fully functional.. Hope I helped!
EDIT: uinput is for the touch scrolling, this (https://github.com/SinuXVR/pocket-board) seems to be the solution to hat you asked.
talmid01 said:
I was able to install LineageOS on the Titan Pocket, following this tutorial:
Rooting Cubot KingKong Mini 2 | Deadbadger
Jakub Kaderka personal webpage, electronic hacking, projects,etc.
deadbadger.cz
What I am not able to do is to use the numbers on the physical keyboard, does anyone have an idea how to make it work? I assume it's something with the keyboard layout. I installed the KIkaInput.apk thinking that is the one missing, but still not working.
Click to expand...
Click to collapse
Can you tell me what ROM do you use? There are many.
diejuse said:
Can you tell me what ROM do you use? There are many.
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net
sourceforge.net
Also to have the right keyboard settings you need to edit the keylayout files.
talmid01 said:
Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net
sourceforge.net
Also to have the right keyboard settings you need to edit the keylayout files.
Click to expand...
Click to collapse
Can you edit /system/usr/keylayout with LineageOS? I can't edit it with stock rom?
There are any problem? All is working?
Can you explain the steps to install it?
Download the latest bvS version of GSI Lineage from this folder:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Enter Settings->Phone info and tap several times on the Build number, now in Settings->System->For Developers allow Debug over USB and Bootloader unlock
Connect to PC with android SDK installed and run adb reboot bootloader, you'll need to confirm device authorization on your phone.
Once in bootloader, run fastboot flashing unlock to unlock the bootloader and follow the instructions on your phone (this step factory resets the phone, you'll loose all your data).
Download the official stock ROM and unpack the downloaded rar. (
https://www.reddit.com/r/unihertz/comments/r2dz0a
)
In the directory with unpacked ROM, run fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img to flash the vbmeta.img with disabled Android Verified Boot to allow flashing unofficial ROMs.
Reflash the recovery and boot partitions by running fastboot flash boot boot.img and fastboot flash recovery recovery.img. Technically this shouldn't be needed, but if your phone is running a different stock ROM version, it's advisable.
fastboot reboot fastboot reboot to fastboot, the system can be flashed only from this mode, for some reason it doesn't work in the previous mode...
Now you can flash the system.img by running the fastboot flash system YOUR_SYSTEM_IMAGE.img. Select system.img file from the ROM you want to flash.
fastboot reboot and you are booted in your new ROM!
Once it is booted into Lineage enable Rooted ADB debugging in the Developer Settings. Now we need to fix the keyboard settings. Download and install the following apk:
com.blackberry.keyboard-4.1904.2.16698.apk
drive.google.com
Then disable the soft keyboard in the Settings.
Download https://github.com/SolidHal/Unihertz-Titan-lineageos-microg
adb root
adb remount
adb shell mount -o remount,rw /
adb push system_usr_idc/* /system/usr/idc/
adb push system_usr_keychars/* /system/usr/keychars/
adb push system_usr_keylayout/* /system/usr/keylayout/
Then restart your phone. I hope it will work for you.
On the Pocket, the system partition is called "Super".
The command should then be "fastboot flash super (My System ROM.img)...". Correct?
Medionato said:
On the Pocket, the system partition is called "Super".
The command should then be "fastboot flash super (My System ROM.img)...". Correct?
Click to expand...
Click to collapse
The Titan Pocket and Titan Slim use a super partition, which has a number of different .img files embedded inside of it. You can flash the super.img to your super partition from the stock rom zip, but you can't just flash system alone, you need to repackage the super.img in order to then flash it. I am working on a number of projects for the Titan series, i just ordered a Slim this morning, so i will get to work detailing the differences in the process between the Titan and the Titan Slim (which will mostly be transferable to the Titan Pocket, at least i expect so).
I also flashed Andy Yan's personal build of lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img on my Titan Pocket. It booted up, but with one problem: mobile communication does not work at all: the SIM is recognised correctly, but it is completely disconnected from the mobile network and shows 'emergency call only'.
I have flashed the image using the following steps:
fastboot flashing unlock
fastboot -w
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot # I don't know the details, but the Titan Pocket cannot flash system in Bootloader mode.
fastboot flash system lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img
fastboot reboot
I have been struggling with this problem for a month now and am stuck. Does anyone have any information on this? Thanks.
argxentakato said:
I also flashed Andy Yan's personal build of lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img on my Titan Pocket. It booted up, but with one problem: mobile communication does not work at all: the SIM is recognised correctly, but it is completely disconnected from the mobile network and shows 'emergency call only'.
I have flashed the image using the following steps:
fastboot flashing unlock
fastboot -w
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot # I don't know the details, but the Titan Pocket cannot flash system in Bootloader mode.
fastboot flash system lineage-18.1-20220715-UNOFFICIAL-arm64_bvS.img
fastboot reboot
I have been struggling with this problem for a month now and am stuck. Does anyone have any information on this? Thanks.
Click to expand...
Click to collapse
Your steps look questionable. Titan Pocket and Titan Slim dont have flashable system partitions. As noted above they have super partitions.
Hi everyone, Im new here and will start by saying I've never successfully installed a custom ROM, so I'm heavily in the research phase.
I have a Titan Pocket in route and is my goal to set it up with a new os and trashcan Google for good. I'm at a toss-up right now between LineagOS or GrapheneOS.
From what I've read so far, Graphene is only "officially" supported for Google pixel phones. Does anyone know if it can still work on the Pocket?
If not I might default to Lineage and follow the advice in this thread. I'm also open to any suggestions for security base ROMs I should consider. TIA.
I'd like to start by saying after 2 weeks of researching and piecing guides together to unbrick my phone was hell. But once i found the right route it took me less thank 10mins all from a simple tool called Fastboot Enhanced V1.3.0. Now this Nifty little tool took me from bricked phone which was saying "Your img(Boot, Recovery) have been destroyed please flash the right files or contact customer service to fix this problem to Unbricked in less than 10 minutes. It took me 2 weeks of researching but it's finally done. Now most of you will say well you could have use MSMTool or the MTK or even SP Flash Tool. Those are all fine and dandy and all but one problem with those. YOU have to SCOUR the internet to TRY to find files you need to actually be able to use them. I been over several guides. I had when a guide basically says this 1) DO THIS SKIP SKIP SKIP important parts 2) NOW DO THIS. Like WTH was i supposed to do in between 1 and 2. Todays guides lack thoroughism and complettioin. Guides these days take Half Ste;ps and then thrown together.
I will also leave a step by step instructions on how to use the Fastboot Enhanced V1.3.0 in DETAIL on how to get your phone from what mine did to Unbricked state. I will also attack Nord N200 5G DE2118 .img FIles for those who have a hard time scouring the internet for things. I for one get agitated and aggravated as hell when searching the internet for things. Especially when you have to pc things together. I will leave files if it's Fine by staff. Now these files have come directly from my OnePlus Nord N200 DE2118 extracted less than 2 hours ago 10:04 p.m. EST September 10th 2022. Can Only attach One File? and i can't even remove the accidental clicked bmp pic of COD BO Cold War Zombies.
Guide For Using Fastboot Enhanced V1.3.0
1) Download Fastboot Enhanced Tool from: https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ from XDA Which is how I came across it. . The Tool is a WINDOWS ONLY Tool. (How many guides i came accross that didn't state whether it's for Windows or Linux) I use Dual Boot so I have both.
2) Install Fastboot Enhanced V1.3.0 and wait for it to finish. Now you will only have to be in Fastboot Mode to do any of this. I can't believe how a semi hard problem was fixed really easy
3) Now you will Have to Have a Payload.Bin File which can be found with any OEM Firmware for Your specific Phone. The Payload.bin allows you to be able to do a Payload Dump Using Fastboot enhance it is at this point if any of your partitions are missing or corrupt you will find out because it will tell you if you can understand the way it's explains it.
4) This Nifty little tool will tell you your device naem whether your phone is using secure boot or not, current slot your phone is using if you have an a/b partition scheme and the update Status. This is Listed Under basice properties. AGAIN MAKE SURE YOUR IN FASTBOOT MODE.
5) Next tab is the Partitions Tab which will List all your partitions currently on your phone . To the right of your listed partitions you will have and ACTIONS Tab. This is the tab where you can flash, erase, delete, create, and Resize your partitions. With this tool You CAN Flash Important Partions So be careful what you flash.
6) Next Tab Over is the Payload Dumper. This is the Tab where you need the Payload.bin File for your specific phone. this will give you payload version manifest size, metadata signatures size Metadata Signatures (Base64), data blobs, singatures size signatures (Base64) Fuill package Yes or No. Timestamp and block size. also under payload dumper tab another tab shows up called the Dynamic Partition Metadata. Now this will list your REALLY IMPORTANT Dynamic Partitions These are the partitions you don't want to flash anything over them. It will give you the Partition group size, which partitions are included and tells you wheter snapshot is enabled or not.
7) Under The payload Dumper tab the partitions tab gets a different Actions box. This time i'ts a box that let's you extract your .IMG files from your phone it allows for incremental as well as to ignore unknown operations and ignore checksums also under this partitions tab it gives you a checksum for each and every one of your partitionss. Ok now on to the Simple but yet comprehensive guide.
8) Now to start you want to add the Payload.bin to the Payload Dumper and then click on the Partitions tab. Once under this tab you will select each partition and hit the extract button and extract it to a folder named something like Flash FIles.
9) you hace to do this for each partition. Once done you will have your .IMG files from your exact phone for future use as well. You then want to click on the Fastboot Visualization tab and then click on Partitions.
10) Once under the partitions tab here, you will want to start flashing your .IMG files to the partitions. it should take you around 10 to 15 mins total to finish flashing everything.
11) Once your finished flashing you want to do a quick Terminal and do a FASTBOOT -W and then Fastboot Reboot and watch your phone start working again.
FEEL FREE TO LEAVE ANY COMMENTS SUGGESTIONS ON WHAT COULD HAVE BEEN BETTER OR IF IT'S NOT ENOUGH DETAIL. I TAKE CONSTRUCTIVE CRITICISM WITH A GRAIN OF SALT. THIS WAS MY FIRST GUIDE I EVER PUT TOGETHER. LOL THIS GUIDE TOOK ME LONGER THAN IT DID UNBRICKING MY PHONE.
BELOW YOU WILL FIND .IMG FILES FOR ONEPLUS NORD N200 DE2118
Thanks so much man. This phone has been an absolute pain in my ass to unbrick, the issue Ive had with Fastboot enchance is that all the firmware versions Ive found seem to contain images it doesnt recognize for the phone.
Do you have the original OTA for these , or the un-extracted payload.bin youd possibly be able to post?
So I went through the process without success, the only abnormalities I noticed were that my device did not have a partition for "my_carrier.img" , so that wasnt flashed.
And upon using the fastboot -w command, it did execute but at the end was given the message "Erase successful, but not automatically formatting.
File system type raw not supported."
Silent_Song1982 said:
Thanks so much man. This phone has been an absolute pain in my ass to unbrick, the issue Ive had with Fastboot enchance is that all the firmware versions Ive found seem to contain images it doesnt recognize for the phone.
Do you have the original OTA for these , or the un-extracted payload.bin youd possibly be able to post?
Click to expand...
Click to collapse
I found the way MSMTool works too. I'm going to probably write a guide for that too. MSMTool is so much easier.
Silent_Song1982 said:
So I went through the process without success, the only abnormalities I noticed were that my device did not have a partition for "my_carrier.img" , so that wasnt flashed.
And upon using the fastboot -w command, it did execute but at the end was given the message "Erase successful, but not automatically formatting.
File system type raw not supported."
Click to expand...
Click to collapse
I had a lot of issues with Fastboot Enhance too until I realized I was the one causing errors. Any logical partition it doesn't recognize you can create an empty partition wiht that name and it will resize it then copy it over. Also make sure whatever slot you're on, so say slot a, your logic paritions would be system_a, system_ext_a, vendor_a, product_a and odm_a except I dont see odm.img in the list of file by OP so I'm not sure if that will even help.
and now i have ran into HARD BRICKED mode trying to flash a custom from. phone will only load EDL and everytime I try msmtool I get the error Check OCDT CDT file empty please redownload it. and I scoured the internet for 4 days now and all I can find is stuff like What is .CDT extension but nothing about having and empty CDT file for android. getting frustrated with it now
Link575 said:
I had a lot of issues with Fastboot Enhance too until I realized I was the one causing errors. Any logical partition it doesn't recognize you can create an empty partition wiht that name and it will resize it then copy it over. Also make sure whatever slot you're on, so say slot a, your logic paritions would be system_a, system_ext_a, vendor_a, product_a and odm_a except I dont see odm.img in the list of file by OP so I'm not sure if that will even help.
Click to expand...
Click to collapse
here is the ODM file. if you might be able to post a cdt file much apppreciated
sorry took so long to upload it for you
MiniNinja2024 said:
here is the ODM file. if you might be able to post a cdt file much apppreciated
sorry took so long to upload it for you
Click to expand...
Click to collapse
Hey I appreciate it but I didn't need it I was just informing the poster above that the ODM file was missing and that might cause an issue when using Enhanced Fastboot. Not really sure what a cdt file is though, sorry.
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
hitsndc said:
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
Click to expand...
Click to collapse
my phones being recognized as a Oneplus A5000 for some reason now. and it's a Nord N200 i've also been stumped by the attached pic and my phone is stuck in EDL mode
hitsndc said:
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
Click to expand...
Click to collapse
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
vipermark7 said:
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
Click to expand...
Click to collapse
this is my version
DE18CB_T-Mobile-MetroPCS_OxygenOS_11.0.1.7.zip | by Scanman0 for OnePlus Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
also my phone is stuck in EDL mode and it registers as an android oneplus a5000 tablet for some odd reason i've tried just about every single n200 file out ever since my phone got stuck in EDL mode and evertime same result cdt file
also i had some with same version that i know personally send me his cdt file and same thing says it's empty
and my phone is the Metro-by Tmobile
vipermark7 said:
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
Click to expand...
Click to collapse
and i'm in Florida
Can someone please dump the firmware from this phone & upload it please?
cryptojoe37 said:
Can someone please dump the firmware from this phone & upload it please?
Click to expand...
Click to collapse
I gave up on this phone. no long working on it. Was having major pains with it.
I need the loader from the firmware
cryptojoe37 said:
I need the loader from the firmware
Click to expand...
Click to collapse
the loader ? bootloader?
michaelwaycraig67 said:
the loader ? bootloader?
Click to expand...
Click to collapse
abl/xbl partitions. perhaps some other.
zmashine said:
abl/xbl partitions. perhaps some other.
Click to expand...
Click to collapse
uploading now will give a link after uploaded
zmashine said:
abl/xbl partitions. perhaps some other.
Click to expand...
Click to collapse
2.74 GB file on MEGA
mega.nz
MiniNinja2024 said:
I'd like to start by saying after 2 weeks of researching and piecing guides together to unbrick my phone was hell. But once i found the right route it took me less thank 10mins all from a simple tool called Fastboot Enhanced V1.3.0. Now this Nifty little tool took me from bricked phone which was saying "Your img(Boot, Recovery) have been destroyed please flash the right files or contact customer service to fix this problem to Unbricked in less than 10 minutes. It took me 2 weeks of researching but it's finally done. Now most of you will say well you could have use MSMTool or the MTK or even SP Flash Tool. Those are all fine and dandy and all but one problem with those. YOU have to SCOUR the internet to TRY to find files you need to actually be able to use them. I been over several guides. I had when a guide basically says this 1) DO THIS SKIP SKIP SKIP important parts 2) NOW DO THIS. Like WTH was i supposed to do in between 1 and 2. Todays guides lack thoroughism and complettioin. Guides these days take Half Ste;ps and then thrown together.
I will also leave a step by step instructions on how to use the Fastboot Enhanced V1.3.0 in DETAIL on how to get your phone from what mine did to Unbricked state. I will also attack Nord N200 5G DE2118 .img FIles for those who have a hard time scouring the internet for things. I for one get agitated and aggravated as hell when searching the internet for things. Especially when you have to pc things together. I will leave files if it's Fine by staff. Now these files have come directly from my OnePlus Nord N200 DE2118 extracted less than 2 hours ago 10:04 p.m. EST September 10th 2022. Can Only attach One File? and i can't even remove the accidental clicked bmp pic of COD BO Cold War Zombies.
Guide For Using Fastboot Enhanced V1.3.0
1) Download Fastboot Enhanced Tool from: https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ from XDA Which is how I came across it. . The Tool is a WINDOWS ONLY Tool. (How many guides i came accross that didn't state whether it's for Windows or Linux) I use Dual Boot so I have both.
2) Install Fastboot Enhanced V1.3.0 and wait for it to finish. Now you will only have to be in Fastboot Mode to do any of this. I can't believe how a semi hard problem was fixed really easy
3) Now you will Have to Have a Payload.Bin File which can be found with any OEM Firmware for Your specific Phone. The Payload.bin allows you to be able to do a Payload Dump Using Fastboot enhance it is at this point if any of your partitions are missing or corrupt you will find out because it will tell you if you can understand the way it's explains it.
4) This Nifty little tool will tell you your device naem whether your phone is using secure boot or not, current slot your phone is using if you have an a/b partition scheme and the update Status. This is Listed Under basice properties. AGAIN MAKE SURE YOUR IN FASTBOOT MODE.
5) Next tab is the Partitions Tab which will List all your partitions currently on your phone . To the right of your listed partitions you will have and ACTIONS Tab. This is the tab where you can flash, erase, delete, create, and Resize your partitions. With this tool You CAN Flash Important Partions So be careful what you flash.
6) Next Tab Over is the Payload Dumper. This is the Tab where you need the Payload.bin File for your specific phone. this will give you payload version manifest size, metadata signatures size Metadata Signatures (Base64), data blobs, singatures size signatures (Base64) Fuill package Yes or No. Timestamp and block size. also under payload dumper tab another tab shows up called the Dynamic Partition Metadata. Now this will list your REALLY IMPORTANT Dynamic Partitions These are the partitions you don't want to flash anything over them. It will give you the Partition group size, which partitions are included and tells you wheter snapshot is enabled or not.
7) Under The payload Dumper tab the partitions tab gets a different Actions box. This time i'ts a box that let's you extract your .IMG files from your phone it allows for incremental as well as to ignore unknown operations and ignore checksums also under this partitions tab it gives you a checksum for each and every one of your partitionss. Ok now on to the Simple but yet comprehensive guide.
8) Now to start you want to add the Payload.bin to the Payload Dumper and then click on the Partitions tab. Once under this tab you will select each partition and hit the extract button and extract it to a folder named something like Flash FIles.
9) you hace to do this for each partition. Once done you will have your .IMG files from your exact phone for future use as well. You then want to click on the Fastboot Visualization tab and then click on Partitions.
10) Once under the partitions tab here, you will want to start flashing your .IMG files to the partitions. it should take you around 10 to 15 mins total to finish flashing everything.
11) Once your finished flashing you want to do a quick Terminal and do a FASTBOOT -W and then Fastboot Reboot and watch your phone start working again.
FEEL FREE TO LEAVE ANY COMMENTS SUGGESTIONS ON WHAT COULD HAVE BEEN BETTER OR IF IT'S NOT ENOUGH DETAIL. I TAKE CONSTRUCTIVE CRITICISM WITH A GRAIN OF SALT. THIS WAS MY FIRST GUIDE I EVER PUT TOGETHER. LOL THIS GUIDE TOOK ME LONGER THAN IT DID UNBRICKING MY PHONE.
BELOW YOU WILL FIND .IMG FILES FOR ONEPLUS NORD N200 DE2118
Click to expand...
Click to collapse
I still do not understand what I have to flash to get an OS back on this device. All I have is fastboot... soft bricked. I have de2117 ( "best buy" model). Reading all these instructions and I am still very confused
I'm new to forums, I apologize if this is all wrong and such. I was wondering if there is a way I can root a MetroPCS TCL IonX (T430W) running android 12 with magisk. I can't find anything for the IonX, it's all other variants of "Ion." I'm quite familiar with rooting and such, I'm just looking for the files, twrp or such. If you know where I can get them, please lemme know.
I'm sorry if this is in the wrong spot. I didn't see anything for TCL devices, I've never used forums before.
Hi! I don't see your particular device, but here (link below this paragraph) is where you can find all TCL devices we do have sections for. I am not knowledgeable about TCL, otherwise I'd help you myself, and these days on my Pixel, I don't even use TWRP to root - just Magisk, but I know this varies depending on the device and the files that are available. Hopefully, someone in one of the other TCL device sections can help you.
TCL
forum.xda-developers.com
If you ever get a different brand device, you can look for your device or your brand at the top level of the forum https://forum.xda-developers.com/. In the middle of the screen, there is All categories, which you can either expand to see a condensed copy of the brands and links to their sections, or click on it and it'll take you to a more expanded view of all brands we have forum sections for.
You can also use the following thread to request new device forums. There's no guarantee one would be created, but if there's enough demand, it might be.
*** New Device Forum Requests ***
Please post all your requests here. The forum admins choose new device forums carefully, based on several factors. There's no guarantee your device will have a forum created here, but feel free to posts your requests in this thread :) Please do...
forum.xda-developers.com
roirraW edor ehT said:
Hi! I don't see your particular device, but here (link below this paragraph) is where you can find all TCL devices we do have sections for. I am not knowledgeable about TCL, otherwise I'd help you myself, and these days on my Pixel, I don't even use TWRP to root - just Magisk, but I know this varies depending on the device and the files that are available. Hopefully, someone in one of the other TCL device sections can help you.
TCL
forum.xda-developers.com
If you ever get a different brand device, you can look for your device or your brand at the top level of the forum https://forum.xda-developers.com/. In the middle of the screen, there is All categories, which you can either expand to see a condensed copy of the brands and links to their sections, or click on it and it'll take you to a more expanded view of all brands we have forum sections for.
You can also use the following thread to request new device forums. There's no guarantee one would be created, but if there's enough demand, it might be.
*** New Device Forum Requests ***
Please post all your requests here. The forum admins choose new device forums carefully, based on several factors. There's no guarantee your device will have a forum created here, but feel free to posts your requests in this thread :) Please do...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks man, I'll see if I can get help. More or less, I need the firmware, I can do it if I have it. Thanks once again
DrAkuma said:
Thanks man, I'll see if I can get help. More or less, I need the firmware, I can do it if I have it. Thanks once again
Click to expand...
Click to collapse
You're welcome! I hope you can find it.
roirraW edor ehT said:
You're welcome! I hope you can find it.
Click to expand...
Click to collapse
Definitely looking. Thanks for the quick reply.
DrAkuma said:
I'm new to forums, I apologize if this is all wrong and such. I was wondering if there is a way I can root a MetroPCS TCL IonX (T430W) running android 12 with magisk. I can't find anything for the IonX, it's all other variants of "Ion." I'm quite familiar with rooting and such, I'm just looking for the files, twrp or such. If you know where I can get them, please lemme know.
I'm sorry if this is in the wrong spot. I didn't see anything for TCL devices, I've never used forums before.
Click to expand...
Click to collapse
I have the T430W as well and after a month of trial and error I was able to get it rooted with magisk. I'll give you the quick summary of how I did it right now and once I get home from work I will try to get a more complete step by step guide for you.
1. Download and setup mtkclient by bkerler on github.
2. Enable usb debugging and oem unlock in developer options
3. Power off device
4. Open a terminal and mtk meta --metamode FASTBOOT
5. Plug phone up to computer. You should see the TCL logo and then black screen with fastboot mode in lower left corner.
6. fastboot flashing unlock and confirm on device with volume keys(WARNING this will erase your userdata)
7. Install LineageOS pre rooted GSI using DSU sideloader from github.
8. Either use a partition backup or adb shell then dd if=/dev/block/by-name/boot of=/sdcard/boot.img
9. Reboot to return to original system.
10. Patch boot image with magisk manager make sure the disable vbmeta option is selected.
11. Repeat steps 3 & 4
12. fastbooot --disable-verity --disable-verification flash vbmeta vbmeta.img {flash blank vbmeta image(I used the one from the google source page for DSU)}
13. fastboot flash boot /path/to/magisk_patched_img
14. Reboot and enjoy your rooted Ion X.
Or if you would like I can upload either the stock boot image or magisk patched image as long as you have done the UG67 OTA update.
We have no DA or AUTH files for SP Flash Tool and none of the current bypass methods work on our chipset, so whatever you do make sure you do not flash mmcblk0boot0 or mmcblk0boot1 as this will render your device hard bricked. The kernel source is available on sourceforge, I have gotten it to compile with no errors but haven't had a chance to test it yet. I'm working on getting TWRP or OFRP for our device compiled but haven't gotten very far. So far I haven't had any issues being rooted on the stock rom. I'm really glad that you posted this because I have been meaning to type up a guide as I believe being able to root your phone should be an option for everyone, but you posting this gave me the kick in the rear to actually do it.
Here is the stock boot and magisk patched boot image plus the blank vbmeta image